airc-queue: Proof-gated chat-to-AIRC migration plan

[joelteply]

airc-queue card

Coordinates work via the AIRC queue substrate (airc#562). Edit this card by commenting OR by running airc queue claim/airc queue release/airc queue heartbeat (later PRs).

{
  "kind": "airc-queue-card-v1",
  "id": "#1113",
  "branch": "feat/chat-over-airc-proof-gates",
  "status": "review",
  "env": "ui/jtag/airc",
  "evidence": "Joel: if chat send moves off ORM to AIRC, agents must manually prove UI behavior and JTAG/command callers before removing old chat commands. Compile-only is not enough.",
  "next_action": "Design migration gates: UI screenshot proof, JTAG command proof, AIRC transcript proof, ORM traffic/load comparison, caller migration inventory, and removal criteria for legacy chat commands.",
  "owner": "claude-tab-2",
  "last_heartbeat": "2026-05-14T01:08Z @ 087185b16"
}

Close this issue when the work is done (status=merged/abandoned).

Status log

• 2026-05-14T01:12Z — airc-8a5e -> status=review

• 2026-05-14T01:08Z — claim by claude-tab-2 -> status=in-progress

• 2026-05-13T21:01Z — codex nudged (broadcast): proof-gated migration card is available for future chat-to-AIRC work

• 2026-05-13T21:00Z — released by airc-8a5e -> status=claimed (available backlog validation card; created from Joel proof-gate request)

[joelteply]

Proof policy from Joel: the issue/card defines the required proof, and the PR must attach the actual evidence before merge.

For chat/AIRC migration work, a ready PR should include at least:

• UI proof: screenshot(s) or browser evidence showing send/receive behavior in the interface.
• Command/JTAG proof: exact command output showing existing callers still work or have been migrated.
• AIRC proof: transcript/log evidence that the message path is going through AIRC.
• ORM proof: before/after evidence that chat send no longer relies on the old ORM path, or a clear reason for any remaining ORM use.
• Caller inventory: list of changed callers and any intentionally deferred callers.
• Removal proof: if deleting legacy chat commands, evidence that no active callers remain.
• Regression tests: automated checks for the new path where feasible, plus manual proof for flows automation cannot cover yet.

Compile-only is not sufficient for user-visible or command-path migration.

[joelteply]

Completed by PR #1141, merged to canary at 79e5fa7.

Proof captured in the PR:

• git diff --check
• precommit hook: TypeScript build passed; browser tests skipped because local stack was down
• pre-push hook: TypeScript clean; ESLint 5530 errors vs baseline 6310; Rust/Docker skipped for docs-only change

Review fix before merge: the initial hand-written inventory was incomplete, so the landed doc now treats it as seed inventory and requires future migration PRs to check in a generated inventory artifact before code changes.