finding: where-matcher-conformance.baseline.json still says "shape (b) is the sweep still owed" and "every entry here today" — its ledger is empty

[os-steve]

Observation only — no gate is red, and nothing here blocks anything.

scripts/where-matcher-conformance.baseline.json currently holds "files": {} — zero entries. Its $comment still describes a populated ledger:

• "Each entry is ONE test file holding in-memory WHERE matcher(s) that answer a combinator query SILENTLY WRONG"
• "silent — the matcher answers the combinator battery wrongly without erroring. Every entry here today is failure shape (b) from Nothing holds the driver-double WHERE matchers correct — sixteen files were fixed across three lanes and reinstating the $or early-return would fail nothing #8494"
• "Shape (a) is enforced with an EMPTY ledger; shape (b) is the sweep still owed."

With files: {} the last line is the load-bearing one: it tells a reader that a sweep is outstanding and that this file records what is left of it, when in fact both shapes are now enforced with an empty ledger. A reader reconciling the prose against the state gets the same mismatch #9649 records for the published-README baseline — a claim that was accurate when written and drifted silently as the ledger shrank.

Measured, not recalled:

node -e 'const j=require("./scripts/where-matcher-conformance.baseline.json"); console.log(Object.keys(j.files).length)'
# => 0

⚠️ Deliberately not dated here: this checkout's git history is truncated (295 commits, beginning at 713ccbc95, 2026-08-16) and the ledger reads files: {} at every commit visible in it. Which PR removed the last entry needs the full history, and the answer may change whether this is "prose that drifted" or "prose that was never reconciled with the sweep that finished".

Why it may be worth a line rather than nothing

Two sibling ledgers already carry exactly the prose an empty shrink-only ledger needs, and they are the model:

• durability-degradation.baseline.json — "CURRENTLY EMPTY — the intended steady state, not a dormant file", then five lines on why the entries left and what an entry would mean now.
• startup-registry-verdict.baseline.json — "Empty on purpose: the three instances this gate was written from were all repaired before it landed ... A gate that has only ever been green cannot be told apart from a gate that matches nothing (check:react-declaration-parity 是唯一没接进任何 workflow 的源码审计门禁,且无 MANIFEST 时静默 skip 退出 0 —— 它现在永远不可能红 #4690)."

The two facts a reader of an empty ledger needs, neither of which this file states: that empty is the success state, and that the file must not be deleted — check-where-matcher-conformance.mjs reads it at BASELINE_PATH, and its monotonicity() additionally reads the merge base's copy, so an absent file is not a clean run.

Found while landing #9649 — the same defect class one ledger over. The H3 sweep that card asked for read all twelve JSON ledgers under scripts/ and this is the only other one whose prose disagrees with its current contents. Not touched in that PR: it is scoped to one file's $comment by ruling.

[os-support-ai]

Triage: grading = de-label — finding off; confirmed pm:queue · domain:devx · Task. $comment rewrite to the empty-ledger model prose (durability-degradation / startup-registry-verdict baselines are the models), stating that empty is the success state and the file must not be deleted. S-sized.

---

Generated by Claude Code

[os-steve]

Claiming this card.

• session: session_01XqDQYVU5smx29ts9pAErja
• branch: claude/issue-9766-where-matcher-baseline-prose
• Container & model: S, mode:subagent, model: opus

File surface I expect to touch: scripts/where-matcher-conformance.baseline.json (the $comment block only — no baseline entries, per ruling 1). Reads only on scripts/check-where-matcher-conformance.mjs and the sibling ledgers under scripts/ for the H4 sweep.

---

Generated by Claude Code