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.

TODO.md

@@ -42,6 +42,26 @@ Pick anything from here when relevant. Cross-cutting design notes live in
   derived from the same config so the operator stays in control of
   what's exposed.
 
+## Bugs
+
+- **Pending question doesn't always appear on the dashboard.**
+  Repro: manager calls `ask_operator`, tool result is
+  `question queued (id=N)` (so the row is in sqlite), but the
+  M1ND H4S QU3STI0NS section keeps showing "no pending
+  questions". Last seen with id=5. Suspected paths:
+  - `OperatorQuestions::pending()` returns Err and the
+    `unwrap_or_default()` in `api_state` hides it. Surface the
+    error (warn-log) and check.
+  - serialization: a new field in `OpQuestion` (e.g.
+    `deadline_at: Option<i64>`) deserializes wrong against an
+    old row whose columns don't match the new SELECT order →
+    `row.get(N)?` panics for that row, the whole iterator
+    errors, `pending()` returns Err. Diagnose by curl
+    `/api/state | jq '.questions'` and compare with sqlite
+    counts.
+  - dashboard JS swallows a render error. Open browser console
+    and look for exceptions during `renderQuestions`.
+
 ## UI / UX
 
 - **xterm.js terminal** embedded per-agent, attached to a PTY exposed by