tools: command records, Workshop runs and session budget group - examples, prohibitions (#142)

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

CHANGES.md

@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
 
 ---
 
-## 7.1.0-beta.14 - 2026-09-26 - Command records, Raw material and uploads group: one line per cause, examples, prohibitions
+## 7.1.0-beta.15 - 2026-09-26 - Command records, Workshop runs and session budget group: examples, prohibitions
 
 **Author:** Torben Nehmer
 
@@ -83,6 +83,7 @@ concern - readable here, never shipped as something to parse.
 - Command records, Finding and checking group: one line per cause, examples, prohibitions
 - Command records, Provenance group: examples, exit lines per cause
 - Command records, Raw material and uploads group: one line per cause, examples, prohibitions
+- Command records, Workshop runs and session budget group: examples, prohibitions
 <!-- /wikitool:bumps -->
 
 ### CalDAV task-tracker provider (Nextcloud Tasks, iOS Reminders); review reports unknown-value findings instead of skipping them
@@ -279,6 +280,13 @@ reaction and in NEVER, what `raw/CONTRACT.md` already asks of an agent: show the
 wait, since only the user can tell a new edition from a second source. `upload accept` states its
 gate's shape itself instead of pointing at the Mass-Update Gate's.
 
+### Command records, Workshop runs and session budget group: examples, prohibitions
+
+`work new`, `work close`, `budget status` and `budget reset` rewritten the same way; text only.
+`budget reset` now carries AGENTS.md invariant 6's rule as NEVER - it is never run on an agent's
+own initiative to get past a budget refusal - and `work close` states the caller's side of its
+`--yes`: the run's conclusions are in `kb/` first.
+
 ---
 
 ## 7.0.0 - 2026-09-22 - Task-Tracker-Anbindung: Vorhaben als Seitenart, Verpflichtungsschicht, Weekly Review als Read-Time-Join