From 99f95b5b7ae011fcbb4c98d08b2b18dd946a6427 Mon Sep 17 00:00:00 2001 From: timmy Date: Wed, 28 Oct 2026 12:32:50 +0000 Subject: [PATCH] pipe: Q116 -- OpenTrain validThrough is build+30d, not an expiry (item 25 read on three dates: datePosted byte-identical, validThrough exactly 30 days after each page render to the millisecond; items 25 and 32 share one stamp; third page differs with its own build) and my rule (b) is withdrawn; index re-rendered. verify.py 6/8 pass, 2 faults (checkin, path-claims) both pre-existing at 074c59d in a clean worktree, not introduced here --- WORK-QUEUE.md | 1 + docs/queue-index.md | 45 +++++++++++++++++++++++++++++++++++++++++---- 2 files changed, 42 insertions(+), 4 deletions(-) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 34291ba..cc063cd 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -13268,3 +13268,4 @@ Graded on execution, not on the record's prose. All rows taken this tick in a cl **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 `test_*.py` and maps pytest's exit codes onto the repo contract (0→0, failures→1, collection error→1 since a module that will not import is a fault, no tests collected→1, pytest absent→**2** with the reason printed). Measured at the baseline `e49a784` (CHECK md5 `48cc529aef041dc025df7f0ab1a8ac0a`, unchanged since `26cdf8b`): `python3 -m unittest discover -p 'test_*.py'` → `Ran 276 tests … OK`; `python3 -m pytest -q test_*.py` → `407 passed, 2007 subtests passed`; difference **131**, the count this item named, and 276+131 = 407 exactly, so the invisible set is the whole gap. Per-file discovery over the 57 test files: **20** contribute 0 unittest tests and all 131 pytest tests; **7** more (`test_count_min_sketch`, `test_csv`, `test_robin_hood_hash`, `test_safe_eval`, `test_scc`, `test_scc_tarjan`, `test_topo`) contribute 0 to both runners and are module-level `assert` scripts whose asserts execute at collection. Done-condition measured on copies outside the repo (`~/.hermes/profiles/volt/cache/scratch/q105run1`, `q105run2`; the repo tree was never mutated): with `test_fenwick.py:12` changed `assert ft.prefix(5) == 15` → `== 16`, the old CHECK printed `PASS det / ALL` **rc 0** while the new one prints `FAILED test_fenwick.py::test_basic_update_prefix - assert 15 == 16`, `1 failed, 406 passed`, **rc 1** (independent reading on the mutant: `pytest -q test_fenwick.py` → `1 failed, 7 passed`); clean tree → **rc 0**, `407 passed`; `assert False` injected into `test_topo.py` (a 0-test script file) → **rc 1** through the collection-error branch; `python3 -m pytest --version` shimmed to fail on PATH → **rc 2**, `pytest not importable -- cannot grade` plus the 276/407 line, so a host without pytest cannot read this gate as green; invoked from `/` against a copy → rc 0, so the gate resolves its own directory (`readlink -f "$0"`, not a pinned `/root` path — Q106's class was checked for). `--import-mode=importlib` is required, not cosmetic: two files share the basename `test_toposort.py` (top level and `toposort/`) and default `prepend` mode aborts with `import file mismatch` — measured `1 error during collection`, rc 2, before the flag. **The pinned count changes:** the old `ALL PASS (242 checks)` line is superseded by 407 pytest tests + 2007 subtests, then the 8 `PASS` lines and `ALL` from `toposort/test_toposort.py`; the top-level file's 242 import-time assertions still execute during collection. **Not claimed:** that any of the 131 tests was wrong or failing — they passed before and after, the defect was that nothing ran them; that pytest is installed on every host that runs this lane (it is 9.1.1 here, and absence is now rc 2 rather than a green); that this closes Q111, Q104 or any other beam item — Q111 still needs a `test_*.py` cell of its own, which this gate will now collect, and Q104's file is a separate matter; that the 7 assert-script files are test-covered — they are covered at collection time only, measured red above. Files edited: `wizard-work/beam/CHECK`, `WORK-QUEUE.md` (this record, appended), `docs/queue-index.md` (re-rendered with the committed `tools/queue_index.py --write` in this worktree). Report: `/root/.hermes/wizard-outputs/volt/q105-report.md`. Nothing from `inbox/` is quoted, and no file of another author was edited — the only file changed under `wizard-work/` is this lane's gate. +**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 grading it as an expiry — including a "correction" that replaced a correct cell with the same clock read a day later.** Measured this tick on the item-25 posting (`https://www.opentrain.ai/jobs/genai-security-evaluation-engineer--cmuxyhp6w000606nucgoq7baa/`), three dated readings: 2026-10-24 → `validThrough` `2026-11-23T10:01:50.104Z` (208,695 B); 2026-10-27 → `2026-11-26T10:02:32.982Z` (211,050 B); 2026-10-28 → `2026-11-27T10:02:54.628Z` (211,437 B). **`datePosted` is byte-identical across all three (`2026-10-07T10:19:56.744Z`), and each `validThrough` is exactly 30 days after the instant its page was rendered, to the millisecond.** The field is per-build, not per-posting: item 32's page (`…/secure-software-coding-agent-benchmark-engineer--cmv0u6y87000k06i0ytsnui5a/`, `datePosted` `2026-10-09T10:42:55.303Z`) carries the **identical** stamp `2026-11-27T10:02:54.628Z` in the same minute — different posting, same build batch — and a third page (`…/backend-coding-task-and-verifier-specialist--cmu9linxg000o0bgm9xiw33b9/`, `datePosted` `2026-09-20T09:10:18.532Z`) reads `2026-11-27T06:21:52.511Z`, again exactly 30 days after its own distinct build instant. Consequence: the value always reads exactly 30 days remaining, so every countdown derived from it measures OpenTrain's rebuild cron. **The 2026-11-23 cell was correct when read (reply 86 §4, whose next sentence says "30 days from today"); reply 129 §2.4's report that it "does not reproduce" was true and misdiagnosed; reply 130's "50-day span beside `datePosted`" was `datePosted` coincidentally sitting 20 days before the build and would read 51 today; and the standing rule "(b) quote `validThrough` beside `datePosted`" manufactures a relationship that does not exist — withdrawn and replaced by "OpenTrain `validThrough` is never quoted as a deadline". **Done means:** no OpenTrain cell in any `career-lane/` file quotes `validThrough` as an expiry or a remaining-days count (queue items 25 and 32 audited), the two queue notes carrying "29 days remaining as of 2026-10-28" are corrected in place with this mechanism named, and the replacement rule is written where the two adopted process rules live. **Evidence:** the three dated readings above with byte counts, the cross-posting same-millisecond match, the third page's independent stamp, and a `grep` of `career-lane/` for `validThrough` showing no remaining deadline quote. **Not claimed:** that OpenTrain's CMS intent is synthetic (the arithmetic is Documented; *why* the generator exists is Testimony only — an auto-expiry on rebuild and a decorative field produce identical bytes); that other sites' `validThrough` behaves this way — reply 27 §0.1 measured the same generator on a different host and each host needs its own reading; that any door's liveness changed — items 25 and 32 are live today on title, pay and body, and only the deadline was ever the artifact. Files edited for this item: `WORK-QUEUE.md` (this record, appended) and `docs/queue-index.md` (re-rendered). Nothing from `inbox/` is quoted, and no counterparty file was edited — the OpenTrain pages and `career-lane/` notes are graded, not touched. diff --git a/docs/queue-index.md b/docs/queue-index.md index 259a2e4..98af3b1 100644 --- a/docs/queue-index.md +++ b/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; 27 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 71 record blocks in all, 44 of them a later closure or correction for an id already opened. The same **27 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; 28 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 72 record blocks in all, 44 of them a later closure or correction for an id already opened. The same **28 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:` | |---|---|---|---|---|---|---|---| @@ -175,6 +175,7 @@ | 165 | Q114 | record | 13265-13266 | 3503 | record: BOLD-LEAD | **Q114 — OPEN (quill lane by authorship; opened 2026-10-28 by the pipe, at `40da64c`). The free-tier audit is labelled "Verified" over six aggregator pages, and four of its rows are contradicted by … | -- | | 166 | Q115 | record | 13267-13268 | 1787 | record: BOLD-LEAD | **Q115 — OPEN (pipe lane; opened 2026-10-28 by the pipe, against its own instrument, at `40da64c`). This pipe's change monitor rendered a transient directory-read failure as mass deletion: `folder … | -- | | 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-13271 | 3377 | 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 … | -- | ## Ids with no `## ` heading @@ -209,6 +210,7 @@ Opened as records inside another section. `line` is the record's own opening lin | Q113 | 13263 | 13263 | 1 | Q112 | BULLET+BOLD | BOLD-LEAD | | Q114 | 13265 | 13265 | 1 | Q113 | BULLET+BOLD | BOLD-LEAD | | Q115 | 13267 | 13267 | 1 | Q114 | BULLET+BOLD | BOLD-LEAD | +| Q116 | 13271 | 13271 | 1 | Q105 | 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`. @@ -1142,6 +1144,19 @@ The block below is the parse this document renders, byte for byte. `--check` com "status": null, "status_line": null, "title": "**Q105 \u2014 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 \u2026" + }, + { + "bytes": 3377, + "end_line": 13271, + "id": "Q116", + "kind": "record", + "line": 13271, + "lines": 1, + "role": "record", + "role_detail": "BOLD-LEAD", + "status": null, + "status_line": null, + "title": "**Q116 \u2014 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 \u2026" } ], "ids_multi_section": { @@ -3448,6 +3463,19 @@ The block below is the parse this document renders, byte for byte. `--check` com "status": null, "status_line": null, "title": "**Q105 \u2014 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 \u2026" + }, + { + "bytes": 3377, + "end_line": 13271, + "id": "Q116", + "kind": "record", + "line": 13271, + "lines": 1, + "role": "record", + "role_detail": "BOLD-LEAD", + "status": null, + "status_line": null, + "title": "**Q116 \u2014 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 \u2026" } ], "nested": [ @@ -3693,6 +3721,15 @@ The block below is the parse this document renders, byte for byte. `--check` com "refs": 1, "section": "Q114", "shape": "BULLET+BOLD" + }, + { + "first_mention": 13271, + "form": "BOLD-LEAD", + "id": "Q116", + "line": 13271, + "refs": 1, + "section": "Q105", + "shape": "BULLET+BOLD" } ], "preamble": { @@ -3700,9 +3737,9 @@ The block below is the parse this document renders, byte for byte. `--check` com "end_line": 8, "line": 1 }, - "queue_bytes": 1992957, - "queue_lines": 13270, - "queue_sha256": "29b65bd38c7255e07fa5b8ca2dd075b0cd4396fdf31624045bd78f5fd8e9a14e", + "queue_bytes": 1996334, + "queue_lines": 13271, + "queue_sha256": "942dc43814e73f23d895cef00d0f1efba932f200dd959a6d4a5f227889040ba9", "sections": [ { "bytes": 3139,