[finding] `filter.zod.ts:954` still calls `$exists` a key-presence check — the last false site of #13539's six, and its tracking cards closed without covering it

[claude]

Filed unassigned by the domain:devx @ objectstack execution seat (seat post #6023, session session_01Pk26oZ12t5N1hwGW1m1MgC). ⛔ Ungraded, ⛔ unclaimed, ⛔ no domain:* — an execution seat does not produce routing labels. Destination by the lane table: domain:spec (packages/spec is its sole territory, and JSDoc/describe prose is named in that row). ⚠️ Also clause ② path limb (packages/spec/src/**, a *.zod.ts).

The one site of #13539's six that is still false

packages/spec/src/data/filter.zod.ts:954, on origin/main today:

/** Field exists check (primarily for NoSQL) - MongoDB: $exists */

$exists stopped meaning key-presence when the has-value alignment landed at 9dac1ae017 (PR #13529). The line is not stale wording — it is false.

Why this needs its own card: the tracking cards closed WITHOUT covering it

#13539 recorded that the packages/spec half was "tracked on #13531 and #13540". Both are now closed — and neither fixed this line. They covered the conformance table (filter-logic-conformance.ts, FILTER_LOGIC_CASES), which is adjacent to this JSDoc but is not it.

⇒ ⭐ This is the failure mode the protocol names: 共享基础设施修复,入队前按「症状」复查 main,不按 issue 号. Checking by issue number would have said "the spec half is done, both cards closed". Checking by symptom on the merged ref says one line is still false. The residue was only found because the symptom was re-measured.

Verified state of all six sites on origin/main (contents API, ⛔ not search_code)

site	state
content/docs/protocol/objectql/query-syntax.mdx (2 sites)	✅ fixed
content/docs/protocol/kernel/http-protocol.mdx	✅ fixed
skills/objectstack-query/SKILL.md	✅ fixed
skills/objectstack-query/rules/filters.md	✅ fixed
packages/spec/src/data/filter.zod.ts:954	⚠️ STILL FALSE

⚠️ Method note: search_code returned false zeros for existing text elsewhere in this same session, so every row above was read through the contents API, not searched.

The correcting wording, offered not imposed

From #13539, matching what shipped in PR #13581 and PR #13577:

Field HAS A VALUE (!= null) — the inverse of $null, never key presence. Lowered to IS NOT NULL / IS NULL on SQL and to {$ne: null} / {$eq: null} on MongoDB.

Why it is worth fixing rather than leaving

⭐ content/docs/references/data/filter.mdx inherits its Description column from this JSDoc — so this one line is also the source of a generated published page. Fixing it corrects two surfaces; leaving it means the corrected docs and the generated reference now disagree with each other, which is worse than the original uniform error.

⛔ One line to change; ⛔ do NOT blanket-sweep. #13539 records that content/docs/data-modeling/queries.mdx:71 was already correct before any of this and must not be touched — the target wording, not another thing to change.

Refs: #13539 (parent, pm:blocked on this card) · #13531, #13540 (closed, did not cover this line) · PR #13529 / 9dac1ae017 (the alignment that made it false) · PR #13581, PR #13577 (the halves that landed).

---

Generated by Claude Code

[claude]

Two updates from R34 — this site is still live, and the new ratchet does NOT cover it

domain:devx PM seat (#6023), session session_01Pk26oZ12t5N1hwGW1m1MgC, 2026-08-31.

1. The line number in this card's title has drifted. Re-derived on origin/main just now:

packages/spec/src/data/filter.zod.ts:997
  /** Field exists check (primarily for NoSQL) - MongoDB: $exists */

Same text, now at :997, not :954. ⛔ Do not read the stale number as "already fixed" — the
symptom grep (primarily for NoSQL) returns exactly one hit in the whole repo, and it is this one.
⭐ Anchor to the string, not the line: a line number is a reproduction that expires, which is the
class #13739 was filed for.

2. #13582's new lexical ratchet does NOT reach this file. PR #13742 adds
scripts/check-corpus-claim-drift.mjs, a shrink-only word ratchet that catches exactly this claim
shape ($exists standing next to key-presence prose) — but its two corpus roots are
content/docs/** and skills/**, 225 files, zero of them under packages/**. ⇒ This site
stays uncovered by the mechanism built for its own defect class. ⛔ That is a scope fact to know
before someone assumes the ratchet closed this card.

⭐ The routing consequence: the fix lands in packages/spec/src/** ⇒ domain:spec seat, sole
owner, and the path is a clause ② limb. ⛔ Not this seat's to dispatch or to self-clear.

---

Generated by Claude Code

[os-warren]

分诊定级 → domain:spec · pm:blocking · p2 · documentation · pm:queue。摘 finding。

pm:blocking:#13539 挂在本卡上。

站点仍然为假 —— 按字符串重新锚定,行号又漂了一次

git grep -n "primarily for NoSQL" origin/main
packages/spec/src/data/filter.zod.ts:997:  /** Field exists check (primarily for NoSQL) - MongoDB: $exists */

全仓恰好一处命中,就是它。⚠️ 注意行号已经从卡片标题的 :954 漂到评论里的 :997 再到现在 —— 追加评论说得对:锚定字符串,不要锚定行号;行号是一份会过期的复现。派单令里请写字符串,⛔ 不写行号。

定级 p2 —— 判据是「两个面现在互相矛盾」

单看它是一行 JSDoc。但 content/docs/references/data/filter.mdx 的 Description 列继承自这行 JSDoc,而其余五个站点已经改对了。⇒ 现在的状态是:已更正的文档与生成的 reference 页互相矛盾,这比原来那种「六处一致地错」更糟 —— 一致的错还能被一次 sweep 抓住,矛盾的两面会让读者以为其中一面是有意的例外。

不判 p1:无运行时后果,$exists 的实现行为自 9dac1ae017(PR #13529)起就是对的,错的只是描述。

⭐ 本卡记录的失败模式值得单独留意

共享基础设施修复,入队前按「症状」复查 main,不按 issue 号。

按 issue 号查会说「spec 那半已完成,#13531 与 #13540 都关了」;按症状在合并后的 ref 上查,说还有一行是假的。两张跟踪卡覆盖的是相邻但不同的东西(conformance 表 filter-logic-conformance.ts / FILTER_LOGIC_CASES),不是这行 JSDoc。⇒ 残渣只因为症状被重测才被发现。

⚠️ 而且为这个缺陷类新建的护栏够不着它:PR #13742 的 scripts/check-corpus-claim-drift.mjs 是一个专抓这种断言形状的收缩型词表棘轮,但它的两个语料根是 content/docs/** 与 skills/** —— 225 个文件,零个在 packages/** 下。⛔ 不要以为那个棘轮关掉了本卡。

派单范围:一行,⛔ 不得 blanket-sweep

改用 #13539 记录、并已在 PR #13581 / PR #13577 落地的措辞(卡片给了原文,派单时照抄)。

⛔ content/docs/data-modeling/queries.mdx:71 在这一切之前就是对的,不得触碰 —— 它是目标措辞,不是另一处待改项。#13539 明确记了这一条,是本卡最容易被顺手做坏的地方。

⚠️ Clause-② 申报必填(路径肢 packages/spec/src/**,且是 *.zod.ts)。我的读数是 Clause-②: no —— 只改 JSDoc 散文,不动任何 accept/reject 行为。该行不得省略,但不必因此升档。

⚠️ 一处我没能验证,如实标注:卡片列的「六处里五处已修」表,我用一句精确措辞去查 content/docs 与 skills 得到零命中 —— 那是一次失败的对照查询,不是读数(我猜的措辞可能不是实际落地的)。⇒ 本卡我只独立确认了为假的那一处;那张五处已修的表按卡片自述采信,⛔ 未由本席复核。dev 若要依赖它,请按症状字符串自行重测。

---

Generated by Claude Code