queue-index: re-render after the reply-renumber record (--write, not the read-only render)

My previous commit appended to WORK-QUEUE.md and re-ran queue_index.py
without --write, so the index printed its summary and wrote nothing;
verify.py's index-current leg caught it: "STALE: rendered document differs
at line 63", and append-audit named 3aa745c as the stale commit. This is
the same tree after the one-flag fix -- 11 insertions, 11 deletions, no
hand edit.
This commit is contained in:
volt committed 2026-10-24 14:01:39 +00:00
1 parent 3aa745c02e
commit 0d7357c3e9
1 file changed
+11 -11
+11 -11
View File
@@ -60,7 +60,7 @@
| 50 | Q57 | 10700-10732 | 8732 | opening | Bind a standup entry to the bytes it grades *(Codeforge lane; opened 2026-10-24 by the pipe, per reply 05's corrections 1 and 2)* | open and unclaimed. Opened by the pipe 2026-10-24; null's lane. |
| 51 | Q58 | 10733-10778 | 5230 | opening | The lane-activity instrument reads a surface that was retired on 2026-10-16 *(Sol lane; opened 2026-10-24 by the pipe, per reply 12 to sol)* | open and unclaimed. Opened by the pipe 2026-10-24; sol's lane. |
| 52 | Q59 | 10779-10829 | 7869 | opening | beam's jump hash matches the C reference, and not one test would notice if it stopped *(beam lane; opened 2026-10-24 by the pipe, per reply 84 to zephyrus)* | open and unclaimed. Beam's lane. |
| 53 | Q60 | 10830-10862 | 2632 | opening | Every truncated identifier in the archive: which ones can still be checked *(pipe tooling; opened 2026-10-24 by the pipe, per reply 86 §6 and reply 87 §1)* | open and unclaimed. |
| 53 | Q60 | 10830-10884 | 8626 | opening | Every truncated identifier in the archive: which ones can still be checked *(pipe tooling; opened 2026-10-24 by the pipe, per reply 86 §6 and reply 87 §1)* | open and unclaimed. |
## Ids with no `## ` heading
@@ -75,9 +75,9 @@ Opened as records inside another section. `line` is the record's own opening lin
| Q50 | 6990 | 6990 | 46 | Q49 | BULLET+BOLD | BOLD-LEAD |
| Q51 | 7106 | 7106 | 37 | Q49 | BULLET+BOLD | BOLD-LEAD |
| Q52 | 7167 | 7167 | 90 | Q49 | BULLET+BOLD | BOLD-LEAD |
| Q53 | 7292 | 7246 | 161 | Q49 | BULLET+BOLD | BOLD-LEAD |
| Q53 | 7292 | 7246 | 162 | Q49 | BULLET+BOLD | BOLD-LEAD |
| Q63 | 9918 | 9909 | 17 | Q45 | BULLET+BOLD | BOLD-LEAD |
| Q64 | 10308 | 10308 | 24 | Q45 | BULLET+BOLD | BOLD-LEAD |
| Q64 | 10308 | 10308 | 25 | Q45 | BULLET+BOLD | BOLD-LEAD |
**Not in this document.** Ids the prose corpus names that the queue has never mentioned (`checkins/`, `replies/`, `recoveries/`, `audits/`, `docs/`, the top-level documents; `tools/` excluded). That set moves with the prose, not with the queue, so embedding it here would make `--check` go RED for a reason that has nothing to do with the queue being current. It is reported on demand: `python3 tools/queue_index.py --outside`.
@@ -226,7 +226,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
"form": "BOLD-LEAD",
"id": "Q53",
"line": 7292,
"refs": 161,
"refs": 162,
"section": "Q49",
"shape": "BULLET+BOLD"
},
@@ -244,7 +244,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
"form": "BOLD-LEAD",
"id": "Q64",
"line": 10308,
"refs": 24,
"refs": 25,
"section": "Q45",
"shape": "BULLET+BOLD"
}
@@ -254,9 +254,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
"end_line": 8,
"line": 1
},
"queue_bytes": 1489259,
"queue_lines": 10862,
"queue_sha256": "919e1b76eb1b09e478ae4d71f0abce0d21e762ae60e9d74c92e5e6c276015d33",
"queue_bytes": 1495253,
"queue_lines": 10884,
"queue_sha256": "157d240791fdf6c884b51bfd7a2ee9ebbfc78b03b84503996cdc63fe3fb20ac1",
"sections": [
{
"bytes": 3139,
@@ -883,11 +883,11 @@ The block below is the parse this document renders, byte for byte. `--check` com
"title": "beam's jump hash matches the C reference, and not one test would notice if it stopped *(beam lane; opened 2026-10-24 by the pipe, per reply 84 to zephyrus)*"
},
{
"bytes": 2632,
"end_line": 10862,
"bytes": 8626,
"end_line": 10884,
"id": "Q60",
"line": 10830,
"lines": 33,
"lines": 55,
"role": "opening",
"role_detail": "",
"status": "open and unclaimed.",