Add durable event automation admission and recovery

[jonathanKingston]

Implements the first internal slice of the event-driven automation proposal: repeated deliveries and interrupted preparation retain one durable run/thread identity. This is an injected admission/recovery boundary; no event source or model execution is enabled in the app yet.

• Persist bounded, hashed source evidence and matching outcomes before acknowledging admission. Bind events to the saved automation revision, project/repository and authenticated adapter connection; reject instruction-bearing payload fields and filter automation-originated events.
• Claim a stable run identity and enqueue it idempotently through the existing supervisor, including recovery from lost acknowledgements and lookup in archived task history. Existing but corrupt identity records fail closed.
• Recheck eligibility at enqueue and preparation, preserve fenced history across disablement/deletion, and cancel only pending draft preparation. Reported failures are not automatically retried.

The host contract and storage details are documented in docs/plans/event-automation-inbox.md. Slice A keeps the capped 64 KiB redacted evidence inline with its receipt for atomic persistence. Real CI polling, saved-definition/editor controls, coalescing, cost/worktree enforcement and normal app-open turn dispatch remain slice B.

Acceptance criteria from the proposal:

• Duplicate delivery, including after restart, produces one run identity.
• Crashes between inbox write, claim, enqueue, and thread creation recover that run.
• Invalid source, target, payload bounds, and definition revision cannot dispatch.
• Disablement/deletion fences pending work while preserving historical records.

Validation: pnpm run check passed all static gates and 8,783 tests before the final rebase. After rebasing onto main (including the merged automation modal/proposal), pnpm run typecheck and the complete pnpm test suite passed again: 8,813 tests, zero failures. The rebase was conflict-free and changed none of the inbox/supervisor files or dependencies. Durable filesystem tests use the real supervisor/task store and inject interruption after inbox writes, enqueue, and durable thread preparation. Dedicated tests also cover concurrent lifecycle fencing, archived identity, corruption and conflicting evidence. No visible app changes; no visual eval is needed.

[github-actions]

🖥️ PR preview

• Marketing site
• Browser demo
  Interactive, with a mocked backend — jump to a scenario:
• Builds a cupcake site
• Agent-proposed edits open the Changes panel
• Markdown list indentation
• Responsive composer footer
• Subagent display visual reference
• Subagent stays ungrouped beside reading tools
• Semantic search subagent markdown
• Light-theme approval with a bright accent
• Light-theme syntax, fills, and selection
• Grouped outside-sandbox command approval
• Remote desktop discovered-port list with one selected
• Settings scroll + sticky footer geometry
• Per-model reasoning / temperature / top-p
• Thread switch hydration notice
• Thread switch hydration failure
• Chat layout styling
  _{Static demo of the renderer against a mock API — the browser pane, terminal, and all main-process IPC are stubbed, so it never proves main-process behaviour. Rebuilt whenever a push changes the demo bundle; these links go live once the queued deploy lands, shortly after this comment. Removed when the PR closes.}

[copse-release-bot]

Reference screenshots ready for review

Review GitHub’s image diffs in screenshot PR #2616.
Merge it (or enable auto-merge) to apply the accepted PNGs to codex/automation-event-inbox.

Rendered for d103fa68d2a5 by CI run 34303100123; the immutable artifact is reference-screenshot-candidates-34303100123.

If this source branch moves, a later successful render closes the stale review PR and replaces this link.