[objectstack-fleet]

Fixes #20928

Clause-②: yes

The third carrier of the inline grid column is brought to the contract the other two already hold. ComponentPropsMap['object-master-detail-form'].details was z.array(z.unknown()); each entry is now a strict shape of the keys objectui's MasterDetailForm reads, and its columns references InlineGridColumnSchema. defineStack's identity-only check (collectHydratedInlineColumnErrors) now reaches the block on a page, and field-no-consumers reads a detail entry as a child collection. Governed by ruling 5791803339 (#19629, letter B) and ruling 5805782503 (#19910, letter 乙); routed by triage 5919655566.

What changed

• packages/spec/src/ui/component.zod.ts: details is z.array(masterDetailDetailEntry()). The entry is a strictObject with childObject (required), relationshipField, columns (z.array(InlineGridColumnSchema), the same object, not a copy), formFields, inlineMode (grid or form), amountField, sortField, totalField, title, minRows, maxRows, addLabel. The keys shared with a form view's subforms[] entry take that entry's types and alias table. The entry is built inside the props schema's own lazy body, as the subforms[] entry is: a standalone lazySchema element is a function-typed proxy the alias-integrity graph walk never descends into (measured: alias-integrity.test.ts went red on it, see commit e734f15e). New type ObjectMasterDetailFormPropsParsed: the props schema's input and output now differ, because the column schema's are different.
• packages/spec/src/stack.zod.ts: the page-component traversal that collectInlinePageActions owned (regions, slots, nested container arrays) is extracted into forEachPageComponent, unchanged, and the collector walks it for object-master-detail-form blocks, judging details[j].columns against details[j].childObject. A column is judged only once it parses as a column WITHOUT the resolved type. On the two parsed carriers this was already true. On the page carrier, whose properties the stack parse never reaches, it keeps every finding one that the resolved type brings; a column with its own defects is left to the component-props gate.
• packages/lint/src/validate-field-consumers.ts: CHILD_COLLECTION_KEYS gains details. A detail entry's column name, amountField and relationshipField credit the child's field, totalField the parent's, and an entry without columns credits the derived grid. The page slot map's own details key holds components, which carry none of an entry's keys at their own level. A pinned control shows such a component is read the same under slots.details as under slots.header.
• ADR-0087: new D3 semantic entry ui-object-master-detail-form-details-closed, plus a step-18 rationale fragment (order 56). gen:migration-registry regenerated the registry. No D2 conversion, per the census below.
• content/docs/protocol/objectui/layout-dsl.mdx: the master-detail example's columns: [product, quantity, unit_price] (bare strings) becomes three name: columns. The strict entry refuses bare strings, and the renderer could not draw them either: hydrateColumns returns a string column unchanged, and the grid reads col.name.
• Generated: dropped-refinements.baseline.json (one new site, ui/ObjectMasterDetailFormProps at details.element.columns.element, plus its two counts), api-surface/ui.json, export-origins/ui.json, content/docs/references/ui/component.mdx, docs/audits/2026-07-unknown-key-strictness-ledger.counts/ui.md. type-alias-convention.pin.test.ts drops the props schema's isomorphism pin (779 to 778) for the new XParsed alias, the route that file prescribes.
• Changeset .changeset/20928-master-detail-details-closed.md: @objectstack/spec minor (BREAKING, Clause-②: yes (narrowing), marker registered ui-object-master-detail-form-details-closed), @objectstack/lint patch.

Measurements

Premise (origin/main 2c1cef3345 at dispatch, re-read at this head): details: z.array(z.unknown()).optional() sat at component.zod.ts:4776. Premise holds.

The read set, from objectui packages/plugin-form/src/MasterDetailForm.tsx at the .objectui-sha pin 31971ff1e28f. The file is byte-identical at the dispatch pin e420df310f5b. MasterDetailDetailConfig is declared at :64-93. Each of its twelve keys has a live read: childObject :986, :1003; relationshipField :1033, :1312; columns :858, :928, :1034; formFields :847, :1063; inlineMode :850, :1064; amountField :861, :1035, :1550; sortField :862, :1038; totalField :1549; title :755; minRows :863; maxRows :864; addLabel :865. A grep of every d.X, detail.X and e.config.X member read in the file finds no thirteenth key; detail.saving and detail.add are i18n keys. deriveDetail hydrates an authored list with hydrateColumns and derives with deriveColumns, the same rule deriveInlineGridColumns reproduces.

Census (origin/main ebdb6f2aca, the branch point): blocks typed object-master-detail-form appear in the showcase project-workspace.page.ts (one entry, { title, childObject, addLabel }, no columns), in one doc example (three bare-string columns, rewritten here), and in the lint and spec test fixtures (copies of the showcase entry). sdui.manifest.json is objectui's registry, not a producer. field-keyed detail columns: 0. The regex details:.*field: does match three API-error details payloads elsewhere, so the matcher is live. Control: one authored inlineColumns block in examples/ (showcase invoice.object.ts). So only a narrowing marker is owed. Page-component properties is not parsed on the save or load path, so no stored row is ever refused, and no conversion is registered.

Collector reach: config.pages is reachable from the collector, and the existing page walk already reached component properties with hard cross-reference errors (inline actions). Measured below.

Field-consumer scan: before this change it did not read details[].columns[].name (CHILD_COLLECTION_KEYS was subforms only). Ablation A4 below confirms it.

Pinned objectui (31971ff1e28f, git grep): the only non-test importer is packages/types/src/zod/objectql.zod.ts:52 / :3913, which takes ObjectMasterDetailFormPropsSchema by reference through stripImportedDefaults, a generic walk. The tests registered-type-arms-10859-b2.test.ts compare the node's props to SpecObjectMasterDetailFormProps by reference on both sides, and their showcase fixture { title, childObject, addLabel } stays valid. No value the narrowed type refuses was found at that pin. objectui's own suites against this spec: NOT MEASURED (objectui coordination, below).

Public door (os validate --json, CLI built at bfb26d52, a probe stack with a currency child field):

probe column(s)	exit	valid	finding
{ name: 'amount', type: 'currency', scale: 2 }	0	true	advisory component-props-invalid at properties.details.0.columns.1.scale, the ruled first sentence
{ zzz_not_a_key: 1 }	0	true	advisory component-props-unknown-key (zzz_not_a_key) and component-props-invalid (name required)
{ name: 'amount', scale: 2 } over a currency field	1	false	STACK_CROSS_REFERENCE_INVALID: Page 'probe_invoice_entry' (regions.0.components.0) object-master-detail-form details[0].columns[1].scale: column 'amount' declares no type, so it renders as a currency column …
{ name: 'quantity' }, { name: 'amount' } (control)	0	true	none; and field-no-consumers reports neither child field

Verification (at bfb26d52, after merging origin/main 0d421041 through scripts/pm/os-regen-merge.sh)

• @objectstack/spec vitest run --project local, two shards: 297 + 297 files passed, 8915 + 8511 tests passed, 1 todo. --project repo subset (step18-rationale-merge, conversions-major18-merge, retired-key-migrate-sentence): 35 passed. pnpm --filter @objectstack/spec typecheck: exit 0. tsc -p tsconfig.test.json --listFiles includes both edited test files, and none of the errors held in the debt ledger names them.
• @objectstack/lint vitest run: 118 files / 5494 passed. typecheck: exit 0.
• Consumers, each named package exactly (--filter PKG, not a closure): @objectstack/sdui-parser 13 files / 217 passed; @objectstack/metadata-protocol 200 passed, 3 skipped files / 2973 passed, 19 skipped. Packages whose fixtures write the block: spec and lint only, covered above.
• pnpm --filter @objectstack/spec check:generated: all 15 artifacts up to date after a fresh build.
• Derived gates node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands: 114 derived, 114 run, all exit 0. --ran reconciliation: "0 NOT-MEASURED (a DERIVED zero)". Three first exited 3 (PREREQUISITE NOT MET: check:doc-formula-expressions, check:doc-security-posture, check:skill-examples) and were green after turbo run build over ./packages/* and ./packages/*/*. Five roster gates marked as sharing a directory with this diff (check-changeset-fixed, check:meta-url-spelling, check:authz-resolver, check:error-code-casing, check:filter-alias-parity) and check-sdui-manifest: exit 0.
• ESLint, a narrowed run, stated as such. eslint --no-inline-config --format json over the 8 changed .ts files reports files 8, errors 0, warnings 0. The population is eslint.config.mjs:971, **/*.{ts,tsx,mts,cts,js,jsx,mjs,cjs}. That config never enables type-aware linting (its comment at :326-328: no parserOptions.project, no typed rules), so this diff cannot move the verdict on any untouched file.
• Ablations, each through scripts/ablation-replace.mjs from committed state (bfb26d52), each restored with blob equal to HEAD and git diff HEAD empty. A first pass at 074d6ca4, before the entry became a factory, gave the same four counts. The subjects resolve to src through relative imports, so no dist leg was owed.
  • A1 details: z.array(masterDetailDetailEntry()) → z.array(z.unknown()) (blob 72d6abd987ce → 242fee1c1fb5): carriers pin 8 failed | 28 passed (36). All seven props-half refusals went red, plus the first assertion of the "left to the props half" pin. I predicted 7; the eighth is that pin's own props-half check.
  • A2 the collector's page loop emptied (aa6368d1f138 → 318e3e0ee35f): 2 failed | 34 passed. Those are the region refusal and the nested and slot refusal.
  • A3 the valid-without-type precondition deleted (aa6368d1f138 → 047cac280736): 1 failed | 35 passed. The red run printed the misattribution the precondition exists to stop: "column 'amount' declares no type, so it renders as a currency column … Unrecognized key(s) on this inline grid column: zzz_not_a_key".
  • A4 CHILD_COLLECTION_KEYS back to subforms only (3efd1236571e → 7b8b0ab03798): 3 failed | 66 passed (69). Those are the authored column, amountField, and the derived grid.
  • A5 the doc's old bare-string columns restored (b6df7f7748e0 → 2aef1e440273): check:yaml-examples exit 1, "1 of 19 tagged YAML block(s) do not hold their claim … expected object, received string" at layout-dsl.mdx:774.

Acceptance notes

• Two enforcement tiers on one carrier. The entry and column half is read where every page component's props are read: the component-props gate, advisory by its own declared posture (validate-component-props.ts header). So the card's typed and bogus columns move from silent green to valid: true with advisory findings. The identity-only column is a hard cross-reference error, like the inline-action targets already judged on the same pages. Upgrading the props gate is that gate's own step.
• Save door: a page saved through the metadata door keeps a failing detail entry, because properties is not parsed there. This is the same posture as every page-component narrowing in step 18. NOT MEASURED at the door.
• Scan, adjacent position: field-no-consumers still reads a detail entry's sortField and formFields in the parent's context, through the general walk. Not changed here. finding(lint): field-no-consumers still calls two in-use child-context fields "inert" — a lookup's inline-grid join key, and the fields an inline grid's per-row expand form draws (the family's closeout after #20951) #21091's positions are not touched.
• Files beyond the claim's list: layout-dsl.mdx (a producer the census found, which check:yaml-examples reds on, see A5), type-alias-convention.pin.test.ts and dropped-refinements.baseline.json (both forced by referencing the column schema). conversions/registry.ts and the showcase page are untouched, because nothing needed converting or rewriting.
• The D3 entry inline-grid-column-identity-only-currency-scale-refused still names its two carriers. The new entry records the third rather than editing a step-18 text that other open PRs hold.
• origin/main moved after the merge (e18fea6d). Its only spec file is data/filter.zod.ts, which this diff does not touch. Merge-queue revalidation covers it.
• objectui's MasterDetailForm mirror and its spec-parity probes over this row are not in this PR. The seat files the objectui coordination child.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

This PR changes 2 package(s): @objectstack/lint, @objectstack/spec, touching 15 documentable anchor(s). ⚠️ 3 changed file(s) yielded no anchor (packages/spec/api-surface/ui.json, packages/spec/dropped-refinements.baseline.json, packages/spec/export-origins/ui.json), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files.

7 hand-written doc(s) NAME something this change touched and may need an implementation-accuracy re-verification:

• content/docs/data-modeling/field-types.mdx (via relationshipField (literal, a string literal in masterDetailDetailEntry))
• content/docs/data-modeling/fields.mdx (via relationshipField (literal, a string literal in masterDetailDetailEntry))
• content/docs/deployment/validating-metadata.mdx (via childObject (literal, a string literal in masterDetailDetailEntry), relationshipField (literal, a string literal in masterDetailDetailEntry))
• content/docs/getting-started/common-patterns.mdx (via relationshipField (literal, a string literal in masterDetailDetailEntry))
• content/docs/protocol/objectql/types.mdx (via relationshipField (literal, a string literal in masterDetailDetailEntry))
• content/docs/protocol/objectui/layout-dsl.mdx (via childObject (literal, a string literal in masterDetailDetailEntry), relationshipField (literal, a string literal in masterDetailDetailEntry))
• content/docs/ui/pages.mdx (via relationshipField (literal, a string literal in masterDetailDetailEntry))

What this run could not see

• 3 changed file(s) yielded no anchor (packages/spec/api-surface/ui.json, packages/spec/dropped-refinements.baseline.json, packages/spec/export-origins/ui.json) — pages documenting those are invisible to this run
• 6 name(s) were too generic to anchor anything (single lowercase words)
• the SDK route bridge reached 54 of 206 client-bound route-ledger rows — the other 152 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 152: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 97 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
• 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 — 137 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 e18fea6dcdf6af5619cae05eb37c38417230d83b → packageMentionDocs.

Which tree this was computed on

This run read content/docs from e7e00637e6f3b0e5f5990cb12a9b923e57e10bdc — the merge of head bfb26d52e9a14b9f3808510e00aa6400f5c7f9fd into base e18fea6dcdf6af5619cae05eb37c38417230d83b, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin e7e00637e6f3b0e5f5990cb12a9b923e57e10bdc && git checkout e7e00637e6f3b0e5f5990cb12a9b923e57e10bdc
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin e18fea6dcdf6af5619cae05eb37c38417230d83b bfb26d52e9a14b9f3808510e00aa6400f5c7f9fd && git checkout -B drift-repro e18fea6dcdf6af5619cae05eb37c38417230d83b && git merge --no-ff bfb26d52e9a14b9f3808510e00aa6400f5c7f9fd

node scripts/docs-audit/affected-docs.mjs --json e18fea6dcdf6af5619cae05eb37c38417230d83b

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs e18fea6dcdf6af5619cae05eb37c38417230d83b → pass the list as
args.docs, on the commit named under Which tree this was computed on.

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: bfb26d52e9a14b9f3808510e00aa6400f5c7f9fd
Local-runs: none

Inputs, and nothing else: card #20928 (body, triage 5919655566, claim 5934221277, dev report 5936596153), PR #21215 (body, its 15-file list, the net diff of the branch at the head against origin/main, merge-base 0d421041d), and the head's check-runs. Read-only reads of origin/main and of the pinned objectui at 31971ff1e28f (the .objectui-sha on origin/main and on the merge-base) were taken to judge the claims; nothing was built, run or re-run.

① Derived judgments

1. ComponentPropsMap['object-master-detail-form'].details element goes from z.unknown() to a strict entry of twelve keys. RIGHT. objectui packages/plugin-form/src/MasterDetailForm.tsx at 31971ff1e28f declares MasterDetailDetailConfig with exactly these twelve members (lines 64 to 93), each with a live d.X read; the other member reads in the file (detail.saving, detail.add, d.input) are an i18n key pair and a batch-input map, not config keys. inlineMode as grid | form equals the renderer's InlineMode (deriveMasterDetail.ts:423). title and addLabel as plain strings match the renderer (a React child at :755, a button label at :865) and the subforms entry. childObject required matches the renderer's declined branch (:986).
2. The keys shared with the form view's subforms[] entry take that entry's types and alias table. RIGHT, byte-equal against view.zod.ts on origin/main: the ten-alias table and the types of childObject, relationshipField, columns, amountField, totalField, title, addLabel, minRows, maxRows. The three added keys (formFields, inlineMode, sortField) are renderer-read. No alias collides with a declared key.
3. columns references InlineGridColumnSchema by object identity, not a copy. RIGHT, and pinned by the toBe case. Rulings B ([finding] FieldSchema.scale on a currency field is offered to authors by the field designer, ignored by every display face, and still enforced on writes — half-live in the direction that surprises #19629) and 乙 ([Decision] Ruling 5791803339 points currency authors at currencyConfig.precision — but nothing reads that key, and removing scale leaves two console faces rendering currency with zero decimals until objectui#10221 lands #19910) reach this carrier through the column schema's own refinement; no second scale rule was written.
4. Accept-set effect: a narrowing on a published export (ObjectMasterDetailFormPropsSchema, ui namespace, listed in api-surface/ui.json). Refused now: an entry without childObject, an unknown entry key, a bare-string column, a field-keyed column, an unknown column key, scale on a column declaring type: 'currency'. The named producer's entry { title, childObject, addLabel } parses unchanged. A bare-string column gets zod's own expected object, received string (no alias is possible for a string); the changeset's FROM → TO table and the D3 replacement text carry that prescription. RIGHT.
5. Public surface: one additive type export, ObjectMasterDetailFormPropsParsed (api-surface/ui.json and export-origins/ui.json regenerated; the isomorphism pin count 779 → 778 by the pin file's own prescribed route). RIGHT: input and infer differ because the column's readonlyWhen / requiredWhen bare-string arm transforms to an envelope.
6. stack.zod.ts: the page-component traversal is extracted into forEachPageComponent. RIGHT: the regions, slots and nested-array walk and its path spellings are byte-identical to the former collectInlinePageActions body, and the inline-action collector now reuses it.
7. The new precondition inside judge (a column is judged only when InlineGridColumnSchema.safeParse(column) succeeds without the type). RIGHT on all three carriers. validateCrossReferences receives the parsed data, so on the two parsed carriers the column is parse output, and EvaluatedExpressionInputSchema is a union whose envelope arm accepts its own output, so the re-parse is stable and the guard is a no-op there. On the raw page carrier it stops a column's own defects from being reported as currency findings (ablation A3 printed exactly that misattribution). Reach is unchanged: a declared type is skipped, an undeclared child object or field is skipped.
8. Page-carrier reach: config.pages only, every region, slot and nested container array, the same reach the inline-action cross-reference check already has. RIGHT and consistent.
9. validate-field-consumers.ts: CHILD_COLLECTION_KEYS gains details. RIGHT. The walk treats every array element under a details key as a child entry. The only other details arrays in stack metadata are the page slot map's (components, which carry none of an entry's keys at their own level, pinned by the control case) and API error payloads the scan never walks. totalField stays parent-scoped through the general walk and is pinned so.
10. ADR-0087: D3 entry ui-object-master-detail-form-details-closed plus a step-18 rationale fragment at order 56 (unique among the fragments; the (#20928) citation inside a rationale text follows ten sibling fragments that cite the same way). No D2 conversion. RIGHT: PageComponentSchema.properties is z.record(z.string(), z.unknown()), and outside spec and lint tests the only ComponentPropsMap consumer is the dogfood expression-conformance ledger, so nothing on a save or load door parses component props and nothing at rest is refused.
11. dropped-refinements.baseline.json gains one site, details.element.columns.element, the exact analogue of ui/FormView's subforms.element.columns.element; the hand-edited ledger grows because build-schemas refuses an undeclared site. RIGHT.
12. Generated artefacts (references/ui/component.mdx, the strictness ledger counts with one more strict site in component.zod.ts) and the layout-dsl.mdx producer rewrite (the renderer's hydrateColumns cannot draw a string column). RIGHT.
13. Governed surfaces: none in the file list; the record is owed by the Clause-②: yes and packages/spec/src/** limbs, not by tier. Head repo equals base repo; 805 changed lines.

② Semver level

.changeset/20928-master-detail-details-closed.md: @objectstack/spec: minor, @objectstack/lint: patch; Clause-②: yes (narrowing); a BREAKING banner; exactly one adr-0087 disposition marker, registered ui-object-master-detail-form-details-closed, in the comment form the gate reads; a FROM → TO table with the one-line fix; the census on ebdb6f2aca. RIGHT, each clause:

• yes takes at least minor: yes. (narrowing) is BREAKING and carries its migration: yes. minor for a breaking accept-set narrowing is the repo's launch-window convention (fourteen sibling changesets on main say so; check-changeset-no-major refuses major).
• The additive ObjectMasterDetailFormPropsParsed export is covered by minor.
• @objectstack/lint: patch: a false-positive fix in field-no-consumers, no export or option change.
• No tombstone owed: nothing declared was removed, the carrier was z.unknown(); retiredKey() does not apply.
• Declaration consistency: claim 5934221277 declares Clause-②: yes, the PR body repeats it verbatim, the changeset adds the (narrowing) arm where the registration gate reads it. One arm at most, consistent. skip-changeset correctly not applied (spec and lint publish). Check Changeset on the head: success.

③ Boundary flags

Dev open_questions: none. Each deviation and out-of-scope finding in report 5936596153:

• D1 Files beyond the claim's surface (layout-dsl.mdx, type-alias-convention.pin.test.ts, dropped-refinements.baseline.json): ANSWERED, forced by the diff (ablation A5 red, the Iso pin route, the build-schemas refusal); no scope expansion. Claim-listed files left untouched (conversions/registry.ts, the showcase page): ANSWERED, correct, no D2 is owed and the showcase entry is inside the twelve keys.
• D2 forEachPageComponent extraction: ANSWERED, verified unchanged (①6).
• D3 Entry built by a factory inside the parent's lazy body rather than a standalone lazySchema: ANSWERED, acceptable; the alias-integrity walk reaches it, and the subforms entry is built the same way.
• D4 PR body Clause-②: yes with no arm while the changeset carries (narrowing): ANSWERED in ②.
• D5 Pin citation repointed to 31971ff1e28f: ANSWERED; it equals .objectui-sha on origin/main and on the merge-base, and every cited line resolves there.
• D6 origin/main moved after the merge (e18fea6d; its only spec file is data/filter.zod.ts, untouched here): ANSWERED; the queue rebuilds on current main.
• D7 Commit trailers in the model-free pair: ANSWERED, correct per AGENTS.md.
• F1 The objectui coordination child (the MasterDetailForm mirror, and apps/console/src/__tests__/registry-inputs-spec-parity.test.ts row object-master-detail-form.details, whose prose and probes state the spec row is z.array(z.unknown())): ESCALATED to the seat as its owed act; the triage and the claim both assign that filing to the seat, not to this PR. Not a landing blocker here: this is a narrowing, not a removal; at the pin the only non-test importer takes the schema by reference through stripImportedDefaults, whose walker handles lazy, object, array, union and pipe nodes and falls through on the rest; and Console Pin Gate builds the pinned console, it does not run objectui's suites. Those suites against this spec stay NOT MEASURED, as the dev states.
• F2 field-no-consumers still reads a detail entry's sortField and formFields in the parent's context (CHILD_ENTRY_FIELD_KEYS is amountField and relationshipField only): ESCALATED. Two child-field keys credited against the wrong object is a real gap on this carrier, reach unmeasured; it belongs on finding(lint): field-no-consumers still calls two in-use child-context fields "inert" — a lookup's inline-grid join key, and the fields an inline grid's per-row expand form draws (the family's closeout after #20951) #21091 (the named family carrier, same file) as a comment, not only in this PR's acceptance notes.
• F3 Two enforcement tiers (advisory component-props findings for the entry and column half, a hard STACK_CROSS_REFERENCE_INVALID for the identity-only half; the save door does not parse props): ANSWERED; declared in the changeset, the D3 entry and the acceptance notes, so the claim is as narrow as the enforcement (Prime Directive chore: version packages #10).

Check-runs on the head, read 2026-10-01T17:27Z (the fourth read of this round; the first was 2026-10-01T17:16Z): 28 success, 2 skipped (Console Pin Gate and Packed-tarball smoke (opt-in), both paths-filtered), 3 still in_progress: Test Core (3/6), Test Core (5/6), Test Core (6/6); 1 queued: TypeScript Type Check, the required aggregate, which started once its four Type Check · legs went green. Green so far: Lint & Repo Gates, Type Check · source gates, Type Check · consumer gates, Type Check · debt ledger, Type Check · workspace, Build Core, Dogfood Regression Gate and its three shards, Dogfood Verify CLI, Temporal Conformance (live PG + MySQL), Governed Surface Queue Guard, Check Changeset, Spec property liveness, Test Core (1/6), Test Core (2/6), Test Core (4/6). No check-run on the head has failed. A running gate is not a pass: landing waits for the four to conclude green (the Test Core aggregate context among them).

Note, not verdict-bearing: the block-level docblock on ObjectMasterDetailFormPropsSchema still cites the renderer at eb7f586b beside the entry's 31971ff1e28f citation; pre-existing text, not this diff's.

Implemented-by: claude/issue-20928-master-detail-details-strict
Reviewed-by: session_01UtnxvdiN376GF3sgXwAw4d

VERDICT: PASS

Recorded 2026-10-01T17:28Z.

---

Generated by Claude Code