Make great documentation goal 1.2, and plan the README's reorganisation and the nested-template gaps #33

Open
lilleman wants to merge 966 commits from worktree-todo-relative-dates-exact-counts into main
2 changed files with 4 additions and 6 deletions
Showing only changes of commit 7a772ea313 - Show all commits
+1 -1
View File
@@ -1341,7 +1341,7 @@ template.go the {token} grammar: scanning, tokens, operands, validation, com
hold.go the hold: one draw per expansion for paths and operands, and the rows it pins
holdfence.go the load fences over the hold: the routes and spellings that read one held name two ways
holdset.go one reference draw per render and group: the hold set a render reads its paths through
drawfence.go the load fences over reference draws: the drawGroup fences, and the walk over a render's reads
drawfence.go the load fences over reference draws: a drawGroup's, a render's and a record's columns, and the walk over what a render reads
family.go a family of linked tables: what a reference path reads of one, the rows a walk enters, and the fences over paths into it
reference.go reference sigils, and binding references across the tree
graph.go the node graph: tree walks, containment and render edges, and the cycle and repeat fences
+3 -5
View File
@@ -300,11 +300,9 @@ because pairing a street with its exact postnummer rewrites shipped rows.
round on the first and every merge after 7.0 on the second, then holds one "last
score" across both, where the `comprehension-panel` skill has two independent panels
drift unless a calibration seat reads the anchor project without its score.
- Name the draw fences at one level in `doc.go`: the Vocabulary calls them `heldCheck`,
`drawCheck` and `checkFamilies`, where `checkFamilies` runs under `drawCheck` beside
`checkOwnFamily` and `checkColumnDraws`, which it names nowhere — so a reader looking
for the fence over a record's columns finds no entry reaching it. `holdfence.go`,
`drawfence.go` and `family.go` now index the fences by file, so deleting the sentence closes it too.
- Delete `doc.go`'s "The draw fences are …" sentence: it names a function, a type and
a helper reached only through `drawWalk.check`, and misses `checkDrawGroup`,
`checkOwnFamily` and `checkColumnDraws`; the README's Layout indexes the fences by file.
- Cut `AGENTS.md` to the rules only it states: the round procedure stands word for word
in `todo.md` and the `gh` rule opens with the README's GitHub decision, so each is a
second copy that drifts. Split the comprehension rule while there, which packs the