epic(roadmap): kimi-code parity program — workflow and tracking

[dennisonbertram]

Objective

Close the user-facing feature gap between go-code and MoonshotAI's kimi-code CLI/TUI, as identified in the 2026-07-19 comparison review. This is the tracking and sequencing issue for the whole program: 19 child epics in 3 tiers, each containing PR-sized slices.

Context

Comparison basis: kimi-code official docs (slash commands, keyboard, tools, kimi command, interaction, sessions, goals, hooks, plugins, themes, agents, MCP, skills, changelog) versus an inventory of cmd/harnesscli, cmd/harnessd, and internal/ on main.

Areas where go-code already leads (do not regress these, and do not build parity items for them): rollout replay/fork/drift + forensics, container/VM/worktree workspace backends, GitHub/Slack/Linear webhooks, scoped API keys + multi-tenancy, capability profiles, the deferred find_tool system, goals with dependencies, and the trainer/improve loop.

Workflow (how this program executes)

1. Pickup order is tier order, then in-tier order. Tier 1 = high-impact UX where server pieces mostly exist; Tier 2 = strategic differentiators; Tier 3 = cheap polish.
2. One slice = one PR. Slices inside each epic are ordered by dependency; slices marked "parallel-safe" may be picked concurrently.
3. Every slice follows the repo runbooks: bootstrap a worktree with scripts/init.sh <slug>, strict TDD per docs/runbooks/testing.md (no red baseline tolerated), update affected docs and folder indexes, then merge with scripts/verify-and-merge.sh.
4. Cross-epic dependencies are listed in each epic's ## Dependencies section — do not start an epic before its dependencies merge.
5. Each child epic body uses the repo issue template format (.github/ISSUE_TEMPLATE/task.md) extended with Existing Foundation (verified file citations) and Proposed PR Slices sections, matching the house epic style of epic(hooks): config-driven lifecycle hooks (shell/HTTP) adapted onto existing harness hook interfaces #737.
6. Close this issue only when all child epics are closed.

Child Epics

Tier 1 — high-impact UX, server pieces mostly exist

• epic(tui): mid-turn steering from the TUI #820 epic(tui): mid-turn steering from the TUI
• epic(tui): shell mode (! prefix) with background handoff and history #811 epic(tui): shell mode (! prefix) with background handoff and history
• epic(tui): image input — clipboard paste and ReadMediaFile tool #818 epic(tui): image input — clipboard paste and ReadMediaFile tool
• epic(harness): /undo — remove recent prompts from the active context #805 epic(harness): /undo — remove recent prompts from the active context
• epic(harness): /fork — fork the live session with full history #816 epic(harness): /fork — fork the live session with full history
• epic(tui): unified /tasks background panel #814 epic(tui): unified /tasks background panel
• epic(harness): complete plan mode — plan file, restricted writes, exit approval with options #819 epic(harness): complete plan mode — plan file, restricted writes, exit approval with options

Tier 2 — strategic differentiators

• epic(server): read-only session visualizer served by harnessd #812 epic(server): read-only session visualizer served by harnessd
• epic(acp): Agent Client Protocol server mode for Zed/JetBrains #806 epic(acp): Agent Client Protocol server mode for Zed/JetBrains
• epic(subagents): swarm fan-out tool with template, resume, and live progress panel #808 epic(subagents): swarm fan-out tool with template, resume, and live progress panel
• epic(plugins): plugin manifest, GitHub install, trust, and /plugins manager #821 epic(plugins): plugin manifest, GitHub install, trust, and /plugins manager

Tier 3 — polish

• epic(tui): theme system — token schema, JSON theme files, picker, hot reload #810 epic(tui): theme system — token schema, JSON theme files, picker, hot reload
• epic(tui): /compact [instruction] and a visible compaction summary #817 epic(tui): /compact [instruction] and a visible compaction summary
• epic(config): /reload — apply config changes without restart #815 epic(config): /reload — apply config changes without restart
• epic(tui): quality-of-life commands — /title, /init, /add-dir, /feedback, upgrade #822 epic(tui): quality-of-life commands — /title, /init, /add-dir, /feedback, upgrade
• epic(skills): skill argument placeholders and slash-command namespacing #813 epic(skills): skill argument placeholders and slash-command namespacing
• epic(mcp): OAuth login flow for remote MCP servers #809 epic(mcp): OAuth login flow for remote MCP servers
• epic(cli): headless exit-code conventions for runs and goals #823 epic(cli): headless exit-code conventions for runs and goals
• epic(install): OS-service install for harnessd (launchd/systemd) #807 epic(install): OS-service install for harnessd (launchd/systemd)

Acceptance Criteria

• All 19 child epics created with PR-sized slices and the repo template format
• All 19 child epics closed (slices merged to main)

Test Requirements

Per-slice, per the runbooks: behavior tests written first, GOCACHE=/tmp/go-build ./scripts/test-regression.sh green before merge. This tracking issue itself requires no tests.

Documentation Updates Required

Each child epic lists its own doc updates. When the program completes, update README.md ("What You Get") and website/docs/cli/tui.md so the public feature list reflects the new capabilities.

Dependencies

None — this is the root tracker. Inter-epic dependencies are recorded inside each child epic.