nsaspy/hackmode
1
0
Fork 0
Code Issues 46 Pull requests 55 Projects Releases Packages Wiki Activity Actions

Visual evidence: project accepted records through durable outbox #64

Closed
nsaspy wants to merge 5 commits from db/143-visual-outbox into master
pull from: db/143-visual-outbox
merge into: nsaspy:master
Conversation 0 Commits 5 Files changed 5 +211 -2
nsaspy commented 2026-09-04 20:36:55 +00:00
Owner
Copy link

Closes #143.

Implements the Hackmode-side visual-evidence projection into the existing durable StarIntel outbox. Local visual evidence remains canonical and usable offline; projection carries deterministic observation identity, screenshot ref/digest, URL/status/timing/browser/profile/capture/exchange metadata, and selected operation/run/job provenance while intentionally excluding free-form secret-bearing provider provenance.

Repeated projection is idempotent through the existing deterministic outbox ID. Transport outage remains retryable, and only an accepted 2xx response moves the existing outbox entry to :acknowledged / :ingest-accepted.

RED-first contract was committed before implementation. Exact code head: 23c34e097e3b6e9d62bed76698c33ef9b7f62af3.

PR #160 carried the same head and passed core, monorepo, and agent-framework-boundary, but was closed because the connector's ready-for-review mutation is broken. This normal PR must receive fresh exact-head checks before merge.

No StarIntel product repository changes and no BrowserWorker direct persistence.

Closes #143. Implements the Hackmode-side visual-evidence projection into the existing durable StarIntel outbox. Local visual evidence remains canonical and usable offline; projection carries deterministic observation identity, screenshot ref/digest, URL/status/timing/browser/profile/capture/exchange metadata, and selected operation/run/job provenance while intentionally excluding free-form secret-bearing provider provenance. Repeated projection is idempotent through the existing deterministic outbox ID. Transport outage remains retryable, and only an accepted 2xx response moves the existing outbox entry to `:acknowledged` / `:ingest-accepted`. RED-first contract was committed before implementation. Exact code head: `23c34e097e3b6e9d62bed76698c33ef9b7f62af3`. PR #160 carried the same head and passed core, monorepo, and agent-framework-boundary, but was closed because the connector's ready-for-review mutation is broken. This normal PR must receive fresh exact-head checks before merge. No StarIntel product repository changes and no BrowserWorker direct persistence.
api: export visual evidence outbox projection
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 2s
Details
agent-framework-boundary / keep-agent-framework-out-of-product-tree (pull_request) Successful in 25s
Details
core / common-lisp-core (pull_request) Failing after 1m7s
Details
monorepo / hygiene (pull_request) Successful in 9m10s
Details
23c34e097e
nsaspy closed this pull request 2026-09-04 20:57:21 +00:00
Some checks failed
agent-pr-serialization / one-open-pr-per-agent-lane (pull_request_target) Failing after 2s
Details
agent-framework-boundary / keep-agent-framework-out-of-product-tree (pull_request) Successful in 25s
Details
core / common-lisp-core (pull_request) Failing after 1m7s
Details
monorepo / hygiene (pull_request) Successful in 9m10s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
feature
New feature or capability

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
refactor
Code cleanup without behavior change

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
feature
good first issue
help wanted
invalid
question
refactor
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/hackmode!64
No description provided.