docs: full sync ahead of compaction + config-management overhaul

readme: manager mcp surface picks up update; operator-surface
recap mentions /model + last-turn + model chip + the three
collapsibles (inbox / journald / agent.nix).

web-ui.md: details-restore-key story under shape; port-conflict
banner mention on containers; agent.nix viewer alongside journald;
notifications use per-event tags + console.debug log on
block/show; deny endpoint takes note=<reason>; data-prompt /
data-prompt-field generalisation noted.

conventions.md: data-prompt and snapshot/restoreOpenDetails added
to the async-forms section.

persistence.md: operator_questions row picks up deadline_at (ttl)
column with a migration note.

todo.md: new 'Bugs' section captures the manager-question
not-rendering issue with three suspect paths to chase.

claude.md scratchpad rewritten as a clean handoff for the
compaction + the upcoming config-git overhaul. flags the
two-repo (proposed/ + applied/) split as the thing to
reconsider.

CLAUDE.md

@@ -114,17 +114,31 @@ read them à la carte.
 In-flight or recent context that hasn't earned a section yet.
 Prune freely.
 
-- 2026-05-15 ish: tombstones, multi-select ask_operator, broker +
-  events vacuum, docs split into `docs/`, lifecycle_action helper,
-  api_state split.
-- Then: inline +/- diffs on Write/Edit, operator cancel + ttl on
-  questions, dashboard back-link, per-agent inbox view, bind-retry
-  + SO_REUSEADDR, journald viewer, server-side TurnState,
-  recv(wait_seconds) max 180s, runtime /model switch, crash
-  watcher, model persistence, stopped auto-allowing claude-code
-  unfree (operator must opt in), pure-hash agent_web_port (port
-  files reverted), browser notifications, focus-preserving
-  refresh.
-- Open threads: telemetry/charts, custom per-agent MCP tools (the
-  groundwork for moving bitburner-agent into hyperhive),
-  two-step spawn, unprivileged containers, Bash allow-list.
+- **Imminent:** overhaul the git management of agent configs.
+  Current shape: per-agent `proposed/` repo the manager edits
+  + `applied/` repo hive-c0re owns, with `request_apply_commit`
+  shuttling commits between them. Pre-compact note: keep an eye
+  on whether the two-repo split is still the right shape, or if
+  a single repo with `proposed/` and `applied/` branches (or a
+  shared bare repo per agent with refs/proposed and refs/applied)
+  would simplify the diff / approve / apply path.
+- **Recent (since last compaction):** inline +/- diffs on
+  Write/Edit, send full body via collapsed details, operator
+  cancel + ttl on questions, deny-with-reason, dashboard
+  back-link + last-turn timing + model chip, per-agent inbox
+  view, bind-retry + SO_REUSEADDR, journald viewer,
+  agent.nix viewer, server-side TurnState, recv(wait_seconds)
+  max 180s, runtime /model switch + persistence to /state,
+  crash watcher + ContainerCrash / NeedsLogin / LoggedIn /
+  NeedsUpdate events, manager `update` tool, pure-hash
+  agent_web_port + collision banner + spawn/rebuild preflight,
+  browser notifications, focus-preserving refresh, generalised
+  <details data-restore-key> survival, prompt-on-submit pattern.
+- **Open threads:** custom per-agent MCP tools (groundwork for
+  moving bitburner-agent into hyperhive), two-step spawn,
+  per-agent send allow-list, telemetry/charts, notes
+  compaction, unprivileged containers, Bash allow-list,
+  xterm.js. **Known bug** (in TODO.md): question id=5 was
+  queued but didn't render — likely a `pending()` row-decode
+  error swallowed by `unwrap_or_default`; investigate by curl
+  /api/state | jq '.questions' + browser console.