3 Commits

Include renames

Author	SHA1	Message	Date
dtourolle	6b1aac477d	Put the developer docs under docs/dev and index the folder for users first ... docs/ had 26 developer documents flat beside the manual, and the two audiences are very differently sized: most readers want the manual and the gesture reference, a few want the register, the designs and the measurements. The manual and gestures.md stay at the top; everything for someone changing the code moves to docs/dev/, and the two documents that name their own successors — the v0.1 milestone and the UI-refinement plan — go to docs/dev/archive/ rather than being deleted, since both are still cited. docs/README.md is the index, users first. Every reference follows: code comments, Cargo manifests, the workflows, the pre-commit hook, the bench and traceability tools (which locate the repo root by docs/dev/requirements.md now), packaging, the Docker READMEs, CLAUDE.md, CONTRIBUTING.md and the README. The matrix links one level deeper and is regenerated. Links out of the moved documents into the tree gain a level; a link checker over every Markdown file finds none broken.	2026-09-20 16:20:15 +02:00
dtourolleandClaude Opus 5	091306f736	Gate the gesture vocabulary the way the matrix is gated ... Three holes, all found by the gate catching itself out. **Prose that mentions the tag was read as a tag.** `dr-ui`'s module list carries a comment saying where the generated table comes from, and it names `GESTURE:` in passing; the scan extracted that sentence fragment as a gesture with no place and no way to perform it. A tag must now *open* its comment. A line that merely mentions it is describing the mechanism, not declaring a member of it, and position is the only thing that tells the two apart — which also makes the string-literal guard fall out for free rather than being a special case. **Neither artefact was regenerated on commit.** They cite line numbers, so they go stale on anything that moves a line — the sheet commit made the document wrong about every gesture in `library.slint` without touching a single one. The pre-commit hook that already keeps the matrix in step now keeps these too, and unlike the matrix it *fails* rather than shrugging when the scan does: a matrix that will not build leaves a stale one in place, where a malformed gesture block means a user about to be told the wrong thing. **CI did not check them at all.** It does now, blocking. The matrix is read; the gesture table is *shown to somebody using the application*, and a stale one tells them to perform a gesture that no longer exists — from which they will conclude the application is broken rather than the page. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-30 00:51:13 +02:00
dtourolleandClaude Opus 5	ffc40c42d2	Regenerate the matrix where the tags are changed, not after the push ... The traceability gate has failed on six commits in a row, every time for the same reason: someone added a `TRACES:` tag and did not regenerate docs/traceability.md. The gate is right to fail — a matrix that disagrees with the tree is worse than none, because it is read as current — but it says so after a push, on a commit that is otherwise fine, and by then the tag and the matrix are two separate things to remember instead of one. A pre-commit hook regenerates it and stages it, so the two travel together. Enabled with `core.hooksPath`, which is a local setting: run git config core.hooksPath .githooks in a fresh clone, or the hook sits there doing nothing. Only runs when something that can carry a tag is staged, and says nothing unless it changed the matrix — a hook that prints on every commit is one people start passing `--no-verify` to. If the report cannot run at all it leaves the matrix alone and lets the commit through: refusing to commit because a build is broken would be a worse failure than the one it prevents. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-23 15:01:44 +02:00