Docs: the status page and the call record (#109)

nisse-ui (X6) shows the operator each agent's work and, per item, a
walkthrough down to every model request and response, for studying how
context, compaction and memory work. It reads each agent's state store,
call record and memory folder through read-only mounts, so agent code is
unchanged and each agent stays the only writer of its state; it is
released with the agents and tested against stores their own code wrote.

The call record (L7) is new in nisse-core: every request as sent, the raw
response with its reasoning, timing, tokens, prompt reuse and each
message's provenance. It is diagnostic only, never read by the agent, and
deleted at start, so it never migrates.

Commands from the page, including a hold on a task or a whole agent, are
an open question (Part Q). The shared database first proposed in #109 is
dropped. The plan gets M6.6.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk

docs/Development-Plan.md

@@ -578,6 +578,22 @@ Samba AD principal (L12).
 
 **M6.5 The browser tool.** *Pre-approved.* On the internal test network (D7).
 
+**M6.6 The status page.** *Pre-approved (design agreed 2026-10-24, #109).*
+`nisse-ui` (X6), for studying how the agents work: context, compaction, memory.
+Slices a–c are built on this box before the agent host is ready, against
+bring-up, end-to-end and benchmark runs; only d waits for M6.1.
+- **a. The call record** (L7) in `nisse-core`: written by the shared model client
+  and `Driver.run`, with each message's provenance from the per-role view and
+  fitting; wired in each agent's build; deleted at start.
+- **b. The walkthrough:** an item's steps, each run's turns, and each request read
+  against the log it was made from.
+- **c. The overview:** each agent's active, queued, parked and blocked items.
+- **d. Deployment:** its image, the read-only mounts and a Caddy route behind
+  Authelia (with #166).
+
+Commands wait (Part Q). The shared database #109 first proposed is dropped: each
+agent keeps its own store.
+
 ### Phase 7 — `nisse-core` and `nisse-review`
 
 `nisse-review` (Part R) comes before `nisse-ops`: it writes only comments, so it
@@ -796,6 +812,7 @@ the Terraform the operator is writing now. **M8.4 The ops tool VM and deployment
 From the architecture's open questions and older issues: filing issues from
 conversation; stacked PRs; releases; `nisse-ops` issuing credentials; a server
 database; recovering the agent host (an ops issue); more than one active work item;
+commands from the status page, with a hold on a task or agent (X6);
 vision; one local model for every agent; several forges (#26); a room per project
 (#28).
 
@@ -816,6 +833,7 @@ vision; one local model for every agent; several forges (#26); a room per projec
 | #69 inline review comments | M2.1 |
 | #70 watch stall | M2.1 |
 | #77 conversational agent | M2.3 (questions), M2.7 |
+| #109 a UI for every agent's status (no shared database) | M6.6 |
 | #137 block on an unreachable build VM | M4.4 |
 | #144 redact secrets an MCP server returns | After M8.1 |