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
CI / verify (push) Successful in 8m5s
CI / pwsh (push) Successful in 2m43s
Release / converters (push) Successful in 27s
Release / release (push) Successful in 36s
Release / wiki-mirror (push) Skipped

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
This commit is contained in:
torbenandClaude Sonnet 5.5 committed 2026-10-15 23:32:11 +02:00
1 parent 52078bb4b0
commit 3197acfc6a
7 files changed
+57 -16

No files matched your search

+7 -6
View File
@@ -142,8 +142,9 @@ records the issue number, and the transcript stays what it is: evidence.
### 5. Ingest, one transcript at a time
Run `wiki-ingest` per transcript. **Sequentially. Never in parallel**, even when delegating to
subagents.
Run `wiki-ingest` per transcript, **each as a run of its own in a fresh context** - `/clear`
between two runs, as `wiki-ingest` step 12 ends every run. The transcripts are already in `raw/`
after step 3, so the reset loses nothing. **Sequentially. Never in parallel.**
Concurrent ingests of the same corpus collide in three places, and each collision is a silent
lost write rather than an error:
@@ -155,10 +156,10 @@ lost write rather than an error:
- **`publish`.** Two commits racing on one branch, and the Mass-Update Gate's `--confirm` token
digests a file list that the other run is still changing.
When delegating, give each subagent its own `WIKITOOL_SESSION_ID` so the budget is scoped per
transcript rather than shared - see [session-setup.md](session-setup.md). Several ingests are
several planned units, which is what makes a fresh id legitimate rather than a way around a
refusal ([gates.md](gates.md)).
**Not to subagents.** An ingest has stops only the user can answer - the key points and the
commitment in step 4, `fidelity` and `authority` in step 5, a name collision at `raw accept`, an
exit 42 - and a subagent cannot ask them. It would have to guess, which the skill forbids, or
abort.
Start the next one only after the previous has published and its tree is clean.