Docs: runs going in circles end; agents are told they're recorded

A run that repeats itself, or keeps getting the same correction, ends in
code as escalated instead of running to its turn cap (L2, M7.8), and the
page flags such runs (X6). While the call record is on, each system
prompt says so.

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

docs/Development-Plan.md

@@ -584,9 +584,10 @@ 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.
+  fitting; wired in each agent's build; deleted at start. Each system prompt
+  says the calls are recorded, while they are.
 - **b. The walkthrough:** an item's steps, each run's turns, and each request read
-  against the log it was made from.
+  against the log it was made from; runs going in circles flagged.
 - **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).
@@ -796,6 +797,13 @@ publishes `gitea.dongar.net/dev/nisse-review` beside `nisse-dev`, and
 **M7.7 Deployment.** *Waits for the agent host (Phase 6).* Its container on the
 agent host, Gitea account and secrets (R5).
 
+**M7.8 Runs that go in circles end** (L2). *Pre-approved.* In `Driver.run`, for
+every agent. Seen 2026-10-24 on Flash-Next: invented tool names met with the
+prose reminder turn after turn, and a no-thinking run posting the same apology
+comment about 20 times until the turn cap. Repeated near-identical turns, or the
+same correction given too often, end the run as escalated, with what it was
+doing; the limits are tuning.
+
 ### Phase 8 — `nisse-ops`
 
 **M8.1 MCP servers** (#37). Settled so far: redaction scrubs each instance's own