tools: command records, Content migrations group - one line per cause, examples, prohibitions (#142)

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

CHANGES.md

@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
 
 ---
 
-## 7.1.0-beta.17 - 2026-09-26 - Command records, Telemetry group: examples, the missing --fail-on-error exit line
+## 7.1.0-beta.18 - 2026-09-26 - Command records, Content migrations group: one line per cause, examples, prohibitions
 
 **Author:** Torben Nehmer
 
@@ -86,6 +86,7 @@ concern - readable here, never shipped as something to parse.
 - Command records, Workshop runs and session budget group: examples, prohibitions
 - Command records, Types, instructions and docs group: one line per cause, examples, prohibitions
 - Command records, Telemetry group: examples, the missing --fail-on-error exit line
+- Command records, Content migrations group: one line per cause, examples, prohibitions
 <!-- /wikitool:bumps -->
 
 ### CalDAV task-tracker provider (Nextcloud Tasks, iOS Reminders); review reports unknown-value findings instead of skipping them
@@ -306,6 +307,15 @@ always done. The reasoning `docs toc`'s record carried about its scope already l
 has always exited 1 on a failed scorecard, but its record only listed the missing-trace case; it
 now names both.
 
+### Command records, Content migrations group: one line per cause, examples, prohibitions
+
+The five `migrate` commands rewritten the same way; text only. `migrate done` and
+`migrate baseline` state as NEVER what their prose implied - never force the chain's order,
+never advance the version with `baseline --force` or by editing `.wikitool-kb.json` - and
+`migrate verify` separates a bad `--from` revision from the findings it exits 1 on. The reasoning
+behind counting marker pairs rather than comparing their names, and behind an offered migration
+ignoring the chain, moved into the `verify` and `done` docstrings.
+
 ---
 
 ## 7.0.0 - 2026-09-22 - Task-Tracker-Anbindung: Vorhaben als Seitenart, Verpflichtungsschicht, Weekly Review als Read-Time-Join