From ca9f73924ed0e3a5864006d34e7e81869c06b87c Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 10 Aug 2026 03:16:53 +0000 Subject: [PATCH] docs(spec-tooling): fix stale attribution in check-driver-conformance FILTER_TEXT req 3 driver-mongodb's INVALID_FILTER arm was never "the last place a bare new Error escaped the ADR-0112 envelope" repo-wide -- objectql's having face (having-filter.ts) had two bare new Error returns escaping the same envelope until #7047 (edb4af099, PR #7161) closed them. Scope the claim to the DRIVER family (this gate's own case-set), which is checkable against the five driver refusals it actually covers, and keep the trailing note that having sat outside this gate's scope -- that gap is why two consecutive defects on that face (#5905, #7047) were found by hand-run censuses instead of CI. Prose-only change to one comment block; no case-set, gate logic, or exit code touched. --self-test and the real check both stay green. Fixes #7159 --- scripts/check-driver-conformance.mjs | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/scripts/check-driver-conformance.mjs b/scripts/check-driver-conformance.mjs index 9b8efcd906..923f1ee307 100644 --- a/scripts/check-driver-conformance.mjs +++ b/scripts/check-driver-conformance.mjs @@ -335,8 +335,10 @@ const CASE_SETS = [ // Each site now prints `RETIRED_FILTER_OPERATORS[op].why` verbatim, so the // five refusals say one thing; driver-mongodb's `default:` arm was // additionally routed through its own `INVALID_FILTER` helper, which is the -// `code` half the case-set requires and the last place a bare `new Error` -// escaped the ADR-0112 envelope. +// `code` half the case-set requires and the last bare `new Error` in the +// DRIVER family (this gate's own scope, `packages/drivers/*`). The sixth +// refusal face — objectql's `having` (`having-filter.ts`) — was outside +// that scope and kept its bare `new Error` until #7047. // // ## AGGREGATION_CASES: two DEBT rows on arrival, and they are the same pair //