tools: command records, Git group - NOTES as bullets, one exit line per cause, examples and prohibitions (#142)
CI / verify (push) Successful in 1m15s
Release / release (push) Successful in 37s

Files changed:
- CHANGES.md
- VERSION
- tools/CONTRACT.md
- tools/README.md
- tools/chemenu/cli_contract.py
- tools/chemenu/commands/cite_cmd.py
- tools/chemenu/commands/dist_cmd.py
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/commands/doctor.py
- tools/chemenu/commands/eval_cmd.py
- tools/chemenu/commands/git_publish.py
- tools/chemenu/commands/index_build.py
- tools/chemenu/commands/instructions_cmd.py
- tools/chemenu/commands/links_cmd.py
- tools/chemenu/commands/lint.py
- tools/chemenu/commands/log_append.py
- tools/chemenu/commands/migrate_cmd.py
- tools/chemenu/commands/new_page.py
- tools/chemenu/commands/page_ops.py
- tools/chemenu/commands/provenance_cmd.py
- tools/chemenu/commands/raw_cmd.py
- tools/chemenu/commands/review_cmd.py
- tools/chemenu/commands/run_budget.py
- tools/chemenu/commands/search.py
- tools/chemenu/commands/task_cmd.py
- tools/chemenu/commands/touch.py
- tools/chemenu/commands/types_cmd.py
- tools/chemenu/commands/upload_cmd.py
- tools/chemenu/commands/upstream_cmd.py
- tools/chemenu/commands/version_cmd.py
- tools/chemenu/commands/work_cmd.py
- tools/chemenu/commands/xref.py
- tools/chemenu/tests/test_cli_contract.py
- tools/chemenu/tests/test_docs_verify.py
This commit is contained in:
torben committed 2026-09-26 08:25:41 +02:00
1 parent 2a60f3a265
commit fd0f60b2e7
34 files changed
+601 -285

No files matched your search

+23 -1
View File
@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
---
## 7.1.0-beta.6 - 2026-09-26 - dist export no longer cuts the dist export record out of the shipped tools/CONTRACT.md
## 7.1.0-beta.7 - 2026-09-26 - Command records, Git group: NOTES as bullets, one exit line per cause, examples and prohibitions
**Author:** Torben Nehmer
@@ -75,6 +75,7 @@ concern - readable here, never shipped as something to parse.
- version bump no longer points at version release in its output
- stack-close: wait for CI through the authenticated Gitea connection, with timings and a give-up point
- wikitool: usage lines name wikitool, and the -h acceptance checks become tests
- Command records, Git group: NOTES as bullets, one exit line per cause, examples and prohibitions
<!-- /wikitool:bumps -->
### CalDAV task-tracker provider (Nextcloud Tasks, iOS Reminders); review reports unknown-value findings instead of skipping them
@@ -174,6 +175,27 @@ shipped copy against its source until the region became generated. The record no
markers without spelling out the pair, and a new test pins that the export plan ships
`tools/CONTRACT.md` byte-identical to the working tree.
### Command records, Git group: NOTES as bullets, one exit line per cause, examples and prohibitions
First pass of the editorial rewrite of the command records, starting with `sync` and `publish`.
Text only - no command behaves differently. The record model grew what the rewrite needs:
`notes` takes a tuple of present-tense bullets (a plain string, the old form, still renders as
one paragraph until every group is done), and `Failure` is now one cause with its own reaction
and exit code (`cause`, `reaction`, `code` 0/1/42) instead of one lumped "exit 1 means"/"retry
policy" pair per command. EXIT STATUS lists one line per cause; ON FAILURE repeats the cause
next to its reaction so each line reads on its own; an explicit exit-42 cause replaces the
generic gate line, and a record declaring one without a gate is refused at import. The field
rename is mechanical across all records, so every not-yet-rewritten command's ON FAILURE line now
reads `<old exit-1 text> -> <old retry text>`.
`sync` and `publish` now carry copyable EXAMPLES (including the re-run after exit 42), a NEVER
section (do not retry or force a failed git step, do not pass an unapproved token, do not edit
`.wikitool-remotes.json` past a refusal), SEE ALSO, and self-contained NOTES in place of "exactly
like `sync`". Sentences that only explained *why* left the records; each was already a comment
at the code that implements it. `publish`'s `atomic` property says "every gate" instead of
"both gates" - it has three, and all run before staging. How a record's prose is written is now
stated once, in the `CommandRecord` docstring, and `tools/README.md` points there.
---
## 7.0.0 - 2026-09-22 - Task-Tracker-Anbindung: Vorhaben als Seitenart, Verpflichtungsschicht, Weekly Review als Read-Time-Join