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>

todo/workspaces-panels/_index.md

@@ -0,0 +1,14 @@
+---
+theme: workspaces-panels
+heading: "Workspaces & Panels"
+kind: theme
+---
+
+Its own list — **`docs/workspace-panel-todo.md`** — because it is long and actively worked. Full
+analysis behind it: `COMMS/workspace-panel-framework-analysis-2026-08-07.md`.
+
+Headlines: the framework has **no panel lifecycle** (a panel can be destroyed but never told, which is
+the real cause of the terminal orphan leak); three state-key families are **silently dropped on every
+write**, orphaning a pty per reload; Running Shells has **404'd since 2026-07-31**; there are **zero
+error boundaries** anywhere in the repo; and `dashboards.id` is a **global** primary key fed by
+`slugify(name)`, so two members naming a dashboard the same thing collide.