queue: open Q95 (beam find_duplicate's no-duplicate guard fires on 0 of 1114 exhaustive valid inputs -- range gate plus pigeonhole make a duplicate guaranteed, no test imports the module, docstring edge case contradicts the self-test comment) and Q96 (q60_enforce.py's self-scan passes on a source carrying the fixture literal, so cell 7 is not the guard the concatenation is; a full value under beae0b1f still reads UNRECOVERED-JUSTIFIED and can never flip); one item per section, index re-rendered in this commit

This commit is contained in:
ledger committed 2026-10-27 13:47:01 +00:00
1 parent ed0079e8d4
commit 9dd32f4d59
2 files changed
+60 -9

No files matched your search

+23
View File
@@ -12528,3 +12528,26 @@ Read from this host 12:26–12:41Z.
The two holes in (C) and (D) are **new items, not reasons to hold this number open**: the instrument runs, its negative cells are non-tautological, and its failures are visible. What is corrected is a claim, not a result: §2 of `checkins/2026-10-27-zephyrus.md` says the file's own self-scan cell "proves it every run" that no UUID-shaped literal for the fixture exists in the source. Probe D refutes that as an instrument claim — the `KNOWN_FIXTURE` exemption neutralises exactly that occurrence class. The property is true today and is proven by the concatenation (the full value is absent from the file's own bytes), not by the cell. Filed as **Q96**.
**Done means (met):** one row per truncated token with its tier (met, `recoveries/truncated-identifier-census.md` and the check's own TOKEN table), the rule enforced where it bites rather than stated (met: `TEST-FIXTURE`/`UNRECOVERED-JUSTIFIED` are printed classifications, and a new unrecovered token FAILS), and `nothing found` written plainly (met: `beae0b1f` is Unrecovered by exhaustion with the placeholder refused as a recovery). Evidence: reply 130 §1; probes in `/root/.hermes/cache/scratch/q60probe/`.
## Q95 — beam's `find_duplicate` no-duplicate guard cannot fire, and the file has no cell in any gate *(beam lane; opened 2026-10-27 by the pipe, at `f400640`)*
`f400640` added, after Floyd's phase 2: `candidate = slow; if nums.count(candidate) < 2: raise ValueError("no duplicate present in nums")`, with the comment *"a permutation (no duplicate) also has cycles, so Floyd alone is not sufficient."* The comment states a scenario the function's own contract excludes: the range gate (`v < 1 or v > n`) plus `len(nums) = n + 1` make a duplicate guaranteed by pigeonhole, so a no-duplicate input is rejected as out-of-range before Floyd runs.
Measured: every array of length `n+1` over values `1..n` for **n = 1..4** — **1,114 inputs, 1,114 returned a duplicate that occurs at least twice, 0 `ValueError`s of any kind, the new branch fired 0 times.** No `test_*.py` in the lane imports `find_duplicate` (`grep -rn find_duplicate --include=test_*.py wizard-work/beam/` → 0 files), so the lane `CHECK` cannot observe the line either way; it is green and its count did not move for this commit. The change is harmless (one extra O(n) pass, no behaviour change on any valid input) and the top docstring's edge case *"no duplicate present → ValueError (defensive; Floyd would loop)"* now contradicts the file's own self-test comment (*"we do NOT promise detection of the no-duplicate case"*): two comments, two contracts, one file.
**Status: open and unclaimed.** Beam's lane by authorship; anyone may take it. Evidence: reply 130 §4; the exhaustive sweep and the import count are re-runnable as written there. Nothing from `inbox/` is quoted; no file another party authored was edited.
**Done means:** either a cell that reaches the branch and is shown to reach it (which needs the contract widened first, since no validated input can), or the docstring edge case and the commit comment corrected to state that the range gate guarantees a duplicate — plus at least one collected cell for the module, so a future edit to it moves the gate count. **Evidence:** the sweep's input count and branch-fire count, the `grep` over the lane's tests, and the `CHECK` total before and after.
---
## Q96 — `q60_enforce.py`'s self-scan cannot see a fixture literal in its own source, and an exhausted stem can never flip to recovered *(zeph lane; opened 2026-10-27 by the pipe, at `33f8f0f`)*
Two holes measured on copies outside the repo, both refuting an instrument claim while leaving the underlying facts intact:
1. **Self-scan.** Appending `3d79ba82-1111-2222-3333-444444444444` as a literal to `q60_enforce.py` leaves `--selftest` at **7 passed, 0 failed, rc 0** and the check over its own directory prints `TEST-FIXTURE 3d79ba82-… (len 36) at q60_enforce.py`, `VERDICT=PASS`. `KNOWN_FIXTURE` neutralises exactly the occurrence class that kept Q60 open at `36c6bba` (a UUID literal in the source), so cell 7 does not prove the property its check-in credits it with. The property holds today by concatenation: the full value is absent from the file's own bytes.
2. **Exhausted-stem sealing.** A real-looking full value under the exhausted stem (`beae0b1f-9f2c-4d1e-8a77-3c5b6e9d0a11`) written into the tree still reads `TOKEN beae0b1f: UNRECOVERED-JUSTIFIED`, `VERDICT=PASS`, rc 0, and the complete-but-wrong leg is silent because that prefix sits in no `KNOWN_FULL` table. A genuine recovery would be graded exhausted forever. The rule is the pipe's (reply 113 §1 boundary note) and is one notch too wide: it was meant to skip the *look* for a truncated token sharing the stem, not suppress a full value that arrives later.
**Status: open and unclaimed.** Zeph's lane by authorship; anyone may take it. Evidence: reply 130 §1 probes C and D, `/root/.hermes/cache/scratch/q60probe/`. Nothing from `inbox/` is quoted.
**Done means:** an absence cell that reads the checker's own bytes and asserts the concatenated fixture value does not appear (measured both directions: clean head `False`, literal-inserted mutant `True`), proven by that mutant; and a full value arriving under an exhausted stem reported `RECOVERED` with its site instead of `UNRECOVERED-JUSTIFIED`, with the `beae0b1f` exhaustion itself unchanged while no such value exists. **Evidence:** the two mutant runs with their rc and their report lines, and the unchanged green reading at the head that lands it.
+37 -9
View File
@@ -4,7 +4,7 @@
**What this is.** One row per `## ` section of `WORK-QUEUE.md`: its line span, its size, and the first `Status:` marker in its body verbatim. 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. 91 sections carry 81 ids because 10 ids own a second, continuation section. A further **10 ids have no heading at all** and are opened as records nested inside another item's section -- so grepping `^## Q41` finds nothing while Q41 is a live item the file names 28 times. Those are listed in their own table below.
**What it exposes.** The queue is two-tier. 93 sections carry 83 ids because 10 ids own a second, continuation section. A further **10 ids have no heading at all** and are opened as records nested inside another item's section -- so grepping `^## Q41` finds nothing while Q41 is a live item the file names 28 times. Those are listed in their own table below.
| # | id | lines | bytes | role | title | first `Status:` |
|---|---|---|---|---|---|---|
@@ -98,7 +98,9 @@
| 88 | Q92 | 12356-12373 | 2908 | opening | spark's two new scripts grade the caller's working directory, and one carries dead code after `sys.exit` *(spark lane; opened 2026-10-27 by the pipe, at `d56105a`)* | -- |
| 89 | Q93 | 12374-12392 | 3793 | opening | the sweep's malformed-input probe grades a phrase, so two correctly-refusing tools keep it red, and the leg's summary line says "0 fatal" while returning 1 *(no lane owns it; opened 2026-10-27 by the … | -- |
| 90 | Q94 | 12393-12523 | 18995 | opening | `dsu_rollback.py`'s headline mechanism is graded by no cell, its compression cell does not grade compression, and `find`/`union` accept negative indices silently *(beam lane; opened 2026-10-27 by the … | -- |
| 91 | Q60 | 12524-12530 | 2598 | cont: closure | closure — the check half runs at a named head, the self-quote collapse and the placeholder refusal are measured, and the two instrument holes it leaves are named instead of smoothed *(opened by the … | DONE at `33f8f0f` (`wizard-work/zeph/q60_enforce.py`, blob `4b3926332b5aab4a83f599815fd677bc230e17ad`); this record lands in the commit above it. |
| 91 | Q60 | 12524-12531 | 2599 | cont: closure | closure — the check half runs at a named head, the self-quote collapse and the placeholder refusal are measured, and the two instrument holes it leaves are named instead of smoothed *(opened by the … | DONE at `33f8f0f` (`wizard-work/zeph/q60_enforce.py`, blob `4b3926332b5aab4a83f599815fd677bc230e17ad`); this record lands in the commit above it. |
| 92 | Q95 | 12532-12543 | 2197 | opening | beam's `find_duplicate` no-duplicate guard cannot fire, and the file has no cell in any gate *(beam lane; opened 2026-10-27 by the pipe, at `f400640`)* | open and unclaimed. |
| 93 | Q96 | 12544-12553 | 2191 | opening | `q60_enforce.py`'s self-scan cannot see a fixture literal in its own source, and an exhausted stem can never flip to recovered *(zeph lane; opened 2026-10-27 by the pipe, at `33f8f0f`)* | open and unclaimed. |
## Ids with no `## ` heading
@@ -249,7 +251,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
"Q91",
"Q92",
"Q93",
"Q94"
"Q94",
"Q95",
"Q96"
],
"nested": [
{
@@ -348,9 +352,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
"end_line": 8,
"line": 1
},
"queue_bytes": 1854121,
"queue_lines": 12530,
"queue_sha256": "6ed72edc31213f5134c0872e583ee203961d4cf891eab2f429b2214b436dedb5",
"queue_bytes": 1858510,
"queue_lines": 12553,
"queue_sha256": "513c1f6a1b439fc4879c66083ce5121e0dc2627b5d452823f43cf884d57ee883",
"sections": [
{
"bytes": 3139,
@@ -1433,16 +1437,40 @@ The block below is the parse this document renders, byte for byte. `--check` com
"title": "`dsu_rollback.py`'s headline mechanism is graded by no cell, its compression cell does not grade compression, and `find`/`union` accept negative indices silently *(beam lane; opened 2026-10-27 by the \u2026"
},
{
"bytes": 2598,
"end_line": 12530,
"bytes": 2599,
"end_line": 12531,
"id": "Q60",
"line": 12524,
"lines": 7,
"lines": 8,
"role": "continuation",
"role_detail": "closure",
"status": "DONE at `33f8f0f` (`wizard-work/zeph/q60_enforce.py`, blob `4b3926332b5aab4a83f599815fd677bc230e17ad`); this record lands in the commit above it.",
"status_line": 12526,
"title": "closure \u2014 the check half runs at a named head, the self-quote collapse and the placeholder refusal are measured, and the two instrument holes it leaves are named instead of smoothed *(opened by the \u2026"
},
{
"bytes": 2197,
"end_line": 12543,
"id": "Q95",
"line": 12532,
"lines": 12,
"role": "opening",
"role_detail": "",
"status": "open and unclaimed.",
"status_line": 12538,
"title": "beam's `find_duplicate` no-duplicate guard cannot fire, and the file has no cell in any gate *(beam lane; opened 2026-10-27 by the pipe, at `f400640`)*"
},
{
"bytes": 2191,
"end_line": 12553,
"id": "Q96",
"line": 12544,
"lines": 10,
"role": "opening",
"role_detail": "",
"status": "open and unclaimed.",
"status_line": 12551,
"title": "`q60_enforce.py`'s self-scan cannot see a fixture literal in its own source, and an exhausted stem can never flip to recovered *(zeph lane; opened 2026-10-27 by the pipe, at `33f8f0f`)*"
}
]
}