tools: command records, Catalog and log group - bullets, examples, prohibitions (#142)
Files changed: - CHANGES.md - VERSION - tools/CONTRACT.md - tools/chemenu/commands/index_build.py - tools/chemenu/commands/log_append.py
This commit is contained in:
1 parent
fd0f60b2e7
commit
df8ff2fa22
5 files changed
+139
-26
No files matched your search
+11
-1
@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
|
||||
|
||||
---
|
||||
|
||||
## 7.1.0-beta.7 - 2026-09-26 - Command records, Git group: NOTES as bullets, one exit line per cause, examples and prohibitions
|
||||
## 7.1.0-beta.8 - 2026-09-26 - Command records, Catalog and log group: bullets, examples, prohibitions
|
||||
|
||||
**Author:** Torben Nehmer
|
||||
|
||||
@@ -76,6 +76,7 @@ concern - readable here, never shipped as something to parse.
|
||||
- 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
|
||||
- Command records, Catalog and log group: bullets, examples, prohibitions
|
||||
<!-- /wikitool:bumps -->
|
||||
|
||||
### CalDAV task-tracker provider (Nextcloud Tasks, iOS Reminders); review reports unknown-value findings instead of skipping them
|
||||
@@ -196,6 +197,15 @@ at the code that implements it. `publish`'s `atomic` property says "every gate"
|
||||
"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.
|
||||
|
||||
### Command records, Catalog and log group: bullets, examples, prohibitions
|
||||
|
||||
`index rebuild`, `log append` and `log status` rewritten the same way; text only. `log append`
|
||||
now lists its two exit-1 causes separately and states in NEVER what its retry policy said in
|
||||
prose: check the tail of `kb/log.md` before re-running after an uncertain outcome.
|
||||
`index rebuild`'s NOTES name the nested-page warning and what `--dry-run` prints, both of which
|
||||
the command already did. `log status` no longer claims it "reports 0" for a missing log - it
|
||||
reports that nothing is logged yet, which is what it always printed.
|
||||
|
||||
---
|
||||
|
||||
## 7.0.0 - 2026-09-22 - Task-Tracker-Anbindung: Vorhaben als Seitenart, Verpflichtungsschicht, Weekly Review als Read-Time-Join
|
||||
|
||||
Reference in new issue
Block a user