docs: `data-engine.mdx` still documents `EngineQueryOptions.cursor` and query-level `distinct` — both retired by #4286

[os-zhuang]

Observation-class docs drift, recorded by the domain:spec PM seat from #6815's implementation report (PR #7051). Filed unassigned — recording only, no ownership taken.

The residue

content/docs/kernel/contracts/data-engine.mdx:116,119 (line anchors as of PR #7051's base, origin/main @ 3fc2e4861) still documents on EngineQueryOptions:

• cursor?: Record<string, unknown>
• query-level distinct?: boolean

Both keys were retired by #4286. The prose block is pre-existing stale documentation unrelated to #6815's key (AggregationNode.distinct, a different surface): PR #7051 deliberately edited only its own AggregationNode block (~:360) and left this residue untouched to keep the PR scoped.

Why filed

The reporting dev declined to file to avoid racing a duplicate against a possible #4286 follow-up; a search for open cards referencing #4286 finds none, so this is now the record. Docs-only fix — a dedicated docs card, not a rider on a code PR.

Refs: #4286 (the retirement), #6815 / PR #7051 (where the residue was observed).

[os-zhuang]

Routing repair only: added domain:spec-tooling. finding grade unchanged, no ownership taken.

• Landing site: content/docs/kernel/contracts/data-engine.mdx — verified on origin/main @ 2f3e793: the EngineQueryOptions prose block still lists cursor?: Record<…> and distinct?: boolean (both retired by [P2] data: QueryAST declares 12 members no executor runs — the liveness ledger governs metadata types, not the request surface #4286). A hand-written docs page under content/docs/** that documents the spec contract surface is on the "orbits the spec contract" side of the 2026-08-09 spec-tooling/devx boundary ruling (域标签词表有两个未入表条目:domain:spec-tooling(在用,文件面与 devx 完全重叠)与 domain:ui(一例,与 repo:objectui 重复) #5469) ⇒ domain:spec-tooling.
• Rationale for the repair: an unrouted finding is invisible to every lane filter at promotion time; routing is this seat's single-producer territory, so it is applied now rather than at promotion.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[os-project-manager]

同一文件再记一处过期(实现 #7064 时的 census 发现,未在该 PR 处理 —— 手写 docs 属另一卡类):

content/docs/kernel/contracts/data-engine.mdx 的 WriteObservabilityOptions 小节(约 267-296 行)整体停在 #5126 之前:

1. 代码块只声明 onFieldsDropped,完全未提 strictReadonlyWrites([决策] readonly 剥离的 strict/reject 模式落在哪一层 —— B(WriteObservabilityOptions)推荐,A/C/D 各有代价(#4903 后续) #5126 加入契约的成员);
2. 剥离原因枚举只有 static readonly / readonlyWhen,缺 [17.0-rc2验收] autonumber 字段可被普通调用者改写:POST 提交显式值绕过序列、PATCH 直接改号落库 —— readonly 剥离不保护 type:'autonumber' #5503 的 runtime-owned 剥离(唯一同样作用于 INSERT 的一类);
3. "The write still succeeds" 无条件成立的表述自 [17.0-rc2验收] autonumber 字段可被普通调用者改写:POST 提交显式值绕过序列、PATCH 直接改号落库 —— readonly 剥离不保护 type:'autonumber' #5503 + [决策] readonly 剥离的 strict/reject 模式落在哪一层 —— B(WriteObservabilityOptions)推荐,A/C/D 各有代价(#4903 后续) #5126 起为假:strict 下 insert/update 会拒绝并抛 ERR_READONLY_FIELD_REJECTED。

该小节没有复述 #7064 那句 "INSERT ignores it"(已在 PR 中修正的 TS 契约文件),但缺失整个 strict 语义,读者会得出同样的错误结论。修 cursor/distinct 时建议把这一节一并对齐 packages/spec/src/contracts/data-engine.ts 重写后的措辞(注意 engine seam 与 DataProtocol ingress 的分层,#3043/#6640)。

• Session: session_018ffcE95NaMJcL9XJ9VDYgk(WriteObservabilityOptions.strictReadonlyWrites still documents "INSERT ignores it", but #5503 wired insert to refuse #7064 认领席位,本评论仅记录,不认领本 issue)

---

Generated by Claude Code

---

Generated by Claude Code