Runs that go in circles end (M7.8)

Driver.run checks each turn with nisse_core.loop.circles and ends the run
as "circling" when the same calls get much the same back, one harness
correction is given again and again, or the model apologises, for
circle_repeats turns in a row (default 3). Near-identical calls (git add
a.py, b.py) and scattered apologies stay flags on the status page. A
fact in the transcript says why the run ended.

nisse-dev calls in a helper as for a stuck run, then asks the operator;
nisse-review counts a failed run and posts none of its drafts. Tuning:
tuning.driver / tuning.review circle_repeats (0 off) and circle_similar.

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

docs/Development-Plan.md

@@ -811,7 +811,12 @@ 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.
+doing; the limits are tuning. **Done** (this PR): `RunOutcome("circling")`
+after the same calls getting much the same back, one correction, or apologies,
+`tuning.*.circle_repeats` turns in a row (3). Near-identical calls only flag on
+the page (`git add a.py`, `b.py`). nisse-dev calls in a helper as for a stuck
+run, then asks; nisse-review counts a failed run and posts none of its drafts.
+The helper's own loop keeps its caps.
 
 ### Phase 8 — `nisse-ops`