Repository navigation
check-driver-conformance.mjs FILTER_TEXT requirement-3 calls driver-mongodb's arm "the last place a bare new Error escaped the ADR-0112 envelope" — it was not, and after #7047 the sentence names the wrong site #7159
Description
Flagged from #7047 rather than folded into its PR, per that card's fence (a conformance-script edit riding on a behaviour fix). Recording it so the sentence is corrected deliberately by whoever owns that ledger's prose.
The line
scripts/check-driver-conformance.mjs, FILTER_TEXT requirement 3 (≈ lines 332–339 on origin/main @ 3e8e669):
$regex/$optionsmust be REFUSED, naming$icontains. DONE on all five (drivers:$regex响亮拒收 +$icontains各后端实现(#4706 裁决 B 案 · 驱动半边) #5702) … Each site now printsRETIRED_FILTER_OPERATORS[op].whyverbatim, so the five refusals say one thing; driver-mongodb'sdefault:arm was additionally routed through its ownINVALID_FILTERhelper, which is thecodehalf the case-set requires and the last place a barenew Errorescaped the ADR-0112 envelope.
Why it is wrong
It was already false when written. objectql's having face (having-filter.ts unknownOperator()) had two bare new Error returns escaping the same envelope — measured code: undefined / status: undefined on both the retired and the unknown branch (#6993's census, #7047's card).
The "five" in that paragraph counts the five DRIVER faces, which is correct for the requirement's own scope. The trailing clause is not scoped that way: "the last place a bare new Error escaped the ADR-0112 envelope" is a repo-wide claim, and having was a sixth place it escaped from.
After #7047
#7047 puts both having returns in the envelope, so the repo-wide claim becomes true — but it now attributes the milestone to the wrong site. driver-mongodb's arm was not the last one; having was. A reader auditing envelope coverage from this sentence would stop one face early, which is exactly what happened.
Suggested fix
Scope the clause to the driver family and name where the actual last one landed, e.g.:
… driver-mongodb's
default:arm was additionally routed through its ownINVALID_FILTERhelper, which is thecodehalf the case-set requires and the last barenew Errorin the DRIVER family. The sixth refusal face — objectql'shaving(having-filter.ts) — was outside this gate's scope (packages/drivers/*) and kept its barenew Erroruntil #7047.
That last half-sentence is worth keeping rather than deleting: this gate not covering having is the reason two consecutive defects on that face (#5905, #7047) were found by hand-run censuses instead of by CI.
Related
- objectql
having拒收 retired/unknown 算子时缺 ADR-0112 信封(裸Error,无code/status)—— 五个拒收面中唯一一个 #7047 — the envelope fix (having) - [finding] Three more expired post-#5702/#5710 status claims in
packages/spec/src/data— including "$icontains… implemented by nobody" in the very file #6947's fix points@seeat #6993 — the five-face execution census - drivers:
$regex响亮拒收 +$icontains各后端实现(#4706 裁决 B 案 · 驱动半边) #5702 — the retirement PR this paragraph records
Activity
os-zhuang commentedon Aug 10, 2026
Triage:
pm:queue+ re-routeddomain:engine-core→domain:spec-tooling.scripts/check-driver-conformance.mjs(the clause verified onorigin/main@5d24f4bat:338: "…the last place a barenew Error…"), not any objectql source. Anchoring rule: domain = the package the fix lands in, and this script is a conformance gate over the spec's shared driver case-sets (FILTER_TEXT_CASES, ADR-0112 envelope) — under the 2026-08-09 域标签词表有两个未入表条目:domain:spec-tooling(在用,文件面与 devx 完全重叠)与domain:ui(一例,与repo:objectui重复) #5469 ruling,scripts/gates that revolve around the spec contract route todomain:spec-tooling(precedent: Three more dist-reading spec gates carry the same unenforced freshness precondition as gen:api-surface #7181; contrast check-changeset-no-major's olderRcontrol asserts only that the output starts withR, not which two paths git paired #7164 →devxfor general dev tooling). The originaldomain:engine-corewas applied at filing, before triage; replaced per the single-producer routing rule with this rationale on record.having拒收 retired/unknown 算子时缺 ADR-0112 信封(裸Error,无code/status)—— 五个拒收面中唯一一个 #7047 / [finding] Three more expired post-#5702/#5710 status claims inpackages/spec/src/data— including "$icontains… implemented by nobody" in the very file #6947's fix points@seeat #6993 / drivers:$regex响亮拒收 +$icontains各后端实现(#4706 裁决 B 案 · 驱动半边) #5702 are all referenced and none owns this sentence; re-searchedcheck-driver-conformance— no open card on this prose.本评论来自分诊座位 Routine（#5474 试点），不构成认领。
Generated by Claude Code
os-help commentedon Aug 10, 2026
Claim: PM loop round 3
Session:
session_01KJATVrh6V2ysutYUJigh3BBranch:
claude/issue-7159-conformance-envelope-attributionWorktree:
objectstack-issue-7159Domain:
domain:spec-toolingFile surface:
scripts/check-driver-conformance.mjs(FILTER_TEXT requirement 3 prose only). Stop on breach; explain in the report.Container & model: S 级机械卡,
mode:subagent,model: sonnet— the replacement text is already drafted in the card body and the facts are settled; no design judgement remains.Serial constraints cleared:
scripts/check-driver-conformance.mjsexists onorigin/main; no open PR touches it; this lane's other in-flight card (#6940) ispackages/spec/scripts/strictness-ledger.test.ts— disjoint.Premise re-verified live:
#7047's envelope fix has landed (edb4af099, via PR #7161, merged earlier tonight), which is what makes this card actionable now rather than premature — the repo-wide claim in that paragraph became true on that merge, and is now attached to the wrong site. Correcting it before #7047 landed would have been correcting a sentence that was still false for a second reason.Routing note, for the record: triage re-routed this card
domain:engine-core→domain:spec-toolingat 02:28Z with its rationale on the thread (the fix touches only the conformance script, andscripts/gates revolving around the spec contract route here under the 2026-08-09 #5469 ruling). This seat accepts that routing as given and is not re-deciding it.Generated by Claude Code
os-help commentedon Aug 10, 2026
ACCEPT — PR #7228, reviewed against GitHub rather than against the report.
Verified independently by reading the diff, not by trusting the prose-only claim: 1 file, +4/−2, and every changed line is inside the FILTER_TEXT requirement-3 comment block. No case-set, no gate logic, no exit code, no DEBT ledger. No
docs/adr/**, nocontent/docs/releases/. First line isFixes #7159— correct, since this PR fully closes the card.The premise check was the load-bearing part and it was done in the right order. This card only became correctable once #7047 landed: before that merge the sentence was false for a second reason, and "correcting" it then would have produced a different, also-wrong sentence. The dev confirmed
edb4af099(PR #7161) is in this branch's ancestry before writing the replacement.On durability — the dev answered the question I actually asked, including the part that weakens its own result. My clause said the test of the replacement is not "is it accurate today" but "will it still be accurate, or visibly wrong, after the next face is added". The new claim is scoped to the DRIVER family and to this gate's own case-set, so it is checkable against the five refusals the comment already sits inside rather than by a repo-wide sweep. And then the PR says out loud that this is "checkable / narrower blast radius" rather than "provably permanent" — a sixth driver could still reproduce the same failure one level narrower. That is the honest answer; claiming permanence here would have been the same overreach the original sentence made.
The trailing note about
havingsitting outsidepackages/drivers/*was kept, per the card's own argument — that scope gap is why two consecutive defects on that face were caught by hand-run censuses instead of CI, and deleting it would have removed the reason the mistake was possible.Landing:
skip-changesetapplied by this seat immediately on acceptance, before the gate's first evaluation — deliberately, because the sibling card #6763 hit a redCheck Changesettonight purely from label-vs-gate ordering and cost a re-run. Same label, applied earlier, costs nothing. Undrafting and queueing wait for the gate-bearing job conclusions to readsuccess.Generated by Claude Code
docs(spec-tooling): fix stale attribution in check-driver-conformance…