[BunsDev]

The request half of CF-6 (#279), on CF-3's human-request lifecycle (#276): a card is the record of its request across the event journal, snapshots, paired desktops and the phone.

What changes

• Who answered, and whether it arrived. An accepted answer saves answeredBy (desktop or phone) and delivery: "sending" before the CLI hears anything, then delivery: "sent" after the hand-off. These travel as whole field values in the existing item/item_update events, so the journal stores, merges and replays them with no new event type.
• Restart. A card still sending becomes uncertain: Modex stopped between taking the answer and recording its hand-off. The answer is never sent again, a late answer is refused, and the card says "Modex stopped before it could confirm the agent received this answer." Cards nobody answered still close as ended. Answers saved before these fields existed are left as they were.
• The phone gets answeredBy, delivery and withdrawn on approvals, and a question's notice says when delivery is uncertain. A card the phone answered reads "Answered on your phone." in the window.
• Fix: the phone could not act on a thread started on the Mac. Since Install verified macOS updates with durable draft recovery #181 (v0.0.12), such a thread keeps the full UUID its draft reserved, but the companion's thread routes took only 8 hex characters. Answering, sending, setting the policy and archiving from the phone all got a 404. The routes now take any id the store accepts, and the thread must exist. CF-8's fidelity e2e found it.

Journal on and journal off behave as before for everything else. Coding still runs only through codex app-server and claude -p.

Tests, red first

• test/request-journal.test.ts (new). All six cases failed first on the missing fields:
  • who answered and the delivery, in the window, the snapshot, the journal replayed once and twice (a duplicated event), the phone, and after a restart, with no second decision;
  • simultaneous desktop and phone answers: exactly one accepted, the phone's a 409, the CLI hears one decision;
  • a paired desktop over TLS that reconnects after the decision was sent sees it answered, and its stale answer is refused;
  • an expired cursor reloads to a snapshot with the same fields;
  • a crash between taking an answer and recording its hand-off: uncertain, inert, never re-sent;
  • with the journal on, a secret answer reaches the CLI and no file under MODEX_HOME (SQLite pages and WAL included), event or phone snapshot.
• test/human-requests.test.ts: answerNote failed first (no such export).
• test/companion.test.ts: a UUID thread failed first with 404.
• e2e/human-requests.spec.ts: with the journal on, it answers a Codex question, stops a second one, and marks the first card as if Modex died mid-send. After a restart, both cards are inert, the uncertain one says so, a second answer is refused, Codex hears nothing more, and no file holds the secret.

Checks

On 067d89c, rebased onto main 57e7607 (CF-3), macOS 26.7.1, Node v24.18.1, pnpm 10.34.5:

• pnpm build at the root and pnpm typecheck in apps/desktop: passed.
• pnpm test in apps/desktop: 1,589 passed, 16 skipped, 0 failed; second stage 21 of 21.
• pnpm --filter @modex/store-desktop test: passed.
• e2e human-requests (including the new journal-on restart case), companion, event-journal, approvals: 10 of 10.
• On the stacked head before CF-3 landed (same CF-6 code): e2e human-requests, approvals, companion, event-journal, store-desktop, conversation-fidelity: 21 of 21.
• Not run locally: the rest of pnpm test:e2e. CI runs it.

All commits are signed. docs/status.md adds CF-6 under "On main, unreleased" and drops the Markdown parser (#283, landed) from "Still open".

Refs #279, #276. Tracker #273.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
modex	Ready	Preview	Oct 19, 2026 12:05am UTC

[github-code-quality]

Code coverage overview

Languages: TypeScript

TypeScript / code-coverage-agent

main 81798d7	cf6-requests e408f54	+/-
63%	63%	0%

ℹ️ Calculations represent line coverage. Results may change as calculations are updated.

---

_{Updated October 19, 2026 00:43 UTC}