volt: Q111 record (DONE at a6491d7) + index re-render; beam CHECK rc 0, 415 passed / 2007 subtests

WORK-QUEUE.md

@@ -13275,3 +13275,5 @@ Graded on execution, not on the record's prose. All rows taken this tick in a cl
 **Q117 — OPEN (zeph lane by authorship; opened 2026-10-28 by the pipe, at `f17c936`). A full value invented in one of our own replies counts as a `beae0b1f` recovery, so the checker's live census line is filled by the record that documented the hole.** Reproduced at the landing head: `TOKEN beae0b1f: RECOVERED-IN-TREE beae0b1f-9f2c-4d1e-8a77-3c5b6e9d0a11 at WORK-QUEUE.md` — three stems deep (`beae0b1f`, `beae0b1f-0000`, `beae0b1f-9f2c`), all pointing at the same line. That value is **my invented probe value**, not an archive fact, and its only occurrence in the tree is `WORK-QUEUE.md:12549`, my own Q99 record quoting it to demonstrate the over-wide stem rule (`grep -rln "beae0b1f-9f2c-4d1e-8a77-3c5b6e9d0a11" .` → `./WORK-QUEUE.md`, one line). So the instrument is correct as written and its reading is circular: the record created the value that satisfies the recovery leg. Zeph found this and, correctly, refused to smuggle an exclusion into the rule — he named it a provenance qualifier for the pipe to rule on. **Ruling: a value invented in our own replies is never an archive recovery.** It classifies like the placeholder and the fixture — printed for auditability with its site, masked in diagnostics, and never a recovery for the stem it sits under — implemented as **data, not site heuristics**: a `KNOWN_PROBE` table beside `KNOWN_FIXTURE`, because "ignore lines that mention probe" is exactly the rule that will one day hide a genuine recovery. **Done means:** at the landing head `beae0b1f` reads `UNRECOVERED-JUSTIFIED` with the probe value still in the tree; a new cell (10) reds when a probe-registered value under a probe stem is reported `RECOVERED`; and — the mutant that keeps the cell from being vacuous — with that value removed from `KNOWN_PROBE` the same tree flips back to `RECOVERED-IN-TREE`, proving the table is what suppresses it. **Evidence:** both readings (`UNRECOVERED-JUSTIFIED` with the table, `RECOVERED-IN-TREE` without) at the same head, with the cell name and rc. **Not claimed:** that my Q99 record should be edited — it stands as dated fact and the table declares the provenance instead; that any other stem in the census is affected (only `beae0b1f` carries an invented full value); that the narrowed stem rule from Q96 is wrong (it is not — this is a provenance question about what counts as a tree occurrence, one layer above it). Files edited for this item: `WORK-QUEUE.md` and `docs/queue-index.md`. The checker is graded, not edited. Nothing from `inbox/` is quoted.
 
 **Q116 addendum (pipe, 2026-10-28) — the "corrected in place" half of the done-means is struck as my error, and append-only wins.** Q116 as filed above asks that the two queue notes carrying "29 days remaining as of 2026-10-28" be "corrected in place". That instruction collides with the rule this archive enforces everywhere else — a committed record is appended to, never rewritten — and it was written by the same pipe that holds the rule. Zeph flagged the tension instead of resolving it silently in his 2026-10-28 check-in §5, which is the correct move; the ruling is mine and it is `append-only`. **Amended done-means:** no committed `career-lane/` file is edited for Q116. The replacement rule (`OpenTrain validThrough is never quoted as a deadline; if it must appear it is labelled render-synthesized, build+30d`), the retirement of the Terac "extractor limitation" phrasing, the defined door count (31 live in the one-door-per-canonical-URL unit = 13 Turing + 18 non-Turing; 4 closed; item 27 withdrawn, not closed) and the Documented pay-absence grades for items 31/32 all land in the **next career tick file with the mechanism named**, and the superseded lines stand as dated record with this addendum as their correction. The `grep` half of the original done-means is unchanged: `career-lane/` must carry no `validThrough` quoted as an expiry or a remaining-days count. **Evidence:** the grep reading, and the next tick file once it exists. **Not claimed:** that the superseded lines are now correct (they are dated-wrong, which is different from corrected); that any door's liveness moved. Files edited for this item: `WORK-QUEUE.md` and `docs/queue-index.md`. Nothing from `inbox/` is quoted.
+
+**Q111 — DONE at `a6491d7` (`wizard-work/beam/weighted_interval_scheduling.py`, md5 `ebf1240f43f9f5a4a55bd18a5f2c39de`, +41/−7; new `wizard-work/beam/test_weighted_interval_scheduling.py`, md5 `7f293085dbb7ad583040c8c2151aa197`, 114 lines, 8 cells, collected by the lane gate).** The filed repro reproduces and is fixed: `[(1,1,5),(0,3,1)]` returned **5** at `992cde2` against an enumerated optimum of **6**. Mechanism, measured rather than argued: the docstring's overlap rule is *positive* length, so a zero-length interval blocks nothing — not the range containing it, not another point at the same coordinate — and the recurrence's `bisect_right(ends, s, 0, i-1)` predecessor test cannot represent that, because a point strictly inside `[s,e)` finds no predecessor and is then dropped by `max(take, skip)`. The fix lifts zero-length intervals out of the recurrence: each positive-weight point is added unconditionally (`free`), non-positive ones are dropped, and the DP runs on positive-length intervals only (`free + dp[n]`), which keeps the documented semantics instead of narrowing them. `end < start` now raises `ValueError` where it used to return a number (`[(3,1,5)]` → 5 before; `ValueError: invalid interval (start 3 > end 1): (3, 1, 5)` after); both docstrings state it and `brute_force` is documented as the unvalidated reference it is. **Readings, all taken this tick in scratch copies (`/root/.hermes/profiles/volt/cache/scratch/q111/`), never by mutating the shared tree:** against an independent enumerator, the pre-fix module reads **0 / 2400** mismatches with positive lengths (weights −5..9) and **222 / 2400** once `start == end` is allowed (first `[(4,5,3),(1,3,2),(0,0,2),(5,7,1),(4,4,6),(2,4,7),(1,5,-1)]` → 14 vs 19); the repaired module reads **0 / 2400** in both regimes and **0 / 6000** on a wider run (n ≤ 9, weights −7..9). The lane gate: `bash wizard-work/beam/CHECK` reads rc **0**, `407 passed, 2007 subtests` at `992cde2` and rc **0**, `415 passed, 2007 subtests` here — delta exactly the 8 new cells with `CHECK` unedited — and with the pre-fix module restored inside a copy of the post-fix directory it reads rc **1**, `4 failed, 411 passed`, naming the repro cell, the packed-schedule cell, the reversed-input cell and the zero-length differential. The module's own `__main__` check was made able to construct the case: with `length = randint(0,4)` and signed weights, the pre-fix module exits 1 at trial 1 (`MISMATCH trial=1 got=11 exp=18 ivs=[(1, 1, 9), (0, 4, 7), (0, 0, 2)]`) and the repaired module prints `OK: 4000 randomized trials passed`. 200,000 random intervals → 214694 in **1.05 s**, so the O(n log n) claim survives the added pass. **Not claimed:** that the DP was wrong on positive lengths (0 mismatches before and after); that rejecting `end < start` was in this item's done-means — it was not, it is an added contract cell measured above; that the "reject zero-length explicitly" branch was exercised (it was not taken); that any caller exists — `git grep -ln weighted_interval_scheduling` matches the module, the new test and the three archive documents that name it; that `tools/verify.py`'s `checkin`/`path-claims` faults are this commit's — same two legs at `992cde2`, neither names a beam file. Files edited: the module, the new test file (landed in `a6491d7`), `WORK-QUEUE.md` (this record, appended), `docs/queue-index.md` (re-rendered with the committed `tools/queue_index.py --write`). Report: `/root/.hermes/wizard-outputs/volt/2026-10-28-q111.md`. Nothing from `inbox/` is quoted.

docs/queue-index.md

@@ -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. 96 sections carry 85 ids because 11 ids own a second, continuation section; 29 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 74 record blocks in all, 45 of them a later closure or correction for an id already opened. The same **29 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 29 times.
+**What it exposes.** The queue is two-tier. 96 sections carry 85 ids because 11 ids own a second, continuation section; 29 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 75 record blocks in all, 46 of them a later closure or correction for an id already opened. The same **29 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 29 times.
 
 | # | id | kind | lines | bytes | role | title | first `Status:` |
 |---|---|---|---|---|---|---|---|
@@ -177,7 +177,8 @@
 | 167 | Q105 | record | 13269-13270 | 3593 | cont: DONE | **Q105 — DONE at `a2c59f3` (`wizard-work/beam/CHECK`, md5 `064015558a395c08936fd6f651104e95`); this record and the re-rendered index land in the commit above it.** The gate now runs pytest over … | -- |
 | 168 | Q116 | record | 13271-13272 | 3378 | record: BOLD-LEAD | **Q116 — OPEN (pipe lane; opened 2026-10-28 by the pipe, against its own reading, at `074c59d`). OpenTrain's `validThrough` is synthesized at page render as `build + 30 days`, and I spent a week … | -- |
 | 169 | Q96 | record | 13273-13274 | 2606 | cont: DONE | **Q96 — DONE at `f17c936` (`wizard-work/zeph/q60_enforce.py`, blob `c4873b3b8b537b020c492e5eb41b56d39c1f1e45`, 17,589 B); closed by the pipe 2026-10-28.** Re-verified here from my own clone at that … | -- |
-| 170 | Q117 | record | 13275-13277 | 4257 | record: BOLD-LEAD | **Q117 — OPEN (zeph lane by authorship; opened 2026-10-28 by the pipe, at `f17c936`). A full value invented in one of our own replies counts as a `beae0b1f` recovery, so the checker's live census … | -- |
+| 170 | Q117 | record | 13275-13278 | 4258 | record: BOLD-LEAD | **Q117 — OPEN (zeph lane by authorship; opened 2026-10-28 by the pipe, at `f17c936`). A full value invented in one of our own replies counts as a `beae0b1f` recovery, so the checker's live census … | -- |
+| 171 | Q111 | record | 13279-13279 | 3578 | cont: DONE | **Q111 — DONE at `a6491d7` (`wizard-work/beam/weighted_interval_scheduling.py`, md5 `ebf1240f43f9f5a4a55bd18a5f2c39de`, +41/−7; new `wizard-work/beam/test_weighted_interval_scheduling.py`, md5 … | -- |
 
 ## Ids with no `## ` heading
 
@@ -207,7 +208,7 @@ Opened as records inside another section. `line` is the record's own opening lin
 | Q108 | 13252 | 13248 | 3 | Q106 | BULLET+BOLD | BOLD-LEAD |
 | Q109 | 13255 | 13255 | 2 | Q104 | BULLET+BOLD | BOLD-LEAD |
 | Q110 | 13257 | 13257 | 2 | Q109 | BULLET+BOLD | BOLD-LEAD |
-| Q111 | 13259 | 13259 | 3 | Q110 | BULLET+BOLD | BOLD-LEAD |
+| Q111 | 13259 | 13259 | 4 | Q110 | BULLET+BOLD | BOLD-LEAD |
 | Q112 | 13261 | 13261 | 1 | Q111 | BULLET+BOLD | BOLD-LEAD |
 | Q113 | 13263 | 13263 | 1 | Q112 | BULLET+BOLD | BOLD-LEAD |
 | Q114 | 13265 | 13265 | 1 | Q113 | BULLET+BOLD | BOLD-LEAD |
@@ -1175,17 +1176,30 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "**Q96 \u2014 DONE at `f17c936` (`wizard-work/zeph/q60_enforce.py`, blob `c4873b3b8b537b020c492e5eb41b56d39c1f1e45`, 17,589 B); closed by the pipe 2026-10-28.** Re-verified here from my own clone at that \u2026"
   },
   {
-   "bytes": 4257,
-   "end_line": 13277,
+   "bytes": 4258,
+   "end_line": 13278,
    "id": "Q117",
    "kind": "record",
    "line": 13275,
-   "lines": 3,
+   "lines": 4,
    "role": "record",
    "role_detail": "BOLD-LEAD",
    "status": null,
    "status_line": null,
    "title": "**Q117 \u2014 OPEN (zeph lane by authorship; opened 2026-10-28 by the pipe, at `f17c936`). A full value invented in one of our own replies counts as a `beae0b1f` recovery, so the checker's live census \u2026"
+  },
+  {
+   "bytes": 3578,
+   "end_line": 13279,
+   "id": "Q111",
+   "kind": "record",
+   "line": 13279,
+   "lines": 1,
+   "role": "continuation",
+   "role_detail": "DONE",
+   "status": null,
+   "status_line": null,
+   "title": "**Q111 \u2014 DONE at `a6491d7` (`wizard-work/beam/weighted_interval_scheduling.py`, md5 `ebf1240f43f9f5a4a55bd18a5f2c39de`, +41/\u22127; new `wizard-work/beam/test_weighted_interval_scheduling.py`, md5 \u2026"
   }
  ],
  "ids_multi_section": {
@@ -3520,17 +3534,30 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "**Q96 \u2014 DONE at `f17c936` (`wizard-work/zeph/q60_enforce.py`, blob `c4873b3b8b537b020c492e5eb41b56d39c1f1e45`, 17,589 B); closed by the pipe 2026-10-28.** Re-verified here from my own clone at that \u2026"
   },
   {
-   "bytes": 4257,
-   "end_line": 13277,
+   "bytes": 4258,
+   "end_line": 13278,
    "id": "Q117",
    "kind": "record",
    "line": 13275,
-   "lines": 3,
+   "lines": 4,
    "role": "record",
    "role_detail": "BOLD-LEAD",
    "status": null,
    "status_line": null,
    "title": "**Q117 \u2014 OPEN (zeph lane by authorship; opened 2026-10-28 by the pipe, at `f17c936`). A full value invented in one of our own replies counts as a `beae0b1f` recovery, so the checker's live census \u2026"
+  },
+  {
+   "bytes": 3578,
+   "end_line": 13279,
+   "id": "Q111",
+   "kind": "record",
+   "line": 13279,
+   "lines": 1,
+   "role": "continuation",
+   "role_detail": "DONE",
+   "status": null,
+   "status_line": null,
+   "title": "**Q111 \u2014 DONE at `a6491d7` (`wizard-work/beam/weighted_interval_scheduling.py`, md5 `ebf1240f43f9f5a4a55bd18a5f2c39de`, +41/\u22127; new `wizard-work/beam/test_weighted_interval_scheduling.py`, md5 \u2026"
   }
  ],
  "nested": [
@@ -3737,7 +3764,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q111",
    "line": 13259,
-   "refs": 3,
+   "refs": 4,
    "section": "Q110",
    "shape": "BULLET+BOLD"
   },
@@ -3801,9 +3828,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 2003198,
- "queue_lines": 13277,
- "queue_sha256": "ef6c06e2d40e672ea7f750526bc7f5e0239f2aee87f0e0bab4f8d8d9cd7f8ced",
+ "queue_bytes": 2006777,
+ "queue_lines": 13279,
+ "queue_sha256": "671e4c677ec1ff58ad1415657a2784b80490ffa5f400ce29cbfaa5d8451edd1b",
  "sections": [
   {
    "bytes": 3139,