fix(docs): AGENTS.md-Contract-Prosa als Sitzungsarbeit klargestellt, doc-pull-through-Instruction (schliesst #90)
CI / verify (push) Successful in 53s
Release / release (push) Successful in 37s

Files changed:
- AGENTS.md
- CHANGES.md
- VERSION
- instructions/dev/doc-pull-through.md
- instructions/dev/stack-close/SKILL.md
- instructions/dev/stack-dev/SKILL.md
- instructions/dev/testing-conventions.md
- instructions/dev/version-parts.md
- tools/chemenu/commands/docs_verify.py
This commit is contained in:
2026-09-11 11:58:34 +02:00
parent 5b916c6d18
commit 441a8151ab
9 changed files with 148 additions and 19 deletions
+8 -5
View File
@@ -289,11 +289,14 @@ Changes to this schema, the contracts, the instruction layer, `tools/wikitool`,
READMEs go in [CHANGES.md](CHANGES.md) - never in an inline version-history table here. Wiki
*content* operations are logged separately via `tools/wikitool log append` into `kb/log.md`.
**A stack change is not finished until the human docs describe it.** `README.md`, `EVALS.md`
and `tools/README.md` are part of the change that introduced a stage, a command or a workflow,
not follow-up work: nobody comes back for them, and a document that describes a repo which no
longer exists is worse than none. The mechanical half - command tables, contracts, ignore
canaries - is checked by `tools/wikitool docs verify`; the prose half is yours.
**A stack change is not finished until the human docs describe it.** `README.md`, `EVALS.md`,
`tools/README.md`, `tools/CONTRACT.md` and the touched `<stage>/CONTRACT.md` are part of the
change that introduced a stage, a command or a workflow, not follow-up work: nobody comes back
for them, and a document that describes a repo which no longer exists is worse than none. What
`tools/wikitool docs verify` mechanically checks is exactly what its own `docs verify` row in
[tools/CONTRACT.md](tools/CONTRACT.md) lists - no more. **Every cell's text is outside that
check** - a command table entry's description, an error contract's wording, a stage contract's
prose - and is therefore session work, the same as the three README-shaped files.
`docs/` pages are held to a different clock than those three. A README goes stale on every new
flag; a `docs/` page goes stale only when the reasoning it wrote down stops holding - a gate