Files
platform/todo/waiting-on-owner/plan-mode-is-live-and-has-never-been-exercised.md
pastilhasandClaude Fable 5 6071ded175 todo: one file per item, grouped by theme, with a generated index
TODO.md had reached 1050 lines and 72 open items across 28 sections, read mostly
on a phone. It is now a directory: todo/<theme>/<item>.md, one card per file, with
frontmatter carrying id, status, created date and order, and the prose body copied
across verbatim. TODO.md becomes a generated index (bun run todo:index).

Dates: where an item's prose stated one it is used; otherwise its old section's;
otherwise 2026-08-20, floored at the day before the split rather than invented.
date_source records which.

Shaped for a two-way Kanban board, filed as todo/tooling — a card is a file, id is
the identity, frontmatter is the machine's half and the body is the owner's.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-21 05:42:39 +00:00

1.3 KiB

id, title, theme, status, created, date_source, order
id title theme status created date_source order
waiting-on-owner/plan-mode-is-live-and-has-never-been-exercised Plan mode is live and has never been exercised waiting-on-owner open 2026-08-17 stated 2

Plan mode is live and has never been exercised. Landed 1b811dfa on 2026-08-17; all three processes were restarted the same evening, so the code IS running. Not one part of it has been used: not the toggle, not the plan card, not the round trip from the sidecar's pending promise to a browser and back, not the stored column, not settleAllPlans.

docs/chat-plan-mode-test-plan.md is the checklist — eleven ordered tests, what each should show, and what its failure looks like. Test 4 (approve) is the one most likely to be wrong: it is the case that changed the design, because approving ExitPlanMode drops the harness into default rather than back into bypassPermissions.

Safe to leave untested. Plan mode is opt-in and off by default, so a conversation that never touches the toggle behaves exactly as it did before. The one failure worth knowing in advance is a turn that never ends after a plan is answered — that would be a leaked canUseTool promise, and pm2 restart officer-claude-code clears it.

Design and the probe results behind it: docs/chat-plan-mode.md.