[finding] The dissolved #5499 freeze is still asserted in the PRESENT TENSE at ~13 more in-code sites — including three design rationales that rest on it as a live constraint

[os-litant]

Found while doing #13089 (which is scoped to exactly four named sites — two pm-dispatch reference files, two in-code pin annotations). A full-tree sweep for the anchor shows the residue radius is roughly four times what that card names. #13089 is not addressed wider by this finding; it stays scoped to its four sites.

Dissolution evidence, on disk: head note of packages/spec/src/data/aggregation-conformance.ts — "the maintainer lifted the #5499 investment freeze for driver-mongodb on 2026-08-11 and for driver-memory later the same day".

Swept at 56470d86b with grep -rn 5499 packages --include=*.ts, CHANGELOGs excluded. Triage needs to separate three kinds, because they are NOT one repair:

A. Present-tense claims that the freeze is in force — plainly false now

• packages/objectql/src/engine.ts:4465 — "packages/drivers/** is under the [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 investment freeze, so that work is not this change's to do."
• packages/objectql/src/engine-autonumber-resync.test.ts:683 — "packages/drivers/** is under the [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 freeze"
• packages/objectql/src/temporal-comparand-door.ts:60 — "under the [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 investment freeze"
• packages/objectql/src/search-filter.ts:34
• packages/objectql/src/filter-comparand-shape.ts:14 — points at "the [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 freeze argument"
• packages/runtime/src/package-service.null-seam.test.ts:20 — "a package whose investment is frozen ([裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499)"
• packages/spec/src/data/index.ts:11 — "drivers ([裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499)"
• packages/spec/src/data/filter-logic-conformance.ts:179 (measurement-table cell "no — DIVERGENT, frozen ([裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499)"), :202 ("two backends inside the [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 investment freeze"), :212 ("both frozen by [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499")

B. The three that are more than stale prose — a live design rationale on a void premise

These do not merely mention the freeze; they use it as the REASON for a structural choice, so re-reading them today yields an argument whose premise is gone:

• packages/spec/src/data/filter-comparand-type.ts:29 — "…are under the [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 investment freeze, so the policy cannot be grown per driver; it is promoted here, to the face the SQL family already…"
• packages/spec/src/data/filter-comparand-shape.ts:42 — "([裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499), so the policy cannot be grown per driver."
• packages/spec/src/data/filter-comparand-type-conformance.ts:29 — "This is how the frozen drivers ([裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499) inherit the policy without a driver-local patch."

Worth a judgement rather than a search-and-replace: promoting the policy to the spec face may well still be the right shape on its own merits, but the recorded justification is now unsound, and the next reader deciding where a comparand policy belongs will read a constraint that no longer exists. Either the rationale is restated on surviving grounds or the decision is re-opened — silently deleting the clause loses the fact that it was ever argued.

C. Dated / historical records — probably correct as they stand

Listed so a sweep does not "fix" them: they are frozen-in-time records, not present-tense claims.

• packages/runtime/src/autonumber-seed-cross-side-parity.integration.test.ts:72,76 and packages/runtime/src/sandbox/undeclared-field-write-driver-split.integration.test.ts:87 — both quote the dated maintainer ruling 「[裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 冻结令冻的是缺陷修复投入,不禁止作参照物使用」 (2026-08-06) to justify using driver-memory as a reference implementation. The conclusion survives the dissolution; only the premise is moot.
• packages/objectql/src/having-filter.ts:116 — "The [裁决] driver-memory / driver-mongodb 投入冻结 —— 维护者 2026-08-05 口径（跨单锚点） #5499 freeze was lifted for this operator as a sanctioned one-off (maintainer ruling, 2026-08-08)". Already past tense and dated; now merely superseded by the full 2026-08-11 dissolution rather than wrong.
• packages/spec/src/migrations/entries/semantic/17.aggregation-node-distinct-retired.ts:32, 17.query-array-string-agg-retired.ts:24, 17.driver-sql-distinct-bare-filter-typed.ts:44 — ADR-0087 retirement records, authored at their retirement date.

⚠️ packages/spec/src/migrations/registry.ts:1252,1273,1696,2797,4049 carries the same five strings but is GENERATED (pnpm --filter @objectstack/spec gen:migration-registry) from the entries/ files above. Hand-editing it would be reverted by the generator and would trip check:migration-registry.

Note on datasource-autoconnect.test.ts

packages/runtime/src/datasource-autoconnect.test.ts:19 says "surface is being retired (#5499)" — a RETIREMENT claim, not a freeze claim. It cites the same anchor for a different proposition and needs checking on its own terms rather than being swept with the rest.

Related

• The dissolved #5499 investment freeze is still spelled as LIVE in pm-dispatch references and two in-code pin annotations — same staleness class #12672 fixed, wider radius #13089 — the four-site card this was found from; open.
• 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 #13166 — the domain:engine divergence split out of The dissolved #5499 investment freeze is still spelled as LIVE in pm-dispatch references and two in-code pin annotations — same staleness class #12672 fixed, wider radius #13089's sites 3-4, which is what filter-logic-conformance.ts:179 above is the table cell for.

Generated by Claude Code

[huangyiirene]

定级：pm:queue · domain:spec · documentation · priority:p2。finding 已离标。

车道：本卡站点跨三个包——packages/objectql（domain:engine）、packages/runtime（domain:cli）、packages/spec（domain:spec）。判 domain:spec，理由是实质的那一半（B 组）全部在 packages/spec/src/data/，A 组的散文清扫是同一次机械动作里的跨车道搭车项。⛔ 不拆卡：三组都是注释/散文编辑，工作同形（对照 #13072 拆卡的判据是"工作是否同形"，那张不同形，这张同形）。

⛔ 派发围栏——按 A / B / C 分别执行，⛔ 绝不是一次 sed

A 组（~10 处现在时假claim）：机械改写。⛔ 但仍逐处读——立卡人已经指出 datasource-autoconnect.test.ts:19 说的是"surface is being retired (#5499)"，那是一个退休命题不是冻结命题，同一个锚点、不同的主张 ⇒ 必须按自己的条件核，⛔ 不得随 A 组一起扫。

B 组（3 处设计理由）：⭐ 这一组不是散文修复，是判断。 它们不是"提到冻结"，而是用冻结当作某个结构选择的理由："…are under the #5499 investment freeze, so the policy cannot be grown per driver"。前提没了，论证就悬空了。

⇒ 派发范围写死为：若这三条理由在去掉冻结前提后仍然成立，就以幸存的理由重述；⛔ 若实施者发现去掉冻结后理由不成立，停手、回填说明 —— 重开一个设计决定不是开发席位的事，那是人工地板。⛔ 也绝不允许静默删掉那个从句：卡说得对，删掉就丢失了"这件事曾被论证过"这个事实。

C 组（dated / 历史记录）：⛔ 一处都不要动。 它们是时间点记录，不是现在时主张。卡把它们列出来正是为了让清扫不要"修"它们。

⚠️ 最容易踩、也最贵的一条

packages/spec/src/migrations/registry.ts:1252,1273,1696,2797,4049 携带同样的五个字符串，但它是生成物（pnpm --filter @objectstack/spec gen:migration-registry）。

⛔ 手改会被生成器回滚，并且会踩 check:migration-registry。 一次 grep -rn 5499 packages 会把这五处交到实施者手里，看起来和 A 组一模一样。这是本卡里唯一一处"照着做就会出事"的地方，请在动手前先确认自己的 grep 结果里排除了 registry.ts。

与 #13089 / #13166 的关系（已核，⛔ 不去重）

• The dissolved #5499 investment freeze is still spelled as LIVE in pm-dispatch references and two in-code pin annotations — same staleness class #12672 fixed, wider radius #13089（domain:skills，已派发）严格限定在四个命名站点（两个 pm-dispatch reference 文件 + 两处 in-code pin 注解）。本卡明确不扩大它。⇒ 两张卡不重叠，The dissolved #5499 investment freeze is still spelled as LIVE in pm-dispatch references and two in-code pin annotations — same staleness class #12672 fixed, wider radius #13089 保持原范围。
• 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 #13166（domain:engine）是从 The dissolved #5499 investment freeze is still spelled as LIVE in pm-dispatch references and two in-code pin annotations — same staleness class #12672 fixed, wider radius #13089 站点 3-4 拆出的行为分歧，而本卡 A 组里的 filter-logic-conformance.ts:179 正是那个分歧的表格单元格。⇒ 若 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 #13166 先落地改变了那个分歧的事实，本卡该单元格的正确措辞会随之改变。⚠️ 实施者请先看 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 #13166 的状态，⛔ 不要在 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 #13166 未定时把那一格写死。

⭐ 立卡人的普查是有分母的（grep -rn 5499 packages --include=*.ts @ 56470d86b，排除 CHANGELOG），且主动把结果分成了"不是一种修复"的三类——这是本轮质量最高的一张卡之一。分成三类这件事本身就是它最大的价值：一个只报"13 处残留"的卡会诱使下一个人写一次 sed，而那会同时改坏 C 组和生成物。

---

Generated by Claude Code

[os-trump]

Claim: PM loop round R7 (domain:spec seat)
Session: session_01LpRNHxWZgSUgVnFT9mQQo4
Branch: claude/issue-13168-dissolved-freeze-residue
Worktree: objectstack-issue-13168
Domain: domain:spec (per triage 5461079859 — the substantive half is entirely in packages/spec/src/data/; the group-A prose sites in packages/objectql / packages/runtime ride along as one mechanical pass, ⛔ card not split, that reading is triage's and is not re-litigated here)
File surface: the group-A present-tense sites (objectql/src/engine.ts, engine-autonumber-resync.test.ts, temporal-comparand-door.ts, search-filter.ts, filter-comparand-shape.ts; runtime/src/package-service.null-seam.test.ts; spec/src/data/index.ts, data/filter-logic-conformance.ts), the group-B design rationales (spec/src/data/filter-comparand-type.ts, filter-comparand-shape.ts, filter-comparand-type-conformance.ts), and nothing else. ⛔ Group C is not touched. ⛔ spec/src/migrations/registry.ts is a GENERATED artifact carrying the same five strings — excluded from the surface; hand-editing it is reverted by the generator and trips check:migration-registry. Stop on breach; explain in the report.
Container & model: M, mode:subagent, model: claude-opus-5 — Clause-② PATH leg only (the diff touches packages/spec/src/**, so needs:contract-review attaches and the review is parked); CONTENT leg: no — comment and doc prose only, no accept/reject movement, no public-surface change. Fable is not mandatory on this card's own merits and ⛔ no quota exemption is invoked for it.
Route (per triage, binding): A = mechanical rewrite but read each site — runtime/src/datasource-autoconnect.test.ts:19 says the surface "is being retired (#5499)", a RETIREMENT proposition on the same anchor, ⛔ never swept with the freeze claims, judged on its own terms. B = judgement, not prose repair: restate each of the three rationales on surviving grounds if they still hold; ⛔ if a rationale does NOT survive losing the freeze premise, STOP and report — re-opening a design decision is the human floor, not a dev seat's; ⛔ never silently delete the clause (deleting it loses the fact that it was ever argued). C = ⛔ do not touch; the card lists them precisely so a sweep does not "fix" dated records.
Serial constraints cleared: no in-flight claim touches these files (#13135 = kernel/metadata-* + api/metadata + contracts/ + packages/metadata; #13138 = ui/view.zod.ts; the parked #13151 = data/driver/*, data/object.zod.ts, ui/component|action|dashboard|app — disjoint from the data/filter-* and data/index.ts sites here). ⚠️ Cross-card ordering: #13166 (domain:engine) owns the behavioural divergence whose table cell is filter-logic-conformance.ts:179 — the dev reads #13166's current state first and ⛔ does not pin that cell's wording while that card is undecided.

---

Generated by Claude Code

[os-trump]

Dev seat claiming this card.

• session: session_01LpRNHxWZgSUgVnFT9mQQo4
• branch: claude/issue-13168-dissolved-freeze-residue
• worktree: ../objectstack-issue-13168 (shared checkout never edited)

Starting with the card's A/B/C split as the spec: A = present-tense false claims (mechanical, but read every site), B = design rationales resting on the dissolved premise (judgement; stop and report any rationale that does not survive), C = dated/historical records (untouched). packages/spec/src/migrations/registry.ts is generated and excluded from the sweep.

---

Generated by Claude Code