fix: three more #142 command-record mismatches aligned to code (#146)

Files changed:
- CHANGES.md
- VERSION
- kb/CONTRACT.md
- tools/CONTRACT.md
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/commands/git_publish.py
- tools/chemenu/commands/lint.py
- tools/chemenu/commands/xref.py
- tools/chemenu/tests/test_cli.py

CHANGES.md

@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
 
 ---
 
-## 7.1.0-beta.24 - 2026-09-26 - log append: unreadable --body-file is an ERROR line, not a traceback
+## 7.1.0-beta.25 - 2026-09-26 - Command records: three more mismatches from #142 aligned to code
 
 **Author:** Torben Nehmer
 
@@ -93,6 +93,7 @@ concern - readable here, never shipped as something to parse.
 - Command records: NOTES is always a tuple of bullets; every record's examples are tested
 - network: property defined; sync, publish and upstream merge marked networked
 - log append: unreadable --body-file is an ERROR line, not a traceback
+- Command records: three more mismatches from #142 aligned to code
 <!-- /wikitool:bumps -->
 
 ### CalDAV task-tracker provider (Nextcloud Tasks, iOS Reminders); review reports unknown-value findings instead of skipping them
@@ -389,6 +390,23 @@ through `fail()`, which also gives the budget slot back, before `kb/log.md` is o
 stays byte-identical in every failure case, and a parametrised test pins all three. The
 record's cause now names the cases ("missing, not a readable file, or not valid UTF-8").
 
+### Command records: three more mismatches from #142 aligned to code
+
+Four more text-vs-code disagreements from #142's collection issue (Gitea #146), decided in the
+code's favour and fixed in the text - no behaviour change. `lint`'s quote-limit cap counts
+blockquotes, not lines, since #22 changed the unit; `kb/CONTRACT.md`'s Quotation cap section had
+kept the old wording and now names the same unit, with the rule that a fenced code block is
+masked out first. `docs contract`'s record carried no exit-1 cause at all although
+`contract_command` fails when `tools/CONTRACT.md` is missing - the case #143's own follow-up
+flagged - so it now names that cause; the merged-stream test that used to exercise the `see:`
+fallback through this very gap is updated to check the new hint instead, and the fallback itself
+stays covered by its own fixture-based test. `xref add`'s `atomic` property still described the
+two-write shape from before the edge became one-sided, though the code and its own NOTES have
+long said a source-page edge only ever writes A; it now says so. `publish`'s `atomic` property,
+tightened once already in this candidate to "every gate runs before staging", still missed the
+one case that breaks it: the rebase-review gate can exit 42 on the single retry of a rejected
+push, which happens after the commit already landed.
+
 ---
 
 ## 7.0.0 - 2026-09-22 - Task-Tracker-Anbindung: Vorhaben als Seitenart, Verpflichtungsschicht, Weekly Review als Read-Time-Join