driver-memory's reference matcher still answers $notContains / $nin the pre-ruling way on a no-value row — the #5499 freeze that excused it dissolved 2026-08-11, so the divergence is now unexcused and untracked

[os-litant]

Split out of #13089 per its triage instruction ("若测出 HAVING 分歧在解冻后仍真实存在 ⇒ 停下,把它立成 domain:engine 的独立卡"). #13089 remains open and is not addressed by this card; that card's PR delivers only its sites 1-2 (the two pm-dispatch reference files).

The measurement

Run on branch claude/issue-13089-freeze-residue at merge-base 56470d86b, by execution (not by reading), against packages/drivers/driver-memory/src/memory-matcher.ts match(). Fixture: rows 1 (name: 'alpha-one'), 2 (name: 'beta'), 3 (no value) — measured under BOTH readings of "no value", name: null and the key absent. The platform-settled answer (#5146 extended by #5298 option A, re-affirmed after the #5299 reversal was costed and withdrawn) is that a no-value row SATISFIES a negation-carrying operator, i.e. ['2','3']:

Operator	name: null	key absent	ruling answer
$ne: 'alpha-one'	['2','3'] OK	['2','3'] OK	['2','3']
$nin: ['alpha-one']	['2','3'] OK	['2'] DIVERGENT	['2','3']
$notContains: 'one'	['2'] DIVERGENT	['2'] DIVERGENT	['2','3']

Three of six cells diverge. This reproduces exactly the cell already recorded in the filter-logic-conformance.ts measurement table ("driver-memory reference matcher | no — DIVERGENT, frozen (#5499) | MATCH on a null value, no on a missing key"), so the divergence is real, unchanged, and now unexcused.

Mechanism

Two independent causes in memory-matcher.ts checkCondition:

1. The pre-switch guard if (value === undefined && op !== '$exists' && op !== '$ne' && op !== '$null') return false; — its allowlist names $ne but not $nin / $notContains, so a MISSING key short-circuits to "no match" for those two before their arms ever run.
2. The $notContains arm itself: if (typeof value !== 'string' || value.includes(target)) return false; — a null value is not a string, so it fails on the type test rather than on the predicate. That is the name: null half, which the guard above does not reach.

driver-mongodb is NOT part of this: translateFieldOperators maps $nin straight through and compiles $notContains to { $not: { $regex } }, both of which match a missing/null field in MongoDB. It already agrees with the ruling.

Why this is now a card rather than a comment

Two in-code annotations still spell the freeze as LIVE and use it to excuse the divergence — they are #13089's sites 3-4 and were deliberately left untouched:

• packages/objectql/src/having-filter.ts:40-42 — "driver-memory / driver-mongodb still answer the old way only because [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 freezes them; the divergence is against a frozen face, not against the ruling."
• packages/services/service-analytics/src/read-scope-sql.ts:179-180 — "driver-memory / driver-mongodb stay pin-only under the [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 freeze."

Both are wrong on two counts now: the freeze dissolved on 2026-08-11 (corroborated in the head note of packages/spec/src/data/aggregation-conformance.ts), and the driver-mongodb half of the claim was never true for this operator family. Rewriting them to past tense without deciding the divergence would have converted an actionable defect into settled-looking prose, which is what the #13089 triage forbade.

What a fix owes

• Decide the direction first: align driver-memory's reference matcher to the ruling (the include direction), or record a measured, dated exemption. Note this matcher is the reference the SQL family was aligned TO for $not 的语义在 driver-sql 与 driver-memory / formula 之间分叉：NULL 行的去留相反，$not: {} 一个是 TRUE 一个是 FALSE #5146, so moving it is not local.
• $exists is a separate, still-open cell — filter-logic-conformance.ts records that driver-memory's live mingo path and driver-mongodb both still read key-presence rather than has-value, which is why no $exists row can be enrolled yet. Not necessarily this card's scope, but it is the neighbouring cell.
• Enrolment, not a row: the head note of filter-logic-conformance.ts is explicit that a row added ahead of a backend is just a red gate, and that the DEBT ledger in scripts/check-driver-conformance.mjs is per (driver x case-set), with no spelling for "fails one row of thirty-six".

Generated by Claude Code

[huangyiirene]

定级：pm:queue · domain:engine · bug · priority:p1。（domain:engine 是立卡人所打，复核正确：packages/drivers/driver-memory/src/memory-matcher.ts。）

为什么判 pm:queue 而不是进决策箱

卡说 "Decide the direction first"，读起来像要人裁。但方向已经裁过了：

#5146 → #5298 option A → #5299 的反转被计价后撤回，裁决重申。

⇒ "no-value 行满足带否定的算子"是已settled 的平台裁决。driver-memory 与它分歧 3/6 格 ⇒ 这是实现一条既有裁决，⛔ 不是做一个新裁决。故入队，不入决策箱。

⭐ 而且冻结解除后，这个分歧同时失去了两个保护：不再有 #5499 当借口（2026-08-11 解冻，aggregation-conformance.ts 头注佐证），也从来没有被 DEBT 账本追踪。⇒ 现在是"无豁免、无追踪"，这正是 p1 的理由，而不是格数。

⛔ 派发围栏（三条，都来自卡本身）

1. ⚠️ 这个 matcher 是 $not 的语义在 driver-sql 与 driver-memory / formula 之间分叉：NULL 行的去留相反，$not: {} 一个是 TRUE 一个是 FALSE #5146 时 SQL 家族对齐过去的参照物 ⇒ 动它不是局部改动。⛔ 若实施中发现对齐会反过来推翻 SQL 家族已对齐的行为，停手回填，⛔ 不要为了让本卡绿而改动 SQL 侧。
2. ⚠️ 入册（enrolment），不是加一行。 filter-logic-conformance.ts 头注明说：backend 还没跟上就先加行，得到的只是一个红门禁；且 scripts/check-driver-conformance.mjs 的 DEBT 账本粒度是 per (driver × case-set)，没有"三十六行里挂一行"的拼法。⇒ 先把 backend 改对，再谈入册。
3. ⛔ $exists 是邻格，不是本卡。 卡记录 driver-memory 的 live mingo 路径与 driver-mongodb 都还在读 key-presence 而非 has-value ⇒ 那是另一件事，⛔ 不要顺手一起改。

⭐ 两处必须一并修正的错误陈述，否则修完代码注释仍在骗人

#13089 的站点 3-4 至今把冻结写成 LIVE 并用它开脱这个分歧：

• packages/objectql/src/having-filter.ts:40-42
• packages/services/service-analytics/src/read-scope-sql.ts:179-180

两处各错两重：(a) 冻结已于 2026-08-11 解除；(b) 其中"driver-mongodb 也这样"的说法对这个算子族从来就不成立——卡已测：translateFieldOperators 把 $nin 直通、把 $notContains 编译成 { $not: { $regex } }，两者在 MongoDB 里都匹配缺失/null 字段，⇒ mongodb 本来就符合裁决。

⛔ 但不要只把它们改成过去时。#13089 的分诊已经禁止过这个动作，理由很准："Rewriting them to past tense without deciding the divergence would have converted an actionable defect into settled-looking prose." ⇒ 这两处的措辞随本卡的处置一起定，⛔ 不得先于处置改写。

机制已定位到行，接手人不必重新诊断

卡给出两个独立成因，⛔ 修一个不够：

1. checkCondition 的前置守卫 if (value === undefined && op !== '$exists' && op !== '$ne' && op !== '$null') return false; —— 白名单点了 $ne 却没点 $nin / $notContains ⇒ 缺失 key 在它们的分支跑之前就短路成"不匹配"。
2. $notContains 分支自身 if (typeof value !== 'string' || value.includes(target)) return false; —— null 不是字符串，栽在类型测试上而不是谓词上 ⇒ 这是 name: null 那一半，守卫 1 够不到。

⭐ 立卡人对 "no value" 的两种读法（null 与 key 缺失）分别测了，六格表因此是完整的——这就是为什么能看出"两个独立成因"而不是一个。这张卡是由执行而非阅读得出的，质量很高。

---

Generated by Claude Code