docs: raw accept points an occupied captured-bundle name at --replaces-bundle (#177)

The ON FAILURE reaction for an occupied folder name still said there is no
--replaces for a folder; for a captured bundle that sent a new edition down
the rename route. raw/CONTRACT.md names the manifest as a captured folder's
source of the capture fields.

Files changed:
- CHANGES.md
- VERSION
- raw/CONTRACT.md
- tools/CONTRACT.md
- tools/chemenu/commands/raw_cmd.py

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

raw/CONTRACT.md

@@ -85,7 +85,9 @@ tools/wikitool raw accept --fidelity verbatim --authority reporting incoming/pro
 
 The folder name is the bundle name, so the name rule below applies to it and not to the files
 inside: two `README.md` in different subfolders are no conflict. A folder is accepted alone, with
-one `--fidelity`/`--authority` pair for all of it, and `incoming/projekt-x` is gone afterwards.
+one `--fidelity`/`--authority` pair for all of it - a folder `raw capture` wrote takes the pair
+from its manifest instead ([below](#getting-a-repository-in-raw-capture)) - and
+`incoming/projekt-x` is gone afterwards.
 Every check runs before anything moves: an empty folder is refused, and so is one with a hidden
 entry (a name starting with `.`), a symlink or a special file anywhere below it - each is named.
 That is what keeps the clean-up safe: only directories the moves emptied are removed, so no file