Record why each entry point to drawCheck.reads keeps its own doc

This commit is contained in:
2026-09-25 17:24:44 +02:00
committed by Lillem4n
parent 29f1908e5a
commit 191186ec94
2 changed files with 7 additions and 0 deletions
+6
View File
@@ -646,3 +646,9 @@ import drops them by name rather than by a rank a regeneration would move.
`region.municipality.locality` is listed, and `region.locality` resolves too but is not:
the set of every descent through a chain of five tables is every subsequence of it, and
the direct chain is the one a reader can predict from the tables' parents.
## Each entry point to `drawCheck.reads` says what its caller gets
2026-09-25, larv-review; approved 2026-09-25 by lilleman. Goal 2: a reader lands on
`readsPath` or `splitsDraws` from its caller, so each doc states where that walk stops,
though `reads` states the same stop rule. Valid while the two differ in where they stop.