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

+6 -1
View File
@@ -311,7 +311,12 @@ the folder carries a different name, or when either side is not a captured bundl
Afterwards the bundle holds exactly the new manifest's files and `_capture.json`. Like
`--replaces`, it leaves every `raw_files:` as it was: which source page takes a new file, and
whether a source page left with no file is retired, is the ingest's judgment, and the command
prints the `touch` lines that carry it out. `git diff` on the bundle is the edition diff.
prints the `touch` lines that carry it out. The edition diff is `git diff` on the bundle for the
changed and removed files, plus the added ones the accept lists - those are still untracked.
**When to update is the user's call; the rest is not.** Asked to update the captured
repositories, `wiki-ingest` runs `raw status` itself and takes one changed bundle per run through
these two commands - the user never names a commit or a path.
**A captured bundle changes only as a whole.** `raw accept --replaces` and `--page` refuse a
target inside one: replacing or adding a single file would leave the bundle's content no longer