docs: raw accept points an occupied captured-bundle name at --replaces-bundle (#177)
CI / verify (push) Successful in 5m36s
CI / pwsh (push) Successful in 2m5s
Release / release (push) Successful in 36s

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
This commit is contained in:
torbenandClaude Opus 5.5 committed 2026-10-05 12:13:09 +02:00
1 parent 311c8ee059
commit 8ce202a34e
5 files changed
+20 -6

No files matched your search

+11 -1
View File
@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
---
## 8.0.0-beta.41 - 2026-10-05 - raw capture / raw status / --replaces-bundle: documentation from git repositories as a bundle, with drift reporting
## 8.0.0-beta.42 - 2026-10-05 - raw accept: an occupied folder name held by a captured bundle points at --replaces-bundle
**Author:** Torben Nehmer
@@ -152,8 +152,18 @@ concern - readable here, never shipped as something to parse.
- kb/CONTRACT.md names section anchors in wikilinks and the Broken Anchors finding
- kb/CONTRACT.md names unwritten scaffold sections and the Unfilled Template Sections finding
- wiki-ingest and wiki-manage call xref add with --rel, not the --rel-a/--rel-b removed in 4.0.0
- raw accept: an occupied folder name held by a captured bundle points at --replaces-bundle
<!-- /wikitool:bumps -->
### 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
"rename the folder - there is no `--replaces` for a folder". For the new edition of a captured
bundle that is the wrong route: renaming makes it a second, separate source. The reaction now
names `--replaces-bundle` for a name held by a captured bundle and keeps renaming for every other
folder. `raw/CONTRACT.md` § "Getting a file in" says the same about the capture fields of a
captured folder: they come from its manifest, not from one flag pair (Gitea #177).
### raw capture / raw status / --replaces-bundle: documentation from git repositories as a bundle, with drift reporting
Documentation from a git repository used to reach an instance only by hand: copy the files into