feat: wiki-ingest takes updating the captured repositories as a step-1 branch over raw status (#178)
CI / verify (push) Successful in 5m37s
CI / pwsh (push) Successful in 2m2s
Release / release (push) Successful in 35s

Files changed:
- CHANGES.md
- README.md
- VERSION
- instructions/wiki-ingest/SKILL.md
- raw/CONTRACT.md

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
This commit is contained in:
torbenandClaude Opus 5.5 committed 2026-10-05 19:21:12 +02:00
1 parent 8ce202a34e
commit 8fec406463
5 files changed
+74 -11

No files matched your search

+3 -1
View File
@@ -222,7 +222,9 @@ Documentation that lives in a git repository is captured, not copied: `tools/wik
for byte, into `incoming/<bundle>/` together with a `_capture.json` manifest naming the repository,
the ref rule and the commit. Later, `tools/wikitool raw status` tells you which captured bundles
have fallen behind their repository, file by file; `raw capture --update` and `raw accept
--replaces-bundle` take the new edition in as a whole. Git uses your own keys and credential
--replaces-bundle` take the new edition in as a whole. You need not run any of that yourself:
tell the LLM `Update the captured repositories`, and it checks them, takes one changed bundle per
run into the wiki and says how many are still behind. Git uses your own keys and credential
helpers - nothing is stored in the repository.
### Querying Knowledge