docs: cite landing commits where pending changesets and source comments name 32 objectui issues that answer 404 (objectui#10803, batch 3)

[objectstack-fleet]

Part of #10803
Clause-②: no

Dispatched implementation of the domain:ui seat #2 claim (comment 5860873556) on objectui#10803, batch 3, session https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN; patch round 1 applies the seat ruling 5861129870 on the round's two open questions, and patch round 2 applies contract review 5861306588 (two wording fixes and one optional nit) and the ruling's amendment 5861311219. Citations only: no sentence's claim moves, and every edited pending changeset's frontmatter is byte-identical. The runtime text that moves loses its dead pointer and nothing else: four ADR-0049 tombstone guidance strings and two zod .describe() strings in @object-ui/types, and the Studio CEL authoring advisory in @object-ui/app-shell. The six tests that pin the tombstone text, the two changesets and two content/docs pages that quote it follow the changed string, and nothing else in them moves.

Why Part of, not a closing line

The card stays open for the other 83 numbers of the family remainder (seat amendment 5860244997, Q2 = A).

The seat ruling 5861129870 and its amendment 5861311219, as applied

• Q1, the tombstone guidance class: a seat variant of option A, as amended. Each of the four runtime tombstone strings keeps the house RETIRED (REF) — shape with ADR-0049 as the reference, in place of the dead card. The ruling first conditioned ADR-0049 on the key's TypeScript twin comment naming it: the twins of TreeViewSchema.data and ChartDataSeriesSchema.data (data-display.ts) and of TextSchema.value (layout.ts) each read "RETIRED (SHA, ADR-0049 enforce-or-remove)", while the twin of DashboardConfigSchema.aria is a deletion note on DashboardConfig in designer.ts that names no ADR, so round 1 shipped RETIRED — there. The amendment 5861311219 corrects that proxy: the aria retirement is itself ADR-0049 (the comment above DashboardConfigSchema in complex.zod.ts, its landing commit e7957ab87, and the pending dashboard-config-aria-retired-5852.md all say so), so aria's error and describe strings also open RETIRED (ADR-0049) —. All four now read alike. Everything after the dash is unchanged. No sha enters runtime text.
• Q2, the CEL advisory: A. The pointer drop in rowCanonAdvisory stands, as shipped in round 1.
• Folded (triage item 3): the bare PR numbers Bind record into node-level visibleWhen, and stop visible swallowing it #5505 and docs(plugin-form): Phase 0 of the row-predicate deprecation — stop teaching the bare shorthand (#5738) #5758, see Mapping and Special cases 4 and 2.
• Review 5861306588, taken in full: the Row-predicate deprecation is missing its Phase 0: docs and example apps may still teach the bare shorthand / data.* spellings the new warning now flags #5738 stand-down 3 sites name the card by role behind the sha (Special cases 2); the runtime-strings changeset's second sentence no longer says every pointer is dropped; and, the optional nit, the sweep changeset names the role-named case.
• main: main (fab627ff9) was merged in during round 1 by a merge commit (2cb9b253f), no rebase and no force-push. The branch is 0 commits behind it, so round 2 merged nothing. Every reading below is on the head dd37e35d2.

Premise, re-measured

• REST GET /repos/objectstack-ai/objectui/issues/N for each of the 32: all 32 answer 404, and a second read of each answers 404 again (32 of 32). GET .../pulls/N answers 404 for all 32 too. Lit controls: objectui#10533 and objectui#7714 answer 200. No number was dropped from the batch.
• The two folded bare PR numbers, Bind record into node-level visibleWhen, and stop visible swallowing it #5505 and docs(plugin-form): Phase 0 of the row-predicate deprecation — stop teaching the bare shorthand (#5738) #5758, answer 404 on both issues/N and pulls/N.
• The same 32 in objectstack all answer 200. Their subjects are unrelated to the objectui sentences (for example objectstack#5425 is the U+0000 finding about useDatasetFields.ts, objectstack#5418 the language-menu card). The only objectstack-qualified sites these numbers have in the in-scope classes already spell objectstack# (objectstack#5425 in useDatasetFields.ts, objectstack#5418 twice in i18n's provider.tsx, and objectstack#5505 twice in components): live sister citations, untouched. Every other site names an objectui card, confirmed by its landing commit below, so no site is re-qualified.
• Every edited changeset is pending: it is present in .changeset/ on main.
• Branch point: a60539b07. Not a shallow checkout.

Census (the enumeration pin for this batch)

The instrument PR objectui#10854 printed, with this batch's 32 numbers and the two folded ones substituted (REF = a commit):

git grep -nE '(objectui#|#|issues/)(3499|3559|4784|5197|5221|5286|5309|5399|5401|5413|5414|5416|5417|5418|5425|5505|5518|5533|5709|5738|5741|5758|5852|5859|6296|6464|6661|6740|6757|6854|6859|6864|6896|6951)([^0-9]|$)' REF -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | grep -v 'objectstack#' | wc -l

• REF = a60539b07 (branch point): 217 lines (216 for the 32 alone: 56 changeset lines in 47 files and 160 src-nontest lines in 77 files; the folded docs(plugin-form): Phase 0 of the row-predicate deprecation — stop teaching the bare shorthand (#5738) #5758 adds one line, and Bind record into node-level visibleWhen, and stop visible swallowing it #5505 sits on two lines record:alert silently ignores the declared visibleWhen gate that its sibling blocks honour — the same defect already closed on the record-header face #5401 already counts). REF = fab627ff9 (current main): 217.
• REF = dd37e35d2 (this head, main merged in): 0.
• This head merged with a fresh main (fab627ff9, git merge-tree --write-tree, clean): 0.
• The instrument's blind spot, measured: its grep -v 'objectstack#' drops a whole line that ALSO names an objectstack number. One in-scope line was hidden that way, ActionRunner's onSuccess block ("objectui#5221, the console half of objectstack#9566/ci(coverage): give the instrumented lane its own per-test budget so the coverage gate can run #9474"); it is re-pointed here too. Without the filter the instrument reads 5 at this head, all live objectstack# lines (the three above and objectstack#5505 twice).
• Lit control, the same printed instrument over live objectui#7714 at this head: 17 lines. Hex-colour false positives (a number followed by a hex letter) at the branch point: 0.
• Out of scope, as it stands (the card's instrument with the 34 numbers, unfiltered, whole tree at this head): 283 test lines in 121 files, 4 scripts lines in 2 files, 0 .github, 0 governed, and 24 other lines in 20 files (published CHANGELOG.md history, content/docs, two package READMEs, and apps/console; see Acceptance notes 3). The test count includes the @ts-expect-error comments named in Acceptance notes 5.

Citation form

• The 9-character backticked sha of the commit on main that landed the change the sentence rests on, as in PRs objectui#10707 / docs: cite the landing commits where ten objectui issue links answer 404 (objectui#10755) #10766 / docs: cite landing commits where pending changesets and source docblocks name ten objectui issues that answer 404 (objectui#10771) #10797 / docs: cite landing commits where pending changesets and source comments name fourteen objectui issues that answer 404 (objectui#10803) #10854. All 32 distinct shas below (the two folded numbers reuse two of them) are ancestors of main (git merge-base --is-ancestor, exit 0 each; control leg: the head of PR objectui#10714 answers exit 1, and a known ancestor 5f789538d answers exit 0 in the same checkout), and git rev-parse --short=9 returns the same 9 characters for each.
• A changeset's pointer to its OWN card is dropped, not replaced: @changesets/changelog-git prefixes each released entry with the hash of the commit that added the file, which is that landing. Where dropping the pointer left a dangling word, the clause was minimally repaired (listed in Special cases).
• Where the sentence cites a RULING and no single commit is the ruling, the ruling is cited by its date: "the 2026-08-23 ruling" (the dashboard widget-options ruling, option B, recorded in 8d58f46b4's message), "the maintainer ruling of 2026-08-31" (the chart categories ruling, recorded in b0d308da9's).
• Runtime text carries no sha. Inside a zod .describe() string and in the author-facing CEL advisory the dead pointer is dropped (amendment 5860244997, Q1 = A; ruling 5861129870, Q2 = A). A tombstone guidance string keeps its RETIRED (REF) — shape with ADR-0049 as the reference (ruling 5861129870, Q1, as amended by 5861311219).
• Where nothing answers, the pointer is dropped and the sentence names the card by role ([finding] After #4881's flip, StudioNavItemInspector still READS the schema-rejected object spelling as a fallback — the last one in the Interfaces pillar #5518 only).

Mapping (number to resolution)

Lines and files are the branch-point census for that number. "Method" is how the landing was found.

dead number	resolution	method	lines / files	evidence
#3499	48132f7e6	git log --grep	1 / 1	the rc.5 bump; its message lists "HttpMethodSchema -> spec's HttpMethodSubsetSchema (objectstack#5832, objectui#3499)"
#3559	fbc23e094	git log --grep	7 / 3	"keep a field's own option keys when an action param inherits them (#3559)"; it added ActionParamOption and the normaliseOptions preservation
#4784	833c90047	git log --grep	1 / 1	"a 400 FLOW_FAILED or 404 on the flow route is terminal, not retryable"; its body names #4784 as the card it settles
#5197	9c60144b5	git log --grep	4 / 3	"retire the unreachable id-keyed nav label resolvers (#5197)"
#5221	053fdc8f9	git log --grep	4 / 3	"read ActionSchema.onSuccess for post-success navigation", "Part of #5221"; it added 5221-onsuccess-navigation.md and the console openIn: 'self' half
#5286	38ba3ddf3	git log --grep	1 / 1	"API Discovery Storage group reads the canonical storage slot first (#5286)": the alias table the changeset's sentence describes
#5309	c7a74c80d	git log -G (the only commit adding the citation)	3 / 2	"approver membership-tier picker reads the server-published enum; delegated_admin stops rendering (invalid)"
#5399	5a07e67d9	git log --grep + changeset's adding commit	2 / 2	"stop the sparse-predicate warning blaming hidden: true (#5399)"
#5401	c86185eb5	git log --grep	3 / 3	the PR #5505 squash ("Bind record into node-level visibleWhen"); its body "flip[s] the #5401 defect pins" and implements the live successor objectui#5454
#5413	688cb93ad	git log --grep	1 / 1	"resolve four react-pages.md contradictions toward the framework's sources (#5413)"
#5414	77f846a8b	changeset's adding commit	11 / 5	"name the pending approver, not a truncated raw id"; its body names #5414 as the card it settles and states the confirmed-empty-seat surfacing
#5416	add10d8f9	git log --grep + changeset's adding commit	9 / 5	"Studio metadata forms: no errors before input, translated help text, and a publish button clear of the toast"
#5417	c40f3b8ca	git log --grep + changeset's adding commit	4 / 3	"surface a screen flow's resume result, on both outcomes (#5417)"
#5418	7a90afdf9	changeset's adding commit + git log -G	20 / 16	"Studio's 新建对象 asks for the record-sharing baseline, and an unauthored one is reported before Publish instead of by it"; it added the ten locale keys and securityPostureLint.ts
#5425	56f4e34c0	git log --grep + changeset's adding commit	5 / 4	"one header spelling across the table widget family", "Part of #5425"
#5505 (bare PR number, folded)	c86185eb5	the PR's own squash (subject ends "(#5505)")	2 / 2	sits beside c86185eb5 already, so the pair collapses to the sha. See Special cases 4
#5518	nothing answers	git log --grep, git log -S on the fallback read	1 / 1	the node.objectName ?? node.object fallback it asks about is still on main; no commit lands it. See Special cases 1
#5533	2573ff434	git log --grep + changeset's adding commit	12 / 6	"Marketplace package detail page states the marketplace is off, instead of red-erroring (#5533)"
#5709	8d58f46b4; "the 2026-08-23 ruling"	git log --grep + changeset's adding commit	8 / 6	"warn on dashboard widget options keys no renderer consumes (#5709)"; its body records "Maintainer ruling 2026-08-23 (option B)"
#5738	stand-down 3: the card named by role, behind 702c48a62; the recipe: 702c48a62	git log --grep	4 / 3	702c48a62 ("write the requiredWhen example in the row-predicate canon (#5738)") is the Phase-0 corpus-sweep landing and carries the detectNonCanonicalRowSpelling recipe, but not the stand-down 3 finding, which was recorded only on the dead card. See Special cases 2
#5741	83fe6e741	git log --grep + changeset's adding commit	25 / 13	"row predicates on runtime record surfaces bind record.* only (objectui#5741)"; "executed as ruled on objectui#5741 (2026-09-02, amended 2026-09-05)"
#5758 (bare PR number, folded)	702c48a62	the PR's own squash (subject ends "(#5758)")	1 / 1	"PR #5758's recipe" beside 702c48a62 collapses to the sha. See Special cases 2
#5852	e7957ab87; runtime text RETIRED (ADR-0049) —	git log --grep + changeset's adding commit	5 / 4	"retire the designer-surface dashboard aria pair (#5852)"; it wrote the hand-spelled z.never({ error }) tombstone
#5859	41df89320	changeset's adding commit	1 / 1	"retire the orphaned ObjectTrigger and ObjectRelationship exports"; own-card pointer only
#6296	88b15fddc	git log --grep + changeset's adding commit	8 / 3	"caller-supplied subject vocabulary for ConditionBuilder", "Part of #6296"; it added subjects and the per-row quote character
#6464	830ed5803	changeset's adding commit	8 / 6	"offer approval recall to the submitter only"
#6661	969ba84f4	changeset's adding commit	5 / 5	"console renderers for app:launcher and nav:menu"
#6740	7c9b044f4	changeset's adding commit	5 / 5	"flex declares the containment it renders"
#6757	f99932a42	git log --grep + changeset's adding commit	11 / 10	"render global:search and global:notifications instead of the placeholder"; its body names #6757 as the card it settles
#6854	adb2a86db	changeset's adding commit	4 / 3	"render AppAction.items from its declared type, without the two as any reads"; it added the pin LayoutRenderer.appActionItems-6854.test.tsx and ran the app-document census the Chinese changeset refers to
#6859	64d937c53	git log --grep + changeset's adding commit	5 / 2	"correct the injected-editor commit justification, and pin what actually happens (#6859)"
#6864	503cd8b89	changeset's adding commit	5 / 4	"aggregate()'s spec-shape branch refuses the analytics branch's filter / field / function"
#6896	b0d308da9; "the maintainer ruling of 2026-08-31"; runtime text RETIRED (ADR-0049) —	git log --grep + changeset's adding commit	18 / 10	"retire ChartDataSeries.data, correct categories' prose (#6896)"
#6951, ruling A1 (TextSchema.value)	5ad86ddee; runtime text RETIRED (ADR-0049) —	git log --grep + changeset's adding commit	part of 16 / 7	"retire TextSchema.value as an ADR-0049 tombstone (objectui#6951 A1 / objectui#7016)"
#6951, ruling B1 (TreeViewSchema.data)	16a725f96; runtime text RETIRED (ADR-0049) —	git log --grep + changeset's adding commit	part of 16 / 7	"retire TreeViewSchema.data as an ADR-0049 tombstone (objectui#6951 B1)"

Special cases (the judgement calls)

1. [finding] After #4881's flip, StudioNavItemInspector still READS the schema-rejected object spelling as a fallback — the last one in the Interfaces pillar #5518, StudioDesignSurface's nav inspector. "is objectui#5518, deliberately left out of [finding] Studio 的导航消费端读了六种 app nav schema 拒绝的拼写,外加一个不存在的 view 变体 #4881's scope" becomes "is a follow-up card's question, deliberately left out of [finding] Studio 的导航消费端读了六种 app nav schema 拒绝的拼写,外加一个不存在的 view 变体 #4881's scope". Nothing lands it (the fallback read is still there) and no successor is recorded in history, so the card is named by role.
2. Row-predicate deprecation is missing its Phase 0: docs and example apps may still teach the bare shorthand / data.* spellings the new warning now flags #5738 "stand-down 3", and docs(plugin-form): Phase 0 of the row-predicate deprecation — stop teaching the bare shorthand (#5738) #5758. The finding (RLS and flow conditions are not row surfaces) was recorded on the dead Phase-0 corpus-sweep card, not in a commit. 702c48a62 is that sweep's landing and the squash of PR docs(plugin-form): Phase 0 of the row-predicate deprecation — stop teaching the bare shorthand (#5738) #5758, but it is a one-line plugin-form/README.md edit that says nothing about a stand-down, so it cannot carry the finding (review 5861306588). The card is therefore named by role, with the sha only to locate it: "(objectui#5738 stand-down 3)" becomes "(stand-down 3 on the corpus-sweep card behind 702c48a62)" in the conditionScope.ts file docblock and in 7727-conditional-formatting-record-scope.md, and the sharing_rule doc of CONDITION_SCOPE_BY_METADATA_TYPE reads "a stand-down 3 surface of the corpus-sweep card behind 702c48a62". rowPredicateCanon.ts is different: "(the objectui#5738 corpus sweep, PR docs(plugin-form): Phase 0 of the row-predicate deprecation — stop teaching the bare shorthand (#5738) #5758's recipe)" becomes "(the 702c48a62 corpus sweep's recipe)", and that commit's message does carry the recipe (the detectNonCanonicalRowSpelling oracle); the review found it correct.
3. Console half of ActionSchema.onSuccess navigation (objectstack#9566/#9474): SPA route hop, executeAPI handling, ${result.*} interpolation scope #5221, consoleServerAction.ts. "precedence — objectui#5221 escalates it" becomes "precedence — the card behind 053fdc8f9 escalates it": the escalation lived on the card, and no later ruling on that precedence is in history.
4. record:alert silently ignores the declared visibleWhen gate that its sibling blocks honour — the same defect already closed on the record-header face #5401 and Bind record into node-level visibleWhen, and stop visible swallowing it #5505. In visibilityDiagnostic.ts, "(objectui#5401 → Component-level visibleWhen binds no record on record pages — every record.* predicate fails soft to permanently visible, on every block #5454)" becomes "(objectui#5454)": the dead predecessor goes, the live successor the sentence already named stays. In data-table.tsx and 5926-empty-action-visible-when.md, "objectui#5401 / Bind record into node-level visibleWhen, and stop visible swallowing it #5505 closed for record:alert" becomes "c86185eb5 closed for record:alert": c86185eb5 is the squash of PR Bind record into node-level visibleWhen, and stop visible swallowing it #5505, so the card / PR pair is one landing.
5. "that card" after a re-point. Where the next words leaned on the dead card, they were repaired minimally: "on the flag that card was not about" becomes "that change was not about" (MarketplacePackagePage.tsx, gate-listlocalinstalls-marketplace-5620.md); "The card's complaint was" becomes "The complaint it answered was" (StudioDesignSurface.tsx); "is that card's to declare, not this one's to guess" becomes ", the caller's to declare, not this list's to guess" (ConditionBuilder.tsx's REFERENCE_ROOTS); "belongs to objectui#6296" becomes ", which 88b15fddc added" (6293-conditionbuilder-reference-value.md); "the unstaffed state objectui#5414 asks to surface" becomes "the unstaffed state 77f846a8b surfaces"; "is not what objectui#5414 reports" becomes "is not what 77f846a8b fixes".
6. Rulings by date. "(objectui#5709 ruling)" becomes "(maintainer ruling 2026-08-23)" in the A gauge widget's options.invert has no observable effect, and nothing can say so — it is an undeclared key riding DashboardWidgetOptionsSchema.passthrough() #5709 changeset (own card) and "(the 2026-08-23 ruling; ...)" in validate.ts; "whose objectui#5709 ruling states the constraint" becomes "whose 2026-08-23 ruling states" in kanban-quick-add.ts; "ruled LIVE by objectui#6896 (maintainer ruling 2026-08-31, prose follows machine)" becomes "ruled LIVE by the maintainer ruling of 2026-08-31 (prose follows machine)" in ChartRenderer.tsx, and 8650-chart-foreign-dialect-retired.md's "ruled live by objectui#6896" becomes "ruled live by the maintainer ruling of 2026-08-31".
7. "Phase 2" wording. "the warning objectui#5741 deleted" becomes "the warning Phase 2 (83fe6e741) deleted" in celAuthoring.ts, so the next sentence's "That ruling" keeps its antecedent; "objectui#5741 Phase 2 retired" becomes "Phase 2 (83fe6e741) retired" in ConditionBuilder.tsx and 8167-conditionbuilder-mount-scope.md; layout.ts's "objectui#6951 (maintainer ruling A1, 2026-09-04) decided it" becomes "maintainer ruling A1 (2026-09-04, 5ad86ddee) decided it".
8. Own-card pointers that needed a word. dashboard-table-header-one-spelling-5425.md: "the defect class objectui#5425 rules out" becomes "the defect class this change rules out". 6757-global-search-notifications-renderers.md and the two Two alias pairs on TextSchema and TreeViewSchema are now DECLARED in both spellings — and TreeViewSchema.data is required while nodes is the documented one (deferred rulings carried out of #6150) #6951 changesets: the parenthesis opened on its own card, so the line break moved with it ("page blocks.", "is RETIRED" then "(maintainer ruling ...)"). 6854-layout-renderer-retired-onclick.md: "(objectui#6854, maintainer ruling ...)" becomes "(the maintainer ruling ...)".
9. The runtime strings. Only the listed text moves in each (RECORD below stands for the interpolated canonical root).

file	member	before	after
types/src/zod/complex.zod.ts	DashboardConfigSchema.aria, error	"RETIRED (objectui#5852) — aria is no longer part of DashboardConfig; ..."	"RETIRED (ADR-0049) — aria is no longer part of DashboardConfig; ..."
types/src/zod/complex.zod.ts	DashboardConfigSchema.aria, .describe()	"RETIRED (objectui#5852) — the { label, description } spellings ..."	"RETIRED (ADR-0049) — the { label, description } spellings ..."
types/src/zod/data-display.zod.ts	TreeViewSchema.data (tombstone)	"RETIRED (objectui#6951) — data is no longer part of TreeViewSchema; ..."	"RETIRED (ADR-0049) — data is no longer part of TreeViewSchema; ..."
types/src/zod/data-display.zod.ts	ChartDataSeriesSchema.data (tombstone)	"RETIRED (objectui#6896) — ChartDataSeries.data was never read: ..."	"RETIRED (ADR-0049) — ChartDataSeries.data was never read: ..."
types/src/zod/layout.zod.ts	TextSchema.value (tombstone)	"RETIRED (objectui#6951) — value is no longer part of TextSchema; ..."	"RETIRED (ADR-0049) — value is no longer part of TextSchema; ..."
types/src/zod/data-display.zod.ts	TreeViewSchema.nodes	"... no presence rule exists — objectui#6951 B1). ... the data fallback spelling was retired by objectui#6951 (the registration's ..."	"... no presence rule exists). ... the data fallback spelling was retired (the registration's ..."
types/src/zod/layout.zod.ts	TextSchema.content	"... its value fallback spelling was retired by objectui#6951)"	"... its value fallback spelling was retired)"
app-shell/src/views/metadata-admin/celAuthoring.ts	the metadata-layer-root advisory in rowCanonAdvisory	"... binds the record as RECORD and nothing else (objectui#5741). The CEL scope ..."	"... binds the record as RECORD and nothing else. The CEL scope ..."

10. What follows the tombstone strings, and nothing else in it. The literal anchors on the old text in the six pinning tests: dashboard-config.test.ts (/RETIRED \(objectui#5852\)/ becomes /^RETIRED \(ADR-0049\) — /; the "delete the key" remedy anchor stays), tree-view-data-retired-6951.test.ts and text-value-retired-6951.test.ts (the full GUIDANCE literal's opening and the describeOf anchor; PRESCRIPTIVE stays), chart-inline-data-retired.test.ts (three anchors; the xAxisKey and chart-level data remedy anchors stay), chart-data-model-7113.test.ts and chart-series-keys-7546.test.ts (one anchor each). The two changeset quotes (6951-text-value-retired.md, 6951-tree-view-data-retired.md, frontmatter byte-identical) and the two content/docs quotes (text.mdx, tree-view.mdx) open RETIRED (ADR-0049) —. Per the ruling these follow the changed string; they do not widen the card's classes. No test, doc or changeset quotes either aria string (whole-tree search after the amendment: the source line is the only hit).

Held

By the serial rule: nothing. The open-PR list was read at the start (11 open) and re-read for each round; at round 2 there are 9 open besides this one and the release PR: objectui#10873, #10871, #10870, #10852, #10821, #10780, #10777, #10714 and #10278. In round 1, two of them touched files this PR edits: objectui#10821 (types/src/objectql.ts, types/src/zod/objectql.zod.ts) and objectui#10714 (types/src/data-display.ts, types/src/layout.ts, types/src/zod/data-display.zod.ts, types/src/zod/layout.zod.ts). Each one's hunks (3 lines of context) were mapped onto the head through a line alignment of the PR's merge-base file: none of the 22 lines this PR changes in those files lies inside, or beside, any hunk. objectui#10871 (new since) touches celAuthoring.ts and metadata-admin/i18n.ts in disjoint hunks (review 5861306588), and no open PR touches a file round 2 edits. Trial merges of each open PR head with this head (git merge-tree --write-tree): clean for #10873, #10871, #10870, #10852, #10780, #10777 and #10714; #10821 (24bcb0035) and #10278 (eab4c8e52) conflict, but each conflicts identically against main alone, so the conflicts are not this PR's. PR #5400 (Version Packages) regenerates and is not a hold.

Changesets

• .changeset/10803-dead-citation-sweep-third-batch.md, EMPTY frontmatter: the comment-only edits in 12 released packages; no published behaviour changes through them. Its list of citation forms now ends "or a live successor, and where nothing answers they name the card by role" (the review's optional nit), and it points at the second file for the runtime text.
• .changeset/10803-third-batch-runtime-strings.md, '@object-ui/types': patch and '@object-ui/app-shell': patch. Its second sentence now reads "so no dead pointer becomes a commit: tombstones cite ADR-0049 in its place, and every other pointer is simply dropped" (review 5861306588 fix 2, in the amendment's all-four wording). It names the four tombstones, all now opening RETIRED (ADR-0049) — (TreeViewSchema.data, TextSchema.value, ChartDataSeriesSchema.data, and DashboardConfigSchema.aria's error and describe text), with no process clause about a TypeScript twin; then the two describe strings and the advisory. Nothing after a tombstone's dash moves, and no key, path, issue code, accept set, refusal or severity moves.

Proof of prose-only (C4), against main fab627ff9

• Source. Each of the 77 touched non-test .ts / .tsx files was parsed at fab627ff9 (the main merged in, so the diff is exactly this PR's) and at this head with TypeScript 6.0.3's createSourceFile and re-printed by createPrinter({ removeComments: true }): 73 of 77 prints are identical, and the other 4 (celAuthoring.ts, complex.zod.ts, data-display.zod.ts, layout.zod.ts) are equal after exactly the 9 listed string substitutions are applied to the main print (each matched once): the 4 tombstone strings in 5 literals, the 3 describe-string deletions and the advisory's. 0 parse diagnostics. Lit controls on the same instrument: dropping "(ADR-0049)" from the TextSchema.value string moves the print; re-spacing a comment does not.
• Changesets. The frontmatter block of every one of the 47 edited changesets is byte-identical at fab627ff9 and this head (47 of 47); the overwrite gate below agrees.
• Scope of the diff against main: 134 files, +287 / −237: 47 edited and 2 new changesets, 77 non-test source files, the 6 pinning tests and the 2 content/docs pages.

Gates, on this head dd37e35d2

Each line is the gate's own verdict and exit code, captured by redirect-then-$?.

• node scripts/check-changeset-presence.mjs, exit 0: "83 source file(s) of 12 released package(s) changed, and this change declares 2 changeset(s): .changeset/10803-dead-citation-sweep-third-batch.md, .changeset/10803-third-batch-runtime-strings.md." (83 = the 77 sources and the 6 tests under packages/types/src).
• pnpm changeset:check, exit 0: "All workspace packages are in the changeset fixed group." / "No changeset declares a major bump."
• node scripts/check-changeset-overwrite.mjs (report-only), exit 0: "2 changeset(s) added, 47 modified, 0 deleted"; declared at base equals declares now for 47 of 47.
• pnpm check:changeset-claims (report-only), exit 0: born-false "Every one of those 9 address(es) either names the tree it was read from, or points at a line this change does not move"; self-contradiction "Every package declared across those 45 body(ies) is either not negated ..."; and the standing notice "92 pending changeset(s) describe a file this change touches". Read against the diff: a pending changeset quoting a replaced pointer would itself carry the dead number and so sit in the census; the only pending quotes of the four tombstone strings are the two edited here; and none of the words repaired beyond a pointer (Special cases 1, 3 and 5) occurs in any pending changeset.
• pnpm check:control-bytes, exit 0: "check-control-bytes: OK (scanned 9113 tracked text file(s); skipped 85 binary)." Self-scan of the 134 changed files for C0 / DEL bytes: 0.
• Also run: pnpm check:new-line-citations, "VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0"; governed-surface predicate over the 134 paths, exit 0, "NOT GOVERNED — 134 path(s) checked against 5 governed surface(s); none matched." (lit control AGENTS.md: exit 3).

Tests, through the shared verify lock (VERDICT command-exit 0). Round 2, on this head: the six pinning files (dashboard-config, tree-view-data-retired-6951, text-value-retired-6951, chart-inline-data-retired, chart-data-model-7113, chart-series-keys-7546) and tombstone-discriminator-agreement-9684: Test Files 7 passed (7), Tests 144 passed (144). Round 1, on e4bce25b8 (round 2 changed no other tested string): those seven plus tree-view-data-optional-6939, undeclared-but-consumed-keys-6150, zod-mirror-parity, layout-default-jsdoc-7361 in packages/types, and celAuthoring.fieldRuleVerdict-9318, recordScopeDataRoot-8166, ConditionalFormattingEditor in packages/app-shell: Test Files 14 passed (14), Tests 393 passed (393).

Whole-tree search for other verbatim quotes of the four old strings (tests, docs, examples, skills, apps): every hit is one of the source strings, the six anchors, the two changeset quotes or the two docs quotes, all updated. Remaining mentions of the old prefix are six @ts-expect-error comments in text-value-retired-6951.test.ts and tree-view-data-retired-6951.test.ts that describe the TypeScript face, not the runtime string; left as they are (see Acceptance notes 5).

Declared narrowing (per the dispatch: the named checks, not wider sweeps). NOT MEASURED locally: the full suites and type-check of the 12 touched packages, and eslint. Reason: the comment-stripped syntax tree of 73 of the 77 touched source files is identical to main and the other 4 differ only by the listed string-literal edits; every test that quotes a changed string was found by search and run above. CI runs the full farm.

Acceptance notes

1. The remainder rides this card, unchanged (seat amendment 5860244997, Q2 = A). Of the 115 numbers PR objectui#10854's Acceptance notes item 1 lists, this PR carries the first 30 in ascending order plus finding(types/plugin-charts): the static ChartSchema node's two data keys are declared-but-unread — ChartDataSeries.data is required and never read, and categories is read as a SERIES list, not axis labels #6896 and Two alias pairs on TextSchema and TreeViewSchema are now DECLARED in both spellings — and TreeViewSchema.data is required while nodes is the documented one (deferred rulings carried out of #6150) #6951, which that PR's release named. The other 83 are: AppShellBranding.title 的 JSDoc 写 "Page title suffix",代码却是整条覆盖 document.title #6872 finding(core/contract): the newly minted box type is not in PUBLIC_BLOCKS Tier B, so the curated AI-authoring vocabulary omits a type 27 catalog exemplars now teach #6879 [Decision] Declare renderCellEditor and schema-level cellClassName on DataTableSchema? — the two live undeclared keys the #6459 census measured #6882 finding(components): metadata-viewer hand-writes a fifth copy of the select-option shape instead of deriving it #6887 finding(fields): LocationField's THIRD refusal sentence (the #6715 residue arm) is still hard-coded English after the #6755 ruling keyed the other two #6888 finding(data-objectstack): WireDroppedFieldsEntry's guard still asserts more than the shape filter checks — fields element types and object presence #6889 finding(test-infra): 298 more vi.mock factories freeze a workspace package's export surface — the per-specifier sweep worklist #6892 fix(plugin-timeline): judge gantt dates by TYPE — string, finite number, or Date #6905 finding(plugin-timeline): the unusable-gantt-date diagnostic spells an array or an object either BLANKLY or as a text that looks like a valid date #6907 finding(docs): the "every body cell" claim about schema-level cellClassName is false, and it predates #6882 in two upstream texts #6921 [Decision] Where does logic shared between .mjs CI gate scripts and TypeScript tests live? — @object-ui/test-support is TS-source-only, so #5872's class (3) cannot use the class-(1) pattern #6923 finding: a fifth, larger Zod-internals reader family — 15 files cast to { options?: readonly string[] } and read .options straight off a top-level enum node, with the same quiet-permissive failure #5872 catalogues #6924 finding(types): 11 ADR-0049 tombstones still emit zod's generic "expected never" — the shared retirementTombstone() mechanism now exists, so each is a one-line conversion #6931 DataTableSchema.rowActions is z.array in the zod mirror and boolean everywhere else — the mirror is the outlier #6940 TextSchema.variant is a nine-value enum that the ui:text renderer never reads — declared-but-unenforced, and it refuses 5 catalog entries #6942 The Console submits the value of a field its own visibleWhen has hidden, and clears nothing — so visibleWhen on a populated lookup is a dead end, not a hint #6958 finding(test-infra): ObjectGantt.referenceArms-6837.test.tsx:257 reads the lazy Gantt through a SYNCHRONOUS query and ejects unrelated PRs from the merge queue — two ejections in 15 minutes, neither PR touching plugin-gantt #6959 MetadataClient.publish and publishDraft disagree about the dispatcher envelope on the same publish route #6962 Studio: render advisories on the BATCH publish door ("publish whole app") — blocked until objectstack#9343 stops discarding them server-side #6965 finding(cli): validate / check print only TOP-LEVEL zod issues, so every union-shaped schema reports a bare "Invalid input" and the per-arm guidance is never seen #7004 finding(fields): FieldEditWidget still drops the DECLARED non-DOM host-plumbing keys — error, dataSource, dependentValues, dependsOn, dependsOnLabels, emptyHint, onUploadingChange, onSelectRecord, onCreateNew #7008 finding(types): the published Zod AnyComponentSchema accepts the block-family discriminants that the published TS AnySchema excludes — a shipped validator green-lights nodes no renderer renders #7023 finding: the SIXTH Zod-internals reader spelling — 9 sites cast NON-optionally to { options: readonly string[] }, which #6924's instrument cannot see #7025 finding(plugin-timeline): spellGanttDateValue's Array.isArray is the last non-total operation on the gantt date path — a revoked Proxy crashes it #7036 @object-ui/types' Phase-2 ActionCallback surface is a third onSuccess meaning — declared, zod-mirrored, doc-advertised, zero producers #7068 finding(types): no parity ledger watches the mirror-WIDER-than-declared direction — a key the zod face accepts and the TS face refuses is invisible by construction #7069 finding(components): button-group implements no selection, and never wires the per-button onClick / disabled it declares — the catalog authors 29 keys nothing reads #7077 finding(docs): the canonical BaseSchema common-props table under-states five declared types and omits five declared members #7079 finding(types): 18 schemas narrow inherited disabled to boolean while 0 narrow its twin visible — no ruling says which is intended #7087 BaseSchema.hidden's JSDoc promises visibility: hidden, but the renderer returns null for it exactly as for visible: false #7088 feat(app-shell): console renderers for app:launcher and nav:menu (Phase 1 of objectstack#12183) #7091 columns: { "2xl": N } parses and is then silently dropped — the spec accepts six breakpoints, the grid renderer reads five #7097 Approval inbox: render a dead record reference as a "record deleted" tombstone, never the raw record id #7108 ADR-0130(objectstack#14122):Studio 包选择器列出 project 域的 module 包 #7177 Switch the sharing_rule edit-door client gate on — blocked until #7603 stops the _diagnostics decoration reaching the gate #7612 date has the same two-convention split datetime just had: data-table's date-only cell keeps a year that formatDate drops #7620 finding(types): DashboardComponentSchema.title is declared-but-unread once the #7509 retirement lands #7623 finding(plugin-markdown): extractToc strips tag-shaped text INSIDE inline code, so its #id links miss the heading they name #7658 finding(plugin-markdown): extractToc lists a heading the renderer never emits, when the heading sits on the line right after a JSX/raw-HTML block #7666 finding(plugin-markdown): extractToc's emphasis rules eat intraword underscores, so a SCREAMING_SNAKE heading gets an id no anchor carries #7667 feat(types)!: retire FloatingChatbotConfig.triggerIcon as an ADR-0049 tombstone (objectui#7654) #7669 types: the triggerIcon tombstone's rationale contradicts mobile.ts's own retire-vs-remove discriminator, and its tripwire comment overclaims #7678 bug(plugin-charts): a declared per-series type override is DROPPED when every series entry is written with dataKey — the internal-shape fast path forwards the array raw and the renderer reads only chartType #7681 finding(plugin-charts/core/types): series variant carries three different unions across its declarations and readers — current is an undocumented synonym of primary that core's seriesPresentation drops #7682 finding(types/plugin-chatbot): six ChatbotSchema keys are declared and read by no registration — loading, showAvatars, userAvatar, assistantAvatar, markdown, height #7703 finding(types): SchemaRegistry / ComponentType omit chatbot-enhanced and chatbot-floating — two registered keys the layer can now name #7704 finding(plugin-chatbot): chatbot-floating spreads the whole authored node raw and LAST onto its panel — three undeclared keys are live, the authored messages seed overrides the runtime messages (a sent message never renders), and node keys land as DOM attributes #7708 finding(types): 39 handler keys a registered renderer READS are declared by no arm — accepted and KEPT by the passthrough, on main today #7804 finding(scripts/i18n): a key template forwarded into a same-module RESOLVER is seen by neither the argument position nor #7592's key-builder leg — two heads on main, 0 CONFIRMED today #7844 finding(examples): component-fixture-declared-keys.test.ts cites safe-validate-corpus-6318.test.ts:98 by LINE — a comment-only edit above that line moves it, and nothing goes red #7853 finding(types): safeValidateSchema enforces per-type component schemas on the ROOT node only — every nested child is matched against the passthrough BaseSchema, so a DECLARED key with a wrong-typed value passes at any depth #7869 finding(plugin-timeline/i18n): five timeline.relative.* defaults rows have no en key and no caller — invisible to every existing i18n gate #7874 i18n(gate): bring the hand-rolled fallbackT tables into the createSafeTranslation value-compare via a declared registry #7877 finding(types,components,docs): page.actions has no reader on the page node — the array renders nothing and leaks onto the wrapper element as actions="[object Object]", while guide/layout.md teaches it in three passages #7926 finding(app-shell): every envelope reader on the package surfaces drops producer-marked text — fetchPackages discards the whole body, apiJson reads no userMessage #7959 finding(gate): the two twin count pins keep the # markers the third copy strips, so a count that wraps across a comment line is invisible to both — measured #7967 finding(app-shell): PackageFormDialog holds a fourth copy of the envelope ladder and still drops error.userMessage and error.code #7979 finding(console): the agent-key generator reads only error.message, so a marked userMessage and the code never reach the developer #7980 MetadataFieldsPage loses a lookup's target when it is stored under the retired referenceTo spelling — the read door reads reference alone, and the carry-over docblock claims the strip "costs nothing" #8058 MetadataFieldsPage silently rewrites any field whose type is outside DESIGNER_FIELD_TYPES to text on save — a stored master_detail or vector is destroyed by editing anything else on the object #8060 finding(types): InputSchema.wrapperClass is declared on the TS face and absent from its zod mirror — the one schema.wrapperClass reader still ledgered in UnmirroredDeclared #8072 A spec-valid type: 'page' view silently renders as a grid — ViewType in packages/types/src/views.ts never gained page, so six total maps over it compile green while being incomplete #8127 Decision: registry-inputs-spec-parity fails on the 17.3.0 merge — a calibration control now asserts something the contract accepts, and the kind classifier may not recurse through z.union #8137 console: registry-inputs-spec-parity's refusesKind reads a union branch's [invalid_type, too_small] pair as a CONTENT refusal, so an array probe the contract refuses enters the accepted-kind set #8204 finding(components): flex.tsx's own registration declares defaultProps.align: 'center' while its renderer falls back to 'start' #8229 finding(types): objectui#8222's exclusion message still calls the seed decomposition a LIVE figure, which objectui#8243 made historical #8248 plugin-kanban: the lane header count is col.cards.length — it counts the fetched window, not the group, so a board over more than limit rows reports plausible-looking wrong totals #8307 [finding] Public form page /f/:slug renders the object API name as its <h1>: the fallback chain reads form.label, a key FormViewSchema rejects, while the config carries title — and description is never rendered #8408 Studio: the "Create app" dialog's confirm control shares an accessible name with the toolbar button that opens it — a mis-click silently leaves the app uncreated #9231 ci.yml's type-check and e2e decide steps have no markdown stage, and the only thing holding that up is an ASSERTED claim — "type-check reads no document, and no e2e spec does" was never traced #9241 pickSpanClass emits a col-span class for ONE breakpoint tier only, so span: 'full' under-spans at every intermediate tier — and the correct per-tier implementation already exists in plugin-detail #9244 finding(types,components): docblocks assert bridgeListView writes these slots in the PRESENT TENSE — the whole spec-bridge was retired by #6366, and one of them is the stated factual basis of ruling #4580 #9365 bug(plugin-list): ListView's record-detail overlay heading renders [object Object] Detail for an inline-locale-map label — the t() options sink no compiler can name #9373 finding(types): base.ts's vocabulary docblock says the two i18n label shapes "each accept the other's shape vacuously" — an instrument now in the tree refutes it, on the reference face #9375 finding(core/app-shell): ResultDialogSpec hand-copies the contract's resultDialog block and has drifted — title / description / acknowledge are string here and I18nLabel in the contract #9542 finding(docs): AGENTS.md documents a BaseSchema.events key that no schema declares and no renderer reads — BaseSchemaCore is passthrough, so a node authored from the instruction file is silently discarded #9553 measurement only: does the zod refusal gate the collapsible RENDER path, or only validate? — the binary precondition every route on objectui#8236 depends on #9585 [repo:objectui] page:header crashes with React #31 when the record's name field is empty — the title fallback picks a lookup field and renders its expanded record object as a JSX child #10117 App nav item visible (CEL) is served to the client but never evaluated — a silently inert gate (17.2.0) #10119 [repo:objectui] Record edit form posts every displayed field, so a user with field-level editable:false on any form field gets 403 「您没有权限保存这条记录」 even when editing only an allowed field — inline grid sends the dirty cell and succeeds #10120 An action's params dialog renders a field-backed lookup as a bare text input — 0 options, no request on the wire, so the action cannot be launched from the UI at all #10129 console: #7804's GlobalFilterSchema.object is never read, and ChartAxisSchema.title bypasses a locale resolver in its own bundle — two dashboard i18n surfaces declared translatable and not resolved #10132 #14026. None of them was touched here.
2. The census instrument is blind to bare PR numbers, and so is the family list. PR objectui#10854's census enumerated objectui#N and objectui URLs only, so a bare #N that answers 404 never entered the 115: this batch found two by reading its own sentences, Bind record into node-level visibleWhen, and stop visible swallowing it #5505 and docs(plugin-form): Phase 0 of the row-predicate deprecation — stop teaching the bare shorthand (#5738) #5758, both the PRs whose squashes the sentence already cited, and folded them in (ruling 5861129870, triage item 3). The printed instrument above counts a bare number only when the batch names it. ⇒ The next batch's census should first enumerate every distinct bare #N in the two in-scope classes, read each by REST (issues/N and pulls/N), and add the 404s to its number list before it counts. Until that is done the family pin is incomplete for bare numbers, and nothing here re-derives how many there are.
3. Published text outside the two in-scope classes still names some of these numbers, untouched by scope (another class, which the triage split did not scope here): apps/console's useApiDiscovery.ts (non-test source of @object-ui/console, bare API Console endpoint catalog still keys the Storage group by the deprecated file-storage slot — move to the canonical storage key (framework #9683) #5286, not under packages/*/src), the @object-ui/data-objectstack README (finding(data-objectstack): aggregate()'s spec-shape branch never reads filter/field/function, so an array groupBy on the LEGACY shape silently drops both the filter and the measure #6864) and the @object-ui/plugin-detail README ([approvals] The "withdraw approval" button renders for non-submitters on a pending record — a lit button whose click always fails #6464), content/docs (finding(types/plugin-charts): the static ChartSchema node's two data keys are declared-but-unread — ChartDataSeries.data is required and never read, and categories is read as a SERIES list, not axis labels #6896, and the text.mdx / tree-view.mdx "Retired" notes that name Two alias pairs on TextSchema and TreeViewSchema are now DECLARED in both spellings — and TreeViewSchema.data is required while nodes is the documented one (deferred rulings carried out of #6150) #6951; only their verbatim message quotes moved here), and published CHANGELOG.md history (never re-addressed). Carrier: none.
4. Filenames are not citations. Pending changeset FILENAMES carry several of these numbers; they stay, as in PRs objectui#10707, docs: cite landing commits where pending changesets and source docblocks name ten objectui issues that answer 404 (objectui#10771) #10797 and docs: cite landing commits where pending changesets and source comments name fourteen objectui issues that answer 404 (objectui#10803) #10854.
5. Test comments left as they are. text-value-retired-6951.test.ts and tree-view-data-retired-6951.test.ts each keep three @ts-expect-error comments reading "RETIRED (objectui#6951)"; they describe the ?: never TypeScript face, quote no runtime string, and tests are otherwise out of this card's classes.

---

Generated by Claude Code

[github-actions]

changeset-claim-re-read

⚠️ 92 pending changeset(s) describe a file this change touches

Their bodies publish verbatim into the CHANGELOG at the next release, so this is a request to re-read them against your diff — addressed here because you are the one seat that can answer it without re-deriving anything.

⛔ Nothing here blocks, and nothing here is a verdict on your change. This gate exits 0, is not a required context, and judges name resolution, never meaning: it asked whether a pending body names a file you touched. "Is this sentence still true?" is the one question it will not answer, and the one you are being asked to answer.

.changeset/4895-retire-block-schema-family.md

• names packages/types/src/layout.ts → packages/types/src/layout.ts — edited by this change

  ⚠️ Not this family, and not touched. The live slotted record-page vocabulary — PageNodeSchema.kind === 'slotted' with slots?: PageSlotMap (packages/types/src/layout.ts), rendered by usePageAssignment / PageBlockCanvas / PageBlockInspector in @object-ui/app-shell — shares the words "block" and "slot" with the retired family and shares no declaration, type or file with it. Neither is the type: 'component' NAVIGATION item kind ({ type: 'component', componentRef }, NavigationItemSchema in zod/app.zod.ts), a different declaration in a different module.

.changeset/5453-retire-grid-column-wrap-forward.md

• names data-table.tsx → packages/components/src/renderers/complex/data-table.tsx — edited by this change

  generateColumns() copied a per-column wrap onto every column object handed to data-table, and packages/components' data-table.tsx never read it. Measured on the current ref rather than inherited from the card, with comments stripped so prose mentions cannot be counted as reads: a column-level wrap scores 0, against accessorKey 34, align 5, header 4, className 4, width 8 and fitContent 2 in the same query shape. Those sibling counts are the positive control — the search style does find the keys that are genuinely consumed, so the zero is a measurement and not a mis-aimed grep. The raw string wrap does occur in that file; every occurrence is flex-wrap, whitespace-nowrap, or a variable named wrapper.

.changeset/5632-svg-host-dom-passthrough.md

• names packages/types/src/layout.ts → packages/types/src/layout.ts — edited by this change

  Both renderers forwarded their whole prop bag to the SVG they render, so every authored SDUI key on the node became an attribute — 14 per target, and icon="check" on all 71 icon nodes in the schema catalog. The two nodes declare different keys, and each renderer consumes its own node's keys by name: IconSchema (packages/types/src/layout.ts) against the pass-through docblock in renderers/basic/icon.tsx, and SpinnerSchema (packages/types/src/feedback.ts) against the one in renderers/feedback/spinner.tsx. icon and color are IconSchema's alone — SpinnerSchema declares neither. Read those two declarations for what they carry; this paragraph deliberately copies no member list. So the SDUI pass-through list withholds nothing they need.

.changeset/5853-tablecolumn-type-canonical-union.md

• names data-table.tsx → packages/components/src/renderers/complex/data-table.tsx — edited by this change

  @object-ui/types exports TABLE_COLUMN_TYPES (the canonical tuple — the single declaration the zod mirror builds its enum from, so the two cannot drift), the TableColumnType union, and normalizeTableColumnType() for producers. The as any cast in data-table.tsx is deleted and the read is typed, so re-introducing an undeclared spelling is a tsc error rather than a silent widening.

.changeset/5876-one-lookup-predicate.md

• names ObjectDataTable.tsx → packages/plugin-dashboard/src/ObjectDataTable.tsx — edited by this change

  computeLookupExpand in ObjectDataTable.tsx carried its own isLookup, byte-identical to the exported isLookupType in recordFields.tsx after objectui#5692 pointed both at @object-ui/core's EXPANDABLE_FIELD_TYPES. Nothing kept them aligned: a future edit to either — a member added, the retirement gate moved — would have re-forked the $expand decision from the predicate whose docblock claims to drive it. computeLookupExpand now calls isLookupType, which gains its first production consumer, and the module no longer imports the shared family or the retirement gate at all.

.changeset/5903-objectgantt-declared-keys.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  Both halves move together. The TS declaration (packages/types/src/objectql.ts) and its zod mirror (src/zod/objectql.zod.ts) gain the same ten keys at the same requiredness — all optional — and no KnownDrift entry is added. navigation is taken from @objectstack/spec's NavigationConfigSchema by reference rather than restated, matching ObjectGridSchema.navigation.

• names src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Both halves move together. The TS declaration (packages/types/src/objectql.ts) and its zod mirror (src/zod/objectql.zod.ts) gain the same ten keys at the same requiredness — all optional — and no KnownDrift entry is added. navigation is taken from @objectstack/spec's NavigationConfigSchema by reference rather than restated, matching ObjectGridSchema.navigation.

.changeset/5945-asarray-contract-envelope.md

• names useApproverDirectory.ts → packages/app-shell/src/hooks/useApproverDirectory.ts — edited by this change

  useApproverDirectory.ts and views/metadata-admin/AssignedUsersSection.tsx both normalised a find() answer with

.changeset/5993-button-shared-icon-resolver.md

• names complex/data-table.tsx → packages/components/src/renderers/complex/data-table.tsx — edited by this change

  renderers/form/button.tsx carried its own toPascalCase, its own iconNameMap holding the single Home -> House entry, and its own index into lucide's runtime icons record — the same algorithm as renderers/action/resolve-icon.ts, but not the same function. The action:* family, complex/data-table.tsx and both menu renderers already import the shared one. The hazard was drift, not rendering: an alias added to resolve-icon.ts to absorb a lucide retirement (the objectui#5586 / Two more retired lucide spellings reach the icons-record resolver — edit in DetailView's mobile Edit action, smile as the icon renderer's own default — and only one of the four resolver copies is pinned #5622 mechanism) reached every one of those sites and silently missed ui:button, which would have gone on resolving the retired spelling to nothing while the rest of the repo resolved it correctly.

.changeset/6105-tombstone-refusal-message.md

• names zod/tombstone.zod.ts → packages/types/src/zod/tombstone.zod.ts — edited by this change

  One shared mechanism carries the text into both channels. retirementTombstone() (zod/tombstone.zod.ts) takes the guidance string ONCE and writes it to both z.never({ error }) — the parse-time issue message — and .describe() — the generated JSON-Schema and docs surface, unchanged. One string, so the two cannot drift.

.changeset/6124-handler-keys-json-refusal.md

• names zod/tombstone.zod.ts → packages/types/src/zod/tombstone.zod.ts — edited by this change

  Every one of the 58 sites is now a named refusal arm in the shape 手写 FieldValidationRules 在唯一读点既不校验也不归一:pattern.value 写成 string(类型明确允许)被 react-hook-form 静默忽略,未识别的规则名同样静默丢弃 #5099 landed for FieldConstraintsSchema.pattern.value (z.custom + guidance, via handlerKeyRefusal() in zod/tombstone.zod.ts): the message names the key, says why JSON cannot author it, and points at the node-type spelling PR fix(examples,docs): correct the toast demos to spellings the engine executes #6498 established ({ "type": "toast" }, an action:button node with a declared action). The same text is the key's .describe() metadata — one string, two channels. Deleting the keys was measured and refused: under BaseSchema.passthrough() an undeclared key is not refused, it is KEPT, and onClick rides SDUI_DOM_PASS_THROUGH_KEYS into the DOM listener slot where React throws at click.

.changeset/6175-column-state-persistence.md

• names data-table.tsx → packages/components/src/renderers/complex/data-table.tsx — edited by this change

  • @object-ui/components — DataTableSchema has declared onColumnResize?: (columnKey, width) => void all along, and data-table.tsx invoked it nowhere: the resize drag updated the table's local columnWidths state and stopped there. It now reports the settled width once, at mouseup. Once, deliberately — the host turns this callback into a write to shared view config, so a per-mousemove callback would be a write storm. - @object-ui/plugin-grid — ObjectGrid emitted onColumnReorder (singular) while the renderer invokes the near-duplicate onColumnsReorder (with the s), a different declared key with a different signature. The producer now emits the spelling the renderer actually invokes, mapping the reported TableColumn[] to the accessorKey order columnState stores.

.changeset/6238-object-payload-enabled.md

• names packages/app-shell/src/index.ts → packages/app-shell/src/index.ts — edited by this change

  No published type changed. ObjectMetadataPayload is exported from its module but that module is not re-exported by packages/app-shell/src/index.ts, the package's only entry, so the removed enabled?: boolean was never on the published surface and no **/src/index.ts is touched. What consumers can observe is behaviour: MetadataService is reachable through the published useMetadataService() hook, both method signatures are unchanged (PromiseANGLE-BRACKETS(void)), and the HTTP request they issue changes from a PUT with a body to a DELETE.

.changeset/6247-option-visiblewhen-metadata-admin.md

• names SchemaForm.tsx → packages/app-shell/src/views/metadata-admin/SchemaForm.tsx — edited by this change

  Three consuming controls now filter, and each has a pin asserting an option absent on a false predicate: the builtin Select in SchemaForm.tsx, MultiSelectWidget, and colorPaletteOptions → ColorSwatchGroupWidget. Asserting absence is the whole of the test design — this evaluator fails OPEN, so "the option is shown" is equally the outcome of predicate-true, predicate-never-arrived and predicate-faulted, and a positive-only pin passes against the unfixed renderer.

.changeset/6309-delete-object-fields-bridge.md

• names types/src/designer.ts → packages/types/src/designer.ts — edited by this change

  Removing it is not the whole change. Three comments — in types/src/designer.ts, types' designer-field-types.test.ts (twice) and fields' richtext-cell-renderer-5452.test.tsx — cited the bridge as a live corroborating source. Left behind, they would have swapped dead code for false documentation: three in-repo pointers telling a future reader that this bridge mediates between the framework field record and FieldDesigner, and nothing telling them it is unreachable. The two that named it as the consumer deriving an editable-subset check from DESIGNER_FIELD_TYPES now name MetadataFieldsPage, which does exactly that with the same idiom and the same objectui#3017 anchor. The third cited the bridge's richtext → html mapping as one of three corroborations that richtext stores HTML; the other two (the showcase seed and the field-type decision tree) are live and carry the point on their own, so that clause is dropped rather than repointed.

.changeset/6310-designer-formula-key-retired.md

• names packages/app-shell/src/views/metadata-admin/i18n.ts → packages/app-shell/src/views/metadata-admin/i18n.ts — edited by this change

  Not touched: designer.field.formula ('Formula (CEL)') in packages/app-shell/src/views/metadata-admin/i18n.ts, a different and live key belonging to metadata-admin's ObjectFieldInspector — the surface that still authors formula expressions.

.changeset/6335-starred-apps-nav-exclusion.md

• names UnifiedSidebar.tsx → packages/app-shell/src/layout/UnifiedSidebar.tsx — edited by this change

  StarredApps now filters items to type !== 'nav' before rendering — the same exclusion already applied to the sidebar Favorites list in UnifiedSidebar.tsx — restoring declared-equals-enforced behaviour and making the missing locale key correct by construction. No locale packs were touched, and the FavoriteItem / RecentItem union types are unchanged.

.changeset/6349-types-internal-name-collisions-batch-1.md

• names data-display.ts → packages/types/src/data-display.ts — edited by this change

  BreadcrumbItem / BreadcrumbSchema — re-pointed, because one copy was stale. Both were declared in data-display.ts and in navigation.ts. The data-display pair was not a second dialect but a strict SUBSET: no key declared differently on either side, and missing BreadcrumbItem.icon / onClick / siblings and BreadcrumbSchema.maxItems. Everything that reads a breadcrumb was already on the navigation declaration — registry.ts maps the 'breadcrumb' component type to it, src/index.ts re-exports it under the bare names, zod/navigation.zod.ts mirrors it (icon, onClick, siblings, maxItems included), the ui:breadcrumb renderer consumes it, and the component's own documentation page documents icon and maxItems. data-display.ts now re-exports the one authority.

.changeset/6373-datatable-emit-boundary.md

• names data-table.tsx → packages/components/src/renderers/complex/data-table.tsx — edited by this change

  The measured read set of the consumer (data-table.tsx, comments stripped) contains none of the six, so all six retire from the emit rather than being declared — declaring a key nothing reads is the same declared != enforced defect facing the other way. Rendering is unchanged because none of those keys was the live path for its own value: the FieldMeta the cell closure captures is what this widget's type-aware rendering has always read, and it is untouched. Authored spellings still pass through, so a column the author wrote as { format: '$0,0' } keeps its format exactly as before.

.changeset/6424-tablecolumn-declares-headericon.md

• names data-table.tsx → packages/components/src/renderers/complex/data-table.tsx — edited by this change

  Scope of the enforcement claim, measured: the declaration, the parse road, and the renderer's behaviour now agree; the renderer's internal column reads remain any-mediated (the col: any normalization in data-table.tsx) — a standing instrument gap, not closed here.

.changeset/6444-evaluator-fault-warn-dedupe.md

• names visibilityDiagnostic.ts → packages/react/src/utils/visibilityDiagnostic.ts — edited by this change

  This is the one-per-source rate limit both sibling reporters already carry (warnPredicateFailure in fieldRules.ts, visibilityDiagnostic.ts in @object-ui/react), not a third mechanism. The dedupe key is the predicate's authoring identity — the fault site plus the source text, never the scope it ran against — which is both the siblings' precedent and the defect itself: the 200-row flood is one authored source evaluated against 200 distinct scopes, so a scope-sensitive key would emit all 200 lines again.

.changeset/6499-inactive-values-retained.md

• names flow-node-config.ts → packages/app-shell/src/views/metadata-admin/inspectors/flow-node-config.ts — edited by this change

  • New inactiveRetainedKind(field, node, fields) in flow-node-config.ts — a pure read that reports a field rendered ONLY because the stored-value re-show rule fired. It distinguishes 'controller-off' (a real toggle the author can switch back on) from 'no-controller' (the __legacy__ render-only keys, where no such toggle exists and saying otherwise would be a fresh lie). - FlowNodeConfigField renders the notice beside the affected control, with a "Clear value" action so the author can discard the residue deliberately. Read-only inspectors show the notice without the action. - Coverage is every showWhen group in the inspectors, pinned mechanically: all 33 gated fields across the descriptor tables, plus the two runtime producers (an engine-published configSchema and a connector input schema) that mint groups no source file contains.

.changeset/6515-record-form-current-user-normaliser.md

• names console/AppContent.tsx → packages/app-shell/src/console/AppContent.tsx — edited by this change

  The normaliser moved from console/AppContent.tsx to providers/expressionUser.ts, beside the ExpressionProvider it feeds. That move is what made the fix available: RecordFormPage is lazy()-loaded BY AppContent, so importing the normaliser from its old home would have put a static edge from the split chunk back into the module it was split out of. Both console/AppContent.js and the package entry re-export the name, so buildExpressionUser is published exactly as before.

.changeset/6559-expression-user-input-contract.md

• names packages/app-shell/src/index.ts → packages/app-shell/src/index.ts — edited by this change

  WHAT BREAKS, AND FOR WHOM. This tightens a signature published from the package entry (packages/app-shell/src/index.ts), so an external caller that passes an unchecked or under-declared value stops compiling on upgrade. That is accepted (maintainer ruling 2026-08-27, option A): the only calls it refuses are calls that were never conformant with the contract the module already declared. It ships as minor, not major — objectui's major tracks @objectstack's, so its own breaking changes ship as a minor with the break written down (scripts/check-changeset-no-major.mjs). ⛔ Keeping unknown and ⛔ adding a second, wider entry point were both declined.

• names console/AppContent.tsx → packages/app-shell/src/console/AppContent.tsx — edited by this change

  NO RUNTIME BEHAVIOUR MOVES. All four in-repo production call sites pass useAuth().user, typed AuthUser | null, and type cleanly unchanged — two in console/AppContent.tsx, one in views/RecordFormPage.tsx, one in apps/console's InternalFormRoute.tsx. The body is byte-equivalent: the same keys, the same ?? defaults, the same anonymous branch. ⛔ No consumer-side fallback was added; id: u.id ?? null remains the rejected shape (triage ruling 2026-08-26), because a lenient default in the consumer is what AGENTS.md #0.1 forbids and it silently equates "signed in, no id" with "signed out".

.changeset/6681-declared-lazy-marketplace-routes.md

• names views/studio-design/StudioDesignSurface.tsx → packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx — edited by this change

  Both marketplace chunks were held by CHUNK CO-TENANCY, not by any import of the page: rolldown had parked components/SuggestedBindingsPanel.tsx (statically imported by the eager views/studio-design/StudioDesignSurface.tsx) in the first, and console/marketplace/InstalledListWidget.tsx (bare-imported by the package barrel for its SDUI registration) in the second. An app-shell-eager-leaves group in apps/console/vite.config.ts isolates those co-tenants so the three declared-lazy pages chunk by their own dynamic-only reachability. The console eager closure moves 3180.2 KB → 3171.5 KB gzipped (−8,888 bytes, 48 → 45 eager chunks) with the three per-chunk ceilings unmoved.

.changeset/6771-retire-body-child-list-dialect.md

• names renderers/layout/containers.tsx → packages/components/src/renderers/layout/containers.tsx — edited by this change

  Non-rendering readers keep their arm on the same rule, and none of them renders anything: while a renderer still reaches stored body content, a reader that must see the SAME content keeps its arm, or the renderer draws what the reader cannot find. Those are the two tab-subtree walkers in renderers/layout/containers.tsx, app-shell's pageSchemaIntrospect (CONTAINER_KEYS) and PageBlockInspector (STRUCTURAL_PROP_KEYS, the inspector half of a stored properties.body), and the CLI's OBJECTUI_STRUCTURAL_KEYS — a file-IDENTIFICATION marker, where keeping body is what lets an old file still be recognised as an ObjectUI node and therefore refused, instead of silently not judged.

.changeset/6881-retire-data-table-toolbar.md

• names data-display.ts → packages/types/src/data-display.ts — edited by this change

  What was measured. The key was declared on both published faces — data-display.ts (toolbar?: SchemaNode[], "Table toolbar actions/content") and the Zod mirror (SchemaNode | SchemaNode[]) — documented, mirrored, and read by NOTHING: data-table.tsx, the registered renderer for type: 'data-table', contains the word only in two prose comments and never reads schema.toolbar. The sibling emptyAction slot on the same interface IS mounted through SchemaRenderer, so the census zero is a reading, not a blind query. An author who wrote a toolbar got a green document and a blank result, with no signal anywhere that said so — the declared-vs-enforced failure mode that is worst for AI-authored metadata, which has nothing but the declaration to go on.

• names data-table.tsx → packages/components/src/renderers/complex/data-table.tsx — edited by this change

  What was measured. The key was declared on both published faces — data-display.ts (toolbar?: SchemaNode[], "Table toolbar actions/content") and the Zod mirror (SchemaNode | SchemaNode[]) — documented, mirrored, and read by NOTHING: data-table.tsx, the registered renderer for type: 'data-table', contains the word only in two prose comments and never reads schema.toolbar. The sibling emptyAction slot on the same interface IS mounted through SchemaRenderer, so the census zero is a reading, not a blind query. An author who wrote a toolbar got a green document and a blank result, with no signal anywhere that said so — the declared-vs-enforced failure mode that is worst for AI-authored metadata, which has nothing but the declaration to go on.

.changeset/6882-datatable-declare-render-cell-editor-and-cell-classname.md

• names data-table.tsx → packages/components/src/renderers/complex/data-table.tsx — edited by this change

  data-table has read both keys on its production path all along — renderCellEditor through a (schema as any) cast, cellClassName by destructuring it into the class of its three utility cells (the selection checkbox, the row number, the row actions). Neither was declared, so authoring either one was unchecked: a misspelling produced no error and no widget, and no editor completion offered them. DataTableSchema now declares both, and the cast in data-table.tsx is gone rather than replaced.

.changeset/6909-fieldeditwidget-dom-pass-through.md

• names data-table.tsx → packages/components/src/renderers/complex/data-table.tsx — edited by this change

  Also corrects a comment in @object-ui/components' data-table.tsx that this change falsifies. It justified the injected editor's document-level pointerdown listener partly with "FieldEditWidget forwards autoFocus and nothing else out of the DOM block, so a host handler could not reach the control through it even if one were passed" — no longer true. The listener is still load-bearing for the other half of that reason, which is untouched: the renderCellEditor context object has nowhere to put an onBlur in the first place. Comment only; no behaviour change in that package.

.changeset/6939-kanban-column-cards.md

• names complex.zod.ts → packages/types/src/zod/complex.zod.ts — edited by this change

  Breaking, deliberately. KanbanColumn declared its card list as items in complex.ts and in the zod mirror complex.zod.ts. Every board reads cards. Measured on origin/main 78a3cc238: KanbanImpl.tsx reads .cards on 12 lines, KanbanEnhanced.tsx on 8, and bucketCardsIntoColumns twice more as col.cards || []; .items had zero read sites in either board (a same-shaped .title control on the same two files returns 8 and 3, so those zeros are readings and not a mis-shaped probe). Both catalog entries, the plugin docs and content/docs/api/schema-reference.md all author cards.

.changeset/6940-rowactions-boolean-mirror.md

• names zod/data-display.zod.ts → packages/types/src/zod/data-display.zod.ts — edited by this change

  The hand-written zod mirror in zod/data-display.zod.ts declared rowActions: z.array(z.any()).optional(). Every other face of the same key says boolean: the TS declaration it mirrors (rowActions?: boolean), the renderer's destructuring default (rowActions = false), its two truthiness gates and two colSpan arithmetic sites, the registered authoring input ({ type: 'boolean', label: 'Show Row Actions' }), defaultProps: { rowActions: true }, and the renderer's own docblock example, which authors "rowActions": true. The mirror was the single outlier — and the published one, so safeValidateSchema refused the exact spelling the component's documentation, defaults and authoring UI all teach. Two shipped examples/schema-catalog entries (user-table.json, full-featured-table.json) failed validation for this and no other reason; both now validate unchanged.

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  The list view's same-named rowActions in zod/objectql.zod.ts — z.array(z.string()), the legacy bare-name action list on ObjectGridSchema — is a different key that is correct as it stands, is in parity with its own TS twin (rowActions?: string[]), and is not touched.

.changeset/6972-markdown-inert-keys-retired.md

• names data-display.ts → packages/types/src/data-display.ts — edited by this change

  What was measured, on this branch's base. sanitize was declared ?: boolean with @default true on both published faces — data-display.ts and the Zod mirror — documented, and read by NOTHING. Worse than an ordinary inert key, it implied a switch that does not exist: sanitization is unconditional. rehypePlugins in plugin-markdown/src/MarkdownImpl.tsx is a module-level const array whose last link is [rehypeSanitize, sanitizeSchema], handed to ReactMarkdown as-is — no ternary, no if, no runtime assembly. MarkdownRenderer forwards exactly content and className, and MarkdownImplProps accepts only those two. A repo-wide grep for schema.sanitize over packages/ and apps/ returns nothing, against a control of 20 .tsx files reading schema.content in the same query shape, so the zero is a reading, not a blind query. An author writing sanitize: false believed they turned XSS filtering off; one writing sanitize: true believed they turned it on. Neither was true.

.changeset/7125-dashboard-empty-state-keys-retired.md

• names packages/app-shell/src/views/metadata-admin/i18n.ts → packages/app-shell/src/views/metadata-admin/i18n.ts — edited by this change

  Not touched: table.noRows ('No rows to display') and engine.form.noRows (packages/app-shell/src/views/metadata-admin/i18n.ts, read at widgets.tsx) — two different, same-named keys in different namespaces. Nor the comments in WidgetEmptyState.tsx, DatasetWidget.tsx, ObjectDataTable.tsx and PivotTable.tsx that record WHY three widgets with three strings became one shared empty state; the packs' own comment keeps that rationale and now names the retirement instead of a row that is gone.

• names ObjectDataTable.tsx → packages/plugin-dashboard/src/ObjectDataTable.tsx — edited by this change

  Not touched: table.noRows ('No rows to display') and engine.form.noRows (packages/app-shell/src/views/metadata-admin/i18n.ts, read at widgets.tsx) — two different, same-named keys in different namespaces. Nor the comments in WidgetEmptyState.tsx, DatasetWidget.tsx, ObjectDataTable.tsx and PivotTable.tsx that record WHY three widgets with three strings became one shared empty state; the packs' own comment keeps that rationale and now names the retirement instead of a row that is gone.

.changeset/7182-declared-action-ids-one-rule.md

• names containers.tsx → packages/components/src/renderers/layout/containers.tsx — edited by this change

  New on @object-ui/types, beside actionRendersAt: the pure resolveDeclaredActionIds(elements, registeredActions), with the DeclaredActionsResolution / DeclaredActionsRefusal result types (the shape classifier stays module-internal: called with no registry, the function already returns the registry-independent verdict a renderer needs before its lookup). Both renderers call it; the whole-array switch in record-quick-actions.tsx and the per-element normalisation in containers.tsx are gone. The rule is closed: a string is an id, a non-null non-array object is an inline definition, and any other element (null, a number, a nested array) is refused at its index too. An all-id array resolves by name in authored order, first registration winning on a duplicate name; ids that name nothing are reported back with their index for the caller to warn about once its lookup has settled.

.changeset/7200-object-form-section-style-keys-undeclared.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  The authored-metadata type now agrees with @objectstack/spec, whose FormSectionSchema is a strict object declaring neither key, and with the ruling's rationale (maintainer 2026-09-01, verbatim): "retire the reads … Declaring the keys was weighed and not adopted: it would formally invite free Tailwind strings into authored metadata, the exact class the boundary exists to keep out." A ?: never tombstone was not used: ObjectFormSection has no zod mirror (ObjectFormSchema in zod/objectql.zod.ts does not declare sections), so there is no parse door to refuse at, and a tombstone is still a declaration in completion and in the published .d.ts.

.changeset/7265-types-user-filter-field-derives.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  zod/objectql.zod.ts declared two schemas under names @objectstack/spec/ui already exports. They were triaged separately, by reading their sites, and went different ways.

.changeset/7322-object-kanban-group-by-limit.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  Breaking for authored metadata: ObjectKanbanSchema.groupField is RETIRED (objectui#7322, ADR-0049 enforce-or-remove), and the two keys the object-kanban renderer actually reads — groupBy and limit — are now DECLARED and validated on both published faces: the TypeScript interface in objectql.ts and the Zod mirror in zod/objectql.zod.ts.

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Breaking for authored metadata: ObjectKanbanSchema.groupField is RETIRED (objectui#7322, ADR-0049 enforce-or-remove), and the two keys the object-kanban renderer actually reads — groupBy and limit — are now DECLARED and validated on both published faces: the TypeScript interface in objectql.ts and the Zod mirror in zod/objectql.zod.ts.

.changeset/7352-drill-down-config-mirror.md

• names zod/data-display.zod.ts → packages/types/src/zod/data-display.zod.ts — edited by this change

  DrillDownConfigSchema is the zod mirror of DrillDownConfig, and both declarations that carry drillDown reference it — ChartSchema (zod/data-display.zod.ts) and ObjectDataTableSchema (zod/objectql.zod.ts) — so the published validator under @object-ui/types/zod reads the key for the first time (objectui#7352).

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  DrillDownConfigSchema is the zod mirror of DrillDownConfig, and both declarations that carry drillDown reference it — ChartSchema (zod/data-display.zod.ts) and ObjectDataTableSchema (zod/objectql.zod.ts) — so the published validator under @object-ui/types/zod reads the key for the first time (objectui#7352).

.changeset/7363-objectql-union-arms.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectGallerySchema and ObjectDataTableSchema are members of ObjectQLComponentSchema on both faces — the TS union in objectql.ts and the zod union in zod/objectql.zod.ts — so AnyComponentSchema, and with it validateSchema / safeValidateSchema / objectui validate, has an arm for object-gallery and object-data-table nodes (objectui#7363).

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectGallerySchema and ObjectDataTableSchema are members of ObjectQLComponentSchema on both faces — the TS union in objectql.ts and the zod union in zod/objectql.zod.ts — so AnyComponentSchema, and with it validateSchema / safeValidateSchema / objectui validate, has an arm for object-gallery and object-data-table nodes (objectui#7363).

.changeset/7632-shared-record-source-config.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  That ladder is published contract on both faces — packages/types/src/objectql.ts and its zod mirror both ship .describe() strings naming getDataConfig's order (77cb489b4, maintainer ruling 2026-09-02), pinned by objectql-record-source-refinement-6939.test.ts — and it was hand-copied into five plugin components with no gate holding them together. A change to the ruled order had five edit sites and nothing that noticed a missed one; that is the AGENTS.md #0.1 drift class.

.changeset/7703-chatbot-dark-keys-retired.md

• names packages/types/src/zod/complex.zod.ts → packages/types/src/zod/complex.zod.ts — edited by this change

  Each member goes to ?: never on packages/types/src/complex.ts and to retirementTombstone(...) on packages/types/src/zod/complex.zod.ts — both halves, in lockstep, the convention MarkdownSchema.sanitize (objectui#6972), TimelineSchema.timeScale (objectui#6355) and ObjectViewSchema.viewTabBar (objectui#7779) already carry. Each refusal names the key, says why it is retired, and points at what to write instead; one string feeds both the parse-time message and the .describe() metadata, so the two cannot drift.

.changeset/7722-wrapper-class-five-more.md

• names data-display.ts → packages/types/src/data-display.ts — edited by this change

  Each of renderers/form/switch.tsx, textarea.tsx, date-picker.tsx, select.tsx and renderers/data-display/list.tsx reads schema.wrapperClass onto its wrapper element, and neither the TypeScript interface (form.ts, data-display.ts) nor the zod mirror (zod/form.zod.ts, zod/data-display.zod.ts) declared the key. The reads compiled through BaseSchema's index signature (objectui#5155) and the values parsed through .passthrough(), admitted unexamined. The same key, on the same class of read, is declared on CheckboxSchema (b74a8598d), FileUploadSchema and FilterBuilderSchema (objectui#6150); these five were left out only because their doc pages never listed it.

• names zod/data-display.zod.ts → packages/types/src/zod/data-display.zod.ts — edited by this change

  Each of renderers/form/switch.tsx, textarea.tsx, date-picker.tsx, select.tsx and renderers/data-display/list.tsx reads schema.wrapperClass onto its wrapper element, and neither the TypeScript interface (form.ts, data-display.ts) nor the zod mirror (zod/form.zod.ts, zod/data-display.zod.ts) declared the key. The reads compiled through BaseSchema's index signature (objectui#5155) and the values parsed through .passthrough(), admitted unexamined. The same key, on the same class of read, is declared on CheckboxSchema (b74a8598d), FileUploadSchema and FilterBuilderSchema (objectui#6150); these five were left out only because their doc pages never listed it.

.changeset/7735-zod-mirrors-stop-authoring-defaults.md

• names flex.tsx → packages/components/src/renderers/layout/flex.tsx — edited by this change

  | key | mirror wrote | the renderer applies | |---|---|---| | ContainerSchema.maxWidth | 'lg' | container.tsx: ?? 'xl' | | FlexSchema.align | 'center' | flex.tsx: \|\| 'start' |

• names layout.zod.ts → packages/types/src/zod/layout.zod.ts — edited by this change

  What changed. All 41 .default() call sites under packages/types/src/zod/ are removed — layout.zod.ts 22, crud.zod.ts 11, form.zod.ts 5, views.zod.ts 2, app.zod.ts 1. @object-ui/components reconciles the third face objectui#8229 found: flex's registration defaultProps.align seeded 'center', the value its own renderer never applies, so a designer-made node laid out differently from a hand-authored one; it now seeds 'start'.

.changeset/7804-data-table-handler-key-arms.md

• names renderers/complex/data-table.tsx → packages/components/src/renderers/complex/data-table.tsx — edited by this change

  BaseSchema is .passthrough(), so a key no arm declares is not refused — it stops being judged and the value is KEPT. All seven were in that state while renderers/complex/data-table.tsx read and INVOKED each one, so an authored { "type": "data-table", "onRowClick": { "action": "toast" } } parsed GREEN and that action object was handed to a call site expecting a function. Each key is now a named refusal on the mirror (handlerKeyRefusal, the objectui#6124 shape), and the arm's message says why JSON cannot author it and what to write instead.

.changeset/7804-objectql-handler-key-arms.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  The four plain objectql.ts node faces declare the nine handler keys their registered renderers read (objectui#7804, the objectql.ts slice): ObjectFormSchema.onCancel / .onError / .onOpenChange / .onStepChange / .onSuccess, ObjectGallerySchema.onCardClick / .onRowClick, ObjectGridSchema.onNavigate and ObjectViewSchema.onNavigate.

.changeset/7804-tree-view-handler-slot.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  'runtime-slot' and not 'retired', measured at this key's own channel. 'retired' publishes "no renderer reads this key, so nothing could ever run it" — true of the two siblings already tombstoned on this arm (onSelectChange, onExpandChange) and flatly false here, since the read is live and INVOKED. ⚠️ No in-repo host builds a tree-view node carrying the key: the channel is wired end to end and only the supplier is absent, which is the same shape as ObjectFormSchema.onStepChange in this card's objectql.ts slice and is not evidence of a dead read. The TypeScript declaration is unchanged and still callable, so a programmatic host supplies it exactly as before.

.changeset/7917-export-breadcrumb-object-tree-zod-schemas.md

• names objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  AnyComponentSchema declares 107 node component types. 105 of them could be named on the ./zod barrel — ButtonSchema.safeParse(node), which is what a designer, a form builder or a targeted test needs. The arms declaring type: 'breadcrumb' (navigation.zod.ts) and type: 'object-tree' (objectql.zod.ts) could not: both were already export const in their own module, but index.zod.ts — the package's only zod entry point — did not re-export them, so the schemas existed, were maintained, and were applied by the union while no consumer could name them.

.changeset/7963-alert-dialog-footer-keys-retired.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  Nothing else moves. These spellings are overloaded across the tree and every other owner is a live key on a different declaration — FormSchema.cancelLabel, objectql.ts's confirmLabel, plugin-designer's ConfirmDialog React props, plugin-grid's def.confirmLabel, and plugin-form's ModalForm / DrawerForm, which build a local cancelLabel from schema.cancelText. None is an AlertDialogSchema; none is touched, and a pin asserts it. No fixture, catalog schema, example app or doc fence authored any of the three on an alert-dialog node, so no shipped document is stranded.

.changeset/7997-detail-view-related-retired.md

• names RecordDetailView.tsx → packages/app-shell/src/views/RecordDetailView.tsx — edited by this change

  Why it retired. @objectstack/spec declares no DetailView schema at all — every DetailView occurrence in packages/spec/src is prose about this repo's own RecordDetailView.tsx — so this array mirrored no protocol schema and drifted freely: it declared columns as TableColumn[] while the renderer it fed also accepted bare field names, { field, label } and legacy { name, label } spellings. The axis that carried the ruling was measured zero pull: no application code authored the member, both internal producers of a detail-view node (RecordDetailDrawer, renderers/record-details.tsx) synthesize it without related, and the only in-tree authorings carrying real columns were two documents — both rewritten here.

.changeset/8155-app-root-residue-swept.md

• names containers.tsx → packages/components/src/renderers/layout/containers.tsx — edited by this change

  Swept as a class, not as two coordinates. Every other place in this tree that stated app was a bound expression-scope root is corrected in the same change — the diagnostic copy and its byte-pin, the ambient-scope docblocks in @object-ui/react (SchemaRenderer, useExpression), @object-ui/core (ActionRunner.ParamDef.visible, RowPredicateOptions.scope), @object-ui/components (form.tsx, containers.tsx), @object-ui/plugin-detail, @object-ui/plugin-form (docblock and README), @object-ui/app-shell and the console app, plus fourteen test fixtures that transcribed the old bag with an app key. The fixtures in @object-ui/app-shell now call buildExpressionScope instead of transcribing it, so that pair cannot drift again.

.changeset/8318-jsdoc-default-tag-corrections.md

• names core/src/actions/ActionRunner.ts → packages/core/src/actions/ActionRunner.ts — edited by this change

  • CRUDDialogSchema.size / .closeOnOutsideClick / .closeOnEscape / .showClose — there is no register('crud-dialog' anywhere, so no node of that type ever reaches a renderer. Recorded once on the interface. Per key, the name census differs: two spellings occur nowhere outside the declaration and its zod twin, and showClose's one other occurrence (renderers/overlay/drawer.tsx:38) belongs to DrawerSchema. - ActionSchema.level — type: 'action' is not a rendered node type, and core/src/actions/ActionRunner.ts, which is what makes method / chainMode / reload / close live, does not read level. - CardSchema.variant — card IS registered, twice, and neither registration reads it: the ui route forwards the key to ui/card.tsx, which spreads onto a div and mentions variant nowhere, and the page route forwards only its designer props. - PageNodeSchema.isDefault — page IS registered, and PageRenderer neither reads the key nor forwards it: the wrapper element gets toDomProps(props), an allow-list that does not carry it.

.changeset/8331-data-table-empty-action-primitive-node.md

• names packages/types/src/data-display.ts → packages/types/src/data-display.ts — edited by this change

  Behaviour change on a published surface, deliberately. DataTableSchema.emptyAction is declared SchemaNode on both published faces — packages/types/src/data-display.ts and its Zod twin in packages/types/src/zod/data-display.zod.ts — and SchemaNode is BaseSchema | string | number | boolean | null | undefined. The empty-state render path additionally required typeof … === 'object', so an authored emptyAction: 'Create the first record' rendered nothing and reported nothing: declared wider than enforced, failing in the direction that loses the author's content without a diagnostic. A node that renders nothing today therefore starts rendering.

• names packages/types/src/zod/data-display.zod.ts → packages/types/src/zod/data-display.zod.ts — edited by this change

  Behaviour change on a published surface, deliberately. DataTableSchema.emptyAction is declared SchemaNode on both published faces — packages/types/src/data-display.ts and its Zod twin in packages/types/src/zod/data-display.zod.ts — and SchemaNode is BaseSchema | string | number | boolean | null | undefined. The empty-state render path additionally required typeof … === 'object', so an authored emptyAction: 'Create the first record' rendered nothing and reported nothing: declared wider than enforced, failing in the direction that loses the author's content without a diagnostic. A node that renders nothing today therefore starts rendering.

.changeset/8415-filter-builder-condition-id.md

• names zod/complex.zod.ts → packages/types/src/zod/complex.zod.ts — edited by this change

  Breaking for authored metadata: a filter-builder CONDITION must now declare id (objectui#8415). It is declared on both published faces — the TypeScript interface FilterBuilderCondition in complex.ts and the Zod mirror FilterBuilderConditionSchema in zod/complex.zod.ts — so a key the renderer has always required is finally validated instead of silently discarded.

.changeset/8478-describe-line-addresses.md

• names zod/data-display.zod.ts → packages/types/src/zod/data-display.zod.ts — edited by this change

  Remove stale source-line citations (NAME.ext:NNN) from twelve published .describe() schema descriptions in packages/types/src/zod/overlay.zod.ts, zod/data-display.zod.ts and zod/objectql.zod.ts (finding(types): 27 published .describe() schema descriptions in packages/types/src/zod/** cite source line addresses — the authorable surface carries a citation nothing reads #8478).

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Remove stale source-line citations (NAME.ext:NNN) from twelve published .describe() schema descriptions in packages/types/src/zod/overlay.zod.ts, zod/data-display.zod.ts and zod/objectql.zod.ts (finding(types): 27 published .describe() schema descriptions in packages/types/src/zod/** cite source line addresses — the authorable surface carries a citation nothing reads #8478).

• names layout.zod.ts → packages/types/src/zod/layout.zod.ts — edited by this change

  The remaining 15 addresses (form.zod.ts, layout.zod.ts, complex.zod.ts) were out of scope for this PR — form.zod.ts / layout.zod.ts were held while PR fix(types): arm AnyComponentSchema for seven registered node-slot renderers (objectui#8499) #8763 was open; complex.zod.ts's hold (PR feat(types): FilterFieldSchema.type — the published doc's fourteen members, optional #8766) cleared when that PR merged during this round, so its 6 addresses returned to the queue rather than riding this PR's scope.

• names complex.zod.ts → packages/types/src/zod/complex.zod.ts — edited by this change

  The remaining 15 addresses (form.zod.ts, layout.zod.ts, complex.zod.ts) were out of scope for this PR — form.zod.ts / layout.zod.ts were held while PR fix(types): arm AnyComponentSchema for seven registered node-slot renderers (objectui#8499) #8763 was open; complex.zod.ts's hold (PR feat(types): FilterFieldSchema.type — the published doc's fourteen members, optional #8766) cleared when that PR merged during this round, so its 6 addresses returned to the queue rather than riding this PR's scope.

.changeset/8478-zod-pins-complex.md

• names packages/types/src/zod/complex.zod.ts → packages/types/src/zod/complex.zod.ts — edited by this change

  Remove stale source-line citations (NAME.ext:NNN) from all 6 published .describe() schema descriptions in packages/types/src/zod/complex.zod.ts (finding(types): 27 published .describe() schema descriptions in packages/types/src/zod/** cite source line addresses — the authorable surface carries a citation nothing reads #8478) — the last file of this card's remainder, which the card now closes.

.changeset/8478-zod-pins-form-layout.md

• names zod/layout.zod.ts → packages/types/src/zod/layout.zod.ts — edited by this change

  Remove stale source-line citations (NAME.ext:NNN) from eleven published .describe() schema descriptions in packages/types/src/zod/form.zod.ts (9) and zod/layout.zod.ts (2) (finding(types): 27 published .describe() schema descriptions in packages/types/src/zod/** cite source line addresses — the authorable surface carries a citation nothing reads #8478).

• names zod/complex.zod.ts → packages/types/src/zod/complex.zod.ts — edited by this change

  The remaining 6 addresses (zod/complex.zod.ts) stayed out of scope for this PR and returned to the queue rather than riding this PR's scope — the card did not close here.

.changeset/8499-node-slot-registered-arms.md

• names zod/layout.zod.ts → packages/types/src/zod/layout.zod.ts — edited by this change

  • SemanticElementSchema (zod/layout.zod.ts) — the seven HTML sectioning tags renderers/layout/semantic.tsx registers: aside main header nav footer section article. - HtmlElementSchema (zod/layout.zod.ts) — the 37 safe flow/inline tags renderers/basic/html-elements.tsx registers (h1…h6, p, a, ul, img, …), plus the per-tag keys that module forwards to the DOM (href, target, rel, title, src, alt, width, height, dateTime, cite). ⚠️ Dated note, 2026-09-27 — that set has since gained code — objectui#10756. At this change TAGS and this arm both named 37 tags; both now name 38, and the parity pin counts 38. The rest of this entry is kept as the reading of this change. - InputShorthandSchema (zod/form.zod.ts) — email / password, the two aliases renderers/form/input.tsx registers onto the input renderer with inputType pinned. inputType is deliberately NOT declared on this arm: the wrapper spreads its own value last, so an authored one is overwritten. - UiCalendarSchema (zod/form.zod.ts) — ui:calendar, the date-picker primitive renderers/form/calendar.tsx registers under exactly that key (skipFallback, because bare calendar belongs to the plugin-calendar view).

.changeset/8505-grid-columns-breakpoint-narrowing.md

• names zod/layout.zod.ts → packages/types/src/zod/layout.zod.ts — edited by this change

  The zod mirror WAS deliberately not narrowed here — corrected in fix(types): key the grid and report zod mirrors by their own declaration vocabulary (objectui#8516, objectui#8556) #8573. This paragraph said zod/layout.zod.ts still validates columns as z.record(z.string(), z.number()), so the JSON authoring face — objectui validate in @object-ui/cli, the real consumer of these mirrors — still admits { xxl: 6 }. fix(types): key the grid and report zod mirrors by their own declaration vocabulary (objectui#8516, objectui#8556) #8573 narrowed that mirror to a partial record over the six breakpoints (objectui#8516), so the JSON face now refuses { xxl: 6 } exactly as the declaration above does. Its two supporting statements went with it, and fix(types): key the grid and report zod mirrors by their own declaration vocabulary (objectui#8516, objectui#8556) #8573 quotes each in its current state rather than re-arguing it: the byte measurement that deferred the narrowing — 70,999 gzip bytes against a 71,000 framework ceiling, one byte of headroom — is retired, because PR ci(budget): raise the framework per-chunk ceiling to 100,000 by maintainer ruling #8550 landed the maintainer's raise to PER_CHUNK_GZIP_CEILINGS.framework 100_000 against a PER_CHUNK_BASELINE.framework of 72_245; and the handoff assertion described here as holding the current reading visible is flipped to a refusal in fix(types): key the grid and report zod mirrors by their own declaration vocabulary (objectui#8516, objectui#8556) #8573, so it no longer asserts acceptance.

.changeset/8516-8556-mirror-partial-record-narrowing.md

• names zod/layout.zod.ts → packages/types/src/zod/layout.zod.ts — edited by this change

  | key | mirror was | mirror is | | :-- | :--------- | :-------- | | GridSchema.columns (zod/layout.zod.ts) | z.record(z.string(), z.number()) | a PARTIAL record over the six breakpoints | | ReportComponentSchema.exportConfigs (zod/reports.zod.ts) | z.record(z.string(), ReportExportConfigSchema) | a PARTIAL record over ReportExportFormat |

.changeset/8632-malformed-picklist-option-loud.md

• names views/metadata-admin/i18n.ts → packages/app-shell/src/views/metadata-admin/i18n.ts — edited by this change

  Two new strings land in the designer's own en / zh tables — the metadata-admin console owns its strings in views/metadata-admin/i18n.ts and is deliberately outside the ten locale packs (packages/i18n/README.md, "Scope — the engine.* carve-out").

.changeset/8735-objectql-mirror-docblocks-not-defaulted.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Correct four zod/objectql.zod.ts docblocks that described the behaviour objectui#8317 removed. Since that change the zod mirrors strip imported @objectstack/spec defaults at this package's import boundary, but the docblocks on HttpRequestSchema, ListColumnSchema, SelectionConfigSchema and PaginationConfigSchema still said, in the present tense, that method, prefix.type, type and pageSize are defaulted on parse — the opposite of what each export does. Each now says the key is declared and accepted but NOT defaulted on parse.

.changeset/8767-object-grid-refuses-string-sort.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  Migration. Write the array: sort: [{ field: 'name', order: 'desc' }]. Both keys are required. SortConfig.order carries no ? in @object-ui/types (packages/types/src/objectql.ts) and no .optional() in its zod mirror, and the protocol's own reusable SortItemSchema requires order as well — measured: that schema refuses [{ field: 'name' }] with invalid_value at 0.order. Do not omit it: this block's array arm interpolates whatever is present, so an omitted order lowers to $orderby: 'name undefined' today. That is pre-existing behaviour on the arm this change does not touch, and it is filed as a successor card rather than widened into here.

.changeset/8801-object-kanban-allow-collapse-retired.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  • the declarations retired here — packages/types/src/objectql.ts and its mirror packages/types/src/zod/objectql.zod.ts; - the pins that assert the retirement — object-kanban-allow-collapse-retired-8801.test.ts and bare-kanban-node-key-retired-8802.test.ts; - a comment in packages/types/src/zod/complex.zod.ts, recording that the deleted retiredZeroReadKanbanKey helper once carried this spelling on the SIBLING arm; - one row of content/docs/api/schema-reference.md; - the .changeset/ release notes that discuss it — this one, the two historical entries covering the sibling arm's own spelling, and objectui#9629's note recording the correction to this paragraph.

• names packages/types/src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  • the declarations retired here — packages/types/src/objectql.ts and its mirror packages/types/src/zod/objectql.zod.ts; - the pins that assert the retirement — object-kanban-allow-collapse-retired-8801.test.ts and bare-kanban-node-key-retired-8802.test.ts; - a comment in packages/types/src/zod/complex.zod.ts, recording that the deleted retiredZeroReadKanbanKey helper once carried this spelling on the SIBLING arm; - one row of content/docs/api/schema-reference.md; - the .changeset/ release notes that discuss it — this one, the two historical entries covering the sibling arm's own spelling, and objectui#9629's note recording the correction to this paragraph.

• names packages/types/src/zod/complex.zod.ts → packages/types/src/zod/complex.zod.ts — edited by this change

  • the declarations retired here — packages/types/src/objectql.ts and its mirror packages/types/src/zod/objectql.zod.ts; - the pins that assert the retirement — object-kanban-allow-collapse-retired-8801.test.ts and bare-kanban-node-key-retired-8802.test.ts; - a comment in packages/types/src/zod/complex.zod.ts, recording that the deleted retiredZeroReadKanbanKey helper once carried this spelling on the SIBLING arm; - one row of content/docs/api/schema-reference.md; - the .changeset/ release notes that discuss it — this one, the two historical entries covering the sibling arm's own spelling, and objectui#9629's note recording the correction to this paragraph.

.changeset/8871-page-node-refuses-breadcrumbs.md

• names packages/types/src/zod/tombstone.zod.ts → packages/types/src/zod/tombstone.zod.ts — edited by this change

  Why ADR-0049 and not a fresh ruling. objectui#7926 refused actions on this same node and, by its own comments, ruled on that key ONLY — its ruling is not borrowed here. What reaches this key is the standing enforce-or-remove gate, which this repository applies to this exact face: packages/types/src/zod/tombstone.zod.ts's retirementTombstone is documented as the "ADR-0049 RETIREMENT TOMBSTONE" helper and is internal to these zod modules, 63 changesets cite the ADR, and PageNodeSchema already carried one of its refusal arms one member up. objectui#7926 left this key parsing on purpose so that retiring it would be a decision rather than an accident, and wrote a pin saying so; that pin is flipped, not deleted.

• names layout.ts → packages/types/src/layout.ts — edited by this change

  What was measured, on this branch's base 93127bd6f. Zero readers, with a point-access probe rather than a bare word: on that base \.breadcrumbs scores 0 tree-wide (exit 1) against \.breadcrumb\b's 12 files tree-wide (10 under packages/) as the lit control. At head the same two probes read 16 and 13 and \.breadcrumbs is exit 0 over 4 files — every hit one of this branch's own four files (this changeset, the refusal pin, layout.ts, zod/layout.zod.ts) quoting the probe string, and the pin's own exclusions put head back at exit 1. The base reading is the measurement; the head reading is this branch's echo of it. The bare word would have lied — it also names Sentry's own unrelated concept (app-shell/src/observability/sentry.ts) and appears in two comments listing UI surfaces (core/src/utils/record-title.ts, layout/src/NavigationRenderer.tsx), so a bare probe reports five readers that do not exist.

• names zod/layout.zod.ts → packages/types/src/zod/layout.zod.ts — edited by this change

  What was measured, on this branch's base 93127bd6f. Zero readers, with a point-access probe rather than a bare word: on that base \.breadcrumbs scores 0 tree-wide (exit 1) against \.breadcrumb\b's 12 files tree-wide (10 under packages/) as the lit control. At head the same two probes read 16 and 13 and \.breadcrumbs is exit 0 over 4 files — every hit one of this branch's own four files (this changeset, the refusal pin, layout.ts, zod/layout.zod.ts) quoting the probe string, and the pin's own exclusions put head back at exit 1. The base reading is the measurement; the head reading is this branch's echo of it. The bare word would have lied — it also names Sentry's own unrelated concept (app-shell/src/observability/sentry.ts) and appears in two comments listing UI surfaces (core/src/utils/record-title.ts, layout/src/NavigationRenderer.tsx), so a bare probe reports five readers that do not exist.

• names layout/src/NavigationRenderer.tsx → packages/layout/src/NavigationRenderer.tsx — edited by this change

  What was measured, on this branch's base 93127bd6f. Zero readers, with a point-access probe rather than a bare word: on that base \.breadcrumbs scores 0 tree-wide (exit 1) against \.breadcrumb\b's 12 files tree-wide (10 under packages/) as the lit control. At head the same two probes read 16 and 13 and \.breadcrumbs is exit 0 over 4 files — every hit one of this branch's own four files (this changeset, the refusal pin, layout.ts, zod/layout.zod.ts) quoting the probe string, and the pin's own exclusions put head back at exit 1. The base reading is the measurement; the head reading is this branch's echo of it. The bare word would have lied — it also names Sentry's own unrelated concept (app-shell/src/observability/sentry.ts) and appears in two comments listing UI surfaces (core/src/utils/record-title.ts, layout/src/NavigationRenderer.tsx), so a bare probe reports five readers that do not exist.

.changeset/8885-object-chart-drilldown-title-compareto.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectChart.tsx reads all three off schema, and until now neither published copy declared any of them: not the TS interface (packages/types/src/objectql.ts) and not the zod mirror (packages/types/src/zod/objectql.zod.ts). They rode BaseSchema's index signature / .passthrough() and arrived unvalidated. drillDown was the sharpest case — this component's registry inputs advertise it to the designer palette, and @objectstack/spec publishes ChartDrillDownSchema for exactly this carrier, so an author was offered a key that neither published shape mentioned.

• names packages/types/src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectChart.tsx reads all three off schema, and until now neither published copy declared any of them: not the TS interface (packages/types/src/objectql.ts) and not the zod mirror (packages/types/src/zod/objectql.zod.ts). They rode BaseSchema's index signature / .passthrough() and arrived unvalidated. drillDown was the sharpest case — this component's registry inputs advertise it to the designer palette, and @objectstack/spec publishes ChartDrillDownSchema for exactly this carrier, so an author was offered a key that neither published shape mentioned.

.changeset/8913-object-kanban-columns-declared.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  What moved. ObjectKanbanSchema gains columns on both halves that move together — the TypeScript interface (objectql.ts) and its Zod mirror (zod/objectql.zod.ts). Retiring the bare kanban node type key (objectui#8802) removed the only face that judged a lane, and object-kanban had never declared the key, so it rode BaseSchema's [key: string]: any / .passthrough(): read by the renderer at three sites, named by no published face.

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  What moved. ObjectKanbanSchema gains columns on both halves that move together — the TypeScript interface (objectql.ts) and its Zod mirror (zod/objectql.zod.ts). Retiring the bare kanban node type key (objectui#8802) removed the only face that judged a lane, and object-kanban had never declared the key, so it rode BaseSchema's [key: string]: any / .passthrough(): read by the renderer at three sites, named by no published face.

.changeset/8990-object-kanban-groupby-optional.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  @objectstack/spec declares the key optional — groupBy: z.string().optional() on ObjectKanbanPropsSchema — while this package required it on the TypeScript declaration (packages/types/src/objectql.ts) and on the Zod mirror (packages/types/src/zod/objectql.zod.ts). objectui was therefore narrower than the protocol on a published key: ObjectKanbanSchema.safeParse and safeValidateSchema refused an object-kanban node the protocol accepts, and such a node could not be annotated with its own type.

• names packages/types/src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  @objectstack/spec declares the key optional — groupBy: z.string().optional() on ObjectKanbanPropsSchema — while this package required it on the TypeScript declaration (packages/types/src/objectql.ts) and on the Zod mirror (packages/types/src/zod/objectql.zod.ts). objectui was therefore narrower than the protocol on a published key: ObjectKanbanSchema.safeParse and safeValidateSchema refused an object-kanban node the protocol accepts, and such a node could not be annotated with its own type.

.changeset/8992-user-actions-collapse-and-docblock.md

• names objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  objectql.zod.ts's UserActionsSchema read stripImportedDefaults(Spec).extend({ group, hideFields, rowColor }), an extension that existed only because @objectstack/spec did not declare those three keys while normalizeListViewSchema folded objectui's legacy showGroup / showHideFields / showColor onto them. The protocol adopted all three in 17.3.0 (objectui#5435's ruling), so the extension is now a second local copy of a protocol declaration — the shape two faces start drifting from — and it collapses into the plain by-reference re-export its own note always said it would become.

.changeset/9092-inline-locale-declared-face.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  • AppComponentSchema.label (app.ts) - ObjectGridSchema.label and .description (objectql.ts) - PageNodeSchema.aria.ariaLabel (layout.ts)

• names layout.ts → packages/types/src/layout.ts — edited by this change

  • AppComponentSchema.label (app.ts) - ObjectGridSchema.label and .description (objectql.ts) - PageNodeSchema.aria.ariaLabel (layout.ts)

.changeset/9172-dashboard-grid-series-label.md

• names packages/plugin-dashboard/src/utils.ts → packages/plugin-dashboard/src/utils.ts — edited by this change

  Fix DashboardGridLayout composing chart series with no label at all (objectui#9172), so a grid-laid-out dashboard legended a measure like close_date under the raw field key while the read-only DashboardRenderer relay legended the same widget "Close Date". The three-arm label decision (synthetic aggregate name / bundle-or-humanized field label) is now composeSeriesLabel (packages/plugin-dashboard/src/utils.ts), a single authority both relays call, rather than a second copy of the logic.

.changeset/9174-interpolate-fastpath-trim.md

• names packages/components/src/renderers/layout/containers.tsx → packages/components/src/renderers/layout/containers.tsx — edited by this change

  At this change page:header's title/subtitle (and the record-title titleFormat) all went through interpolate() in packages/components/src/renderers/layout/containers.tsx. When the template contained a {token} the function collapsed and trimmed whitespace before returning; when it contained no { at all it returned the raw string untouched. A whitespace-only authored title (e.g. ' ') has no token, so it came back unchanged — truthy — and PageHeaderRenderer's {explicitTitle && ANGLE-BRACKETS(h1)} gate drew a blank h1. Because literalTitleText (page.tsx), which decides whether PageRenderer delegates its own heading to the authored header, already trimmed and correctly read "no title", PageRenderer also drew its own implicit heading — two ANGLE-BRACKETS(h1) elements on one document, the broken outline objectui#3434 closed, arriving through a different door.

.changeset/9256-list-timeline-content-channels.md

• names packages/types/src/data-display.ts → packages/types/src/data-display.ts — edited by this change

  These two were held out of the previous family-D slice for a SERIAL constraint on packages/types/src/data-display.ts and never for a verdict. Readership was re-derived for both rather than inherited: a TypeScript compiler-API sweep files every .body / .children read under the declared type of its receiver and answers zero for ListSchema and TimelineSchema while its live controls fire. timeline's bare-key owner is any-typed, so it was attributed directly as well — packages/plugin-timeline contains no channel read of any kind.

.changeset/9278-end-outcome-select.md

• names packages/app-shell/src/views/metadata-admin/inspectors/flow-node-config.ts → packages/app-shell/src/views/metadata-admin/inspectors/flow-node-config.ts — edited by this change

  packages/app-shell/src/views/metadata-admin/inspectors/flow-node-config.ts declared the end group's outcome key as a free-text box with placeholder: 'success · failure'. EndConfigSchema.outcome is a closed enum of completed | refused defaulting to completed, and FlowNodeSchema discriminates an end node's config through it — so both printed words are refused at parse, not ignored at run time. Measured against the installed @objectstack/spec (17.4.0), with the accepted row in the same output so the refusals are a reading rather than a dead probe:

.changeset/9309-object-gallery-filter-destination-typed.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectGallerySchema.filter is typed as the destination its own docblock names — QueryParams['$filter'] — on both faces, the TS interface in objectql.ts and the zod mirror in zod/objectql.zod.ts (objectui#9309).

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectGallerySchema.filter is typed as the destination its own docblock names — QueryParams['$filter'] — on both faces, the TS interface in objectql.ts and the zod mirror in zod/objectql.zod.ts (objectui#9309).

.changeset/9511-record-id-is-a-string.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  The three authorable keys, each on BOTH faces. ObjectFormSchema.recordId (objectql.ts + zod/objectql.zod.ts), DetailViewSchema.resourceId (views.ts + zod/views.zod.ts) and DetailSchema.resourceId (crud.ts + zod/crud.zod.ts). ⚠️ The crud pair is DetailSchema, not DetailViewSchema, and it reaches the same renderer — not by symbol but by data flow: plugin-detail registers the 'detail' node type onto DetailView. A read that follows TypeScript symbols alone finds two keys and is incomplete.

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  The three authorable keys, each on BOTH faces. ObjectFormSchema.recordId (objectql.ts + zod/objectql.zod.ts), DetailViewSchema.resourceId (views.ts + zod/views.zod.ts) and DetailSchema.resourceId (crud.ts + zod/crud.zod.ts). ⚠️ The crud pair is DetailSchema, not DetailViewSchema, and it reaches the same renderer — not by symbol but by data flow: plugin-detail registers the 'detail' node type onto DetailView. A read that follows TypeScript symbols alone finds two keys and is incomplete.

.changeset/9549-tree-filter-declared.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectTreeSchema.filter is declared on both faces, in the shape objectui#9309 settled for ObjectGallerySchema.filter: QueryParams['$filter'] by indexed access on the TS interface in objectql.ts, and the same two-arm union (array first) on the zod mirror in zod/objectql.zod.ts (objectui#9549).

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectTreeSchema.filter is declared on both faces, in the shape objectui#9309 settled for ObjectGallerySchema.filter: QueryParams['$filter'] by indexed access on the TS interface in objectql.ts, and the same two-arm union (array first) on the zod mirror in zod/objectql.zod.ts (objectui#9549).

.changeset/9550-object-tree-root-barrel.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectQLComponentSchema declares the node types an ObjectQL block may be. Every one of its arms was a named export of this package's root barrel except ObjectTreeSchema, which was declared in objectql.ts, applied by the union, and re-exported by the ./zod barrel (objectui#7917) — while no TypeScript consumer could name it. There is no ./objectql subpath to reach around the barrel: the package's exports map is pinned by packages/types/src/__tests__/package-exports-manifest.test.ts, and the root barrel was the only route to this type.

.changeset/9606-object-kanban-card-title.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Both published faces of the object-kanban arm now name the key: the zod mirror ObjectKanbanSchema in zod/objectql.zod.ts and its TypeScript twin, the ObjectKanbanSchema interface in objectql.ts. Both declare it OPTIONAL, at the same requiredness the other face uses, so the two faces accept and refuse the same documents. (Located and cited by SYMBOL: line addresses in zod/objectql.zod.ts have drifted before, and this change is itself about a drifted mirror.)

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  Both published faces of the object-kanban arm now name the key: the zod mirror ObjectKanbanSchema in zod/objectql.zod.ts and its TypeScript twin, the ObjectKanbanSchema interface in objectql.ts. Both declare it OPTIONAL, at the same requiredness the other face uses, so the two faces accept and refuse the same documents. (Located and cited by SYMBOL: line addresses in zod/objectql.zod.ts have drifted before, and this change is itself about a drifted mirror.)

.changeset/9628-kanban-column-collapsed-honoured.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  The key was declared on both published faces of the object-kanban arm — the lane element of ObjectKanbanSchema (objectql.ts and its Zod mirror) and the runtime lane KanbanColumn (complex.ts and its mirror) — and read by KanbanEnhanced alone, a module no production source imports. An authored { "id": "todo", "title": "To Do", "collapsed": true } therefore parsed green on both faces and reached a board that did nothing with it: KanbanImpl's only collapse is the SWIMLANE row's, held in viewer state under objectui:kanban-collapsed:ANGLE-BRACKETS(swimlaneField) and never keyed to a lane's declared value. That is the ADR-0049 declared-but-unhonoured shape.

.changeset/9952-condition-placeholder-derives-from-offered-roots.md

• names conditionScope.ts → packages/app-shell/src/views/metadata-admin/conditionScope.ts — edited by this change

  The placeholder was a string literal — record.status != 'done' && user.isAdmin — handed to CelPredicateField at every mount, scope or no scope. The same component had already narrowed a record-scoped mount's autocomplete to RECORD_CONDITION_ROOTS (objectui#9645), which carries no user, and narrowed that mount's subject dropdown the same way (objectui#9855). At such a mount user is not merely unadvertised: conditionScope.ts states that a hook condition and a validation rule's guard are evaluated with { record, previous } and only those, fail-CLOSED at the validation host, and objectstack's wrapDeclarativeHook docblock says the condition formula is evaluated against two bindings, record and previous. So the one line an author reads before typing anything taught a root the evaluator never binds, and copying it cost the author the write.

.changeset/action-keys-warning-text-5642.md

• names ActionRunner.ts → packages/core/src/actions/ActionRunner.ts — edited by this change

  Both halves of the message's tail had outlived the change they described. It told the author the key was warned about rather than rejected because ActionDef "still carries [key: string]: any" — objectstack#4075 step 3 deleted that index signature, and actionKeys.pin.test.ts pins the deletion in the opposite direction ({ ActionDef: false, ActionContext: true }), while actionDef-closed-surface.test.ts pins that tsc now rejects exactly such a key at the construction site. And it prescribed promoting the key to an explicit field on ActionDef "(packages/core/src/actions/actionKeys.ts)" — that file holds the INVENTORY (ACTION_DEF_KEYS); the interface is in ActionRunner.ts. The wrong pointer had teeth: an author who followed it edited the inventory alone, which is precisely the half-change the pin test reddens on, since it re-derives the inventory from the interface's AST.

.changeset/console-form-container-specs-one-declaration-5596.md

• names SchemaForm.tsx → packages/app-shell/src/views/metadata-admin/SchemaForm.tsx — edited by this change

  objectui#5542 converged the LEAF of this contract — the field spec — and left the two containers above it untouched, because converging them was a bigger call than a mechanical import. FormSectionSpec and FormViewSpec were each hand-declared twice under the same names, once in packages/app-shell's SchemaForm.tsx and once in apps/console's FormPage.tsx. Unlike the leaf — whose console copy was a clean subset — these two had already drifted, in both directions, so neither copy was a subset of the other and there were two live answers to "what may an author write":

.changeset/dashboard-expandable-family-convergence-5692.md

• names ObjectDataTable.tsx → packages/plugin-dashboard/src/ObjectDataTable.tsx — edited by this change

  plugin-dashboard's two private copies of the reference-bearing field family now read @object-ui/core's published EXPANDABLE_FIELD_TYPES instead of restating it — LOOKUP_TYPES in recordFields.tsx and the inline disjunction inside computeLookupExpand in ObjectDataTable.tsx. Both carry the identity pin the already-converged consumers carry, so a member-identical private copy fails rather than quietly re-forking the table.

.changeset/dashboard-stable-empty-rows-4629.md

• names data-table.tsx → packages/components/src/renderers/complex/data-table.tsx — edited by this change

  Nothing rendered wrong before or after; this is wasted work in the empty window, plus the live react-hooks/exhaustive-deps warning the conditional raised. It is the same module-scope frozen empty data-table.tsx adopted for its own EMPTY_ROWS (objectui#4618), applied to the provider: 'object' siblings.

.changeset/formfieldspec-dependson-5040.md

• names SchemaForm.tsx → packages/app-shell/src/views/metadata-admin/SchemaForm.tsx — edited by this change

  No runtime behaviour changes: MetadataField already handed dependsOn through and both widgets already read it. What changes is the type face — it now admits what the runtime has always accepted. The two descriptions are one declaration, extracted to a leaf module (views/metadata-admin/form-spec.ts) that both halves import, because SchemaForm.tsx imports ./widgets.js and a back-edge would close a cycle. SchemaForm.tsx re-exports FormFieldSpec and VisibilityPredicate, so every existing importer is unaffected.

.changeset/layout-default-jsdoc-7361.md

• names layout.ts → packages/types/src/layout.ts — edited by this change

  The published @default documentation on two layout.ts members now matches the value the renderer actually applies. ContainerSchema.maxWidth documented 'lg' while container.tsx applies schema.maxWidth ?? 'xl', and the shared FlexLayoutProps.align documented 'center' while flex.tsx applies schema.align || 'start' and stack.tsx applies schema.align || 'stretch'. The renderers are unchanged — they are the authority for what runs — so only the docblocks moved; align now states both consumers in prose instead of carrying a single @default, because one member shared by two deliberately divergent component types cannot have one correct default.

• names flex.tsx → packages/components/src/renderers/layout/flex.tsx — edited by this change

  The published @default documentation on two layout.ts members now matches the value the renderer actually applies. ContainerSchema.maxWidth documented 'lg' while container.tsx applies schema.maxWidth ?? 'xl', and the shared FlexLayoutProps.align documented 'center' while flex.tsx applies schema.align || 'start' and stack.tsx applies schema.align || 'stretch'. The renderers are unchanged — they are the authority for what runs — so only the docblocks moved; align now states both consumers in prose instead of carrying a single @default, because one member shared by two deliberately divergent component types cannot have one correct default.

.changeset/layout-direction-default-jsdoc-7734.md

• names flex.tsx → packages/components/src/renderers/layout/flex.tsx — edited by this change

  The published @default documentation on FlexLayoutProps.direction no longer states a value that only one of its two consumers applies. The member is declared once (objectui#6151) but flex.tsx reads schema.direction || 'row' while stack.tsx reads schema.direction || 'col' ("Default to column for Stack"), so the single @default 'row' was correct for flex and wrong for stack — whose own defaultProps.direction is 'col'. The renderers are unchanged — they are the authority for what runs — so only the docblock moved: direction now names both consumers in prose, the same remedy objectui#7361 applied to the sibling align. justify is shared by the same two consumers and both read || 'start', so its tag is correct and stays: the criterion is a DIVERGENT shared member, not a shared one.

.changeset/objectchart-fieldoptionlabel-ref-5587.md

• names useObjectLabel.ts → packages/i18n/src/useObjectLabel.ts — edited by this change

  Pinned by ObjectChart.fieldOptionLabelRefetch.test.tsx, which counts fetches across forced re-renders both outside and inside a provider. Reverting useObjectLabel.ts to its pre-objectui#5564 state turns the no-provider case red (2 fetches instead of 1, alongside React's "Maximum update depth exceeded"), so the removal is pinned to the fix that unlocked it rather than to a comment.

.changeset/objectpivottable-i18n-resolver-refs-5625.md

• names useObjectLabel.ts → packages/i18n/src/useObjectLabel.ts — edited by this change

  Pinned by ObjectPivotTable.i18nResolverDeps.test.tsx, which counts derivations across forced re-renders both outside and inside a provider, checks that the two derived state maps settle, and asserts the language-switch re-derivation. Reverting useObjectLabel.ts to its pre-objectui#5585 state turns the no-provider case red (derivations in the dozens instead of 1), so the removal is pinned to the fix that unlocked it rather than to a comment.

.changeset/record-alert-row-binding-4807.md

• names providers/ExpressionProvider.tsx → packages/app-shell/src/providers/ExpressionProvider.tsx — edited by this change

  • row-action shorthand (status == 'x') resolved nothing, so the evaluator threw. The legacy ${…} path answers a throw with its own source text, a non-empty and therefore truthy string, so the verdict was SHOWN on every row. A banner the author had gated was permanently on screen. - legacy data.* (data.status == 'x') did not throw at all. App-shell's ambient predicate scope (providers/ExpressionProvider.tsx) carries data: {}, so the predicate read that object instead of the row, compared undefined, and the verdict was a constant false — never shown.

.changeset/record-picker-label-placeholder-i18n-5637.md

• names renderers/layout/containers.tsx → packages/components/src/renderers/layout/containers.tsx — edited by this change

  KNOWN GAP, unchanged by this release: the sibling label read sites in renderers/layout/containers.tsx compose translateLabel(pickLocalized(…), language), and that second helper is not applied here — translateLabel and its KNOWN_LABEL_DICT are module-private to that file. Only the locale-map resolution lands in this change; a plain-English string label is still rendered verbatim in every language, exactly as before.

.changeset/row-predicate-record-canon-5330.md

• names evaluator/rowPredicateCanon.ts → packages/core/src/evaluator/rowPredicateCanon.ts — edited by this change

  • @object-ui/core exports detectNonCanonicalRowSpelling, warnNonCanonicalRowSpelling, resetRowPredicateCanonWarnings and ROW_PREDICATE_CANONICAL_ROOT from a new evaluator/rowPredicateCanon.ts, which carries the canon statement and the measurement. - Both evaluation tiers report once, in dev: evalRowPredicate (core) and useCondition (react, for bags bound by usePredicateRecordContext). - Detection reuses the server's own oracles (collectCelRootIdentifiers, firstUndeclaredReference) rather than a regex, so no second dialect judgement is invented client-side.

.changeset/table-renderer-declared-column-contract-5350.md

• names packages/types/src/data-display.ts → packages/types/src/data-display.ts — edited by this change

  renderers/complex/table.tsx resolved a heading as col.header || col.label and a cell as row[col.accessorKey || col.name]. Neither label nor name is declared on TableColumn, which declares header and accessorKey — both required (packages/types/src/data-display.ts). This was the fourth site of the column-alias family, after data-table, ObjectDataTable and ObjectGrid (objectui#5350).

Read the paragraph, not the line: both false halves of the objectui#8617 claim sat in one paragraph, and correcting either alone would have left it asserting the same wrong thing.

If a claim did go false, correct the body. That is precedented and prose-only, frontmatter untouched; check-changeset-overwrite.mjs will report the correction as its own case 2 ("correcting a declaration on purpose … legitimate"), which is the intended shape — one gate asks for the read, the other records the write.

Not covered, stated so nobody reads this as more: a born-false claim that spells no line address at all (objectui#9495 coordinated one by ORDINAL — "a grep finds that member first" — and deciding that means reading what the sentence means), a claim spelled as a symbol or a package rather than a backticked file name, and a file named ambiguously.

Angle-bracketed names in the quoted prose above are rewritten as ANGLE-BRACKETS(name): GitHub deletes tag-shaped fragments from a stored body, and a quote that silently loses the identifier it is about is worse than a visible repair.

Compared the checked-out tree with fab627ff9 (merge-base with origin/main): 85 file(s) changed outside .changeset/, read against 1600 pending declaration(s) that publish a body (2187 pending in total). · run

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3082.4 KB	3104.5 KB
Main entry chunk (gzip)	148.5 KB	350 KB
Entry file	index-Cir-gKV1.js	—
Status	PASS	—

The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it.

---

📦 Bundle Size Report

Package	Size	Gzipped
app-shell (consoleActionDispatch.js)	0.20KB	0.19KB
app-shell (index.js)	16.57KB	6.17KB
app-shell (runtime-config.js)	20.68KB	7.36KB
app-shell (types.js)	0.01KB	0.04KB
app-shell (urlParams.js)	10.06KB	3.86KB
auth (ActiveOrganizationStorage.js)	27.95KB	10.04KB
auth (AuthContext.js)	0.31KB	0.24KB
auth (AuthGuard.js)	2.07KB	1.00KB
auth (AuthProvider.js)	40.17KB	10.58KB
auth (AuthShell.js)	3.49KB	1.40KB
auth (ForgotPasswordForm.js)	12.21KB	3.45KB
auth (LoginForm.js)	18.15KB	5.39KB
auth (PreviewBanner.js)	0.90KB	0.50KB
auth (RegisterForm.js)	6.65KB	2.22KB
auth (SocialSignInButtons.js)	9.61KB	3.89KB
auth (UserMenu.js)	3.39KB	1.21KB
auth (auth-gate-events.js)	1.29KB	0.66KB
auth (authStyles.js)	5.04KB	1.72KB
auth (createAuthClient.js)	40.21KB	10.80KB
auth (createAuthenticatedFetch.js)	8.52KB	3.45KB
auth (index.js)	3.63KB	1.64KB
auth (invitation-status.js)	1.22KB	0.70KB
auth (org-roles.js)	6.66KB	2.78KB
auth (phone-identifier.js)	1.11KB	0.66KB
auth (types.js)	0.59KB	0.35KB
auth (useAuth.js)	5.30KB	1.02KB
auth (useWorkspaceAdminStatus.js)	11.08KB	4.58KB
collaboration (CommentThread.js)	27.13KB	7.95KB
collaboration (LiveCursors.js)	3.17KB	1.27KB
collaboration (PresenceAvatars.js)	6.49KB	2.64KB
collaboration (PresenceProvider.js)	2.79KB	1.13KB
collaboration (index.js)	1.68KB	0.73KB
collaboration (useCollaborationTranslation.js)	6.05KB	2.52KB
collaboration (useCommentSearch.js)	1.98KB	0.88KB
collaboration (useConflictResolution.js)	7.75KB	1.86KB
collaboration (useMentionNotifications.js)	1.81KB	0.68KB
collaboration (usePresence.js)	6.33KB	1.84KB
collaboration (useRealtimeSubscription.js)	7.91KB	2.01KB
components (index.js)	557.20KB	133.48KB
core (index.js)	9.93KB	3.94KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	225.01KB	62.50KB
fields (index.js)	261.26KB	66.37KB
i18n (LocalizationContext.js)	1.76KB	0.96KB
i18n (builtinAggregateLabels.js)	0.86KB	0.49KB
i18n (currency.js)	2.59KB	1.22KB
i18n (fallbackInterpolation.js)	6.25KB	2.77KB
i18n (i18n.js)	8.87KB	3.64KB
i18n (index.js)	5.24KB	2.27KB
i18n (pickLocalized.js)	9.86KB	3.95KB
i18n (provider.js)	39.40KB	12.91KB
i18n (translateFn.js)	0.20KB	0.18KB
i18n (useDisplayLocale.js)	3.52KB	1.76KB
i18n (useObjectLabel.js)	34.34KB	9.17KB
i18n (useSafeTranslation.js)	5.60KB	2.33KB
layout (index.js)	39.28KB	11.09KB
mobile (MobileProvider.js)	0.92KB	0.49KB
mobile (ResponsiveContainer.js)	0.94KB	0.38KB
mobile (breakpoints.js)	1.51KB	0.70KB
mobile (createOfflineDataSource.js)	5.61KB	1.75KB
mobile (index.js)	1.99KB	0.87KB
mobile (offlineQueue.js)	3.91KB	1.35KB
mobile (pwa.js)	0.97KB	0.49KB
mobile (serviceWorker.js)	1.48KB	0.62KB
mobile (serviceWorkerSource.js)	3.41KB	1.48KB
mobile (useBreakpoint.js)	1.54KB	0.65KB
mobile (useGesture.js)	6.96KB	1.98KB
mobile (useOfflineSync.js)	1.99KB	0.72KB
mobile (usePullToRefresh.js)	6.62KB	2.45KB
mobile (useResponsive.js)	0.72KB	0.42KB
mobile (useSpecGesture.js)	5.52KB	2.10KB
mobile (useTouchTarget.js)	1.01KB	0.54KB
permissions (MePermissionsProvider.js)	13.52KB	4.88KB
permissions (PermissionContext.js)	0.31KB	0.25KB
permissions (PermissionGuard.js)	0.89KB	0.45KB
permissions (PermissionProvider.js)	6.24KB	2.16KB
permissions (discardProofCache.js)	1.04KB	0.55KB
permissions (evaluator.js)	8.33KB	3.07KB
permissions (index.js)	0.93KB	0.41KB
permissions (store.js)	0.91KB	0.42KB
permissions (useFieldPermissions.js)	1.28KB	0.53KB
permissions (usePermissions.js)	4.83KB	2.27KB
plugin-ai (index.js)	16.01KB	3.93KB
plugin-calendar (index.js)	51.73KB	14.72KB
plugin-charts (index.js)	83.99KB	22.86KB
plugin-chatbot (index.js)	197.67KB	46.90KB
plugin-dashboard (index.js)	135.87KB	36.15KB
plugin-designer (index.js)	216.42KB	44.47KB
plugin-detail (index.js)	233.48KB	61.79KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	158.78KB	40.61KB
plugin-gantt (index.js)	169.83KB	41.99KB
plugin-grid (index.js)	218.66KB	59.90KB
plugin-kanban (index.js)	48.43KB	15.11KB
plugin-list (index.js)	114.78KB	28.44KB
plugin-map (index.js)	22.90KB	7.62KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	44.17KB	12.20KB
plugin-timeline (index.js)	31.00KB	9.09KB
plugin-tree (index.js)	11.21KB	3.89KB
plugin-view (index.js)	87.86KB	22.02KB
providers (DataSourceProvider.js)	0.75KB	0.39KB
providers (MetadataProvider.js)	1.37KB	0.59KB
providers (ThemeProvider.js)	1.90KB	0.85KB
providers (UploadProvider.js)	11.81KB	3.58KB
providers (index.js)	0.45KB	0.23KB
providers (types.js)	0.01KB	0.04KB
react-runtime (index.js)	5.62KB	2.34KB
react (LazyPluginLoader.js)	4.47KB	1.63KB
react (SchemaRenderer.js)	119.16KB	39.05KB
react (data-invalidation.js)	5.05KB	2.08KB
react (index.js)	4.03KB	1.86KB
react (schema-input.js)	4.25KB	2.04KB
react (spec-input.js)	0.20KB	0.18KB
sdui-parser (body-dialect.js)	4.78KB	2.09KB
sdui-parser (codegen.js)	7.50KB	3.05KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	6.16KB	2.71KB
sdui-parser (input-type.js)	2.84KB	1.40KB
sdui-parser (kanban-quick-add.js)	3.89KB	1.87KB
sdui-parser (parse.js)	25.28KB	7.80KB
sdui-parser (provenance.js)	3.84KB	1.90KB
sdui-parser (types.js)	0.28KB	0.23KB
sdui-parser (validate.js)	18.27KB	6.22KB
types (ai.js)	4.11KB	2.06KB
types (api-types.js)	0.20KB	0.18KB
types (app.js)	3.52KB	1.36KB
types (base.js)	0.20KB	0.18KB
types (blocks.js)	0.20KB	0.18KB
types (complex.js)	2.93KB	1.49KB
types (crud.js)	0.20KB	0.18KB
types (dashboard-filter-alias.js)	6.23KB	2.74KB
types (data-display.js)	3.75KB	1.85KB
types (data-protocol.js)	0.20KB	0.19KB
types (data.js)	0.20KB	0.18KB
types (designer.js)	1.85KB	0.85KB
types (disclosure.js)	0.20KB	0.18KB
types (error-code.js)	1.54KB	0.88KB
types (expression.js)	0.20KB	0.18KB
types (feedback.js)	0.20KB	0.18KB
types (field-types.js)	0.20KB	0.18KB
types (form.js)	0.20KB	0.18KB
types (http-inflight.js)	8.87KB	3.73KB
types (http-retry.js)	4.32KB	2.02KB
types (icon-key-migration.js)	4.26KB	1.63KB
types (index.js)	4.74KB	2.26KB
types (layout.js)	0.20KB	0.18KB
types (managed-by.js)	0.19KB	0.18KB
types (mobile.js)	5.00KB	2.39KB
types (navigation.js)	0.20KB	0.18KB
types (objectql.js)	0.20KB	0.18KB
types (overlay.js)	0.20KB	0.18KB
types (permissions.js)	2.52KB	1.31KB
types (plugin-scope.js)	0.20KB	0.18KB
types (record-components.js)	0.20KB	0.19KB
types (record-semantics.js)	1.28KB	0.67KB
types (registry.js)	0.20KB	0.18KB
types (reports.js)	0.20KB	0.18KB
types (select-option.js)	0.20KB	0.19KB
types (spec-report.js)	5.05KB	1.93KB
types (spec-ui-namespace.js)	0.20KB	0.19KB
types (strict-authoring-face.js)	17.15KB	6.32KB
types (system-fields.js)	3.33KB	1.54KB
types (theme.js)	6.27KB	2.87KB
types (ui-action.js)	8.11KB	3.32KB
types (views.js)	0.20KB	0.18KB
types (widget.js)	0.20KB	0.18KB

Size Limits

• ✅ Core packages should be < 50KB gzipped
• ✅ Component packages should be < 100KB gzipped
• ⚠️ Plugin packages should be < 150KB gzipped

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3082.4 KB	3104.5 KB
Main entry chunk (gzip)	148.5 KB	350 KB
Entry file	index-v9hRC_K7.js	—
Status	PASS	—

The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it.

---

📦 Bundle Size Report

Package	Size	Gzipped
app-shell (consoleActionDispatch.js)	0.20KB	0.19KB
app-shell (index.js)	16.57KB	6.17KB
app-shell (runtime-config.js)	20.68KB	7.36KB
app-shell (types.js)	0.01KB	0.04KB
app-shell (urlParams.js)	10.06KB	3.86KB
auth (ActiveOrganizationStorage.js)	27.95KB	10.04KB
auth (AuthContext.js)	0.31KB	0.24KB
auth (AuthGuard.js)	2.07KB	1.00KB
auth (AuthProvider.js)	40.17KB	10.58KB
auth (AuthShell.js)	3.49KB	1.40KB
auth (ForgotPasswordForm.js)	12.21KB	3.45KB
auth (LoginForm.js)	18.15KB	5.39KB
auth (PreviewBanner.js)	0.90KB	0.50KB
auth (RegisterForm.js)	6.65KB	2.22KB
auth (SocialSignInButtons.js)	9.61KB	3.89KB
auth (UserMenu.js)	3.39KB	1.21KB
auth (auth-gate-events.js)	1.29KB	0.66KB
auth (authStyles.js)	5.04KB	1.72KB
auth (createAuthClient.js)	40.21KB	10.80KB
auth (createAuthenticatedFetch.js)	8.52KB	3.45KB
auth (index.js)	3.63KB	1.64KB
auth (invitation-status.js)	1.22KB	0.70KB
auth (org-roles.js)	6.66KB	2.78KB
auth (phone-identifier.js)	1.11KB	0.66KB
auth (types.js)	0.59KB	0.35KB
auth (useAuth.js)	5.30KB	1.02KB
auth (useWorkspaceAdminStatus.js)	11.08KB	4.58KB
collaboration (CommentThread.js)	27.13KB	7.95KB
collaboration (LiveCursors.js)	3.17KB	1.27KB
collaboration (PresenceAvatars.js)	6.49KB	2.64KB
collaboration (PresenceProvider.js)	2.79KB	1.13KB
collaboration (index.js)	1.68KB	0.73KB
collaboration (useCollaborationTranslation.js)	6.05KB	2.52KB
collaboration (useCommentSearch.js)	1.98KB	0.88KB
collaboration (useConflictResolution.js)	7.75KB	1.86KB
collaboration (useMentionNotifications.js)	1.81KB	0.68KB
collaboration (usePresence.js)	6.33KB	1.84KB
collaboration (useRealtimeSubscription.js)	7.91KB	2.01KB
components (index.js)	557.20KB	133.48KB
core (index.js)	9.93KB	3.94KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	225.01KB	62.50KB
fields (index.js)	261.26KB	66.37KB
i18n (LocalizationContext.js)	1.76KB	0.96KB
i18n (builtinAggregateLabels.js)	0.86KB	0.49KB
i18n (currency.js)	2.59KB	1.22KB
i18n (fallbackInterpolation.js)	6.25KB	2.77KB
i18n (i18n.js)	8.87KB	3.64KB
i18n (index.js)	5.24KB	2.27KB
i18n (pickLocalized.js)	9.86KB	3.95KB
i18n (provider.js)	39.40KB	12.91KB
i18n (translateFn.js)	0.20KB	0.18KB
i18n (useDisplayLocale.js)	3.52KB	1.76KB
i18n (useObjectLabel.js)	34.34KB	9.17KB
i18n (useSafeTranslation.js)	5.60KB	2.33KB
layout (index.js)	39.28KB	11.09KB
mobile (MobileProvider.js)	0.92KB	0.49KB
mobile (ResponsiveContainer.js)	0.94KB	0.38KB
mobile (breakpoints.js)	1.51KB	0.70KB
mobile (createOfflineDataSource.js)	5.61KB	1.75KB
mobile (index.js)	1.99KB	0.87KB
mobile (offlineQueue.js)	3.91KB	1.35KB
mobile (pwa.js)	0.97KB	0.49KB
mobile (serviceWorker.js)	1.48KB	0.62KB
mobile (serviceWorkerSource.js)	3.41KB	1.48KB
mobile (useBreakpoint.js)	1.54KB	0.65KB
mobile (useGesture.js)	6.96KB	1.98KB
mobile (useOfflineSync.js)	1.99KB	0.72KB
mobile (usePullToRefresh.js)	6.62KB	2.45KB
mobile (useResponsive.js)	0.72KB	0.42KB
mobile (useSpecGesture.js)	5.52KB	2.10KB
mobile (useTouchTarget.js)	1.01KB	0.54KB
permissions (MePermissionsProvider.js)	13.52KB	4.88KB
permissions (PermissionContext.js)	0.31KB	0.25KB
permissions (PermissionGuard.js)	0.89KB	0.45KB
permissions (PermissionProvider.js)	6.24KB	2.16KB
permissions (discardProofCache.js)	1.04KB	0.55KB
permissions (evaluator.js)	8.33KB	3.07KB
permissions (index.js)	0.93KB	0.41KB
permissions (store.js)	0.91KB	0.42KB
permissions (useFieldPermissions.js)	1.28KB	0.53KB
permissions (usePermissions.js)	4.83KB	2.27KB
plugin-ai (index.js)	16.01KB	3.93KB
plugin-calendar (index.js)	51.73KB	14.72KB
plugin-charts (index.js)	83.99KB	22.86KB
plugin-chatbot (index.js)	197.67KB	46.90KB
plugin-dashboard (index.js)	136.82KB	36.44KB
plugin-designer (index.js)	216.42KB	44.47KB
plugin-detail (index.js)	233.48KB	61.79KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	158.78KB	40.61KB
plugin-gantt (index.js)	169.83KB	41.99KB
plugin-grid (index.js)	218.66KB	59.90KB
plugin-kanban (index.js)	48.43KB	15.11KB
plugin-list (index.js)	114.78KB	28.44KB
plugin-map (index.js)	22.90KB	7.62KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	44.17KB	12.20KB
plugin-timeline (index.js)	31.00KB	9.09KB
plugin-tree (index.js)	11.21KB	3.89KB
plugin-view (index.js)	87.86KB	22.02KB
providers (DataSourceProvider.js)	0.75KB	0.39KB
providers (MetadataProvider.js)	1.37KB	0.59KB
providers (ThemeProvider.js)	1.90KB	0.85KB
providers (UploadProvider.js)	11.81KB	3.58KB
providers (index.js)	0.45KB	0.23KB
providers (types.js)	0.01KB	0.04KB
react-runtime (index.js)	5.62KB	2.34KB
react (LazyPluginLoader.js)	4.47KB	1.63KB
react (SchemaRenderer.js)	119.16KB	39.05KB
react (data-invalidation.js)	5.05KB	2.08KB
react (index.js)	4.03KB	1.86KB
react (schema-input.js)	4.25KB	2.04KB
react (spec-input.js)	0.20KB	0.18KB
sdui-parser (body-dialect.js)	4.78KB	2.09KB
sdui-parser (codegen.js)	7.50KB	3.05KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	6.16KB	2.71KB
sdui-parser (input-type.js)	2.84KB	1.40KB
sdui-parser (kanban-quick-add.js)	3.89KB	1.87KB
sdui-parser (parse.js)	25.28KB	7.80KB
sdui-parser (provenance.js)	3.84KB	1.90KB
sdui-parser (types.js)	0.28KB	0.23KB
sdui-parser (validate.js)	18.27KB	6.22KB
types (ai.js)	4.11KB	2.06KB
types (api-types.js)	0.20KB	0.18KB
types (app.js)	3.52KB	1.36KB
types (base.js)	0.20KB	0.18KB
types (blocks.js)	0.20KB	0.18KB
types (complex.js)	2.93KB	1.49KB
types (crud.js)	0.20KB	0.18KB
types (dashboard-filter-alias.js)	6.23KB	2.74KB
types (data-display.js)	3.75KB	1.85KB
types (data-protocol.js)	0.20KB	0.19KB
types (data.js)	0.20KB	0.18KB
types (designer.js)	1.85KB	0.85KB
types (disclosure.js)	0.20KB	0.18KB
types (error-code.js)	1.54KB	0.88KB
types (expression.js)	0.20KB	0.18KB
types (feedback.js)	0.20KB	0.18KB
types (field-types.js)	0.20KB	0.18KB
types (form.js)	0.20KB	0.18KB
types (http-inflight.js)	8.87KB	3.73KB
types (http-retry.js)	4.32KB	2.02KB
types (icon-key-migration.js)	4.26KB	1.63KB
types (index.js)	4.74KB	2.26KB
types (layout.js)	0.20KB	0.18KB
types (managed-by.js)	0.19KB	0.18KB
types (mobile.js)	5.00KB	2.39KB
types (navigation.js)	0.20KB	0.18KB
types (objectql.js)	0.20KB	0.18KB
types (overlay.js)	0.20KB	0.18KB
types (permissions.js)	2.52KB	1.31KB
types (plugin-scope.js)	0.20KB	0.18KB
types (record-components.js)	0.20KB	0.19KB
types (record-semantics.js)	1.28KB	0.67KB
types (registry.js)	0.20KB	0.18KB
types (reports.js)	0.20KB	0.18KB
types (select-option.js)	0.20KB	0.19KB
types (spec-report.js)	5.05KB	1.93KB
types (spec-ui-namespace.js)	0.20KB	0.19KB
types (strict-authoring-face.js)	17.15KB	6.32KB
types (system-fields.js)	3.33KB	1.54KB
types (theme.js)	6.27KB	2.87KB
types (ui-action.js)	8.11KB	3.32KB
types (views.js)	0.20KB	0.18KB
types (widget.js)	0.20KB	0.18KB

Size Limits

• ✅ Core packages should be < 50KB gzipped
• ✅ Component packages should be < 100KB gzipped
• ⚠️ Plugin packages should be < 150KB gzipped

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: e4bce25b808d6fd8eac93d4c7b2c8d52f6fc2dc4

① Derived judgments

Census: reproduced. The reviewer ran the printed instrument with git grep. It reads 217 at the branch point a60539b07, 217 at main fab627ff9 and 0 at the head. The head is 0 commits behind main, so the head merged with main also reads 0. Without the objectstack# filter the head shows 5 lines, all of them live objectstack#5425 / #5418 / #5505 sister citations.

• A sweep for forms the instrument might miss (bare digits, issues/N or pull/N URLs, #N in backticks) hits only changeset or test filenames and the sha 5505aec.
• Out-of-scope classes: the only files touched are the 6 test anchors and the 2 content/docs quote followers. Nothing in scripts, .github or governed text is touched.

Shas: all check out. All 32 distinct shas pass git merge-base --is-ancestor against main (exit 0 each), and rev-parse --short=9 returns the same 9 characters for each.

Mapping. 15 numbers were sampled, each against its sha's git show:

• Right landing, sentence still true: spec 把 5 值 HTTP 方法子集改名(HttpMethodSchema → HttpMethodSubsetSchema、HttpMethodType → HttpMethodSubset),packages/types 两处 import 需跟名 #3499, interpretFlowResponse must classify a 400 FLOW_FAILED on flow resume as terminal, not retryable — lands BEFORE the backend status flip (objectstack#8684) #4784, Console half of ActionSchema.onSuccess navigation (objectstack#9566/#9474): SPA route hop, executeAPI handling, ${result.*} interpolation scope #5221 (both sites), Approver membership-tier select hardcodes three tiers — delegated_admin is not offered and a stored value renders "(invalid)" #5309, record:alert silently ignores the declared visibleWhen gate that its sibling blocks honour — the same defect already closed on the record-header face #5401 / Bind record into node-level visibleWhen, and stop visible swallowing it #5505, The approval panel identifies the pending approver as a truncated raw id — positi…ager — so nobody can tell who is holding the record #5414 (including the "surfaces" / "fixes" repairs), [finding] After #4881's flip, StudioNavItemInspector still READS the schema-rejected object spelling as a fallback — the last one in the Interfaces pillar #5518 (named by role), A gauge widget's options.invert has no observable effect, and nothing can say so — it is an undeclared key riding DashboardWidgetOptionsSchema.passthrough() #5709, ConditionBuilder: caller-supplied subject vocabulary (scope prefix + previous.FIELD subjects) — prerequisite for the flow-entry wiring ruled on #6226 #6296 (the REFERENCE_ROOTS and 6293 repairs), contract: should AppAction.items be re-typed to the overlay MenuItem? — the runner reads two overlay fields through as any today #6854 (the zh changeset), finding(types/plugin-charts): the static ChartSchema node's two data keys are declared-but-unread — ChartDataSeries.data is required and never read, and categories is read as a SERIES list, not axis labels #6896, Two alias pairs on TextSchema and TreeViewSchema are now DECLARED in both spellings — and TreeViewSchema.data is required while nodes is the documented one (deferred rulings carried out of #6150) #6951 A1 (5ad86ddee) and B1 (16a725f96).

• One mis-attribution, Row-predicate deprecation is missing its Phase 0: docs and example apps may still teach the bare shorthand / data.* spellings the new warning now flags #5738. Three sites read "the 702c48a62 corpus sweep's stand-down 3":

  • the conditionScope.ts docblock;
  • the CONDITION_SCOPE_BY_METADATA_TYPE.sharing_rule doc;
  • .changeset/7727-conditional-formatting-record-scope.md.

  702c48a62 is a one-line plugin-form/README.md edit. Its message says nothing about a stand-down, RLS or flow surfaces. Special case 2 in the PR body itself concedes that the finding "was recorded on the dead Phase-0 corpus-sweep card, not in a commit".

  So the sha does not carry what it is cited for. Under the order (Zone 1 item 3) and the docs: cite landing commits where pending changesets and source comments name fourteen objectui issues that answer 404 (objectui#10803) #10854 precedent (its finding(ci): check-spec-range-floors reports [floor-too-low] on @object-ui/types — its declared ^17.0.0 does not carry FilterCondition, and the blocking copy runs on the publish path #7688 finding-card case), nothing answers here, and the card is named by role, the form this PR already uses for Console half of ActionSchema.onSuccess navigation (objectstack#9566/#9474): SPA route hop, executeAPI handling, ${result.*} interpolation scope #5221.

  The fourth Row-predicate deprecation is missing its Phase 0: docs and example apps may still teach the bare shorthand / data.* spellings the new warning now flags #5738 site is fine: rowPredicateCanon.ts cites "the 702c48a62 corpus sweep's recipe", and that commit's message does carry the recipe (the detectNonCanonicalRowSpelling oracle).

Runtime strings: only the listed text moved. The full word diff of all 77 source files was read:

• 73 files change only inside //, /* */ or JSX {/* */} comments.
• The other 4 files carry exactly the 9 listed substitutions:
  • 5 tombstone literals (the aria error and describe strings, plus 3 retirementTombstone strings);
  • 3 pointer deletions in describe strings (TreeViewSchema.nodes twice, TextSchema.content once);
  • 1 in the advisory.
• Everything after each dash is byte-unchanged.

The ADR-0049 condition, per key:

• The TypeScript twins of TreeViewSchema.data, ChartDataSeriesSchema.data and TextSchema.value read "RETIRED (SHA, ADR-0049 enforce-or-remove)", so (ADR-0049) is correct for those three.
• The twin of DashboardConfigSchema.aria is the comment on DashboardConfig in designer.ts. It does not name ADR-0049, so RETIRED — is correct by the ruling's letter.
• aria versus the zod-side comment: consistent. The comment above DashboardConfigSchema in complex.zod.ts calls aria an "ADR-0049 retirement tombstone". So do e7957ab87's message and the pending dashboard-config-aria-retired-5852.md.
  • RETIRED — makes no ADR claim, so it contradicts none of them.
  • The ruling's premise was mis-measured for this key: aria's twin is a deletion note.
  • Moving aria to (ADR-0049) is the seat's call, not a defect in this PR.

Pinning tests: literal anchors only; remedy anchors survive.

• The delete the key anchor survives, as do the xAxisKey / chart-level data anchors and the PRESCRIPTIVE checks.
• dashboard-config.test.ts tightened /RETIRED \(objectui#5852\)/ to /^RETIRED — /. That is a stronger check, so it is acceptable.
• No test pins the two describe strings or the advisory text.
• The remaining "RETIRED (objectui#6951)" @ts-expect-error comments and test titles are out of class and disclosed.

Changesets.

• The frontmatter of all 47 edited changesets is byte-identical (extracted from both refs and compared by md5). No frontmatter line appears in the diff, and 2 changesets are added.
• All 47 edited changesets were read; none carries a false sentence, apart from the Row-predicate deprecation is missing its Phase 0: docs and example apps may still teach the bare shorthand / data.* spellings the new warning now flags #5738 site above.
• .changeset/10803-third-batch-runtime-strings.md is false as written, sentence 2. It says "so each dead pointer is dropped rather than replaced (objectui#10803)". Its own next bullet says three tombstones now open RETIRED (ADR-0049) — "in place of the dead card". This is round-1 text that survived ruling 5861129870.
• .changeset/10803-dead-citation-sweep-third-batch.md (non-blocking): the list "the commit …, the ruling by its date …, or a live successor" leaves out the role-named [finding] After #4881's flip, StudioNavItemInspector still READS the schema-rejected object spelling as a fallback — the last one in the Interfaces pillar #5518 site.

Dated notes: none added, and none owed.

② Semver level

patch for @object-ui/types and @object-ui/app-shell is correct:

• only message and description text moves;
• no key, accept set, issue code, path or severity moves;
• there is no narrowing, so Clause-②: no stands;
• the comment sweep correctly carries empty frontmatter;
• no changeset declares major (the Changeset Bump Policy check and changeset:check agree).

③ Boundary flags

• CI on the head: 43 check runs, all final. 40 succeeded; 3 were skipped (Test (coverage), the coverage-shard matrix row, dependabot); none failed. The combined status (Vercel) is success.
• git merge-tree --write-tree against a fresh main fab627ff9: clean (exit 0, tree 37ae6f7ec).
• Open PRs touching these files:
  • fix(app-shell): the action, agent, skill, tool and job previews and the CEL try-it dialog read the designer locale (objectui#10862, slice 1) #10871 (new since the dev's re-list): touches celAuthoring.ts and metadata-admin/i18n.ts, but its hunks are disjoint and a trial merge is clean.
  • feat(components,types)!: a list item and a tabs item draw content only, and both item faces refuse body by name (objectui#9590) #10714: clean.
  • feat(types,plugin-view,app-shell)!: ObjectViewSchema.listViews mirrors the spec's ObjectListViewSchema by reference; ViewPreview folds a stored options bag (objectui#7928) #10821: conflicts only in imported-defaults-8317.test.ts and object-view-unmirrored-keys-7779.test.ts. It has the same conflicts against main alone, so they are not this PR's.
  • chore: release packages #5400: the release PR; it regenerates and is not a hold.
• check-governed-merges.mjs --pr: NOT MEASURED.
  • It refused twice with HTTP 403 reading page 2 of the PR's files; the same page reads 200 over curl.
  • The same predicate via --test over the 134-path three-dot list reads 0 of 134, NOT governed (exit 0). The lit control AGENTS.md exits 3.
  • The head repo is objectstack-ai/objectui. Size is 524 lines, under 5000.
• Draft: yes. Assignee: os-elon-musk.
• Commit trailers: model-free (4 by 4).

Implemented-by: claude/issue-10803-dead-citations-third-batch
Reviewed-by: session_014mXUNuFomfj24w7s1pZzhN

VERDICT: FAIL

Two wording fixes, then this can land:

1. Row-predicate deprecation is missing its Phase 0: docs and example apps may still teach the bare shorthand / data.* spellings the new warning now flags #5738 mis-attribution (2 source comments and 1 changeset line).
   • In the conditionScope.ts file docblock and in .changeset/7727-conditional-formatting-record-scope.md, replace "(the 702c48a62 corpus sweep's stand-down 3)" with "(stand-down 3 on the corpus-sweep card behind 702c48a62)".
   • In the sharing_rule doc of CONDITION_SCOPE_BY_METADATA_TYPE, replace "the 702c48a62 corpus sweep's stand-down 3 surface" with "a stand-down 3 surface of the corpus-sweep card behind 702c48a62".
   • The PR body's Special case 2 follows. The census stays at 0, and the changeset frontmatter is untouched.
2. .changeset/10803-third-batch-runtime-strings.md, sentence 2. Replace "so each dead pointer is dropped rather than replaced (objectui#10803)." with "so no dead pointer becomes a commit: three tombstones cite ADR-0049 in its place, and every other pointer is simply dropped (objectui#10803)."

Optional, same round:

• In .changeset/10803-dead-citation-sweep-third-batch.md, change "or a live successor" to "or a live successor, and where nothing answers they name the card by role".
• Drop the process clause "because its TypeScript twin on DashboardConfig does not name ADR-0049" from release text.

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3082.4 KB	3104.5 KB
Main entry chunk (gzip)	148.5 KB	350 KB
Entry file	index-BEsdoG1W.js	—
Status	PASS	—

The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it.

---

📦 Bundle Size Report

Package	Size	Gzipped
app-shell (consoleActionDispatch.js)	0.20KB	0.19KB
app-shell (index.js)	16.57KB	6.17KB
app-shell (runtime-config.js)	20.68KB	7.36KB
app-shell (types.js)	0.01KB	0.04KB
app-shell (urlParams.js)	10.06KB	3.86KB
auth (ActiveOrganizationStorage.js)	27.95KB	10.04KB
auth (AuthContext.js)	0.31KB	0.24KB
auth (AuthGuard.js)	2.07KB	1.00KB
auth (AuthProvider.js)	40.17KB	10.58KB
auth (AuthShell.js)	3.49KB	1.40KB
auth (ForgotPasswordForm.js)	12.21KB	3.45KB
auth (LoginForm.js)	18.15KB	5.39KB
auth (PreviewBanner.js)	0.90KB	0.50KB
auth (RegisterForm.js)	6.65KB	2.22KB
auth (SocialSignInButtons.js)	9.61KB	3.89KB
auth (UserMenu.js)	3.39KB	1.21KB
auth (auth-gate-events.js)	1.29KB	0.66KB
auth (authStyles.js)	5.04KB	1.72KB
auth (createAuthClient.js)	40.21KB	10.80KB
auth (createAuthenticatedFetch.js)	8.52KB	3.45KB
auth (index.js)	3.63KB	1.64KB
auth (invitation-status.js)	1.22KB	0.70KB
auth (org-roles.js)	6.66KB	2.78KB
auth (phone-identifier.js)	1.11KB	0.66KB
auth (types.js)	0.59KB	0.35KB
auth (useAuth.js)	5.30KB	1.02KB
auth (useWorkspaceAdminStatus.js)	11.08KB	4.58KB
collaboration (CommentThread.js)	27.13KB	7.95KB
collaboration (LiveCursors.js)	3.17KB	1.27KB
collaboration (PresenceAvatars.js)	6.49KB	2.64KB
collaboration (PresenceProvider.js)	2.79KB	1.13KB
collaboration (index.js)	1.68KB	0.73KB
collaboration (useCollaborationTranslation.js)	6.05KB	2.52KB
collaboration (useCommentSearch.js)	1.98KB	0.88KB
collaboration (useConflictResolution.js)	7.75KB	1.86KB
collaboration (useMentionNotifications.js)	1.81KB	0.68KB
collaboration (usePresence.js)	6.33KB	1.84KB
collaboration (useRealtimeSubscription.js)	7.91KB	2.01KB
components (index.js)	557.20KB	133.48KB
core (index.js)	9.93KB	3.94KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	225.01KB	62.50KB
fields (index.js)	261.26KB	66.37KB
i18n (LocalizationContext.js)	1.76KB	0.96KB
i18n (builtinAggregateLabels.js)	0.86KB	0.49KB
i18n (currency.js)	2.59KB	1.22KB
i18n (fallbackInterpolation.js)	6.25KB	2.77KB
i18n (i18n.js)	8.87KB	3.64KB
i18n (index.js)	5.24KB	2.27KB
i18n (pickLocalized.js)	9.86KB	3.95KB
i18n (provider.js)	39.40KB	12.91KB
i18n (translateFn.js)	0.20KB	0.18KB
i18n (useDisplayLocale.js)	3.52KB	1.76KB
i18n (useObjectLabel.js)	34.34KB	9.17KB
i18n (useSafeTranslation.js)	5.60KB	2.33KB
layout (index.js)	39.28KB	11.09KB
mobile (MobileProvider.js)	0.92KB	0.49KB
mobile (ResponsiveContainer.js)	0.94KB	0.38KB
mobile (breakpoints.js)	1.51KB	0.70KB
mobile (createOfflineDataSource.js)	5.61KB	1.75KB
mobile (index.js)	1.99KB	0.87KB
mobile (offlineQueue.js)	3.91KB	1.35KB
mobile (pwa.js)	0.97KB	0.49KB
mobile (serviceWorker.js)	1.48KB	0.62KB
mobile (serviceWorkerSource.js)	3.41KB	1.48KB
mobile (useBreakpoint.js)	1.54KB	0.65KB
mobile (useGesture.js)	6.96KB	1.98KB
mobile (useOfflineSync.js)	1.99KB	0.72KB
mobile (usePullToRefresh.js)	6.62KB	2.45KB
mobile (useResponsive.js)	0.72KB	0.42KB
mobile (useSpecGesture.js)	5.52KB	2.10KB
mobile (useTouchTarget.js)	1.01KB	0.54KB
permissions (MePermissionsProvider.js)	13.52KB	4.88KB
permissions (PermissionContext.js)	0.31KB	0.25KB
permissions (PermissionGuard.js)	0.89KB	0.45KB
permissions (PermissionProvider.js)	6.24KB	2.16KB
permissions (discardProofCache.js)	1.04KB	0.55KB
permissions (evaluator.js)	8.33KB	3.07KB
permissions (index.js)	0.93KB	0.41KB
permissions (store.js)	0.91KB	0.42KB
permissions (useFieldPermissions.js)	1.28KB	0.53KB
permissions (usePermissions.js)	4.83KB	2.27KB
plugin-ai (index.js)	16.01KB	3.93KB
plugin-calendar (index.js)	51.73KB	14.72KB
plugin-charts (index.js)	83.99KB	22.86KB
plugin-chatbot (index.js)	197.67KB	46.90KB
plugin-dashboard (index.js)	136.82KB	36.44KB
plugin-designer (index.js)	216.42KB	44.47KB
plugin-detail (index.js)	233.48KB	61.79KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	158.78KB	40.61KB
plugin-gantt (index.js)	169.83KB	41.99KB
plugin-grid (index.js)	218.66KB	59.90KB
plugin-kanban (index.js)	48.43KB	15.11KB
plugin-list (index.js)	114.78KB	28.44KB
plugin-map (index.js)	22.90KB	7.62KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	44.17KB	12.20KB
plugin-timeline (index.js)	31.00KB	9.09KB
plugin-tree (index.js)	11.21KB	3.89KB
plugin-view (index.js)	87.86KB	22.02KB
providers (DataSourceProvider.js)	0.75KB	0.39KB
providers (MetadataProvider.js)	1.37KB	0.59KB
providers (ThemeProvider.js)	1.90KB	0.85KB
providers (UploadProvider.js)	11.81KB	3.58KB
providers (index.js)	0.45KB	0.23KB
providers (types.js)	0.01KB	0.04KB
react-runtime (index.js)	5.62KB	2.34KB
react (LazyPluginLoader.js)	4.47KB	1.63KB
react (SchemaRenderer.js)	119.16KB	39.05KB
react (data-invalidation.js)	5.05KB	2.08KB
react (index.js)	4.03KB	1.86KB
react (schema-input.js)	4.25KB	2.04KB
react (spec-input.js)	0.20KB	0.18KB
sdui-parser (body-dialect.js)	4.78KB	2.09KB
sdui-parser (codegen.js)	7.50KB	3.05KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	6.16KB	2.71KB
sdui-parser (input-type.js)	2.84KB	1.40KB
sdui-parser (kanban-quick-add.js)	3.89KB	1.87KB
sdui-parser (parse.js)	25.28KB	7.80KB
sdui-parser (provenance.js)	3.84KB	1.90KB
sdui-parser (types.js)	0.28KB	0.23KB
sdui-parser (validate.js)	18.27KB	6.22KB
types (ai.js)	4.11KB	2.06KB
types (api-types.js)	0.20KB	0.18KB
types (app.js)	3.52KB	1.36KB
types (base.js)	0.20KB	0.18KB
types (blocks.js)	0.20KB	0.18KB
types (complex.js)	2.93KB	1.49KB
types (crud.js)	0.20KB	0.18KB
types (dashboard-filter-alias.js)	6.23KB	2.74KB
types (data-display.js)	3.75KB	1.85KB
types (data-protocol.js)	0.20KB	0.19KB
types (data.js)	0.20KB	0.18KB
types (designer.js)	1.85KB	0.85KB
types (disclosure.js)	0.20KB	0.18KB
types (error-code.js)	1.54KB	0.88KB
types (expression.js)	0.20KB	0.18KB
types (feedback.js)	0.20KB	0.18KB
types (field-types.js)	0.20KB	0.18KB
types (form.js)	0.20KB	0.18KB
types (http-inflight.js)	8.87KB	3.73KB
types (http-retry.js)	4.32KB	2.02KB
types (icon-key-migration.js)	4.26KB	1.63KB
types (index.js)	4.74KB	2.26KB
types (layout.js)	0.20KB	0.18KB
types (managed-by.js)	0.19KB	0.18KB
types (mobile.js)	5.00KB	2.39KB
types (navigation.js)	0.20KB	0.18KB
types (objectql.js)	0.20KB	0.18KB
types (overlay.js)	0.20KB	0.18KB
types (permissions.js)	2.52KB	1.31KB
types (plugin-scope.js)	0.20KB	0.18KB
types (record-components.js)	0.20KB	0.19KB
types (record-semantics.js)	1.28KB	0.67KB
types (registry.js)	0.20KB	0.18KB
types (reports.js)	0.20KB	0.18KB
types (select-option.js)	0.20KB	0.19KB
types (spec-report.js)	5.05KB	1.93KB
types (spec-ui-namespace.js)	0.20KB	0.19KB
types (strict-authoring-face.js)	17.15KB	6.32KB
types (system-fields.js)	3.33KB	1.54KB
types (theme.js)	6.27KB	2.87KB
types (ui-action.js)	8.11KB	3.32KB
types (views.js)	0.20KB	0.18KB
types (widget.js)	0.20KB	0.18KB

Size Limits

• ✅ Core packages should be < 50KB gzipped
• ✅ Component packages should be < 100KB gzipped
• ⚠️ Plugin packages should be < 150KB gzipped

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: dd37e35d221ed7b229005d35f67e8229ee025844

A narrow re-review of the patch-round-2 delta e4bce25b8..dd37e35d2 (one commit, 6 files, +15 / −15) against the FAIL record 5861306588 and the ruling amendment 5861311219. It was run in-seat: the delta is prose, one test anchor, and one runtime string pair. Everything the record found sound stands: the census, the 32 shas, the mapping sample, the C4 proof, the 47 frontmatters and semver.

① Derived judgments

• Fix 1 (Row-predicate deprecation is missing its Phase 0: docs and example apps may still teach the bare shorthand / data.* spellings the new warning now flags #5738): applied verbatim at all three sites.
  • The conditionScope.ts file docblock and .changeset/7727-conditional-formatting-record-scope.md read "(stand-down 3 on the corpus-sweep card behind 702c48a62)".
  • The sharing_rule doc of CONDITION_SCOPE_BY_METADATA_TYPE reads "a stand-down 3 surface of the corpus-sweep card behind 702c48a62, the same as permission".
  • The sha now only locates the card; it no longer claims to carry the finding. rowPredicateCanon.ts's recipe site is unchanged, as the record found it correct.
• Fix 2 (the runtime-strings changeset, sentence 2): applied. It reads "so no dead pointer becomes a commit: tombstones cite ADR-0049 in its place, and every other pointer is simply dropped". This is true at head for all four tombstones (see the amendment below). The dropped "ONE" in "Each tombstone's guidance" is a correct accuracy repair: aria's error and describe are two hand-spelled strings.
• Amendment 5861311219: applied.
  • DashboardConfigSchema.aria's z.never({ error }) string and its .describe() string both open RETIRED (ADR-0049) —. The text after each dash is byte-unchanged.
  • The dashboard-config.test.ts anchor is /^RETIRED \(ADR-0049\) — /, and the "delete the key" remedy anchor survives.
  • The changeset lists all four tombstones under the one spelling, and the process clause about the TypeScript twin is gone.
  • A whole-tree grep for either aria opening finds only the source line.
• Optional nit: taken. The sweep changeset's list now ends "or a live successor, and where nothing answers they name the card by role".
• Frontmatter: byte-identical at e4bce25b8 and dd37e35d2 for the three changesets this round touches.
• Census: the printed instrument (the 32 numbers plus Bind record into node-level visibleWhen, and stop visible swallowing it #5505 and docs(plugin-form): Phase 0 of the row-predicate deprecation — stop teaching the bare shorthand (#5738) #5758) reads 0 at dd37e35d2.

② Semver level

Unchanged: patch for @object-ui/types and @object-ui/app-shell, and an empty frontmatter for the comment sweep. Clause-②: no. Nothing is major.

③ Boundary flags

• The branch is 0 behind main fab627ff9, and the dev reports git merge-tree clean.
• Open PRs touching a round-2 file: none.
• Commit trailers are model-free (1 commit).
• CI on dd37e35d2: in progress at the time of this record. The landing waits for all of it to be final green.

Implemented-by: claude/issue-10803-dead-citations-third-batch
Reviewed-by: session_014mXUNuFomfj24w7s1pZzhN

VERDICT: PASS