wiki-ingest: ein Lauf endet nach einer Quelle mit Stopp und /clear-Empfehlung - keine Schleife über mehrere Einträge im selben Kontext; Subagents für den Ingest verworfen, capture-session delegiert nicht mehr; gates.md: neuer Lauf auf ausdrücklichen Wunsch ist eine Einheitsgrenze (#219); 10.1.0-beta.13

Files changed:
- CHANGES.md
- VERSION
- docs/how-to/capture-repository-docs.md
- docs/how-to/ingest-a-source.md
- instructions/capture-session.md
- instructions/gates.md
- instructions/wiki-ingest/SKILL.md

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

instructions/gates.md

@@ -229,6 +229,12 @@ never in response to a gate refusal.** The plan is the human approval the gate w
 have to ask for; a refusal means that approval has not been given yet. If you are tempted to
 re-export the variable after an `ERROR` line, that is the gate working.
 
+**A run the user explicitly asked to start in the same context is the other legitimate
+boundary.** `wiki-ingest` ends every run after one source and recommends `/clear`; when the user
+asks to go on in this context regardless, that request is the human approval, the finished run is
+the unit boundary, and the new run takes a new id ([wiki-ingest](wiki-ingest/SKILL.md) § Decision
+points). The agent never proposes this itself, and it is no way past a refusal.
+
 **One tool takes a new id itself, for a fixed set of read commands.** `tools/bugreport.py`
 ([bug-report.md](bug-report.md)) runs `instructions verify` and `docs verify` under
 `WIKITOOL_SESSION_ID=bugreport-<stamp>`, so that collecting a report neither spends the