366180da
docs: a comment is two lines in place, and the rest has somewhere to go
a73x 2026-08-30 13:50
Commit message
CLAUDE.md
| Old | New | ||
|---|---|---|---|
| @@ -305,6 +305,10 @@ own. Test fixtures in `test/`: | |||
| 305 | prose meets its byte figure in `docscheck.budget` exactly); `zig build | 305 | prose meets its byte figure in `docscheck.budget` exactly); `zig build |
| 306 | doc-report` is the worklist. Raising a budget line is a diff someone has | 306 | doc-report` is the worklist. Raising a budget line is a diff someone has |
| 307 | to sign; lowering one is the point. | 307 | to sign; lowering one is the point. |
| 308 | - **A comment is at most two lines in place.** Longer rationale goes to | ||
| 309 | `docs/decisions.md` or a test's failure message, where it is dated or run. | ||
| 310 | Five consecutive comment lines are an essay, and every file meets its count | ||
| 311 | in `docscheck.blocks` exactly — the same ratchet, down only. | ||
| 308 | - Commit often with `--fixup`/`--squash`, autosquash before delivery. The final | 312 | - Commit often with `--fixup`/`--squash`, autosquash before delivery. The final |
| 309 | history should tell the feature's story, not the development's. | 313 | history should tell the feature's story, not the development's. |
| 310 | - `git-collab` tracks issues (`git-collab issue list`); the commit-msg hook | 314 | - `git-collab` tracks issues (`git-collab issue list`); the commit-msg hook |