chore(todo): file runtime-portability child tasks and stamp a review

Eight child tasks under the generic-agent-runtime parent decompose what's left to run a non-Claude agent (Codex-style or local LLM) in this system: instruction bootstrap, skill parity, hook parity, launcher flag, session plumbing, memory story, MCP portability, local model floor. Each names the spec blocker decision it feeds. Also stamps the build-to-prototype task's review.

1 files changed, 28 insertions, 0 deletions

diff --git a/todo.org b/todo.org
index 9fbd6f6..ec51fbb 100644
--- a/todo.org
+++ b/todo.org
@@ -42,6 +42,7 @@ Tags are assigned and refreshed by =task-audit=; =task-review= keeps them honest
 ** TODO [#B] Extend ui-prototyping rule with build-to-prototype :feature:
 :PROPERTIES:
 :CREATED: [2026-07-11 Sat]
+:LAST_REVIEWED: 2026-07-13
 :END:
 .emacs.d proposal (2026-07-11, Craig-approved promotion), extending the ui-prototyping rule shipped tonight (=claude-rules/ui-prototyping.md=, 53f6ce6). The base rule covers research → prototypes → iterate → decisions-backed-by-a-prototype, but not the "build to the prototype" half. Add: after prototyping, fold what settled back into the spec and make the *build target* the prototype rather than the original spec text — the built feature should match the prototype, and any deviation is documented in a "Prototype & deviations" addendum section the build keeps current. Wire into four touch points: =brainstorm= Phase 3 (a UI design isn't "accepted" until it's been through the prototype loop; Next Steps say "build to the prototype"), =spec-create= (emit the deviations-addendum section for UI specs), =spec-response= (a UI spec decomposes into a prototype loop first, then build-to-prototype tasks), =start-work= (its verify phase drives the UI end-to-end; the bar becomes "matches the prototype," deviations logged). Worked example: the takuzu Emacs game — colored tiles read as all-black in the real terminal frame (dark faces + GUI-only box cursor), caught by a prototype loop on the first screenshot where build-to-spec would have shipped an unusable board. Multi-asset synced-rule change, so review-gated and needs a focused session; decide brainstorm-vs-lifecycle placement with Craig. Source: =inbox/PROCESSED-2026-07-11-0222-from-.emacs.d-ui-prototype-rule-proposal.org=.
 
@@ -253,6 +254,33 @@ Codex ran the spec-review workflow. Outcome: the combined spec is =Not ready= be
 *** 2026-06-12 Fri @ 02:39:38 -0500 Second review after response pass
 Codex re-ran spec-review after the dispositions were folded in. Outcome by arc: Phase 1.5 helper instances =Ready with caveats=; phases 2-5 remain =Not ready= behind the explicit decisions/reverification gate. No new blocking findings for the helper slice. Review file updated in place: [[file:docs/design/2026-05-28-generic-agent-runtime-spec-review.org]].
 
+*** 2026-07-13 Mon @ 13:26:57 -0500 Gap assessment decomposed into child tasks
+Craig asked what's left to run ChatGPT or a local LLM as the agent. Assessment: the =.ai/= layer (protocols, workflows, scripts, inbox, todo, session anchors) is already runtime-neutral — plain org + bash, and a Codex session has run in it (2026-06-13). The Claude-bound remainder decomposed into the child tasks below; each overlapping spec-blocker decision is named in its body. The phases 2-5 go/no-go above still gates any big build, but several children are useful standalone.
+
+*** TODO Instruction bootstrap per runtime
+An install target that emits the non-Claude entry file (=AGENTS.md= for Codex-style agents; assembled system prompt for a local harness) pointing at =protocols.org= and the agent-neutral rules. Resolves the spec's "generic instruction-file strategy" blocker. Overlaps the shared-source thread of the =Multiple agent-source improvements= task (line ~150) — reconcile rather than build twice.
+
+*** TODO Skill parity across runtimes
+The user-invoked skills (voice, review-code, flush, …) are Claude Code registrations wrapping portable markdown prompts. Decide per skill: re-register in the target harness's custom-command system, or fold into =.ai/workflows/= (already runtime-neutral). Model-invoked skills need a per-harness answer or graceful absence (commits.md already defines the /voice-unavailable fallback pattern).
+
+*** TODO Hook parity inventory
+Inventory every settings.json hook (AskUserQuestion hard-deny, PostToolUse validators, wrap-teardown Stop hook, session-clear-resume) and map each to the target harness's mechanism or an accepted prose-only downgrade. The deny hooks exist because prose enforcement failed — a downgrade is a real regression, so decide per hook, not wholesale.
+
+*** TODO Launcher runtime flag
+=ai --runtime <claude|codex|local>=. The =AI_AGENT_ID= shape already carries a runtime segment (=host.project.runtime.epoch=). Keep the change small and contained per the 2026-06-24 helper-task caveat — the helper's =ai --helper= touches the same launcher.
+
+*** TODO Session plumbing per runtime
+=/flush auto= self-inject types Claude-specific keystrokes (=/clear= + resume line); clear/resume mechanics differ per harness. Also confirm =session-context-path= and the suspend/startup anchor cycle behave identically when a non-Claude agent drives them.
+
+*** TODO Memory story for non-Claude agents
+Claude's auto-memory is harness-owned. The org-roam KB is the designed cross-agent store — document that a non-Claude agent skips harness memory and leans on the KB + session files, and verify knowledge-base.md reads cleanly for a non-Claude reader.
+
+*** TODO MCP portability check
+MCP is cross-vendor; the self-hosted servers (signal-mcp, google-calendar, linear, slack) should attach to any MCP-speaking harness — verify. The claude.ai-managed connectors (Gmail, Drive, Calendar) don't travel; list self-hosted replacements where a workflow depends on them.
+
+*** TODO Local model floor evaluation
+The workflows assume long-context instruction-following (startup's multi-file read; the commits.md publish chain). Establish the minimum viable local tier (likely strong-70B+/MoE, 100k+ context), and what compensations a weaker model needs: shortened protocols, more checklist gates, more hook-level enforcement. Feeds the spec's "default local runtime/server" and "first supported local editing CLI" blocker decisions.
+
 ** TODO [#C] Docs-lifecycle convention — manual validation :test:
 The human-eyes half of the docs-lifecycle acceptance surface. The convention shipped IMPLEMENTED 2026-07-04 (spec [[id:80b0787b-4a60-4c82-8a16-b383d3e3c8f2][docs-lifecycle]]); these checks confirm the human-facing behavior. A failed check promotes to a bug.