feat: wiki-ingest takes updating the captured repositories as a step-1 branch over raw status (#178)

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

CHANGES.md

@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
 
 ---
 
-## 8.0.0-beta.42 - 2026-10-05 - raw accept: an occupied folder name held by a captured bundle points at --replaces-bundle
+## 8.0.0-beta.43 - 2026-10-05 - wiki-ingest: updating the captured repositories is a step-1 branch over raw status
 
 **Author:** Torben Nehmer
 
@@ -109,6 +109,7 @@ concern - readable here, never shipped as something to parse.
 - lint: Unfilled Template Sections - a section still holding only its template's TODO placeholders (advisory)
 - Comparison and source pages accept the sources: that cite add writes; sources may cite sources
 - raw capture / raw status / --replaces-bundle: documentation from git repositories as a bundle, with drift reporting
+- wiki-ingest: updating the captured repositories is a step-1 branch over raw status
 
 **Low impact**
 - version bump no longer points at version release in its output
@@ -155,6 +156,27 @@ concern - readable here, never shipped as something to parse.
 - raw accept: an occupied folder name held by a captured bundle points at --replaces-bundle
 <!-- /wikitool:bumps -->
 
+### wiki-ingest: updating the captured repositories is a step-1 branch over raw status
+
+`raw status`, `raw capture --update` and `raw accept --replaces-bundle` existed, but nothing told
+a session what to do when asked to update the captured repositories: the decision point for a new
+edition began with "`raw status` reported it" and nobody ran `raw status`. Step 1 of `wiki-ingest`
+now has that entry, built like the existing branch over `raw pending`. It runs `raw status`, ends
+the run when nothing changed (naming every unreachable or refused repository with its reason),
+otherwise takes one changed bundle per run (the one the user named, else the first in the output),
+announces it with `old -> new` and how many others changed, and runs the `raw capture --update`
+line `raw status` printed. From step 5 the existing decision point carries the run. The user never
+names a commit or a path. The skill's description and example triggers name the request ("update
+the captured repositories", "pull the repo docs").
+
+The decision point now says what the edition diff is: `git diff -- <raw-bundle>` for changed and
+removed files, plus the `A` list `raw accept` prints, because added files are still untracked and
+never show up in `git diff`. `raw/CONTRACT.md` § "Getting a repository in" and `README.md` say how
+an update is started.
+
+Instruction text only, no interface changed - drop-in in both directions; an older version simply
+lacks the branch (Gitea #178).
+
 ### raw accept: an occupied folder name held by a captured bundle points at --replaces-bundle
 
 The ON FAILURE reaction `raw accept incoming/<folder>` prints for an occupied name still said