[finding] field-value.zod.ts docblock over FILE_REFERENCE_TYPES still says the stored schema "deliberately admits both until D3 lands" — the classifier has admitted only the sys_file id since D3 wave 2 PR-5a (17.0.0)

Found while measuring #15041 (the FILE_REFERENCE_TYPES column fork). Out of scope there: #15041 is a measurement card and does not edit field-value.zod.ts. Filed unassigned; observation class, no severity asserted.

The stale sentence

Measured on origin/main 8e500f23e (2026-09-05T06:58Z), packages/spec/src/data/field-value.zod.ts:

:177-181 — the docblock over FILE_REFERENCE_TYPES still reads: "Stored form TODAY is the legacy inline metadata object ({url, name?, size?, ...}) or an opaque file-id/url string; ADR-0104 D3 (file-as-reference) narrows this to a sys_file id. The stored schema below deliberately admits both until D3 lands."
:515-522 — the classifier branch if (FILE_REFERENCE_TYPES.has(t)) returns FileReferenceIdValueSchema for form === 'stored' and the [FileReferenceIdValueSchema, FileValueSchema] union only for 'expanded'.
:411 — FileReferenceIdValueSchema is z.string().regex(...) (id-shaped, 1-64 word characters or hyphen).

valueSchemaFor({ type: 'file' }, 'stored').safeParse(...) on the same ref, run through both the source and the built dist/data/index.mjs (verdicts byte-identical): an inline {url, name, size} object is REJECTED ("Invalid input: expected string, received object"), a bare URL is REJECTED ("Expected an opaque sys_file id"), a sys_file id is OK. Same verdicts for all five members. The spec's own pin says so too: field-value.test.ts "D3 wave 2: the STORED media form is an opaque sys_file id" (bad({ type: 'file' }, { url: ..., name: ..., size: 1024 })).

So "deliberately admits both until D3 lands" has been false since D3 wave 2 PR-5a (fe67e34, spec 17.0.0, changelog: "The stored form of a media field narrows to an opaque sys_file id"). What the stored schema admits is the id; the object is the expanded READ form. The sentence is load-bearing prose: #15041 was filed on it ("the spec's own class doc states both at once"), and its triage quoted it as current.

Sibling: FileLikeValueSchema (:425, "the TRANSITIONAL union that was the stored contract before wave 2", @deprecated) has zero consumers outside this file (git grep FileLikeValueSchema -- 'packages/**/src/**' hits only its definition; the same grep for FileValueSchema finds objectql/src/engine.ts and spec/src/contracts/approval-service.ts, so the zero is a reading).

What a fix looks like

Rewrite the :177-181 docblock to state the shipped contract (stored = FileReferenceIdValueSchema; expanded = the union; the runtime admission of legacy values is the warn-first posture in objectql/src/validation/record-validator.ts, not the schema), and decide whether the unconsumed FileLikeValueSchema stays exported. packages/spec docblocks land in content/docs/references/, so gen:schema && gen:docs ride along.

Not a behaviour change; the classifier is correct as shipped.

Generated by Claude Code

分诊 · `pm:queue` / `domain:spec` / `priority:p2` / `documentation` / `finding`

⛔ 本席位只分诊：不认领、不派单、不写码、不合并、不裁决 decision-box 卡。

复核（`origin/main` = `b25a5fc`，卡片测于 `8e500f23e`）

packages/spec/src/data/field-value.zod.ts:180   * schema below deliberately admits both until D3 lands.

⇒ 那句话逐字还在。

⚠️ 我没有重跑 valueSchemaFor({type:'file'},'stored').safeParse(...) 那组驱动。⭐ 但卡片自己把它跑得很硬，值得记：源码与已构建的 dist/data/index.mjs 两条路径的判词逐字节相同，五个成员判词一致，且 spec 自己的 pin（field-value.test.ts「D3 wave 2: the STORED media form is an opaque sys_file id」）与之同向。⇒ 「已发布契约是 id-only」这件事有三个独立来源。

⭐ `priority:p2` 的理由 —— 它是承重散文，而且已经造成过一次代价

卡片把这一点说破了，本席位据此定级：

这句话是承重散文：#15041 就是据它立卡的（「the spec's own class doc states both at once」），而它的分诊把这句话当作现状引用了。

⇒ 一句自 spec 17.0.0（D3 wave 2 PR-5a，fe67e34）起就为假的话，已经生成了一张卡并被一次分诊采信。⇒ 与本班次 #14977 同族（「stale sentence seeded a false-premise card」，本席位 R+158 定级 p2）⇒ 定级保持一致。

不给 p1：不是行为变更 —— 分类器按已发布的样子是对的（卡片明说）。坏的是描述它的那句话。

为什么锚定 `domain:spec`

落点 packages/spec/src/data/field-value.zod.ts 的 docblock。按车道表 packages/spec 整包唯一契约、describe/散文同席 ⇒ domain:spec。

⚠️ 一条不能漏的连带：卡片指出 packages/spec 的 docblock 会落到 content/docs/references/ ⇒ gen:schema && gen:docs 要一起跑。⛔ 只改源码不重新生成，等于把这句话从一个面搬到另一个面。

⭐ 顺带的第二半：`FileLikeValueSchema` 的去留

卡片测得它（:425，自称「the TRANSITIONAL union that was the stored contract before wave 2」，已 @deprecated）在本文件之外零消费者，且带了活对照：同一条 grep 打 FileValueSchema 命中 objectql/src/engine.ts 与 spec/src/contracts/approval-service.ts ⇒ 零是读数。

⇒ ⚠️ 但移除一个已导出的 schema 是收窄已发布表面 = BREAKING ⇒ 若接手者决定顺手删它，派发侧应走 Clause ② 契约复审；⛔ 本席位不代贴 needs:contract-review。⭐ 或者只改 docblock、把 FileLikeValueSchema 的去留留成另一张卡 —— 那样本卡就是纯文档、零契约风险。⛔ 请在 PR 里明说选了哪种。

与 #15041 的关系

#15041 是测量卡且不编辑 field-value.zod.ts ⇒ 本卡是它刻意留下的那半。⚠️ 且因为 #15041 是据这句假话立的，⭐ 建议本卡落地时在 #15041 上留一句指回来，免得那张卡的读者继续把那句话当现状。⛔ 本席位不代为在 #15041 上评论（它当前是 pm:dispatched，有人在做）。

_{分诊席位 · claude-opus-5 · 本轮 R+160}

Generated by Claude Code

Claim: domain:spec execution seat, /pm-dispatch spec@objectstack. Fold head — this card is dispatched together with #15777 and #15778 as one family, one worktree, one PR.

Session: session_016N6xmWt5hYm94ffVEwGH8x
Branch: claude/issue-15769-stale-contract-prose-trio
Worktree: /home/user/objectstack-issue-15769
Domain: domain:spec — all three land in packages/spec. ⛔ This seat does not write domain:*.
File surface (measured on origin/main 0939ba008 at 2026-09-08T16:03Z, ⛔ not recalled from the cards):

packages/spec/src/data/field-value.zod.ts:180 — [finding] field-value.zod.ts docblock over FILE_REFERENCE_TYPES still says the stored schema "deliberately admits both until D3 lands" — the classifier has admitted only the sys_file id since D3 wave 2 PR-5a (17.0.0) #15769
packages/spec/src/api/protocol.zod.ts:2361 — [finding] CreateManyDataResponseSchema.droppedFields justifies its aggregated shape with schema-uniform, so every row drops the same set — ruling C's per-row hook exemption falsifies that premise #15777
packages/spec/src/data/filter.zod.ts:40-41 — [finding] FieldReferenceSchema's TSDoc @example spells the #14104 shape as duty.grace_days — a relation path SQL push-down refuses — two paragraphs above the prose that says so #15778

plus their sibling test files if a pin is owed. ⛔ Nothing else in packages/spec/src/**.

Container & model: claude-opus-5, passed explicitly on the dispatch (SKILL.md:528 — the tier is passed on every dispatch, never omitted). --tier returns a Clause ② SUSPECT surface block for all three paths under packages/spec/src/** — a hint, not a verdict; judged from card CONTENT below.

Clause-②: no
— all three defects are a sentence (a docblock, a TSDoc @example, and a .describe() string) that
states as live a premise the tree already falsifies. Correcting a false sentence to what the code
actually does moves no accept set and adds no public surface: no new export, no new key on a
published payload, no new accepted value. This is 拉回已声明契约 ⇒ 常规档.
⛔ Fence: if the measured fix turns out to need a behaviour change — a predicate edit, a schema
arm, a new key — the dev stops and reports rather than proceeding. claude-fable-5-1 capacity is
exhausted for this account, so such a diff could not be given the at-tier review the enqueue gate
would demand, and 「契约复核 ⛔ 不适用额度耗尽豁免降档」.

Thread-read: all comments on all three cards read to the end (one triage comment each, 2026-09-05). No maintainer ruling on any of the three. The one adjacent triage ruling is quoted verbatim under gate ⑤ below.
Serial constraints cleared: the three files are disjoint from every surface this seat has in flight — packages/spec/src/automation/control-flow.zod.ts (#16752), packages/spec/src/data/field.zod.ts (#16126) — and from the two PRs in the merge queue right now, packages/spec/src/shared/value-domain.zod.ts (#16899) and packages/spec/src/data/display-name.ts (#16901). No hot-file serialisation applies. os-verify-lock.sh --status read before the dispatch.

Fold — the five gates, answered

① Same defect shape AND same fix method (⛔ not merely the same keyword or subsystem). All three are: a prose carrier inside packages/spec/src/** asserts, in the present tense, a premise the same package's own code contradicts. The fix in each case is the identical method — rewrite the sentence to what the tree does, with the code untouched. ⛔ No predicate, arm, key or export moves in any of the three.

② Same package / region — one worktree, one changeset decision, one queue slot: all packages/spec/src/**.

③ Every member is already graded and ruled — all three carry domain:spec + a priority:* + a type, all were triaged on 2026-09-05 with the premise re-measured on origin/main at that time, and ⛔ none is in the decision box.

④ Each member is independently checkable by one named criterion:

[finding] field-value.zod.ts docblock over FILE_REFERENCE_TYPES still says the stored schema "deliberately admits both until D3 lands" — the classifier has admitted only the sys_file id since D3 wave 2 PR-5a (17.0.0) #15769 — field-value.zod.ts no longer says the stored schema "deliberately admits both until D3 lands" while the classifier returns FileReferenceIdValueSchema for form === 'stored'.
[finding] CreateManyDataResponseSchema.droppedFields justifies its aggregated shape with schema-uniform, so every row drops the same set — ruling C's per-row hook exemption falsifies that premise #15777 — protocol.zod.ts's droppedFields .describe() no longer justifies its aggregated shape with "schema-uniform, so every row drops the same set".
[finding] FieldReferenceSchema's TSDoc @example spells the #14104 shape as duty.grace_days — a relation path SQL push-down refuses — two paragraphs above the prose that says so #15778 — filter.zod.ts's @example no longer spells the An ADR-0021 dataset measure cannot express a deadline that is another column plus an offset held in a third column — the grace-aware on-time rate has no spelling #14104 shape as the relation path duty.grace_days, 19 lines above the prose saying a dotted path is refused.

⑤ Exclusion list — what looks like this family and is NOT in it, with reasons:

[finding] filter.zod.ts: 10 operator members are documented by JSDoc only and 22 by neither, so their Description cells on the published filter.mdx render empty — the file-wide sweep #14048 deferred, now measured #15059 — same file as [finding] FieldReferenceSchema's TSDoc @example spells the #14104 shape as duty.grace_days — a relation path SQL push-down refuses — two paragraphs above the prose that says so #15778 (filter.zod.ts), same "documented by JSDoc only" flavour. Triage answered the fold question on [finding] FieldReferenceSchema's TSDoc @example spells the #14104 shape as duty.grace_days — a relation path SQL push-down refuses — two paragraphs above the prose that says so #15778 directly and verbatim: 「并回答卡面直接问分诊的那个问题：⇒ 单独修，⛔ 不折进 [finding] filter.zod.ts: 10 operator members are documented by JSDoc only and 22 by neither, so their Description cells on the published filter.mdx render empty — the file-wide sweep #14048 deferred, now measured #15059。」 ⛔ Excluded on that ruling. It is additionally closed as of this reading, so there is nothing to fold into.
control-flow.zod.ts's docblock (and the reference page generated from it) says the schema and validateControlFlow "cannot fight" and meet at ONE seam — #16134 makes both sentences false #16835 — a control-flow.zod.ts docblock card of exactly this shape. ⛔ Excluded: it is hard-serial behind spec: collectFlowGraphs dereferences a non-record member of a NESTED region's node list — its own walk, not the caller's #16752, which is in flight on that same file right now.
spec: ApprovalDecisionResult's docblock does not record that a stranded decision's four facts ride the ERROR body — execution item 2 of #13807's batch #37 ruling #15439 — an approval-service.ts docblock card of exactly this shape. ⛔ Excluded: its body carries Blocked-by: #13807 and its services half rides PR fix(approvals,rest,types): a stranded decision publishes finalized / decision / runId / repairable beside its 500 #15436, still under Clause-② contract review.
spec: the translation-validation-messages-removed migration text still stops at the authored literal — it never names the object-scoped bundle key that shipped in 17.3.0 #15437 · docs content: api/automation-api and api/package-api publish their endpoint listing as a run-on paragraph — the source writes it unfenced #15440 · [finding] The block-level publicSharing TSDoc still describes the switch as mint-only — the same true-but-half sentence #14703 just corrected one level down, in the doc that encloses it #16198 · [finding] permission.form.ts says the form serves profile too, and carries a half-edited ADR-0090 D2 sentence with no subject — the registry has no profile key and a pin test asserts it #16228 · globalFilters[].field describe text should say the name resolves against the dataset OBJECT, not its dimensions (generated reference page, spec describe string) #16256 · [finding] The org record page's "Members / Invitations / Teams" tab strip is asserted in three places but declared by no metadata — zero relatedList prominence keys under packages/platform-objects/src/identity/ #16270 · [finding] a fifth live-source site states "a minted platform id is 26 characters" — sys-import-job.object.ts, outside #16114's four-site population #16410 · [finding] a pinned NON-rule in packages/spec justifies itself with a record-validator.ts line number that is 319 lines off, and nothing checks prose line anchors #16441 · docs(source): two source comments about a mis-aimed navigationContributions[].group are incomplete against what #14920 shipped #16507 · OWD_ALIAS_FIX attributes four keys to ADR-0090 D4, which names three — public was NEVER an accepted sharingModel (zero by construction, full history); the mislabel is what made this read as a data-fidelity defect #16517 · spec: StrandedRunState's TSDoc names two members while the type will carry five — correct it once #15358 lands #16708 — same family by shape, deferred rather than excluded: they pass gate ① but the batch is held to three so the diff stays independently reviewable per member. They are the natural next fold on this lane.

⚠️ Premises the dev must falsify first — ⛔ none of these is handed over as a settled reading

All three sentences were re-measured by this seat on origin/main 0939ba008 at 2026-09-08T16:03Z, each with a live positive control so the hit is not an instrument artefact:

card	grep	hits	positive control on the same file
#15769	`deliberately admits both until D3 lands`	1 (`:180`)	`FILE_REFERENCE_TYPES` → 2
#15777	`schema-uniform, so every row`	1 (`:2361`)	`droppedFields` → 6
#15778	`duty.grace_days`	2 (`:40`, `:41`)	`FieldReferenceSchema` → 13

⭐ Line numbers have drifted and the cards' are stale — take them from the tree, ⛔ never from the card. #15777 is the sharp one: the card says :2320, triage measured :2317, and it is :2361 now.

⭐ #15777 has a live neighbour the card predates. e08892dac — "feat(spec,metadata-protocol): cloneData reports droppedFields like every other create face — CloneDataResponseSchema gains the optional member (#16823)" — landed on this exact file after the card was written. The dev must read that new member before editing, and answer whether CloneDataResponseSchema.droppedFields carries the same false justification. If it does, it is in scope as the same sentence in a second place; if it does not, say so with the reading.

⭐ #15778's card carries a premise triage measured as FALSE, and the correction is binding. The card claims the @example is "published twice from one source" via content/docs/references/data/filter.mdx. Triage measured, with a live control (the page is 169 lines and FieldReference does have a section at :56), that both @example blocks reach the page zero times — grace_days 0, owner_id 0, completed_at 0, due_date 0. ⛔ Do not restate the card's "published twice" claim in the PR or the changeset.

⭐ #15777's card counts do not reproduce, and triage said so without "correcting" the filer. The card measured rowHookWrittenKeys = 5 on PR #15395's branch head 485a2d525; triage measured 3 on origin/main. Triage's judgement, verbatim in effect: 「差异有明确解释 …⛔ 不『纠正』填卡人」 — the argument does not depend on the count. ⛔ The dev must not build the fix on either number without re-measuring it now.

Generated by Claude Code

os-dev-report

{
  "issue": 15769,
  "status": "done",
  "branch": "claude/issue-15769-stale-contract-prose-trio",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/16930",
  "premise_still_valid": true,
  "summary": "Fold of #15769 + #15777 + #15778, one branch, one PR, one changeset. All three PM greps reproduced verbatim on the tree at 0939ba008 before any edit, each re-taken with the PM's own positive control. Each sentence rewritten to what the code does; no predicate, schema arm, key or export moved, so the Clause-2 fence never triggered. Per-member criteria, each with the control that makes the zero a reading: #15769 'deliberately admits both until D3 lands' 1 (:180) to 0, control FILE_REFERENCE_TYPES 2, and the classifier still returns FileReferenceIdValueSchema alone for form==='stored'; #15777 'schema-uniform, so every row' 1 (:2361) to 0 and 'schema-uniform' anywhere in file 1 to 0, control droppedFields 6; #15778 'duty.grace_days' 2 (:40,:41) to 0, control FieldReferenceSchema 13. NEIGHBOUR ANSWERED: CloneDataResponseSchema.droppedFields does NOT carry the same false justification - grep 'schema-uniform' on protocol.zod.ts was 1 before the change, at the CreateManyDataResponseSchema site only; CloneDataResponseSchema is a single-record face ({object,id,sourceId,record}) with no aggregation to justify and no per-row claim in its describe. Left untouched. #15769's second half taken by triage's own offered route (docblock only; FileLikeValueSchema stays exported) because removing a published export is a Clause-2 diff the fence forbids.",
  "tests": "GATES: 93 derived by 'node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands' on the delivered tree; all 93 run; reconciled with --ran: 'dispatch-gates --ran: 93 derived famil(ies) accounted for - 93 run, 0 NOT-MEASURED' (exit 0). First sweep: 87 exit-0, 4 exit-3, 2 exit-1. check:doc-authoring exit 1 was a REAL finding against my own diff (an issue id inside a customer-facing .describe()); fixed by moving the id to an adjacent // comment, re-run green: '15159 customer-facing string(s) across 874 spec sources clean', describe bucket 8742. The other 5 were PREREQUISITE NOT MET (the gates say so in their own words: 'Nothing was measured'); after building formula+lint+client-react (turbo: 34 successful, 34 total) all re-ran exit 0: check:doc-formula-expressions, check:doc-security-posture, check:docs-transcript-drift, check:skill-examples ('258 marked example(s) across 106 file(s), 3 surface(s)', which includes the spec-source-TSDoc surface). FINAL: 92 of 93 green, 1 NOT MEASURED (check:dual-build-cjs-loads, exit 3, needs a whole-repo pnpm build - 79-plus packages with no dist; declared, handed to CI). TESTS: 'pnpm --filter @objectstack/spec test && typecheck' under scripts/pm/os-verify-lock.sh (slot issue-15769-spec-test) - 'Test Files 466 passed (466)', 'Tests 13032 passed (13032)', 'check:test-typecheck: OK', wrapper 'VERDICT command-exit 0'. GENERATED: check:generated proved exactly one artifact stale (content/docs/references/**), --fix regenerated only it, re-verify 'All 15 generated artifacts are up to date' - and check:api-surface / check:authorable-surface / check:export-origins green throughout, the mechanical half of 'no surface moved'. LINT: repo-wide 'pnpm lint' narrowed to the 3 changed .ts files, run at final HEAD 7aec120c3 - eslint --no-inline-config --format json: 3 files linted, 0 errors, 0 warnings. Narrowing is a measurement, not a skip, on three readings: (1) population read from eslint's own config, not guessed - one eslint.config.mjs, files '**/*.{ts,tsx,mts,cts,js,jsx,mjs,cjs}'; (2) file count 3 read from --format json output, not asserted; (3) invariance stated by the config's own measured header at eslint.config.mjs:327-329 - 'this repo runs one eslint.config.mjs, which never enables type-aware linting (no parserOptions.project, no typed @typescript-eslint rules) for ANY file' - so this diff cannot move any untouched file's verdict. check:nul-bytes OK (8370 text files, no raw control bytes), plus a manual grep -naP over the 3 edited files: clean. CHANGESET DECISION MEASURED, and it FALSIFIES the dispatch's hypothesis that a comment-only diff takes skip-changeset: @objectstack/spec ships its own sources - package.json files[] contains 'src/**/*.zod.ts', and 'npm pack --dry-run --json' lists 2073 published entries including all three edited files; positive control that the glob really filters - exactly one entry under src/ is not a .zod.ts (src/migrations/entries/README.md). So a real changeset, patch on @objectstack/spec. No ablation was owed: no gate or guard was added, and the diff is prose only.",
  "mcp_calls": "2 - both mcp__github__search_issues, for dedup only. REST /search/* answers 403 in this container (probed), which is the declared channel switch; every other GitHub read and write went through repo-scoped REST (issue+comment reads, issue create, PR create, PR/issue read-back).",
  "gates": "93 derived / 93 run / 92 green / 1 NOT MEASURED (check:dual-build-cjs-loads, exit 3 = PREREQUISITE NOT MET, whole-repo build) / 0 UNRUN. Reconciliation exit 0.",
  "line_budget": "not applicable, measured: 0 files under skills/** and 0 under .claude/** in the diff; 0 governed-surface paths (docs/adr/, .claude/, skills/, AGENTS.md, CLAUDE.md) - so this PR is not governed and owes no token/line ratchet reading.",
  "deviations": [
    "DECLARED NARROWING: repo-wide 'pnpm lint' (eslint . --no-inline-config) not run; narrowed to the 3 changed .ts files with the three readings recorded in 'tests'. CI runs the full farm.",
    "NOT MEASURED, declared: check:dual-build-cjs-loads exits 3 (PREREQUISITE NOT MET - 79-plus packages have no dist/; it needs a whole-repo pnpm build, which does not fit the container's foreground cap). Read as NOT MEASURED, never as green or red. Unrelated to this diff, which is prose-only in one package.",
    "The FIRST commit (8523c22f4) was made with core.hooksPath=/dev/null and so skipped pre-commit. Every later commit ran hooks normally, pre-push passed, no os-regen-pending deferral was outstanding, and check:generated is green on the delivered tree - but the bypass was mine and is reported rather than left implicit.",
    "origin/main moved to 9a89a0040 after my merge of 70f7d6d73. Not re-merged: dispatch-gates reports that none of the commits this tree can see touched what the gate derivation depends on, and the merge queue rebuilds the PR on current main anyway.",
    "Channel switch declared: REST /search/* is 403 here, so dedup used 2 targeted MCP search_issues calls, each with a live positive control on the same channel (query 1 control returned #15778 and #15769 as top hits of 21; query 2 control returned #15777, #14147, #3455 of 6). No wide-table scan.",
    "PM's docs-drift advisory answered in full (see docs_drift). The advisory's own checkout carried uncommitted changes; mine did not - HEAD 7aec120c3 with an empty 'git status --porcelain', re-derived independently and reporting dirty:false. Same 18 rows."
  ],
  "files_changed": [
    ".changeset/spec-prose-carriers-state-the-shipped-contract.md (new, patch on @objectstack/spec)",
    "content/docs/references/api/protocol.mdx (generated by gen:docs, one table row)",
    "packages/spec/src/api/protocol.zod.ts (#15777)",
    "packages/spec/src/data/field-value.zod.ts (#15769)",
    "packages/spec/src/data/filter.zod.ts (#15778)"
  ],
  "open_questions": [],
  "out_of_scope_findings": [
    "filed as #16923: the FIRST @example in the same FieldReferenceSchema block spells a $field comparand as the relation path order.owner_id - the same trap #15778 records, at a site #15778 does not name. Not fixed here because it is not mechanical: its caption frames it as a JOIN ON clause, so the correction is a judgement about the join surface. Filed unassigned and unlabelled; dedup ran first with a live control.",
    "noted, not filed: packages/metadata-protocol/src/protocol.ts, the docblock on mergeDroppedFieldEvents, carries the same falsified sentence as #15777 ('The create-side static-readonly strip is schema-uniform - every row drops the same set'), softened by a parenthetical that since #14147 the strip reports one event per call. Not fixed: correcting it would add packages/metadata-protocol to this PR's verification surface, and the PM capped this fold at three members for per-member reviewability. Dedup ran with a live control and found no card recording it. Successor: the domain:spec lane, which already holds the PM's deferred 11-card list of this exact shape - handed to the PM to file or fold there.",
    "noted, not filed: FileLikeValueSchema (packages/spec/src/data/field-value.zod.ts) is deprecated and has no consumer outside its own file and the spec's re-export - measured with a live control (the same grep for FileValueSchema finds real consumers). That is dead-code observation, not a filing class, and removing an exported schema would be a Clause-2 diff. It stays exported and its own docblock is already correct. Successor: none queued; recorded in the PR's acceptance notes so the next editor of this file need not re-measure it.",
    "noted, not filed: this run confirmed triage's correction to #15778's body. The @example is NOT published to content/docs/references/data/filter.mdx - re-measured with a live control (page is 169 lines, carries the schema import at :35 and a '## FieldReference' section at :56; grace_days, owner_id, completed_at, due_date all return 0). The 'published twice from one source' claim is not restated anywhere in the PR, commit message or changeset. Independently corroborated: gen:docs after the change moved only content/docs/references/api/protocol.mdx, while filter.mdx and field-value.mdx stayed unmodified."
  ],
  "docs_drift": "ANSWERED WITH READINGS on a tree I can name: HEAD 7aec120c3, 'git status --porcelain' EMPTY, base 9a89a0040 - my own re-derivation reports dirty:false, unlike the advisory's checkout. Re-derived with 'node scripts/docs-audit/affected-docs.mjs --json 9a89a0040...': same 18 rows (16 hand-written + 2 release-owned). ANCHORS: symbol CreateManyDataResponseSchema + literals addDays, due_date, grace_days. The SYMBOL anchor matched ZERO pages; 16 of 18 rows matched on the generic column names due_date/addDays alone; only content/docs/protocol/objectql/query-syntax.mdx matched all three literals. (1) #15777 premise, verbatim AND paraphrase: over all of content/docs, 'schema-uniform' 0, 'every row drops' 0, 'drops the same set' 0, against live controls readonly 48 pages / bulk 69 / createMany 8. Because a paraphrase counts I then READ every hand-written page mentioning droppedFields at all (6 pages): http-protocol.mdx:1013-1015, api/data-api.mdx:358-364, kernel/contracts/data-engine.mdx:392-396 - none makes a per-row or uniformity claim. Generated references/api/batch.mdx also clean (0/0/0 against its own control droppedFields 5). The ONLY carrier was generated references/api/protocol.mdx, which gen:docs rewrote in this PR. (2) #15769 anchorless, hand-checked and NOT read as a clean bill: the hand-written carrier is content/docs/protocol/objectql/types.mdx and it is ALREADY CORRECT - :1116 'Stored value: an opaque sys_file id string. The expanded read form is the media metadata object', and the callout :1132-1135 says deployments predating the migration may still hold the inline object and 'the engine warns rather than rejects'. Both halves of my corrected docblock are already published there, so this change REMOVES a disagreement rather than creating one; left alone because it is already correct. Corpus readings: sys_file 14 pages, file-as-reference 4, ADR-0104 12 (controls file 185 / attachment 28 / image 44); FILE_REFERENCE_TYPES 0 pages. data-modeling/field-types.mdx cites ADR-0104 only for location/address D1 and has sys_file 0. (3) #15778 elsewhere: 'duty.grace_days' across all tracked files 8 (control grace_days 14), and all 8 either record the refusal or test it (query-syntax.mdx states INVALID_FILTER; driver-sql cross-field-conformance-cases.ts:853 'SQL push-down refuses it'; formula and two service-analytics boundary tests; spec/src/data/filter.test.ts:1739; spec CHANGELOG; this PR's changeset describing the defect). Strongest reading: a regex for a $field comparand naming a DOTTED path across hand-written content/docs/**/*.mdx returns 0 hits, live positive control 6 same-table $field spellings from the same regex minus the dot requirement. Triage's measurement that neither @example reaches references/data/filter.mdx is NOT re-litigated. RELEASE-OWNED: content/docs/releases/** is read-only and NOTHING was edited there. Both rows are coincidental token matches, checked not assumed: v16.mdx:731,1009 matches 'addDays' because it names the FORMULA function addDays(d,n), a different surface from the filter addDays offset key; v17.mdx:556 matches 'due_date' inside a conditionalRequired-to-requiredWhen example, and its droppedFields passage at :1579-1584 makes no uniformity claim. NEITHER is factually wrong about any of these three defects, so there is NO docs-only card to file. Same reasoning retires the addDays rows on data-modeling/fields.mdx:407 and formulas.mdx:177,228 (formula helper, not filter key). NET: zero doc pages are falsified by this change, so zero pages were edited; every page above was left alone for a stated reason. Full section with the same readings is in the PR body.",
  "files_changed_note": "5 files, all listed above. ZERO content/docs pages edited beyond the ONE generated file gen:docs rewrote (content/docs/references/api/protocol.mdx). ZERO release-owned pages touched. ZERO governed-surface paths."
}

Generated by Claude Code

Navigation Menu

Repository navigation

[finding] field-value.zod.ts docblock over FILE_REFERENCE_TYPES still says the stored schema "deliberately admits both until D3 lands" — the classifier has admitted only the sys_file id since D3 wave 2 PR-5a (17.0.0) #15769

The stale sentence

What a fix looks like

分诊 · `pm:queue` / `domain:spec` / `priority:p2` / `documentation` / `finding`

复核（`origin/main` = `b25a5fc`，卡片测于 `8e500f23e`）

⭐ `priority:p2` 的理由 —— 它是承重散文，而且已经造成过一次代价

为什么锚定 `domain:spec`

⭐ 顺带的第二半：`FileLikeValueSchema` 的去留

与 #15041 的关系

Fold — the five gates, answered

⚠️ Premises the dev must falsify first — ⛔ none of these is handed over as a settled reading

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[finding] field-value.zod.ts docblock over FILE_REFERENCE_TYPES still says the stored schema "deliberately admits both until D3 lands" — the classifier has admitted only the sys_file id since D3 wave 2 PR-5a (17.0.0) #15769

Description

The stale sentence

What a fix looks like

Activity

os-zhuang commented on Sep 5, 2026

分诊 · pm:queue / domain:spec / priority:p2 / documentation / finding

复核（origin/main = b25a5fc，卡片测于 8e500f23e）

⭐ priority:p2 的理由 —— 它是承重散文，而且已经造成过一次代价

为什么锚定 domain:spec

⭐ 顺带的第二半：FileLikeValueSchema 的去留

与 #15041 的关系

claude commented on Sep 8, 2026

Fold — the five gates, answered

⚠️ Premises the dev must falsify first — ⛔ none of these is handed over as a settled reading

claude commented on Sep 8, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

分诊 · `pm:queue` / `domain:spec` / `priority:p2` / `documentation` / `finding`

复核（`origin/main` = `b25a5fc`，卡片测于 `8e500f23e`）

⭐ `priority:p2` 的理由 —— 它是承重散文，而且已经造成过一次代价

为什么锚定 `domain:spec`

⭐ 顺带的第二半：`FileLikeValueSchema` 的去留