write down the north star: agents coordinating with each other

docs/agent-coordination.md is the objective the workspace/panel work serves —
several agents on one dashboard handing work to each other instead of routing
every step through the human, with the human authoring the workflow at the top.
Written from the owner's own words during the 2026-08-07 conversation; where a
section records a decision, that decision is his.

It settles the questions that were blocking: sessions may be reaped and resumed
from the durable sessionKey→claudeSessionId map (no heartbeat), the address is
the human-assigned panel name rather than the panel id, roles are prompts rather
than features, and the protocol is turn-boundary-only by construction — which
routes around the mid-output restart failure instead of fixing it.

Cross-referenced from CLAUDE.md, workspace-panels.md and workspace-panel-todo.md
so it is findable from any of them. The todo is still ordered by defect severity
and now says so; the re-rank against the objective is deferred, not forgotten.

Also corrects two items dated 2026-08-08 to the day they were actually found.

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

docs/workspace-panels.md

@@ -4,6 +4,10 @@ Orientation for anyone building a panel app or a dashboard route. This describes
 is**, not as it should be; the defect list and the work queue live in `workspace-panel-todo.md`, and the
 full reasoning behind them in `COMMS/workspace-panel-framework-analysis-2026-08-07.md`.
 
+Where the framework is *going* — and why anything here is worth changing at all — is
+**`agent-coordination.md`**: agents on one dashboard coordinating with each other instead of through
+the human. Read that first if you are deciding what to build; read this one if you are deciding how.
+
 Code: `src/workspaces/officerdev/src/components/Workspace/` — 12 files, ~1,700 lines, no tests.
 
 ---