checkGuardAdoption still passes a gate that counts messages from `lintText()` — the adoption check tests the call it names, not the measurement it guards

[os-zhuang]

Filed unassigned from the #10458 dev seat (session session_01DdCnBGcHeufjrq7drTD3wt, branch
claude/issue-10458-fatal-guard-adoption-mask, PR #10598). #10458 closed the two holes it named —
comments counting as code, and nothing asserting the guard is CALLED. This is the residue it named
in passing and deliberately did not close, recorded so it is not lost.

The gap

After #10598, checkGuardAdoption() asks three questions of each gate's comment-masked source:

if (!/eslint-fatal-guard\.mjs/.test(src)) … // imported
else if (!/lintFilesStrict\s*\(/.test(src)) … // and called
if (/\.lintFiles\s*\(/.test(src)) … // and not bypassed

A gate that kept its lintFilesStrict() call for one population and measured a second one through
eslint.lintText() would satisfy all three while the lintText() path does zero guarding —
lintFilesStrict wraps lintFiles only. The check proves a call site exists; it does not prove
every measured population goes through it.

Why #10598 did not just ban .lintText(

Measured, not assumed: scripts/check-query-options-erasure-ratchet.mjs calls eslint.lintText()
throughout its own --self-test (the unparseable-file fixture at ~L405 and the parses-cleanly
control right after it, among others). A blanket /\.lintText\s*\(/ problem would report that gate
as unguarded on main today — a false positive on the gate whose self-test drives the check.

Severity: latent, and narrower than #10458 was

Neither gate measures anything through lintText() today; both route their real population through
lintFilesStrict(). This is a bound on what the adoption check can claim, not a live false green.
It is worth writing down because the same sentence — "both gates still routed through it" — is what
the check prints, and that sentence is now true of the call site rather than of the measurement.

Shapes worth weighing, none obviously right

1. Leave it, and narrow the printed sentence to what is actually proved.
2. Ban .lintText( only OUTSIDE a self-test region, which needs a region concept the check does not
   have and which a gate could drift out of.
3. Assert the guard from the RUN rather than the source — e.g. lintFilesStrict() records that it
   ran and the gate asserts it — which is a real behaviour change to both gates, not a check change.

Refs: #10123 (the card that created the guard) · #10458 / PR #10598 (where this was measured).

---

Generated by Claude Code

[claude]

⚠️ This claim comment is LATE and that is a defect on the PM seat, recorded rather than quietly backfilled. The assignee and pm:dispatched were set at dispatch time, but CLAUDE.md's Prime Directive is explicit that a claim is assign plus a claim comment carrying the session ID and branch — and all-agents-share-one-identity means the assignee field alone cannot tell a later reader whose claim it is. Caught by the dev seat working #10595, which read the comments as instructed, found none, and said so instead of assuming. No competing claim existed on any of these, so no work was duplicated; the exposure was real regardless.

Claim: /pm-dispatch domain:devx execution seat (bug-first round).
Session: session_01DdCnBGcHeufjrq7drTD3wt
Branch: claude/issue-10599-fatal-guard-linttext
Worktree: objectstack-issue-10599
Domain: domain:devx
File surface: scripts/eslint-fatal-guard.mjs (checkGuardAdoption) + the --self-test in scripts/check-query-options-erasure-ratchet.mjs

⛔ Governed surface out of scope for the diff (docs/adr/**, .claude/**, skills/**, AGENTS.md, CLAUDE.md, content/docs/releases/**) and the #9465 epic fence (.changeset/ tooling, cut-rc.yml, release.yml, root package.json).
⭐ Changeset: AGENTS.md:943 — "Pure bug fixes do not require a changeset"; a scripts/**-only diff that publishes nothing takes the skip-changeset label via the additive POST /labels (⛔ never a whole-set PUT — see #5533). Precedent: PR #10502.

---

Generated by Claude Code

[claude]

{
 "issue": 10599,
 "status": "done",
 "branch": "claude/issue-10599-fatal-guard-linttext",
 "pr": "https://github.com/objectstack-ai/objectstack/pull/10624",
 "premise_still_valid": true,
 "summary": "The hole is real but narrower than the title, exactly as suspected. Measured against guardAdoptionProblems() as PR #10598 left it: a gate that measures ONLY through lintText is already caught (1 problem, 'Importing the guard does not arm it') because #10598's positive lintFilesStrict( assertion has nothing left to find; the MIXED gate — keeps one guarded call for population 1, measures population 2 through eslint.lintText() — came back with 0 problems. That mixed shape is what this PR closes. It was also NOT latent as the card rated it: this gate's own self-test helper hits() was a bare eslint.lintText() with no fatal check, and hits(code)===0 is precisely what its ten `silent` cases assert, so a fixture that stopped parsing would have read as proof the rule is quiet (measured: the `argument 1, object literal` report fixture minus its closing paren gives hits()=0, fatalErrorCount=1, \"Parsing error: ')' expected.\"). A blanket ban was unavailable, so the check does not guess which lint result is counted (data flow, not text): it bans the BARE spelling and the gate declares each call — lintTextStrict() when counted, lintTextUnguarded({ why }) when it is ground truth for the guard. The armed test was widened to accept either strict entry point, since a text-only gate never calls lintFilesStrict( and reporting it unguarded would be a false positive of this change's own making.",
 "tests": "All on final HEAD 46dad29f40 (worktree clean, 0 modified paths at the time of the run). Union re-run AFTER the last commit because the first full-gate run predated it. `bash scripts/pm/os-verify-lock.sh -c '...'` → `os-verify-lock: VERDICT command-exit 0 · held the lock 172s (2m52s) · waited 34s`, wrapping: `pnpm check:query-options-erasure` → `✓ self-test: 10 reporting shape(s), 10 silent counterpart(s), … every counted lint call in both gates routed through it (adoption proved both ways over 11 synthetic gate source(s), files AND text) …` and `✓ query-options-erasure ratchet holds: 67 unswept non-test site(s) in 17 file(s), none new, and every file measured parsed.`; `pnpm check:slot-lookup` → `✓ slot-lookup ratchet holds: 107 unswept site(s) in 25 file(s), none new`; `pnpm check:cross-package-test-inputs` → `All 60 self-test cases passed. OK: 12 package(s) read outside themselves`; `node scripts/check-nul-bytes.mjs` → `check-nul-bytes: OK (scanned 6203 text file(s) … no raw ASCII control bytes)`. Gate list derived by `node scripts/pm/dispatch-gates.mjs` with no paths (3 families matched, all run). ESLint on both changed files: exit 0, and proved it really inspected them via -f json → 2 results, messages=0, fatal=0 each (an empty stylish report alone does not distinguish 'clean' from 'matched nothing'). NEGATIVE CONTROL (the load-bearing one): the real check-query-options-erasure-ratchet.mjs, with its four legitimate lintText calls, is NOT flagged — after the migration the comment-masked sources of BOTH guarded gates carry 0 bare `.lintText(` and both gates run green; check-slot-lookup-ratchet.mjs had 0 to begin with and is untouched. ABLATIONS, each mutation confirmed ON DISK by anchor count before the run and each restore by an empty `git diff HEAD` (no build/dist involved — these are plain .mjs run directly by node): (1) delete the `.lintText(` ban → test lines 1→0, marker 1 → RED, 3 failures, including `a guarded call plus a second population measured through lintText: expected [\"A counted lintText result discards a parse failure\"], got []`; (2) narrow the armed disjunction back to lintFilesStrict only → RED, 1 failure, `armed through lintTextStrict alone: expected [], got [\"…never calls lintFilesStrict() or lintTextStrict()…\"]`; (3) make lintTextStrict a pass-through → `collectFatalMessages` call sites 2→1 → RED, 2 failures; (4) drop lintTextUnguarded's required `why` → guard clause 1→0 → RED, 1 failure `(threw: nothing)`. Restored tree green after each, final restored self-test exit=0. ⚠️ Ablation (2) was VOID on its first attempt and is reported as such: the mutation was written with `perl -0pi`, which matched zero times, exited 0, and left the file unchanged — the self-test then went green, which would have read as 'this assertion cannot fail'. The on-disk anchor count caught it (`disjunction present = 1` where 0 was required); it was redone with a verified Python anchor and the actual diff hunk printed alongside the count. os-verify-lock.sh behaved correctly throughout, including a 132s queue wait behind another worktree's build with the budget counting down — nothing odd to report against PR #10609. No changeset (scripts/**-only, publishes nothing; AGENTS.md:943); `skip-changeset` applied by additive POST /labels and READ BACK twice — second read `['size/m', 'skip-changeset']`, so it survived the bot's write.",
 "open_questions": [],
 "out_of_scope_findings": [
 "filed as #10625: [finding] checkGuardAdoption's call bans only read the gate FILE — a measurement moved one import out into a sibling helper module is invisible to all three tests (latent: neither gate has a helper today, but 'pull the measuring part into a module' is the natural next refactor of two 700+ line gates and it would silently remove the gate from its own guard with no diff to the check)"
 ]
}

---

Generated by Claude Code