docs: add missing TODO items from PR comment commitments

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: brooksc

KNOWN-TODOS.md

@@ -61,3 +61,44 @@
 **Naming:** "Take Control" / "Return to Orchestrator" overstate what happens. The coordinator agent is still running — only its ability to send prompts to that sub-task is blocked. More accurate labels: **"Pause coordinator"** / **"Resume coordinator"** (or just "Pause" / "Resume" with banner context).
 
 **Input gating:** When the coordinator has control, the sub-task's PromptInput textarea and raw xterm terminal are not gated — the user can type freely, which could collide with a coordinator `send_prompt` firing simultaneously. The fix: dim/disable PromptInput and suppress xterm keyboard input when `controlledBy === 'coordinator'`, with "Pause coordinator" as the only way to re-enable input. This makes the model discoverable rather than relying on the user reading the banner before typing.
+
+---
+
+## Beta gating — `experimental.coordinatorMode` flag
+
+**Status:** Not implemented. Coordinator mode is currently always available.
+
+**What's needed (per repo owner feedback):**
+
+- A single `experimental.coordinatorMode` setting, off by default
+- When off: MCP server module is not started (lazy `import()` on flag flip), Coordinator option in NewTaskDialog is hidden, and coordinator-related IPC channels are not registered — zero footprint for users who don't opt in
+- When on: current behavior
+
+**Note:** The settings UI placement for this flag depends on the tabbed settings dialog (separate PR — see below).
+
+---
+
+## Tabbed settings dialog (separate PR)
+
+**Status:** Not implemented. Settings is a flat scrollable list that's getting long.
+
+**What's needed:** Split into tabs, e.g. General / Experimental (or Beta). The `experimental.coordinatorMode` flag and other power-user settings live in the Experimental tab. This should land as its own PR independent of coordinator work.
+
+---
+
+## Post-restart MCP path — integration test
+
+**Status:** No integration test. The port/token rotation that rewrites the sub-task MCP config on coordinator restart is the most fragile part of the system by design.
+
+**What's needed:** An integration test that confirms after a coordinator restart (new port, new token), the config file the sub-agent reads is correctly rewritten and the sub-agent can reconnect. Unit tests don't cover this path.
+
+---
+
+## `skipPermissions` guardrail
+
+**Status:** Sub-tasks silently inherit `--dangerously-skip-permissions` from the coordinator if the coordinator was started with it. No per-task confirmation.
+
+**What's needed:** Two changes:
+
+1. An explicit UI confirmation when creating a coordinator task with skip-permissions, making clear that all sub-tasks will inherit it
+2. A "propagate skip-permissions to sub-tasks" checkbox (default off) so users must explicitly opt in to inheritance rather than getting it automatically — important for the "40 tasks" workflow where per-task confirmation would be impractical