add a living todo for the workspace/panel framework

the framework has no tests, no error boundaries and a handful of known
defects that keep resurfacing mid-feature. write them down once, ranked,
so they can be picked off in the context of whatever is being built.

notable: the dashboards PATCH dispatcher silently drops any key family it
has no branch for, and three in use today (tmux, nvim, claude-code, all
from Terminal's statePrefix) match nothing — so that state never persists.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

TODO.md

@@ -135,6 +135,17 @@ day. Kept here for what the policy work turned up, which is not obvious from the
       behind nginx, `tailnet` is not a headscale concept and has to be recorded on the invite, and
       `/api/v1/enroll/*` collides with headscale's own namespace.
 
+## Workspaces & Panels
+
+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.
+
 ## Known bugs
 
 - [ ] **`bootstrap.ts` runs `npm install -g` for Pi on every boot.** `findPiPackageDir` checks stale