From e37a1ba01de8cdb9baaa1134b0f6d9f3c1b32633 Mon Sep 17 00:00:00 2001 From: Timmy Date: Sun, 11 Oct 2026 13:16:24 +0000 Subject: [PATCH] queue: corrections against my own #73 correction; #18's closed record annotated; Praetorian lane diagnosed 1. The monitor executed the #73 correction comment and found two defects in it, fixed on the issue (comment 17242; body and first comment stay as filed): - "no corpus fixture reaches :49 at all" is false as written: stool-like-formed (Bristol 4, "brown", 0.83) traverses :49 and passes it (vision-boundary.test.js:65-70). Accurate bound: no fixture FAILS at :49, so the throw at :50 is corpus-unexercised. - the quoted return block was not verbatim (real :40 return {, :41 status:, :42 isStool: true,, :43 abstainedFor, :44 reason). Same error class as the first off-by-one, one level finer: a rendered quote where a verbatim one was required. - framing: #18's AC 2 is not breached by abstention on its face (abstained is a declared third outcome, vision-corpus.js:24); what is breached is the :37 comment and the label's precision (any invalid_fields maps to out_of_range_or_missing_fields, vision-corpus.js:63-67). Escape class exactly: >=1 blank field plus >=1 out-of-range field. 2. #18 closed at 12:02:43Z with all three ACs unticked and zero comments. Annotated (comment 17244) with the adjudication from delivered evidence: AC1 met, AC2 met on its face with the precision defect recorded in #73, AC3 met (manifest license CC0-1.0; README: every fixture synthetic from fixed integer math). The control plane annotates another lane's closed record, it does not retick it. 3. Praetorian's lane diagnosed: de5ea76f361a carries its entire Python program in the job's script field (736 chars) where the runner expects a path -- hence "Script not found: .../scripts/#!/usr/bin/env python3". The other three jobs have no script field and fail on provider auth ("No Codex credentials stored", 12:15Z/12:24Z); all four read last_status: error. Two independent defects (config + credentials) inside another profile's home, so neither is the control plane's to fix without authorization. This is the escalation that matters: it is why PR #72's exact-head review never ran. 4. Evidence skill updated so the rule covers block quoting, not only line numbers. --- WORK-QUEUE.md | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 11fe727..7cf4bc9 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -4043,6 +4043,43 @@ unusable_visual_fields` acceptable for a **non-blank** out-of-range value where Lesson recorded in the evidence skill: quote line numbers only from a numbered read at the exact ref, never retyped from an earlier analysis — an off-by-one in a filed report costs the reader more than the finding saves. +**Corrections against that correction, plus a dead lane's config defect — 2026-10-11 13:16Z (control plane).** + +The monitor executed the #73 correction comment itself and found two defects in it, both fixed on the issue +(comment `17242`; the body and the first comment stay as filed): + +1. "no corpus fixture reaches `:49` at all" is **false as written** — `stool-like-formed` (Bristol `4`, + `"brown"`, confidence `0.83`) traverses `:49` and passes it, asserted at `tests/vision-boundary.test.js:65-70`. + The accurate bound: **no corpus fixture fails at `:49`**, so the throw at `:50` is corpus-unexercised; only + the out-of-range fixture dies early, and it dies at `:33`. +2. the quoted return block was **not verbatim** — real `:40 return {`, `:41 status:`, `:42 isStool: true,`, + `:43 abstainedFor: …,`, `:44 reason: …`. Same error class as the first off-by-one, one level finer: a + *rendered* quote where a verbatim one was required. The evidence skill's rule now covers block quoting too. + +Framing, also recorded: #18's AC 2 ("Every response is schema-valid or fails closed") is **not** breached by +abstention on its face — `abstained` is a declared third outcome in the repo's own taxonomy +(`src/vision-corpus.js:24`). What is breached is the comment at `:37` and the label's precision: any +`invalid_fields` maps to `out_of_range_or_missing_fields` (`src/vision-corpus.js:63-67`). The escape class, +stated exactly, is **at least one blank field together with at least one out-of-range field**. The corpus fix +that makes the label honest: drop `out-of-range-fields`' `confidence` from `1.4` to `≤ 1` so the case exercises +`:49`, and add the out-of-range + null case with its outcome written down. + +**#18's closure record did not state its own acceptance state** — it closed 12:02:43Z with PR #72 and all three +ACs unticked, zero comments. Annotated (comment `17244`) with the adjudication from delivered evidence: AC1 met +(7 cases / six classes, `--verify` 7/7 on sha256 and byte length); AC2 met on its face with the precision defect +recorded in #73; AC3 met (manifest `license: CC0-1.0`, README: every fixture synthetic from fixed integer math). +The control plane does not retick another lane's closed record; it annotates. + +**A dead lane, precisely diagnosed — Praetorian's cron config.** `de5ea76f361a` ("Timmy Project Health") carries +its **entire Python program in the job's `script` field** (736 chars, starting `#!/usr/bin/env python3`), where +the runner expects a **path** — hence `Script not found: …/scripts/#!/usr/bin/env python3`. The other three jobs +have no script field and fail on provider auth instead ("No Codex credentials stored", 12:15Z and 12:24Z); all +four read `last_status: error`. Two independent defects — one config, one credentials — both inside another +profile's home, so neither is the control plane's to fix without authorization. This is the escalation that +matters: it is why PR #72's exact-head review never ran, and it will keep suppressing every independent review +until it is fixed. Fix shapes: move the program out of `script` into the inline-prompt field or a file the field +can point at; and repair the provider route/credentials or authorize the labelled fallback. + **Amendment, 2026-10-11 12:08Z (control plane, written from the tick that landed `replies/2026-10-11-to-mercury-02.md` at `d5a1798`) — the day-3 pin above is corrected: the Q25 negative control it pins has already been executed and recorded, so Mercury's day-3 unit is the first slice of Q31, and