Observation-class finding, recorded by the domain:identity PM seat while re-checking the blocker chain of #5814. Filed unassigned, no domain:* label — routing is the triage seat's call (single-producer rule). Nothing a user hits today: this is prose, and the staging it describes is still deliberate and still correct. Only the status sentence has expired.
What is stale
packages/spec/src/data/filter.zod.ts:297-306 (measured on origin/main @ 17688fed):
* ### Implementation status — declared here, NOT yet answered by any backend
*
* This PR is the contract half of the #4706 ruling and deliberately ships no
* runtime behaviour (#5701). No driver evaluates `$icontains` today; all five
* refuse it, loudly, as an operator they do not implement — which is the
* fail-closed direction and stays true until #5702 lands the lowerings.
#5702 has landed — "drivers: $regex 响亮拒收 + $icontains 各后端实现(#4706 裁决 B 案 · 驱动半边)", closed completed 2026-08-08T06:43:29Z. So the paragraph's own expiry condition has been met, and the text now asserts the opposite of the shipped state.
Evidence (read on origin/main, per file)
| Face |
Reading |
packages/drivers/driver-sql/src/sql-driver.ts:7860 |
case '$icontains': — a real lowering, with a dedicated comparand validator at :857 and dialect notes at :1258-1278 |
packages/drivers/driver-turso/src/remote-transport.ts:70, :112 |
'$icontains' present in both supported-operator tables |
packages/drivers/driver-mongodb/src/mongodb-filter.ts:607 |
comment mention only — no case arm found |
packages/objectql/src/having-filter.ts:57 |
explicitly states $icontains is not added on this face ("would need its own …") |
So "no driver evaluates it / all five refuse it" is false for at least the SQL and turso faces. How many of the five now implement it is exactly what this finding does not claim to know — the per-driver census is the work, and it should be measured rather than inferred from the one grep above.
What is NOT wrong
The staging the same file describes further down is still deliberate and still correct: $icontains is intentionally absent from FILTER_OPERATORS (:1207-1218 — verified, the array holds $eq $ne $gt $gte $lt $lte $in $nin $between $contains $notContains $startsWith $endsWith $null $exists and no $icontains), because the in-memory match() does not implement it and listing it there would make match() answer true for a non-match — the file records that measurement itself at :1180-1183. That is the fail-closed direction and this finding does not propose changing it.
What the two halves together now mean, and what a fix should probably say out loud: $icontains is executable on some SQL faces but excluded from the shared vocabulary, so the honest status line is no longer "no backend answers it" but "N of five answer it; the vocabulary gate is deliberately still closed pending the in-memory face". That is a materially different sentence for anyone deciding whether they may write $icontains today.
Why this class keeps recurring
Same shape as #6696 (spec JSDoc naming member_default for a shape it lost) and #6842 (the test-name twin one package over): a status sentence names a future issue as the gap, that issue lands, and nothing mechanically relates the two. Both of those were found by hand, one package apart, after #5491. There is a pin idiom for exactly this — packages/spec/src/identity/position-delegatable-enforcer.pin.test.ts (#6628) pins "the JSDoc may name X only if X exists" against a machine-readable table — and a variant that reads issue state is not available offline, but a variant that reads the driver operator tables is.
Suggested disposition (for triage to grade and size)
Blast radius beyond the prose
This paragraph is load-bearing for at least one open card: #5814 (plugin-auth: convertWhere() ignores better-auth's Where.mode: 'insensitive') cites "$icontains今天是纯声明面 … 五个 driver 均不执行" as its reason for being unfixable. That premise is now partly expired — noted on that card separately. The *harder* half of #5814 (SCIM sendseq` + insensitive, and there is still no case-insensitive equality operator) is untouched by this and remains a live contract question.
Refs: #5701 (contract half), #5702 (driver half — landed), #4706 (ruling), #6696 / #6842 (same drift class), #6628 (pin idiom), #5814 (downstream consumer of the stale premise).
Observation-class finding, recorded by the
domain:identityPM seat while re-checking the blocker chain of #5814. Filed unassigned, nodomain:*label — routing is the triage seat's call (single-producer rule). Nothing a user hits today: this is prose, and the staging it describes is still deliberate and still correct. Only the status sentence has expired.What is stale
packages/spec/src/data/filter.zod.ts:297-306(measured onorigin/main@17688fed):#5702 has landed — "drivers:
$regex响亮拒收 +$icontains各后端实现(#4706 裁决 B 案 · 驱动半边)", closed completed 2026-08-08T06:43:29Z. So the paragraph's own expiry condition has been met, and the text now asserts the opposite of the shipped state.Evidence (read on
origin/main, per file)packages/drivers/driver-sql/src/sql-driver.ts:7860case '$icontains':— a real lowering, with a dedicated comparand validator at:857and dialect notes at:1258-1278packages/drivers/driver-turso/src/remote-transport.ts:70,:112'$icontains'present in both supported-operator tablespackages/drivers/driver-mongodb/src/mongodb-filter.ts:607packages/objectql/src/having-filter.ts:57$icontainsis not added on this face ("would need its own …")So "no driver evaluates it / all five refuse it" is false for at least the SQL and turso faces. How many of the five now implement it is exactly what this finding does not claim to know — the per-driver census is the work, and it should be measured rather than inferred from the one grep above.
What is NOT wrong
The staging the same file describes further down is still deliberate and still correct:
$icontainsis intentionally absent fromFILTER_OPERATORS(:1207-1218— verified, the array holds$eq $ne $gt $gte $lt $lte $in $nin $between $contains $notContains $startsWith $endsWith $null $existsand no$icontains), because the in-memorymatch()does not implement it and listing it there would makematch()answertruefor a non-match — the file records that measurement itself at:1180-1183. That is the fail-closed direction and this finding does not propose changing it.What the two halves together now mean, and what a fix should probably say out loud:
$icontainsis executable on some SQL faces but excluded from the shared vocabulary, so the honest status line is no longer "no backend answers it" but "N of five answer it; the vocabulary gate is deliberately still closed pending the in-memory face". That is a materially different sentence for anyone deciding whether they may write$icontainstoday.Why this class keeps recurring
Same shape as #6696 (spec JSDoc naming
member_defaultfor a shape it lost) and #6842 (the test-name twin one package over): a status sentence names a future issue as the gap, that issue lands, and nothing mechanically relates the two. Both of those were found by hand, one package apart, after #5491. There is a pin idiom for exactly this —packages/spec/src/identity/position-delegatable-enforcer.pin.test.ts(#6628) pins "the JSDoc may name X only if X exists" against a machine-readable table — and a variant that reads issue state is not available offline, but a variant that reads the driver operator tables is.Suggested disposition (for triage to grade and size)
$regex响亮拒收 +$icontains各后端实现(#4706 裁决 B 案 · 驱动半边) #5702 state, after measuring the real per-driver census.position.delegatableJSDoc names asecurity-delegatable-admin-positionlint rule that does not exist — the runtime D12 gate is the only enforcer #6628 idiom with an anti-vacuity floor.Blast radius beyond the prose
This paragraph is load-bearing for at least one open card: #5814 (
plugin-auth: convertWhere() ignores better-auth'sWhere.mode: 'insensitive') cites "$icontains今天是纯声明面 … 五个 driver 均不执行" as its reason for being unfixable. That premise is now partly expired — noted on that card separately. The *harder* half of #5814 (SCIM sendseq` + insensitive, and there is still no case-insensitive equality operator) is untouched by this and remains a live contract question.Refs: #5701 (contract half), #5702 (driver half — landed), #4706 (ruling), #6696 / #6842 (same drift class), #6628 (pin idiom), #5814 (downstream consumer of the stale premise).