docs(guides): slice 1 identities runbook (row SR); lead decision 56

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/plans/2026-09-26_lead-decisions.md

@@ -914,3 +914,24 @@ which stay with him. Each item names who decided it and what happened.
       and the new project id when the reason is `moved`. The v2 schema
       checks `credential.*` bodies the same way, and an event the reader
       can't act on is worse than a refused write.
+56. **Dewey's S5 questions (2026-10-04).** Source: Dewey, design note
+    `agents/dewey/work/wui/SLICE1-VIEWS.md` (uncommitted, Dewey's working
+    file). All five recommendations are accepted.
+    - Q1: the inbox, tasks, agents and trail reads live in one module in
+      `packages/bus`, over the broker client. Both the CLI (S4) and the
+      WebUI server (S5) import it, so REQ-WEB-1's "same data" holds by
+      construction. The WebUI never opens `bus.sqlite`. Rocko owns it,
+      because S2 and S4 are both his rows.
+    - Q2: the broker gains a status read giving the last successful board
+      and cursor read per project, plus the last poll error. Row S3 builds
+      it, since the poller is S3's.
+    - Q3: any event about one task carries the task ref in `subject`. The
+      `task.create` body also names the `human.input` event that asked
+      for it, so a trail can begin at Jason's request. These are body
+      rules, so the kind list doesn't change. Darkwing decides whether a
+      trigger or the broker enforces each one.
+    - Q4: the WebUI writes nothing in slice 1, not even `seen`. The inbox
+      detail shows the `mosaic decide` command to copy.
+    - Q5: S5 also fixes `escalating` staying set after a throw, and a
+      takeover followed by Enter in one chunk, because both sit in files
+      S5 owns. The freeze-ordering test stays in DEFERRED.