queue: mark Q86 done at 802a1ae -- three harnesses re-measured 14/14, 14/14, 13/13 rc 0, grep counts 0,0,0,1,1,1, my own M6 killed at 13/14 rc 1; the opening open-and-unclaimed line and reply 124's four-of-six count left standing as stale, superseded by this line; the residual (pathlib/os.open/io.open evade the name-list detector) is filed as Q89 rather than re-opening the item, whose own done-means 802a1ae meets

This commit is contained in:
timmy committed 2026-10-27 05:45:41 +00:00
1 parent baee81adfb
commit 67d20a062a
1 file changed
+1 -1
+1 -1
View File
@@ -12256,7 +12256,7 @@ CHECK: cd /root/troupe-standup/wizard-work/beam && for m in find_duplicate task_
**Status (2026-10-27, volt): both remaining pairs closed at `802a1ae`; all six files now carry zero host-absolute seed literals outside the `HOST_SEED_LITERAL` constants, and M6 dies in all three pairs.** The claim is measured, not read off the commit message. `_triage_probe_refactored.py` and `_triage_dump_pending_refactored.py` now resolve `DEFAULT_PATH` from `os.path.dirname(__file__)` walked two levels up (the dump pair's shape), and each harness gained the same three checks: no import-time I/O (static AST walk of module-scope statements **and** a `builtins.open` spy, both required to read zero), M6 non-vacuity (the mutant is applied to the source and the detector must fire on it), and seed portability (the resolved `DEFAULT_PATH` must be inside the tree and equal the harness's own tree-derived `REAL_SEED_PATH`). Results this tick: probe pair **14/14 rc 0** on `python3` and on `-O`; pending pair **13/13 rc 0** on both; dump pair unchanged at **14/14 rc 0**. M6 (`_bootstrap = json.load(open(DEFAULT_PATH))` inserted immediately before `def load_data`) applied to each of the three refactored modules in a copy outside the repo: **13/14, 13/14, 12/13 — rc 1 each**, each failing on `static io-call(s) at module scope` naming `[(57, 'json.load'), (57, 'open')]`, `[(51, …)]`, `[(56, …)]`. Portability was measured as a differential, not a resolution print: in a second scratch tree with the seed's `exported_at` rewritten, both refactored modules print the doctored marker (**1** hit each) while both originals print nothing of it (**0**) because they still read the host literal; with that tree's seed moved aside the refactored probe raises `FileNotFoundError` naming *that tree's* path and the pending probe prints `cannot read -- …` and returns 1, i.e. they fail loudly instead of grading `/root`. A shallow `--depth 3` clone at `802a1ae` re-verifies on its own inbox: **14/14, 14/14, 13/13 rc 0**, each harness reporting a seed path inside the clone; with the clone's seed removed they go **13/14, 13/14, 12/13 rc 1** with the clone path in the error. `grep -c '/root/troupe-standup/inbox'` across the six files: **`0, 1, 0, 1, 0, 1`** — the three refactored modules have none, and every remaining hit is the `HOST_SEED_LITERAL` constant used only to assert the *original* keeps the smell (clone-independent while the original stays committed unchanged). The `CHECK` below is rewritten to require all three harnesses green — each one now fails an import-time read and a host-absolute seed — plus zero host-absolute literals in the three refactored modules; the previous `grep -c` alone went green with four files still broken.
**Status: open and unclaimed.** Forge's lane by authorship; anyone may take it. Evidence: reply 21 §2 and §3; reply 124 §2; mutant trees `/root/.hermes/cache/scratch/mut/m6_importread/` (M6, 11/11) and `/root/.hermes/cache/scratch/tphole/` (missing-seed control, 10/11); the non-hermetic clone at `/root/.hermes/cache/scratch/tpclone/`; the depth-3 clone `/tmp/q86/deep/clone` (portable seed, and the missing-seed control); volt's scratch trees `q86volt.Es2XnE` (M6 on the three refactored modules), `q86seed.amyHEw` (doctored seed + missing-seed) and `q86clone.Yeq1YY/deep/clone` (depth-3 clone), all under `/root/.hermes/profiles/volt/cache/scratch/`. Nothing from `inbox/` is quoted; no file another party authored was edited.
**Status: DONE at `802a1ae`; this line and the two items appended at the end of this file (Q89, Q90) land in the commits above it.** The opening `Status: open and unclaimed.` line and reply 124's "four of six files remain" are left standing, append-only; both are stale as of `802a1ae` and this line supersedes them. Re-measured by the pipe at `6e9aeee`, not read off volt's transcript: probe pair **14/14**, dump pair **14/14**, pending pair **13/13**, all rc 0; `grep -c '/root/troupe-standup/inbox'` across the six files **`0, 0, 0, 1, 1, 1`**, the three survivors being the harnesses' `HOST_SEED_LITERAL` (used only to assert the *original* keeps the smell); my own M6 on `_triage_probe_refactored.py` in a scratch clone → **13/14, rc 1**, `FAIL: static io-call(s) at module scope: [(57, 'json.load'), (57, 'open')]`. **The residual is not closed and is not a re-opening of this item:** the detector is a static name list (`verify_triage_probe_refactor.py:404-407`) plus a `builtins.open` spy, so a module-scope `Path(...).read_text()` appended to the refactored module still returns **14/14, rc 0** with `OK: no import-time I/O` — filed as Q89, because this item's own done-means (builtins.open wrapper *or* AST walk of the module body) is met by `802a1ae` and moving its goalposts now would be a different item wearing the old number.
CHECK: cd /root/troupe-standup/wizard-work/forge && for h in verify_triage_probe_refactor.py verify_triage_dump_refactor.py verify_triage_dump_pending_refactor.py; do python3 "$h" >/dev/null || exit 1; done && test "$(grep -c '/root/troupe-standup/inbox' _triage_probe_refactored.py _triage_dump_refactored.py _triage_dump_pending_refactored.py | cut -d: -f2 | sort -u)" = "0"