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

Files changed:
- CHANGES.md
- VERSION
- tools/CONTRACT.md
- tools/chemenu/commands/new_page.py
- tools/chemenu/commands/page_ops.py
- tools/chemenu/commands/task_cmd.py
- tools/chemenu/commands/touch.py

CHANGES.md

@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
 
 ---
 
-## 7.1.0-beta.9 - 2026-09-26 - Command records, Distribution and versioning group: one line per cause, examples, prohibitions
+## 7.1.0-beta.10 - 2026-09-26 - Command records, Pages group: one line per cause, examples, prohibitions
 
 **Author:** Torben Nehmer
 
@@ -78,6 +78,7 @@ concern - readable here, never shipped as something to parse.
 - Command records, Git group: NOTES as bullets, one exit line per cause, examples and prohibitions
 - Command records, Catalog and log group: bullets, examples, prohibitions
 - Command records, Distribution and versioning group: one line per cause, examples, prohibitions
+- Command records, Pages 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
@@ -224,6 +225,20 @@ which stopped being true when `!/incoming/.gitkeep` was added, and `dist upgrade
 now carries the reasoning for writing the stamp whole after `--keep-local`, which used to live
 in the record.
 
+### Command records, Pages group: one line per cause, examples, prohibitions
+
+`new`, `task new`/`list`/`close`, `touch`, `rename`, `rm` and `move` rewritten the same way;
+text only. `new`'s long per-variant notes moved into NOTES bullets, leaving each variant one line
+that says where the page lands, and `new project`'s tracker cases - name taken, read-only access
+path, a provider that cannot create projects (exit 42, cleared with `--resume`) - each got their
+own exit line and reaction. Every "same posture as `new project`" and "same reasoning as
+`task new`" in the three `task` records is replaced by the fact it pointed at. The records also
+name failures the code already had and the old text left out: `new`'s missing capture field and
+its page-write failure after the tracker project was confirmed, and the partial-write failures of
+`rename`, `rm` and `move --reconcile`. The reasoning behind `task new`/`task close` never exiting
+42, and behind `task close` taking an id rather than a title, moved into `task_cmd.py`'s module
+docstring.
+
 ---
 
 ## 7.0.0 - 2026-09-22 - Task-Tracker-Anbindung: Vorhaben als Seitenart, Verpflichtungsschicht, Weekly Review als Read-Time-Join