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/Architecture.md

@@ -221,6 +221,10 @@ again after a restart), permissions (L3), and work in progress as intents (L8).
   next tool boundary, unmounts elevated credentials, and asks what next.
 - **`abandon` ends a work item** from any waiting point, closing its record and
   any open PRs with a note and aborting its unresolved intents.
+- **A run going in circles ends** rather than running to its turn cap: turns that
+  repeat near-identically, or one correction (such as "reply with a tool call")
+  given again and again, end it in code, escalated with what it was doing. A loop
+  the model can't leave is the harness's to fix, not the model's to push through.
 - **Every action passes through the three layers** (P4).
 
 ### L3. Authority: scope and approvals
@@ -432,6 +436,8 @@ volume.
 - **It is never load-bearing:** nothing in the agent reads it, a failed write is
   logged and the call goes ahead, and it is deleted when the agent starts. Its
   layout never migrates; it carries its version for the page (X6).
+- **Agents are told:** while it records, each system prompt says in one sentence
+  that the agent's calls are recorded for the operator's study.
 - **On by default, off per agent** in its configuration: an agent that handles
   other people's lives (a household's presence, conversations, cameras) records
   nothing unless they know.
@@ -1175,6 +1181,8 @@ and memory work in practice), more than for daily use.
   reasoning, and the raw JSON. Memory appears as the log records it: the index
   when it was shown, each note read or written. Work from before the agent's last
   start has its steps but no requests.
+- **Loops are flagged:** near-identical turns, repeated apologies, one correction
+  given again and again, so they're seen and fixed (L2).
 - **It reads, never writes:** each agent's state store and call record through a
   read-only mount, opened read-only in short transactions, and the agent's memory
   folder read-only, as SilverBullet does (L10). Each agent stays the only writer