[objectstack-fleet]

Requested by Tesla · project thread

Clause-②: no
Metadata-protocol: none

Fixes #30977

Claim: 6697140710 · Branch: claude/project-thread-kujw5c

维护者速读

• 改了什么：只改注释。协议 18 的转换 cbp-master-detail-required-defaulted 和构建器 forceCbpMasterDetailRequired 的说明里，还写着「显式 required: false 的主表会被构建器和解析拒绝」，现在改成按 feat(spec,security): a controlled_by_parent object may declare an optional master #30940 之后的实际规则来写。
• 为什么改：feat(spec,security): a controlled_by_parent object may declare an optional master #30940（controlled_by_parent admits an optional master (1/3): spec, lint and the read owner branch: a null-master detail row is readable by its owner only #30905 裁决 A）落地后，controlled_by_parent 对象唯一的 master_detail 写 required: false 是合法的可选主表；旧注释会让下一个改这个转换的人按已经不存在的规则推理。
• 对作者的影响：没有。转换行为不变：省略 required 仍补成 true，显式 required: false 仍不转换。
• 风险与回滚：零运行时风险，无行为改动；apply 与 fixture 形状一字未动。回滚即撤本 PR。
• 不在范围：文档和技能里的同类说法归 controlled_by_parent admits an optional master (3/3): docs and the authoring skills teach it instead of a copied owner field #30907（卡 3/3），本 PR 不碰。
• 发布：注释不进发布内容，打 skip-changeset。

Stale sentences found, and how each was resolved

#	Where (on origin/main 81deb54)	Stale claim	Resolution
1	conversions/entries/18/cbp-master-detail-required-defaulted.ts:56-58	"An explicit required: false … The builder refuses it loudly … an author the builder would have stopped"	Rewritten: on the only master_detail it is the optional master (ADR-0055 §1 as amended, #30905 ruling A), kept by the builder and admitted by the parse, so the stored pass keeps it too; beside another master_detail the builder still refuses it.
2	same file :66-68	"a live author still meets the parse's refusal and its prescription"	Rewritten: a live author meets the builder's force through ObjectSchema.create() and os lint's relationship/master-detail-required at error; a raw parse reads the omitted key as the optional master (the field default writes false first).
3	same file :110 (fixture comment)	"refused by the builder, not converted here"	Now "the optional master, kept as written; not converted". Fixture shape untouched.
4	same file :23-26	"Ruling B made the parse refuse … without exactly one master_detail declared required: true"	True as history; kept, with one parenthesis noting ruling A's amendment and that the omitted key this entry converts is unchanged by it.
5	data/object.zod.ts forceCbpMasterDetailRequired docblock, closing paragraph	"the RULE — exactly one required master_detail … so a raw parse of a master_detail without required: true is refused rather than forced"	Rewritten: the rule includes the only master_detail as the optional master, and a raw parse is never forced (it reads an omitted required after its false default). The paragraphs above it already carry #30940's "⚠️ Amended" note and were left.

Read and left as is:

• summary string (:79-82): every clause is still true ("an explicit required: false … not converted"), so it did not change, and no printed text moved.
• migrations/entries/semantic/18.cbp-master-relation-tiers-retired.ts (:50-51, :69-70, :76): its text on an explicit required: false is outdated, but feat(spec,security): a controlled_by_parent object may declare an optional master #30940 added 18.cbp-optional-master-admitted, whose reason says in so many words that it "supersedes what cbp-master-relation-tiers-retired and cbp-master-detail-required-forced say of it … everything else they say stands". The D3 record is superseded by a later entry, not edited, and its strings are printed to authors; left for that reason.
• data/controlled-by-parent-master.ts and conversions/refused-shapes.test.ts: already updated by feat(spec,security): a controlled_by_parent object may declare an optional master #30940; nothing stale.

Verification

• dispatch-gates --commands: 68 derived, 68 run, all exit 0. dispatch-gates --ran: 68 accounted, 0 NOT-MEASURED. 11 of them first exited 3 (not measured) on a fresh worktree; they went green after pnpm build, and check-plugin-teardown-shape --self-test after fetching its pinned fixture commit on this shallow clone.
• vitest run src/conversions src/data/controlled-by-parent-master.test.ts in packages/spec: 24 files, 842 tests passed.
• Open PRs touching these files: none found (docs(skills): name the save_notice node in the automation skill #31044, the one search hit, touches only skills).
• Diff: 2 files, +24 / −15, comments only.

Acceptance notes

• No behaviour change: apply, summary, surface and the fixture objects are byte-identical.
• No changeset: comments only, nothing published moves (skip-changeset).
• Docs and skills untouched (controlled_by_parent admits an optional master (3/3): docs and the authoring skills teach it instead of a copied owner field #30907).

🤖 Generated with Claude Code

https://claude.ai/code/session_01L9qibzpwEPquNhPcgrrjew

[github-actions]

📓 Docs Drift Check

⚠️ 1 changed file(s) yielded no anchor (packages/spec/src/data/object.zod.ts), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files. Nothing else in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 1 changed package(s)).

What this run could not see

• 1 changed file(s) yielded no anchor (packages/spec/src/data/object.zod.ts) — pages documenting those are invisible to this run
• 1 name(s) were too generic to anchor anything (single lowercase words)
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 171 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json b5106af62a28e99365746c1397037a830f931504 → packageMentionDocs.

[objectstack-fleet]

domain:spec#1 · os-tesla · session_01L9qibzzqHZdAVqgBAvxXKB

维护者速读

• 改了什么：只改注释，共 2 个文件（+24/−15）。feat(spec,security): a controlled_by_parent object may declare an optional master #30940（controlled_by_parent admits an optional master (1/3): spec, lint and the read owner branch: a null-master detail row is readable by its owner only #30905 裁决 A）之后，controlled_by_parent 对象唯一的 master_detail 写 required: false 是合法的可选主表。
  • 协议 18 转换 cbp-master-detail-required-defaulted 的说明改成符合这条规则。
  • 构建器 forceCbpMasterDetailRequired 的说明也一样。
• 为什么改：旧注释仍写「显式 required: false 会被构建器和解析拒绝」。下一个改这个转换的人会按已经不存在的规则推理（spec: the cbp-master-detail-required-defaulted conversion still says the parse refuses an explicit required: false master, which is no longer true after #30905 #30977）。
• 风险与回滚：无行为改动。apply、summary、surface 和 fixture 一字未动，打 skip-changeset。回滚即 revert。
• 先看：PR 正文里五行「Stale sentences」表，以及「Read and left as is」中为什么不改 D3 语义条目：它已被 18.cbp-optional-master-admitted 明文取代，并且会打印给作者。
• 两分钟验证：在 packages/spec 下运行 vitest run src/conversions，预期全部通过。
• 需要你做的：无。不属于受治理路径，席位按 pm-dispatch 自主落地。

席位意见：可以落地。

席位核对

ACCEPT · seat domain:spec#1 · head 3fd3b163 · 2026-11-06T23:08Z

1. Shape: Fixes #30977, draft, base main, 2 files, +24/−15, comments only. skip-changeset. Clause-②: no / Metadata-protocol: none, matching claim 6697140710. Not governed.
2. Seat review (review of record; no contract review owed, since no accept set moves): each rewritten sentence was checked against origin/main:
   • forceCbpMasterDetailRequired (object.zod.ts:4508) keeps an explicit required: false on the only master_detail and throws beside another one.
   • relationship/master-detail-required is at error (packages/lint/src/data-model-rules.ts:447).
   • The summary string still reads true.
   • Leaving the D3 semantic entry is right: 18.cbp-optional-master-admitted supersedes it in its own reason, and the record is printed to authors.
3. Gates / check-runs: dev: 68/68 derived gates exit 0, --ran 0 not measured, spec conversions 842 tests passed (report 6697666083). On head 3fd3b163: 69 runs, 55 success, 14 skipped, 0 failed, 0 running. mergeable_state is clean.
4. Accepted deviations: a one-parenthesis ruling-A note was added beside the :23 history, beyond the order's list. It is true and keeps the history readable.
5. Landing: not governed. The seat readies the PR and arms auto-merge via the relay, per Tesla 2026-11-06T14:09Z 「你应该是使用 pm-dispatch 技能自主审核和落地 pr」.