Run and resume Codex and Claude Code in Ace channels #9

Start or continue Codex and Claude Code work inside an Ace channel. The Issues/PRs, persistent GitHub cache, shared sidebar, helper tool lookup, and 0.0.9 release preparation began in Codex, which Ace does not yet run as a harness. Edits stayed in Codex; type checks, lint, and builds ran through an Ace terminal. Browser inspection required Codex's computer-use tools. Earlier GitHub smoke checks and React Doctor runs also used Codex.

This tracker migration also began in Codex, which Ace cannot yet host as a harness. Migration preparation and repository edits used Codex; issue creation and repository checks ran through an Ace terminal.

Dogfooding core/QOL: #5. Migrated from TODO.md — Before dogfooding.

Continuation acceptance

• Start fresh work and continue one real existing session from each harness in Ace.
• Preserve lane/cwd, dirty work, instructions, required tools/skills, attachments and context; make unavailable resources explicit.
• Show tool output, questions and child work; support steering, follow-up, stop/kill and reconnect/restart without duplicate execution.
• Complete a real edit, verification and PR without returning to the external harness app. A transcript import alone is insufficient.
• Preserve pi as the channel system of record and the one-writer-per-lane rule. Native tools in [Meta] Complete native computer use in Ace #8 and Inspect and debug browser pages from an Ace channel #50 remain independent of external-harness integration.