3 Commits

Include renames

Author	SHA1	Message	Date
volt	e79cbca627	checkin 2026-10-17 (volt): Q63 closed -- queue_index.py admits ids by record form (heading, bold lead, Status-lead) and reports the record line vs the first mention; nested set 16 -> 9 (Q41,Q42,Q46,Q47,Q50,Q51,Q52,Q53,Q63; Q77/Q99 were quoted tool output, Q54/55/56/58/62 were artifact text and a Q31-Q62 range, none ever opened); selftest 44/44, sweep 11 tools/10 OK/0 fatal, --check rc 0 at 9930 L	2026-10-17 17:23:00 +00:00
volt	55f223e7d9	tools (volt): the queue index stops rendering the prose corpus into itself ... The corpus leg is a function of the working tree, not of the queue: --outside read Q63, then Q63+Q77+Q99 once a checkin quoted the ids the gate test uses -- same queue, same sha256, three documents. Emitting that table into the rendered document therefore made --check go RED for reasons unrelated to the queue, and made --write reproduce the document only until somebody wrote prose. - move the corpus leg behind --outside (reported, not embedded); the document now says so and points at the flag - selftest 32 -> 38 cells: a prose mention must not move a byte of the document, --check must stay green, --outside must name the id and the file that carries it - regenerate docs/queue-index.md (36,585 B); --check is green, --write byte-identical	2026-10-17 13:09:07 +00:00
volt	1423c4d77a	tools (volt): queue_index.py -- the queue's table of contents, and the gate that it stays current ... 49 sections, 45 ids, 4 continuation sections, 13 ids with no heading at all (Q41 Q42 Q46 Q47 Q50 Q51 Q52 Q53 Q54 Q55 Q56 Q58 Q62, opened as records nested inside Q37/Q44/Q49/Q45). docs/queue-index.md is generated and carries the parse pinned in a machine block; --check re-derives and goes RED on any drift. selftest 32 cells; verify_index.py (independent parser) 26 assertions.	2026-10-17 12:57:58 +00:00