Rotation: a clear ends background agents, so rotate with none in flight; briefings carry each question's options

The 2026-10-03 clear killed three agents that the handoff expected to survive:
commits survived on branches, two cut reports and a verdict were never admitted.
The same morning's catch-up gave the operator recommendations without options,
because it read the handoff instead of the question documents.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

references/tool-calling-cut.md

@@ -227,8 +227,9 @@ Shape:
    at ~500k, which is **~30% of root reads**.
 2. **Rotate the root at about 300k, or at each phase boundary, whichever comes
    first.** All campaign state is in Huginn, so the handoff is short: the
-   campaign slug, the session label, in-flight agent ids, and the next action,
-   written to the scratchpad. Self then asks the operator to `/clear` (Q3). A
+   campaign slug, the session label and the next action, written to the
+   scratchpad. A clear ends the session's background agents (observed
+   2026-10-03), so rotate when none is in flight; see SKILL.md. Self then asks the operator to `/clear` (Q3). A
    fresh root rehydrates with the campaign recipes, at about 100k. At a median
    root context of ~200k instead of ~500k, **every remaining root call costs
    about 60% less**.
@@ -299,7 +300,7 @@ Shape:
 - **451-513 (Self's discipline): add two bullets:**
   - **Self's own context is the most expensive in the pipeline.** Every
     notification re-reads all of it. Rotate at ~300k or at a phase boundary:
-    write the handoff (slug, session label, in-flight agent ids, next action)
+    write the handoff (slug, session label, next action; no agent in flight)
     and ask the operator to `/clear` (ruling: Q3). Never read logs or diffs in
     the root; `view` reports and verdicts.
   - **A subagent that notifies before its report is a brief defect.** Count