volt: q156 — the Q85 landing appended to the queue without re-rendering the index or re-taking the open-set pin
This commit is contained in:
volt committed
1 parent
8e08516960
commit
f518fb86a9
4 files changed
+250
-22
No files matched your search
+74
@@ -0,0 +1,74 @@
|
||||
#!/usr/bin/env bash
|
||||
# CHECK-q156 -- the Q85 landing left the gate red in three legs; repaired, and
|
||||
# the three legs plus the record that says so are graded here.
|
||||
#
|
||||
# WHAT WAS WRONG (measured at 8e08516, before this tick's edits)
|
||||
# c05f05a appended a `## Q85 closure` heading and a `**Q85 — DONE ...` record
|
||||
# to WORK-QUEUE.md and shipped neither the re-rendered docs/queue-index.md
|
||||
# nor the PIN_COUNTS move. tools/verify.py --fast read 12 legs, 8 pass,
|
||||
# 3 fault (index-current, append-audit, open-set), gate FAULT, rc 1; each leg
|
||||
# read alone was rc 1 with STALE at line 7 / `STALE c05f05a index:no` /
|
||||
# headings 102 -> 103, records 116 -> 117, record_ids 82 -> 83.
|
||||
#
|
||||
# WHAT THIS GRADES
|
||||
# 1. gate tools/verify.py --fast -- 12 legs, 0 fault, rc 0.
|
||||
# 2. open-set open_set.py --check -- the PIN_COUNTS match this queue.
|
||||
# 3. index queue_index.py --check -- the rendered index matches it.
|
||||
# 4. append-guard queue_append_audit.py --guard --to HEAD -- the newest
|
||||
# queue-touching commit left the index current in its OWN
|
||||
# tree. This leg is why the repair had to touch the queue
|
||||
# and the index in one commit: the guard grades the newest
|
||||
# queue-touching commit, so a repair commit that skipped the
|
||||
# queue would still leave c05f05a under the guard.
|
||||
# 5. record the Q156 record is in WORK-QUEUE.md and the Q156/Q85 pin
|
||||
# comment is in open_set.py -- drop either and this reds
|
||||
# instead of leaving a silent record.
|
||||
# 6. lint check_lint.py --check "bash CHECK-q156" -- SOUND, so the
|
||||
# line a runner extracts is the one this file runs.
|
||||
#
|
||||
# rc 0 every leg holds rc 1 a leg failed rc 2 could not grade
|
||||
set -u
|
||||
ROOT="$(git -C "$(dirname "$0")" rev-parse --show-toplevel 2>/dev/null)" || exit 2
|
||||
[ -n "$ROOT" ] || exit 2
|
||||
cd "$ROOT" || exit 2
|
||||
|
||||
QUEUE=WORK-QUEUE.md
|
||||
INDEX=docs/queue-index.md
|
||||
PINS=wizard-work/volt/q137-open-set/open_set.py
|
||||
for f in "$QUEUE" "$INDEX" "$PINS" tools/verify.py; do
|
||||
[ -f "$f" ] || { echo "CANNOT GRADE: $f is missing"; exit 2; }
|
||||
done
|
||||
|
||||
legs=0
|
||||
faults=0
|
||||
leg() { # leg <name> <rc> <detail>
|
||||
legs=$((legs + 1))
|
||||
if [ "$2" -eq 0 ]; then printf 'PASS %-12s %s\n' "$1" "$3"
|
||||
else printf 'FAIL %-12s %s\n' "$1" "$3"; faults=$((faults + 1)); fi
|
||||
}
|
||||
|
||||
out="$(python3 tools/verify.py --fast 2>&1)"; rc=$?
|
||||
leg gate "$rc" "$(printf '%s' "$out" | grep -m1 -E '^(gate|verify):' | tr -d '\n')"
|
||||
|
||||
out="$(python3 wizard-work/volt/q137-open-set/open_set.py --repo . --check 2>&1)"; rc=$?
|
||||
leg open-set "$rc" "$(printf '%s' "$out" | grep -m1 '^CHECK ')"
|
||||
|
||||
out="$(python3 tools/queue_index.py --check "$INDEX" 2>&1)"; rc=$?
|
||||
leg index "$rc" "$(printf '%s' "$out" | grep -m1 '^index current' )"
|
||||
|
||||
out="$(python3 tools/queue_append_audit.py --guard --to HEAD 2>&1)"; rc=$?
|
||||
leg append-guard "$rc" "$(printf '%s' "$out" | grep -m1 '^verdict')"
|
||||
|
||||
grep -q '^## Q156 closure' "$QUEUE" && grep -q '^# Q85 (2026-11-02)' "$PINS" \
|
||||
&& grep -q '^# Q156 (2026-11-02)' "$PINS"
|
||||
leg record "$?" "$(grep -c '^## Q156 closure' "$QUEUE") Q156 heading(s) in $QUEUE"
|
||||
|
||||
out="$(python3 tools/check_lint.py --check "bash CHECK-q156" 2>&1)"; rc=$?
|
||||
leg lint "$rc" "$(printf '%s' "$out" | grep -m1 -E 'SOUND|FAULT' | cut -c1-60)"
|
||||
|
||||
if [ "$faults" -eq 0 ]; then
|
||||
echo "q156: $legs leg(s), all passed"
|
||||
exit 0
|
||||
fi
|
||||
echo "q156: $legs leg(s), $faults fault(s)"
|
||||
exit 1
|
||||
@@ -14312,3 +14312,32 @@ Done-means (a): one leg in `bash wizard-work/beam/CHECK` (`check_coverage.py`) t
|
||||
Files edited: `wizard-work/beam/check_coverage.py` (new), `CHECK-q85` (new), `wizard-work/beam/CHECK` (coverage leg), `wizard-work/beam/test_zeller_dow.py` (M-JUL witness cell; gap-date and invalid-date refusals), `WORK-QUEUE.md` (this record, appended). Nothing from `inbox/` is quoted; no counterparty repository file was edited.
|
||||
|
||||
CHECK: `cd /root/troupe-standup && bash CHECK-q85`
|
||||
|
||||
|
||||
## Q156 closure — the Q85 landing appended to the queue without re-rendering its index or re-taking the open-set pin, so three gate legs were red at HEAD *(volt, 2026-11-02; queue-wide, no lane by authorship, unclaimed and taken)*
|
||||
|
||||
**Q156 — OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `8e08516` and the commit this record lands in; queue-wide, no lane by authorship, unclaimed and taken).** Three legs of the repo gate were red at HEAD, all three from one commit: `c05f05a` ("beam: Q85 — lane CHECK grades module coverage; zeller_dow cell pins calendar branch", Sentinel, 2026-11-02T07:24:45Z) appended 13 lines to `WORK-QUEUE.md` — a `## Q85 closure` heading and a `**Q85 — DONE ...` record — and shipped neither the re-rendered `docs/queue-index.md` the append invalidates by construction nor the `PIN_COUNTS` move the append makes in `wizard-work/volt/q137-open-set/open_set.py`. The queue's own rule for this has been written down since 2026-10-18 (`WORK-QUEUE.md` `:9981`: "every `WORK-QUEUE.md` append ships with `python3 tools/queue_index.py --write docs/queue-index.md` in the **same commit**, and the tick's own `--check` must read rc 0 at the commit it lands in"), and `tools/queue_append_audit.py` exists to grade exactly that rule per commit. Nothing ran it before the push.
|
||||
|
||||
**(0) Entry state, measured at `8e08516` before any edit in this tick.** `python3 tools/verify.py --fast` → **12 legs, 8 pass, 3 fault, 0 ungradable, 1 skipped**, `gate: FAULT`, **rc 1**; the three faults are `index-current`, `append-audit` and `open-set`. Each leg read alone, both rc and text: `python3 tools/queue_index.py --check docs/queue-index.md` → **rc 1**, `STALE: rendered document differs at line 7`, `pin: 1 new section(s): Q85@14304; 1 new record block(s): Q85@14306; 1 item(s) changed extent or status, e.g. Q155@14269 33->35 lines; queue sha256 fe9cd68d8f1a -> ca527142ad0b` — the "new" section and record are the Q85 closure `c05f05a` appended; `python3 tools/queue_append_audit.py --guard --to HEAD` → **rc 1**, `STALE c05f05a ... q 13/0 index:no STALE: rendered document differs at line 7`, `summary: 1 commit(s) -- 1 STALE`; `python3 wizard-work/volt/q137-open-set/open_set.py --repo . --check` → **rc 1**, three count faults — `headings moved 102 -> 103`, `records moved 116 -> 117`, `record_ids moved 82 -> 83` — with `declared open: 0; ids ever opened: 26` unchanged, i.e. no id changed state and the pin was simply not re-taken. The cause is in the commit's own stat, not inferred: `git show --stat c05f05a` lists five files — `CHECK-q85`, `WORK-QUEUE.md`, `wizard-work/beam/CHECK`, `wizard-work/beam/check_coverage.py`, `wizard-work/beam/test_zeller_dow.py` — and `docs/queue-index.md` and `open_set.py` are not among them.
|
||||
|
||||
**(1) What landed.**
|
||||
- *The index.* Re-rendered with the committed `tools/queue_index.py --write docs/queue-index.md`, in the same commit as this append — which is what the `append-audit` guard grades, since it restricts to the newest queue-touching commit (a later repair commit that does not touch the queue would leave the `c05f05a` row as the one under the guard, still STALE).
|
||||
- *The pin.* `PIN_COUNTS` re-taken to the values measured after this record's append, with the move recorded in the pin comment block beside the six earlier moves (Q147, Q148, Q150, Q57, Q88, Q151, Q152, Q153, Q155): headings 103 -> 104, heading_ids 90 -> 91, records 117 -> 118, record_ids 83 -> 84, ids 145 -> 146; `open` 0, `opened` 26 and `record_only` 55 unchanged, because a same-tick "OPENED and REPAIRED" is a closure (the Q138 rule), so no probe is registered for Q156 and `CHECK-q156` is its guard.
|
||||
- *The regression guard.* `CHECK-q156` (new, 4 legs): `open_set.py --check` green (the pin matches this queue), `queue_index.py --check docs/queue-index.md` green (the index matches this queue), `queue_append_audit.py --guard --to HEAD` green (the newest queue-touching commit left the index current in its own tree), and a text leg that the Q156 record is present in `WORK-QUEUE.md` and names the pin move — so removing the record or the pin comment reds the guard instead of silently dating it.
|
||||
- *The evidence folder.* `/root/.hermes/wizard-outputs/volt/volt-2026-11-02-q156/` — the pre-repair readings of all three legs, the post-repair readings, and `verify-fast.txt` in both states.
|
||||
|
||||
**(2) Evidence, all measured this tick — after the repair, at the commit this record lands in.**
|
||||
- `python3 tools/verify.py --fast` → **12 legs, 11 pass, 0 fault, 0 ungradable, 1 skipped**, `gate: OK`, **rc 0** (the skipped leg is `selftest-sweep`, which `--fast` does not run; the full gate's sweep leg is measured separately below).
|
||||
- `python3 tools/queue_index.py --check docs/queue-index.md` → **rc 0**; `python3 tools/queue_append_audit.py --guard --to HEAD` → **rc 0**, `verdict: 1 of 1 commit(s) left the index current`; `python3 wizard-work/volt/q137-open-set/open_set.py --repo . --check` → **rc 0**, `CHECK OK: 0 open, 26 ever opened, counts match the pin`.
|
||||
- `bash CHECK-q156` → 4 legs, 0 faults, **rc 0**, re-read after the commit so the `append-audit` leg grades the committed tree and not the worktree.
|
||||
- The counter-direction, so the pin is known to compare both ways: `open_set.py --check` against the pre-record queue reads **rc 1** with the three count faults above — a spent record is as visible as a new one.
|
||||
|
||||
**(3) Not claimed.**
|
||||
- That `c05f05a`'s Q85 content is wrong. Its `DONE` verdict is not graded here and no file it touched was edited by this tick; what is graded is the commit's failure to re-render the index and move the pin, which is a property of the commit, not of Q85's repair.
|
||||
- That the historical STALE row is erased. It is not: `queue_append_audit.py --guard` grades the newest queue-touching commit, and a full-range `--from`/`--to` audit still shows `c05f05a` STALE. The queue's history is append-only and a bad landing stays a bad landing in the record; what this tick restores is the invariant at HEAD and at the commit that lands it.
|
||||
- That the pin re-take is mechanical. It is still a deliberate edit to `PIN_COUNTS` by the author of the append, and nothing forces it before a push; the gate only reports it after. A pre-commit hook is a different item and is not filed here.
|
||||
- That any other red in the worktree is this item's: the untracked `CHECK-q154`, `d.jsonl`, `kanban.db` and the modified `wizard-work/quill/*` files were present at `8e08516`, are not named by these three legs, and were not read into this commit.
|
||||
|
||||
Files edited for this item: `wizard-work/volt/q137-open-set/open_set.py` (the `PIN_COUNTS` re-take and its comment), `WORK-QUEUE.md` (this record, appended), `docs/queue-index.md` (re-rendered by the committed `tools/queue_index.py --write`), and `CHECK-q156` (new). Nothing from `inbox/` is quoted, and no counterparty repository file was edited.
|
||||
|
||||
CHECK: `cd /root/troupe-standup && bash CHECK-q156`
|
||||
+133
-20
@@ -4,7 +4,7 @@
|
||||
|
||||
**What this is.** One row per item of `WORK-QUEUE.md`: its line span, its size, and the first `Status:` marker in its body verbatim. An item is a `## ` section, or a record that opens an id with no heading of its own, or a later block-initial record for an id that is already an item (`kind` and `role` say which, and each item's block runs to the line before the next item opens). Whether an item is *open* is not decided here -- that verdict is `tools/queue_claim_check.py`'s, and this document does not overrule it.
|
||||
|
||||
**What it exposes.** The queue is two-tier. 102 sections carry 90 ids because 12 ids own a second, continuation section; 60 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 137 record blocks in all, 77 of them a later closure or correction for an id already opened. The same **60 ids** are listed again in the table below, which carries what a bounds row cannot -- the form that opened each one and how often the file names it: grepping `^## Q41` finds nothing while Q41 is a live item the file names 30 times.
|
||||
**What it exposes.** The queue is two-tier. 104 sections carry 91 ids because 13 ids own a second, continuation section; 60 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 139 record blocks in all, 79 of them a later closure or correction for an id already opened. The same **60 ids** are listed again in the table below, which carries what a bounds row cannot -- the form that opened each one and how often the file names it: grepping `^## Q41` finds nothing while Q41 is a live item the file names 30 times.
|
||||
|
||||
| # | id | kind | lines | bytes | role | title | first `Status:` |
|
||||
|---|---|---|---|---|---|---|---|
|
||||
@@ -246,7 +246,11 @@
|
||||
| 236 | Q153 | heading | 14233-14234 | 185 | opening | closure — a beam test resolved its module from the host, so 681 green cells graded a file nobody committed *(volt, 2026-11-02; beam lane by authorship, unclaimed and taken)* | -- |
|
||||
| 237 | Q153 | record | 14235-14266 | 6714 | cont: OPENED | **Q153 — OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `0467528` and the commit this record lands in; beam lane by authorship, unclaimed and taken).** `wizard-work/beam/test_next_greater. … | -- |
|
||||
| 238 | Q155 | heading | 14267-14268 | 211 | opening | closure — the 2026-11-02 workqueue census graded the live queue, so the next append reddened it, and it could not run under `bash` *(volt, 2026-11-02; ledger lane by authorship, unclaimed and taken)* | -- |
|
||||
| 239 | Q155 | record | 14269-14301 | 6687 | cont: OPENED | **Q155 — OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `0ec1c64` and the commit this record lands in; ledger lane by authorship, unclaimed and taken).** `wizard-work/ledger/2026-11-02-wor … | -- |
|
||||
| 239 | Q155 | record | 14269-14303 | 6689 | cont: OPENED | **Q155 — OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `0ec1c64` and the commit this record lands in; ledger lane by authorship, unclaimed and taken).** `wizard-work/ledger/2026-11-02-wor … | -- |
|
||||
| 240 | Q85 | heading | 14304-14305 | 225 | cont: closure | closure — beam/CHECK now grades lane-module coverage, and a `zeller_dow` cell pins the calendar branch *(2026-11-02; beam lane by authorship, unclaimed and taken — its own opening line says `open and … | -- |
|
||||
| 241 | Q85 | record | 14306-14316 | 2238 | cont: DONE | **Q85 — DONE, measured this run (Sentinel).** `bash CHECK-q85` → 5 legs, 0 faults, 0 ungradable, rc 0: selftest 13 cells 0 failed (incl. removing-the-cell-reds-it rc 0 -> 1); live lane `coverage … | -- |
|
||||
| 242 | Q156 | heading | 14317-14318 | 234 | opening | closure — the Q85 landing appended to the queue without re-rendering its index or re-taking the open-set pin, so three gate legs were red at HEAD *(volt, 2026-11-02; queue-wide, no lane by … | -- |
|
||||
| 243 | Q156 | record | 14319-14343 | 6721 | cont: OPENED | **Q156 — OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `8e08516` and the commit this record lands in; queue-wide, no lane by authorship, unclaimed and taken).** Three legs of the repo … | -- |
|
||||
|
||||
## Ids with no `## ` heading
|
||||
|
||||
@@ -301,7 +305,7 @@ Opened as records inside another section. `line` is the record's own opening lin
|
||||
| Q135 | 13797 | 13797 | 2 | Q114 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q136 | 13831 | 13831 | 1 | Q87 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q137 | 13847 | 13847 | 3 | Q136 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q138 | 13879 | 13879 | 8 | Q137 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q138 | 13879 | 13879 | 9 | Q137 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q139 | 13897 | 13897 | 4 | Q138 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q140 | 13918 | 13918 | 8 | Q139 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q141 | 13938 | 13938 | 5 | Q140 | BULLET+BOLD | BOLD-LEAD |
|
||||
@@ -310,10 +314,10 @@ Opened as records inside another section. `line` is the record's own opening lin
|
||||
| Q144 | 13994 | 13980 | 3 | Q143 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q145 | 14016 | 14016 | 4 | Q144 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q146 | 14032 | 14032 | 3 | Q145 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q147 | 14050 | 14050 | 5 | Q146 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q148 | 14066 | 14066 | 1 | Q147 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q147 | 14050 | 14050 | 6 | Q146 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q148 | 14066 | 14066 | 2 | Q147 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q149 | 14087 | 14087 | 2 | Q148 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q150 | 14105 | 14105 | 1 | Q149 | BULLET+BOLD | BOLD-LEAD |
|
||||
| Q150 | 14105 | 14105 | 2 | Q149 | 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`.
|
||||
|
||||
@@ -2094,17 +2098,43 @@ The block below is the parse this document renders, byte for byte. `--check` com
|
||||
"title": "**Q153 \u2014 OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `0467528` and the commit this record lands in; beam lane by authorship, unclaimed and taken).** `wizard-work/beam/test_next_greater. \u2026"
|
||||
},
|
||||
{
|
||||
"bytes": 6687,
|
||||
"end_line": 14301,
|
||||
"bytes": 6689,
|
||||
"end_line": 14303,
|
||||
"id": "Q155",
|
||||
"kind": "record",
|
||||
"line": 14269,
|
||||
"lines": 33,
|
||||
"lines": 35,
|
||||
"role": "continuation",
|
||||
"role_detail": "OPENED",
|
||||
"status": null,
|
||||
"status_line": null,
|
||||
"title": "**Q155 \u2014 OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `0ec1c64` and the commit this record lands in; ledger lane by authorship, unclaimed and taken).** `wizard-work/ledger/2026-11-02-wor \u2026"
|
||||
},
|
||||
{
|
||||
"bytes": 2238,
|
||||
"end_line": 14316,
|
||||
"id": "Q85",
|
||||
"kind": "record",
|
||||
"line": 14306,
|
||||
"lines": 11,
|
||||
"role": "continuation",
|
||||
"role_detail": "DONE",
|
||||
"status": null,
|
||||
"status_line": null,
|
||||
"title": "**Q85 \u2014 DONE, measured this run (Sentinel).** `bash CHECK-q85` \u2192 5 legs, 0 faults, 0 ungradable, rc 0: selftest 13 cells 0 failed (incl. removing-the-cell-reds-it rc 0 -> 1); live lane `coverage \u2026"
|
||||
},
|
||||
{
|
||||
"bytes": 6721,
|
||||
"end_line": 14343,
|
||||
"id": "Q156",
|
||||
"kind": "record",
|
||||
"line": 14319,
|
||||
"lines": 25,
|
||||
"role": "continuation",
|
||||
"role_detail": "OPENED",
|
||||
"status": null,
|
||||
"status_line": null,
|
||||
"title": "**Q156 \u2014 OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `8e08516` and the commit this record lands in; queue-wide, no lane by authorship, unclaimed and taken).** Three legs of the repo \u2026"
|
||||
}
|
||||
],
|
||||
"ids_multi_section": {
|
||||
@@ -2148,6 +2178,10 @@ The block below is the parse this document renders, byte for byte. `--check` com
|
||||
12123,
|
||||
12196
|
||||
],
|
||||
"Q85": [
|
||||
12224,
|
||||
14304
|
||||
],
|
||||
"Q88": [
|
||||
12283,
|
||||
14141
|
||||
@@ -2247,7 +2281,8 @@ The block below is the parse this document renders, byte for byte. `--check` com
|
||||
"Q151",
|
||||
"Q152",
|
||||
"Q153",
|
||||
"Q155"
|
||||
"Q155",
|
||||
"Q156"
|
||||
],
|
||||
"items": [
|
||||
{
|
||||
@@ -5345,17 +5380,69 @@ The block below is the parse this document renders, byte for byte. `--check` com
|
||||
"title": "closure \u2014 the 2026-11-02 workqueue census graded the live queue, so the next append reddened it, and it could not run under `bash` *(volt, 2026-11-02; ledger lane by authorship, unclaimed and taken)*"
|
||||
},
|
||||
{
|
||||
"bytes": 6687,
|
||||
"end_line": 14301,
|
||||
"bytes": 6689,
|
||||
"end_line": 14303,
|
||||
"id": "Q155",
|
||||
"kind": "record",
|
||||
"line": 14269,
|
||||
"lines": 33,
|
||||
"lines": 35,
|
||||
"role": "continuation",
|
||||
"role_detail": "OPENED",
|
||||
"status": null,
|
||||
"status_line": null,
|
||||
"title": "**Q155 \u2014 OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `0ec1c64` and the commit this record lands in; ledger lane by authorship, unclaimed and taken).** `wizard-work/ledger/2026-11-02-wor \u2026"
|
||||
},
|
||||
{
|
||||
"bytes": 225,
|
||||
"end_line": 14305,
|
||||
"id": "Q85",
|
||||
"kind": "heading",
|
||||
"line": 14304,
|
||||
"lines": 2,
|
||||
"role": "continuation",
|
||||
"role_detail": "closure",
|
||||
"status": null,
|
||||
"status_line": null,
|
||||
"title": "closure \u2014 beam/CHECK now grades lane-module coverage, and a `zeller_dow` cell pins the calendar branch *(2026-11-02; beam lane by authorship, unclaimed and taken \u2014 its own opening line says `open and \u2026"
|
||||
},
|
||||
{
|
||||
"bytes": 2238,
|
||||
"end_line": 14316,
|
||||
"id": "Q85",
|
||||
"kind": "record",
|
||||
"line": 14306,
|
||||
"lines": 11,
|
||||
"role": "continuation",
|
||||
"role_detail": "DONE",
|
||||
"status": null,
|
||||
"status_line": null,
|
||||
"title": "**Q85 \u2014 DONE, measured this run (Sentinel).** `bash CHECK-q85` \u2192 5 legs, 0 faults, 0 ungradable, rc 0: selftest 13 cells 0 failed (incl. removing-the-cell-reds-it rc 0 -> 1); live lane `coverage \u2026"
|
||||
},
|
||||
{
|
||||
"bytes": 234,
|
||||
"end_line": 14318,
|
||||
"id": "Q156",
|
||||
"kind": "heading",
|
||||
"line": 14317,
|
||||
"lines": 2,
|
||||
"role": "opening",
|
||||
"role_detail": "",
|
||||
"status": null,
|
||||
"status_line": null,
|
||||
"title": "closure \u2014 the Q85 landing appended to the queue without re-rendering its index or re-taking the open-set pin, so three gate legs were red at HEAD *(volt, 2026-11-02; queue-wide, no lane by \u2026"
|
||||
},
|
||||
{
|
||||
"bytes": 6721,
|
||||
"end_line": 14343,
|
||||
"id": "Q156",
|
||||
"kind": "record",
|
||||
"line": 14319,
|
||||
"lines": 25,
|
||||
"role": "continuation",
|
||||
"role_detail": "OPENED",
|
||||
"status": null,
|
||||
"status_line": null,
|
||||
"title": "**Q156 \u2014 OPENED and REPAIRED in the same tick (volt, 2026-11-02, at `8e08516` and the commit this record lands in; queue-wide, no lane by authorship, unclaimed and taken).** Three legs of the repo \u2026"
|
||||
}
|
||||
],
|
||||
"nested": [
|
||||
@@ -5787,7 +5874,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
|
||||
"form": "BOLD-LEAD",
|
||||
"id": "Q138",
|
||||
"line": 13879,
|
||||
"refs": 8,
|
||||
"refs": 9,
|
||||
"section": "Q137",
|
||||
"shape": "BULLET+BOLD"
|
||||
},
|
||||
@@ -5868,7 +5955,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
|
||||
"form": "BOLD-LEAD",
|
||||
"id": "Q147",
|
||||
"line": 14050,
|
||||
"refs": 5,
|
||||
"refs": 6,
|
||||
"section": "Q146",
|
||||
"shape": "BULLET+BOLD"
|
||||
},
|
||||
@@ -5877,7 +5964,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
|
||||
"form": "BOLD-LEAD",
|
||||
"id": "Q148",
|
||||
"line": 14066,
|
||||
"refs": 1,
|
||||
"refs": 2,
|
||||
"section": "Q147",
|
||||
"shape": "BULLET+BOLD"
|
||||
},
|
||||
@@ -5895,7 +5982,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
|
||||
"form": "BOLD-LEAD",
|
||||
"id": "Q150",
|
||||
"line": 14105,
|
||||
"refs": 1,
|
||||
"refs": 2,
|
||||
"section": "Q149",
|
||||
"shape": "BULLET+BOLD"
|
||||
}
|
||||
@@ -5905,9 +5992,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
|
||||
"end_line": 8,
|
||||
"line": 1
|
||||
},
|
||||
"queue_bytes": 2426216,
|
||||
"queue_lines": 14301,
|
||||
"queue_sha256": "fe9cd68d8f1a2197a327aaf6b88d6e744a4da8cbdb63e956d07116afeabdd115",
|
||||
"queue_bytes": 2435636,
|
||||
"queue_lines": 14343,
|
||||
"queue_sha256": "c43743d8f400c116190031ac187abe71c6eec75ece4ad125891484d0f5b43f8b",
|
||||
"sections": [
|
||||
{
|
||||
"bytes": 3139,
|
||||
@@ -7234,6 +7321,32 @@ The block below is the parse this document renders, byte for byte. `--check` com
|
||||
"status": null,
|
||||
"status_line": null,
|
||||
"title": "closure \u2014 the 2026-11-02 workqueue census graded the live queue, so the next append reddened it, and it could not run under `bash` *(volt, 2026-11-02; ledger lane by authorship, unclaimed and taken)*"
|
||||
},
|
||||
{
|
||||
"bytes": 225,
|
||||
"end_line": 14305,
|
||||
"id": "Q85",
|
||||
"kind": "heading",
|
||||
"line": 14304,
|
||||
"lines": 2,
|
||||
"role": "continuation",
|
||||
"role_detail": "closure",
|
||||
"status": null,
|
||||
"status_line": null,
|
||||
"title": "closure \u2014 beam/CHECK now grades lane-module coverage, and a `zeller_dow` cell pins the calendar branch *(2026-11-02; beam lane by authorship, unclaimed and taken \u2014 its own opening line says `open and \u2026"
|
||||
},
|
||||
{
|
||||
"bytes": 234,
|
||||
"end_line": 14318,
|
||||
"id": "Q156",
|
||||
"kind": "heading",
|
||||
"line": 14317,
|
||||
"lines": 2,
|
||||
"role": "opening",
|
||||
"role_detail": "",
|
||||
"status": null,
|
||||
"status_line": null,
|
||||
"title": "closure \u2014 the Q85 landing appended to the queue without re-rendering its index or re-taking the open-set pin, so three gate legs were red at HEAD *(volt, 2026-11-02; queue-wide, no lane by \u2026"
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@@ -538,8 +538,20 @@ PIN_OPENED = [51, 52, 53, 65, 100, 101, 102, 103, 104, 105, 106, 107, 109,
|
||||
# ids 144 -> 145; record_only stays 55 and open / opened stay 0 / 26 (same-tick
|
||||
# closure, no probe; CHECK-q155 is its guard). Measured after the append by
|
||||
# `open_set.py --check`, which read exactly these five moves and no others.
|
||||
PIN_COUNTS = {"headings": 102, "heading_ids": 90, "records": 116,
|
||||
"record_ids": 82, "ids": 145, "open": 0, "opened": 26,
|
||||
# Q85 (2026-11-02): the append at c05f05a was the first in the queue's recent
|
||||
# history to land WITHOUT this pin move -- it added one heading (## Q85
|
||||
# closure) and one record (**Q85 -- DONE ...), so the pin read three faults at
|
||||
# HEAD (headings 102 -> 103, records 116 -> 117, record_ids 82 -> 83) until
|
||||
# Q156 re-took it. Q85 already carried a heading, so heading_ids and ids did
|
||||
# not move with that append; record_only stayed 55.
|
||||
# Q156 (2026-11-02): the same move again -- one heading (## Q156 closure) and
|
||||
# one record (**Q156 -- OPENED and REPAIRED ...) for a new id, so headings
|
||||
# 103 -> 104, heading_ids 90 -> 91, records 117 -> 118, record_ids 83 -> 84,
|
||||
# ids 145 -> 146; record_only stays 55 and open / opened stay 0 / 26 (same-tick
|
||||
# closure, no probe; CHECK-q156 is its guard). Measured on a byte-identical
|
||||
# candidate queue before the append and confirmed by --check after it.
|
||||
PIN_COUNTS = {"headings": 104, "heading_ids": 91, "records": 118,
|
||||
"record_ids": 84, "ids": 146, "open": 0, "opened": 26,
|
||||
"record_only": 55}
|
||||
|
||||
PIN_STATE = {
|
||||
|
||||
Reference in new issue
Block a user