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

[objectstack-fleet]

Part of #10803
Clause-②: no

Dispatched implementation of the domain:ui seat 2 claim (comment 5861571015) on objectui#10803, batch 4, session https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN. 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: the legacy ActionSchema onSuccess / onFailure tombstone guidance strings open RETIRED (ADR-0049) — (ruling 5861129870 as amended by 5861311219), and two DataTableSchema zod .describe() strings drop their pointer (amendment 5860244997, Q1 = A), all in @object-ui/types. The one test that pins the tombstone strings verbatim follows them, and nothing else in it moves.

Patch round 1 answers contract review 5861897723 (FAIL on d21aeb0f6) under seat ruling 5861900779 (route a: tests that pin changed comment text follow it, anchor only). Test (shard 6/8) was red on layout-default-jsdoc-7361, whose TextSchema.variant pin anchored on 6942. The round does four things:

• Three comment-text anchors follow the re-pointed text: the one in layout-default-jsdoc-7361 and two in cellClassNameCensusProse-6921.
• The MarkdownSchema docblock stops crediting 8063bcbdc with retirements it never touched (Special cases 9).
• The 7004-cli-root-path-line.md remnant "(the mechanical half)" goes.
• main (de1b879a6) is merged in by a merge commit (ae0b81089), with no rebase and no force-push.

The round's anchor sweep (Special cases 10) shows those three pins are the only anchors on changed text.

Why Part of, not a closing line

The card stays open for the other 53 numbers of the family remainder (seat amendment 5860244997, Q2 = A), listed in Acceptance notes 1, and for the bare-number 404s the C0 census below found.

Premise, re-measured

• REST GET /repos/objectstack-ai/objectui/issues/N for each of the 30: all 30 answer 404, and a second read of each answers 404 again (30 of 30). GET .../pulls/N answers 404 for all 30 too. Lit controls: objectui#10533 and objectui#7714 answer 200. No number was dropped from the batch.
• The same 30 in objectstack all answer 200, with subjects unrelated to the objectui sentences (for example objectstack#6882 is an examples/app-todo trigger finding, while the objectui sentences are about DataTableSchema.renderCellEditor). Two exceptions were read, not guessed:
  • objectstack#6888 already appears on 5 in-scope lines (i18n.ts, ActionDefaultInspector.tsx, ActionPreview.tsx, block-config.ts, action-bar.tsx), each about the global_nav retirement, which is objectstack#6888's own subject. They are live sister citations, untouched.
  • UnpublishedAppBar.tsx wrote "framework PR TextSchema.variant is a nine-value enum that the ui:text renderer never reads — declared-but-unenforced, and it refuses 5 catalog entries #6942" bare. objectstack#6942 is the pull request "the ADR-0045 publish gate gets its own machine-managed key — app.hidden goes back to meaning navigation", exactly the _unpublished / hidden split that heading describes. It is re-qualified to objectstack#6942 (Zone 1 item 5).
  • Every other site names an objectui card or pull request, confirmed by its landing commit below.
• Every edited changeset is pending: it is present in .changeset/ on main.
• Branch point: e32dae160. main was merged in at de1b879a6 in patch round 1 (merge commit ae0b81089). Not a shallow checkout.

C0: the bare-number census (measurement only; PR objectui#10869 Acceptance note 2)

The instrument, over the two in-scope classes at the branch point (a # not preceded by a word character, #, &, /, . or -, so objectui#N, objectstack#N, cloud#N, hotcrm#N and every other word#N are excluded, as is a #N inside a URL):

git grep -hoP '(?:^|(?<=[^\w#&/.\-]))#\d+(?![0-9A-Za-z_])' e32dae160 -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | sort -u | wc -l

• 1002 distinct bare numbers. That is over 600, so by the order's budget only the 980 at or below 10900 were read (replace the final wc -l with tr -d '#' | awk '$1+0 <= 10900' | wc -l to reproduce 980). The 22 above 10900 were NOT read.
• Each of the 980 was read once with REST GET .../issues/N: 955 answer 200 and 25 answer 404. Each of the 25 was read a second time and answered 404 again (25 of 25), and GET .../pulls/N answers 404 for all 25.
• Lit control on the same instrument: Studio: render the publish door's advisories — the key #4133 scoped out now exists on PublishMetaItemResponse #5026, fix(plugin-timeline): judge gantt dates by TYPE — string, finite number, or Date #6905 and [finding] CloudDeploymentConfig.environment 手写第三套环境拼写('development'|'staging'|'production'),与 spec 两个枚举均不吻合 #3720 are all in its output at the branch point. At this head none of the eight batch numbers it found bare remains.
• The 25, with site counts (lines / files, at the branch point):
  • This batch's own numbers (8), all fixed here: [Decision] Declare renderCellEditor and schema-level cellClassName on DataTableSchema? — the two live undeclared keys the #6459 census measured #6882 (5 / 2), fix(plugin-timeline): judge gantt dates by TYPE — string, finite number, or Date #6905 (7 / 2), 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 (5 / 1), TextSchema.variant is a nine-value enum that the ui:text renderer never reads — declared-but-unenforced, and it refuses 5 catalog entries #6942 (1 / 1, the objectstack pull request above, re-qualified), 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 (1 / 1), MetadataClient.publish and publishDraft disagree about the dispatcher envelope on the same publish route #6962 (1 / 1), finding(plugin-timeline): spellGanttDateValue's Array.isArray is the last non-total operation on the gantt date path — a revoked Proxy crashes it #7036 (8 / 1), finding(types): 18 schemas narrow inherited disabled to boolean while 0 narrow its twin visible — no ruling says which is intended #7087 (2 / 2). The printed census below already counts a bare #N for these.
  • Already on the family list (3), for their own batches: date has the same two-convention split datetime just had: data-table's date-only cell keeps a year that formatDate drops #7620 (2 / 2), types: the triggerIcon tombstone's rationale contradicts mobile.ts's own retire-vs-remove discriminator, and its tripwire comment overclaims #7678 (3 / 3), 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 (1 / 1).
  • New to the family (11), for later batches: [finding] CloudDeploymentConfig.environment 手写第三套环境拼写('development'|'staging'|'production'),与 spec 两个枚举均不吻合 #3720 (5 / 3), [cross-repo] Studio's designer save→publish loop should state ?package= on publish, now that the framework publish route accepts it #5420 (1 / 1), fix(plugin-charts): put the chart min-height floor on the element Recharts measures #5503 (1 / 1), Studio metadata forms: no errors before input, translated help text, and a publish button clear of the toast #5506 (1 / 1), feat(core,react): declare record.* the row-predicate canon and warn on the two deprecated spellings #5737 (4 / 4), R2 of the unused-code program (#4806): promote the unused-IMPORT subclass of no-unused-vars to error and clear the measured 114 sites #6467 (1 / 1), fix(types): one authority for ActionSchema and the Breadcrumb pair #6936 (1 / 1), feat(types): declare the 13 renderer-read keys that no shipped type declared #6945 (1 / 1), fix(dashboard): retire the dashboard-root title read on all five surfaces #7622 (1 / 1), fix(types): SchemaRegistry's kanban entry stops describing a component it cannot name #7662 (1 / 1), fix(types): ChartDataSeriesSchema declares the six series keys the renderer reads (objectui#7546) #7684 (2 / 2).
  • Not citations (3): #0 (257 / 187, the #0 of "AGENTS.md #0.1"), #000 (2 / 2) and #000000 (10 / 6), which are CSS colours.
• Folded here: none. No C0 404 outside this batch's 30 sits in a sentence this batch edits: none of the 11 new numbers, nor any of the other 53 family numbers, occurs in any hunk of this diff (3 lines of context).
• The 200 set is not a citation census: many bare numbers are decision-batch, summons or commandment numbers, or React error codes, that happen to name a live issue.

Census (the enumeration pin for this batch)

The instrument PR objectui#10854 printed and PR objectui#10869 reused, with this batch's 30 numbers substituted (REF = a commit or tree):

git grep -nE '(objectui#|#|issues/)(6872|6879|6882|6887|6888|6889|6892|6905|6907|6921|6923|6924|6931|6940|6942|6958|6959|6962|6965|7004|7008|7023|7025|7036|7068|7069|7077|7079|7087|7088)([^0-9]|$)' REF -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | grep -v 'objectstack#' | wc -l

• REF = e32dae160 (branch point): 170 lines, 48 changeset lines in 38 files and 122 src lines in 45 files. REF = de1b879a6 (the main merged in): 170. REF = c6678b1bd (main at the round's final read): 170.
• REF = ae0b81089 (this head, de1b879a6 merged in): 0. Round 0's head d21aeb0f6 also read 0.
• This head merged with a fresh main (c6678b1bd, git merge-tree --write-tree, clean, tree e109a3bd0): 0.
• The instrument's blind spot, as batch 3 measured it. Its grep -v 'objectstack#' drops a whole line that also names an objectstack number. Three in-scope lines were hidden that way, each naming objectui#6965 beside objectstack#9343: in 10039-publish-drafts-advisories.md, 6965-batch-publish-advisories.md and render-publish-advisory-findings-5026.md. They are re-pointed here too, so the batch's true base population is 173 lines (51 changeset lines in 40 files, 122 src lines in 45 files). Without the filter the instrument reads 178 at the branch point and 7 at this head, all live: the five objectstack#6888 lines, objectstack#6942 in UnpublishedAppBar.tsx, and the same spelling in the new sweep changeset.
• Other spellings at this head: a search for the 30 numbers with no # finds only filenames (action-callback-retired-7068.test.ts, data-table-declared-keys-6882.test.ts and the like) and two SVG path coordinates. Hex-colour false positives (a number followed by a hex letter) at the branch point: 0.
• Lit control, the same printed instrument over live objectui#7714 at this head: 17 lines.
• Out of scope, as it stands (the instrument with the 30 numbers, unfiltered, whole tree at this head): 226 test lines in 96 files (scripts/__tests__ included), 22 scripts lines in 5 files, 0 .github, 0 governed, and 18 other lines in 10 files: published CHANGELOG.md history, three content/docs lines, and four lines of the private @object-ui/test-support README. See Acceptance notes 3.

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 / docs: cite landing commits where pending changesets and source comments name 32 objectui issues that answer 404 (objectui#10803, batch 3) #10869. All 24 distinct shas below are ancestors of main: git merge-base --is-ancestor, exit 0 each. Control leg in the same checkout: the head of PR objectui#10714 (d2afdb6bf) answers exit 1, and a known ancestor, 5f789538d, answers exit 0. 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 (Special cases 5).
• Where the sentence rests on a RULING, the ruling is cited by its date, next to the sha that carried it out where one exists (Special cases 4).
• Where a dead card sits beside a live pull request that IS its landing, the dead card is dropped and the live pointer stays (Special cases 1), as batch 3 dropped the dead predecessor in "(objectui#5401 → Component-level visibleWhen binds no record on record pages — every record.* predicate fails soft to permanently visible, on every block #5454)".
• Where the claim lived only on the dead card (a finding, a triage, a deferral, a quoted ruling), the sha only locates the card: "the card behind SHA" (Special cases 3). This is review 5861306588's lesson: a sha must carry what the sentence cites it for.
• Where nothing answers, the pointer is dropped and the sentence names the card by role (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 only).
• Runtime text carries no sha: see Special cases 7.

Mapping (number to resolution)

Lines / files are the branch-point census for that number (a line naming two batch numbers counts for each, and the three hidden #6965 lines are included). "Method" is how the landing was found. The last column is why that commit carries what the sentence cites it for.

dead number	resolution	method	lines / files	why the commit carries it
#6872	own-card pointer dropped (landing d9a0490b7)	changeset's adding commit	1 / 1	the only site is the #6872 changeset's own pointer
#6879	3619792bf	changeset's adding commit, git log --grep	1 / 1	it curates box into PUBLIC_BLOCKS, the list the comment sits in
#6882	bf97b98c8	changeset's adding commit	20 / 7	it declares renderCellEditor and schema-level cellClassName on DataTableSchema, adds the Equal exact-shape pin, and corrects cellClassName's reach to the three utility cells
#6887	5c09cca27	changeset's adding commit	1 / 1	it derives metadata-viewer's option shape from the spec's SelectOption with the Omit the comment names
#6888	320374d2a	changeset's adding commit	9 / 7	it keys LocationField's residue refusal and the two coordinate nouns into the locale packs
#6889	f75810e7c	changeset's adding commit, git log -S	8 / 1	it parses a dropped-fields entry's fields and object instead of asserting them, the gate the comments describe
#6892	own-card pointers dropped (landings 8d40c18a7, 951fa8e0d)	changesets' adding commits	2 / 2	both sites are slice changesets' pointers to their own card
#6905 (a pull request)	85f6a6097	git log --grep: its squash subject ends "(#6905)"	8 / 2	it judges gantt dates by TYPE before new Date, the "#6781 type rule" the sentences name
#6907	7fc5c3c12	changeset's adding commit, git log -S	7 / 2	it spells a refused gantt date by a rule, and its changeset records the measured throwing-getter crash
#6921	4eb665bcf	changeset's adding commit, git log --grep	2 / 2	it pins, in the rendered DOM, which body cells schema-level cellClassName reaches
#6923	d3bf4fa6f; "the 2026-08-31 ruling"	changeset's adding commit, git log --grep	5 / 4	it gives the wrapper-key list its build-free JSON home "per the 2026-08-31 ruling on objectui#6923"
#6924	78e98bf44; PR #7024 kept	changeset's adding commit, git log --grep	5 / 3	it adds the one enum-options walk for the top-level reader family
#6931	8063bcbdc	changeset's adding commit, git log -S	8 / 5	it converts the remaining eleven tombstones, confirm and the menu divider type included, to retirementTombstone(). At the MarkdownSchema site, which 8063bcbdc never touched (446d93d4e retired those keys), it is cited only as the commit that made that spelling uniform: see Special cases 9
#6940	pointers dropped (landing 0c386dd7f)	changeset's adding commit	2 / 2	the only sites are its own changeset's pointer and a .describe() string
#6942	57f9b077b; one site re-qualified to objectstack#6942	git log --grep; REST for the sister PR	6 / 4	it makes ui:text honour the published variant enum, with a node that omits the key left without a typography class
#6958	6a449fc49	changeset's adding commit	6 / 5	it clears a field its own visibleWhen hides
#6959	c0c436db8	changeset's adding commit	2 / 1	it keeps the find-call gate and adds a second one, and records the trap that a mock call is one resolution ahead of its value
#6962	7b433197d	changeset's adding commit	3 / 2	it removes publishDraft's envelope unwrap after measuring the route at the producer
#6965	ce986aafc; PR objectui#10038 kept at three sites	changeset's adding commit, git log --grep; its body names the card it settles	21 / 9	it routes "publish whole app" through the advisory seam, adds publishPackageDrafts, and writes the "Corrected before release" note
#7004	85b495795 (root Path line); a5d55472b (arm selection)	both changesets' adding commits	7 / 4	the first gives a root-level issue a Path line; the second prints the arm the document selected, per the 2026-09-02 ruling
#7008	f08bcd9af	changeset's adding commit	15 / 11	it makes FieldEditWidget deliver the declared NON-DOM block through toHostProps, and corrects RequiredFieldsDialog
#7023	nothing answers: the card named by role	git log --grep finds only d88e20f55, the #4895 retirement it dissolved into	1 / 1	see Special cases 3
#7025	own-card pointer dropped (landing 14884620e)	changeset's adding commit	1 / 1	the only site is its own changeset's pointer
#7036	869b876c8	git log -S on the timeline renderer	11 / 1	it scopes the speller's totality claim, and refuses a catch because it would substitute an object for a failure
#7068	6bca0e4e8; runtime text RETIRED (ADR-0049) —	changeset's adding commit	8 / 3	it retires the callback pair as ADR-0049 tombstones and deletes ActionCallback / ActionCallbackSchema
#7069	2760075ff	changeset's adding commit	3 / 3	it adds the fifth parity ledger that watches the mirror-wider-than-declared direction
#7077	own-card pointer dropped (landing 00d3f09c5)	changeset's adding commit	1 / 1	the only site is its own changeset's pointer
#7079	own-card pointer dropped (landing ab7dc31ce)	changeset's adding commit	1 / 1	the only site is its own changeset's pointer
#7087	c93b4d5f3	changeset's adding commit	8 / 6	it drops the 18 disabled?: boolean narrowings, adds the twin-symmetry pin, and keeps the six independent boolean declarations
#7088	c1fe272ad	changeset's adding commit	4 / 3	it corrects BaseSchema.hidden's JSDoc to the single hide path and records the synonymy

Special cases (the judgement calls)

1. A dead card beside its own live landing.
   • "objectui#6965 / PR objectui#10038" (AiChatPage.tsx, PendingDraftsBar.tsx, StudioDesignSurface.tsx) becomes "PR objectui#10038". PR objectui#10038 answers 200 and is the landing of ce986aafc, so the dead half goes and the live half stays.
   • 7025-nonoptional-enum-cast.md: "the same walk objectui#6924 converged the optional-cast family onto in PR test(test-support): one enum-options walk for the top-level reader family (#6924) #7024" becomes "the same walk PR test(test-support): one enum-options walk for the top-level reader family (#6924) #7024 converged the optional-cast family onto". PR test(test-support): one enum-options walk for the top-level reader family (#6924) #7024 answers 200 and is 78e98bf44's pull request.
2. The sister-repo number. In UnpublishedAppBar.tsx, "(objectstack#4829 A1, framework PR TextSchema.variant is a nine-value enum that the ui:text renderer never reads — declared-but-unenforced, and it refuses 5 catalog entries #6942)" becomes "(objectstack#4829 A1, framework PR objectstack#6942)". See Premise.
3. The card named by role.
   • 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, in 4895-retire-block-schema-family.md: "and objectui#7023 — the narrower validator-only fix — dissolves into this retirement" becomes "and the separate card for the narrower validator-only fix dissolves into this retirement". That card never landed on its own.
   • "The card behind SHA", where the sentence rests on something that lived only on the card:
     • 6755-field-diagnostics-i18n.md: "objectui#6888 carries it" becomes "The card behind 320374d2a carries it". Carrying a pending item is the card's act.
     • data-objectstack index.ts: "Unlike objectui#6889's exotic case" becomes "Unlike the exotic case on the card behind f75810e7c". The exotic case is not in the commit.
     • toHostProps.ts: "the specific mistake objectui#7008's ruling fences off" becomes "the specific mistake the ruling on the card behind f08bcd9af fences off". The quoted ruling text is the card's, not the commit's.
     • zod-wrapper-keys.ts: "the wall objectui#6923 was filed to get a ruling on" becomes "the wall the card behind d3bf4fa6f was filed to get a ruling on".
     • base.zod.ts: "objectui#7069 called this repo's systematic producer" becomes "the card behind 2760075ff called this repo's systematic producer". The commit's own diff attributes that phrase to the card.
     • The timeline renderer names finding(plugin-timeline): spellGanttDateValue's Array.isArray is the last non-total operation on the gantt date path — a revoked Proxy crashes it #7036's deferral, triage and "1 of 6" trade. These become "the file surface the card behind 869b876c8 deferred", "the triage of the card behind 869b876c8" and "the card behind 869b876c8 was stopped from making". None of the three is in the commit.
4. Rulings by date.
   • union-arm-diagnostics.ts: "the 2026-09-02 ruling on objectui#7004 asks for" becomes "the 2026-09-02 ruling a5d55472b implements asks for".
   • validate.ts: "The ARM-SELECTION half of objectui#7004 landed on the 2026-09-02 maintainer ruling" becomes "The ARM-SELECTION half (a5d55472b) landed on the 2026-09-02 maintainer ruling".
   • 7201-schema-slot-census-gate.md: "across objectui#6882, the ruling that expired both holds" becomes "across the 2026-08-30 ruling that expired both holds (bf97b98c8)".
   • 7687-combobox-option-disabled.md: "by the objectui#7087 twin-symmetry ruling" becomes "by the 2026-09-01 twin-symmetry ruling, c93b4d5f3".
   • defaults-table-scan.ts: "the one objectui#6923 already ruled for exactly that wall" becomes "the one the 2026-08-31 ruling (d3bf4fa6f) already set for exactly that wall".
5. Own-card pointers that needed a word.
   • 6931-tombstone-guidance-remainder.md and 6888-location-residue-refusal-keyed.md: the pointer sat on its own line, so the period moved up with it.
   • 7087-disabled-twin-symmetry.md: the parenthesis opened on the dead card, so the line break moved with it.
   • 7004-cli-root-path-line.md: "(objectui#7004, mechanical half)" is dropped, so the sentence ends "sits at the document root." (patch round 1 took the review's nit), and "left open on objectui#7004 for a maintainer ruling" becomes "left open for a maintainer ruling".
   • shared-zod-wrapper-keys-6923.md: "objectui#6923: the Zod wrapper-key list" becomes "The Zod wrapper-key list".
   • vi-mock-inherit-slice2.md and slice3.md: "(objectui#6892 slice 2)" becomes "(slice 2)", and likewise for slice 3.
6. The totality sequence in the timeline renderer. "(finding(plugin-timeline): two more unusable gantt date ranges — a malformed date still throws, and an inverted author-pinned range silently draws a negative-width bar on no axis #6759 -> 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(plugin-timeline): a slot-less Date impostor passes the gantt type gate and then crashes new Date mid-render #7027)" becomes "(finding(plugin-timeline): two more unusable gantt date ranges — a malformed date still throws, and an inverted author-pinned range silently draws a negative-width bar on no axis #6759 -> 85f6a6097 -> 7fc5c3c12 -> finding(plugin-timeline): a slot-less Date impostor passes the gantt type gate and then crashes new Date mid-render #7027)", and likewise with "-> finding(plugin-timeline): spellGanttDateValue's Array.isArray is the last non-total operation on the gantt date path — a revoked Proxy crashes it #7036" as 869b876c8. finding(plugin-timeline): two more unusable gantt date ranges — a malformed date still throws, and an inverted author-pinned range silently draws a negative-width bar on no axis #6759 and finding(plugin-timeline): a slot-less Date impostor passes the gantt type gate and then crashes new Date mid-render #7027 answer 200 and stay. fix(plugin-timeline): judge gantt dates by TYPE — string, finite number, or Date #6905 was the pull request whose squash is 85f6a6097. "⚠️ objectui#7036 — READ THE TWO PARAGRAPHS" becomes "⚠️ 869b876c8 — READ…", and the "see the objectui#7036 note below" that points at it follows.
7. The runtime strings. Only the listed text moves in each.

file	member	before	after
types/src/zod/crud.zod.ts	ActionSchema.onSuccess (tombstone)	"RETIRED (objectui#7068) — onSuccess is no longer part of this legacy ActionSchema; ..."	"RETIRED (ADR-0049) — onSuccess is no longer part of this legacy ActionSchema; ..."
types/src/zod/crud.zod.ts	ActionSchema.onFailure (tombstone)	"RETIRED (objectui#7068) — onFailure is no longer part of this legacy ActionSchema; ..."	"RETIRED (ADR-0049) — onFailure is no longer part of this legacy ActionSchema; ..."
types/src/zod/data-display.zod.ts	DataTableSchema.rowActions .describe()	"... mirrors the boolean the renderer truthiness-tests (objectui#6940)"	"... mirrors the boolean the renderer truthiness-tests"
types/src/zod/data-display.zod.ts	DataTableSchema.cellClassName .describe()	"... so row density has to be set on both (objectui#6882)"	"... so row density has to be set on both"

The ADR-0049 condition, measured from the retirement itself (Zone 1 item 4):

• the zod comment above the two keys opens "ADR-0049 RETIREMENT TOMBSTONES";
• its landing commit 6bca0e4e8 writes them as tombstones, not deletions, and adds the pending action-callback-retired-7068.md, which says "ADR-0049 enforce-or-remove";
• each string already ends "Retired under ADR-0049 enforce-or-remove".

Both open RETIRED (ADR-0049) —. Their TypeScript twins in crud.ts read "RETIRED (6bca0e4e8, ADR-0049 enforce-or-remove)", the batch 3 twin form.
8. What follows the strings, and nothing else in it. action-callback-retired-7068.test.ts pins both guidance strings as full literals (ON_SUCCESS_GUIDANCE, ON_FAILURE_GUIDANCE), and their openings follow. Its test names and four @ts-expect-error comments still read "RETIRED (objectui#7068)". They describe the ?: never TypeScript face, quote no runtime string, and are out of the card's classes (Acceptance notes 3). No test, doc or changeset quotes either .describe() string: a whole-tree search for each old string returns only the source line.

• Patch round 1: three pins quoted re-pointed COMMENT text, and they follow it, anchor only (ruling 5861900779, route a).
  • layout-default-jsdoc-7361.test.ts: toContain('6942') becomes toContain('57f9b077b') (the TextSchema.variant docblock).
  • cellClassNameCensusProse-6921.test.ts: toMatch(/objectui#6882|#6882/) becomes toMatch(/bf97b98c8/) (the cellClassName census entry).
  • The same file: toMatch(/REDUNDANT since objectui#6882/) becomes a match on "REDUNDANT since bf97b98c8" (the holds-member docblock).
  • Their titles, messages and comments stay as they are.

9. The MarkdownSchema docblock (patch round 1, review 5861897723). Round 0 wrote "Both refuse BY NAME through retirementTombstone() (8063bcbdc), with the remedy in the message". 8063bcbdc never touched MarkdownSchema; 446d93d4e retired sanitize / components. So the sha did not carry what it was cited for, 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 class. It now reads "through retirementTombstone(), the spelling 8063bcbdc made uniform, with the remedy in the message". That commit's own subject says the remaining tombstones carry their remediation text. The edit is a comment, and the file's C4 print is unchanged by it.
10. The anchor sweep that closes the gap (patch round 1).

• Instrument: every string, template, numeric and regex literal in all 3814 test and script files under packages/ and scripts/, enumerated with git ls-tree at this head and parsed with TypeScript.
• Test applied to each literal: does its occurrence count DROP between main and this head in any of the 90 files this PR changes? Raw text and a comment-flattened form are both checked.
• Specific anchors found (a batch number, a changed phrase, or a pattern keyed to them), after reading every hit against the file it sits in:
  • the three pins above;
  • tombstone-discriminator-agreement-9684's /RETIRED (objectui#/ note search, which reads only mobile.ts and is untouched by this PR.
• Everything else: generic tokens (whitespace, punctuation, objectui# spellings in ledger checks over the tests' own data, digit and letter classes), none of them an assertion over text this PR changed.
• Round 0's quote search covered runtime strings only. That is the gap this sweep closes.

Held

By the serial rule: nothing. Round 0's list: objectui#10873, #10871, #10870, #10852, #10821, #10780, #10777, #10714, #10278 and #5400. Since then #10873, #10871, #10870 and #10821 have merged. #10870 touched base.zod.ts in a region apart from this PR's line, and the merge with it is clean.

• Re-read before the round-1 push: 11 open. Besides this PR they are objectui#10880, fix(types,components,docs): correct the texts objectui#6771 left false about body (objectui#8284) #10879, feat(plugin-grid): server-side grid grouping — group headers from the query, rows paged per group (objectui#7189) #10878, refactor(fields): the record picker calls core's withoutDeniedFields, the last copy of the field-read rule (objectui#10594) #10876, docs(skills,console): record why the seven sectioning tags stay off the curated tier; retract the section row (objectui#8775) #10852, docs(skills): the plugin guide's tombstone comment lists the serializer key list with of (objectui#10337) #10780, fix(app-shell): PageView refreshes a page action’s data in place on the invalidation bus instead of remounting the page (objectui#10519) #10777, feat(components,types)!: a list item and a tabs item draw content only, and both item faces refuse body by name (objectui#9590) #10714, feat(plugin-grid): one display page size read from the spec, and a distinct fetch batch (objectui#9853) #10278 and the release PR chore: release packages #5400.
• Four of them hold files this PR edits:
  • objectui#10879: types/src/zod/data-display.zod.ts;
  • objectui#10878: data-objectstack/src/index.ts and plugin-grid/src/ObjectGrid.tsx;
  • objectui#10714: types/src/data-display.ts, types/src/layout.ts and types/src/zod/data-display.zod.ts;
  • objectui#10278: plugin-grid/src/ObjectGrid.tsx.
• Each one's hunks were read against its merge-base, with 3 lines of context. None of the 29 lines this PR changes in those files appears inside or beside any of their hunks.
• Trial merges of each open PR head with this head (git merge-tree --write-tree) are clean for fix(app-shell): the admin previews and the CEL lint advisories read the designer locale (objectui#10862, slice 2) #10880, fix(types,components,docs): correct the texts objectui#6771 left false about body (objectui#8284) #10879, feat(plugin-grid): server-side grid grouping — group headers from the query, rows paged per group (objectui#7189) #10878, refactor(fields): the record picker calls core's withoutDeniedFields, the last copy of the field-read rule (objectui#10594) #10876, docs(skills,console): record why the seven sectioning tags stay off the curated tier; retract the section row (objectui#8775) #10852, docs(skills): the plugin guide's tombstone comment lists the serializer key list with of (objectui#10337) #10780, fix(app-shell): PageView refreshes a page action’s data in place on the invalidation bus instead of remounting the page (objectui#10519) #10777 and feat(components,types)!: a list item and a tabs item draw content only, and both item faces refuse body by name (objectui#9590) #10714.
• feat(plugin-grid): one display page size read from the spec, and a distinct fetch batch (objectui#9853) #10278 (eab4c8e52) conflicts in ObjectGrid.tsx, but it conflicts identically against main alone: one conflict hunk in its own page-size region either way.
• PR chore: release packages #5400 (Version Packages) regenerates and is not a hold.

Changesets

• .changeset/10803-dead-citation-sweep-fourth-batch.md, EMPTY frontmatter: the comment-only edits in 12 released packages and the private @object-ui/test-support. No published behaviour changes through them. It points at the second file for the runtime text.
• .changeset/10803-fourth-batch-runtime-strings.md, '@object-ui/types': patch: the two tombstones open RETIRED (ADR-0049) — with everything after the dash unchanged, and the two describe strings lose their pointer. No key, path, issue code, accept set, refusal or severity moves.

Proof of prose-only (C4), against the merged main de1b879a6

• Source. Each of the 48 touched .ts / .tsx files was parsed at de1b879a6 and at this head with TypeScript 6.0.3's createSourceFile and re-printed by createPrinter({ removeComments: true }). The 48 are the 45 non-test sources and three tests: the one pinning the strings, and the two whose comment-text anchors follow.
  • 43 of 48 prints are identical. That includes all 45 non-test sources except crud.zod.ts and data-display.zod.ts, whose MarkdownSchema comment edit moves nothing.
  • The other 5 are equal once exactly the 9 listed substitutions are applied to the main print, each matched once:
    • crud.zod.ts: the two tombstone strings;
    • data-display.zod.ts: the two describe-string deletions;
    • action-callback-retired-7068.test.ts: the same two tombstone strings;
    • layout-default-jsdoc-7361.test.ts: the one anchor;
    • cellClassNameCensusProse-6921.test.ts: the two anchors.
  • 0 parse diagnostics.
  • Lit controls on the same instrument: dropping "(ADR-0049)" from the onSuccess string moves the print; re-spacing the "ADR-0049 RETIREMENT TOMBSTONES" comment does not.
• Changesets. The frontmatter block of every one of the 40 edited changesets is byte-identical at de1b879a6 and this head (40 of 40, by md5). The overwrite gate below agrees.
• Scope of the diff against the merged main: 90 files, +227 / −184: 40 edited and 2 new changesets, 45 non-test source files, and 3 tests.

Gates, on this head ae0b81089

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

• node scripts/check-changeset-presence.mjs, exit 0: "44 source file(s) of 12 released package(s) changed, and this change declares 2 changeset(s): .changeset/10803-dead-citation-sweep-fourth-batch.md, .changeset/10803-fourth-batch-runtime-strings.md." (44 = the 41 released sources and the 3 tests under released packages' src/; the four test-support files sit under a package changesets ignores.)
• 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, 40 modified, 0 deleted". declared at base equals declares now for 40 of 40.
• pnpm check:changeset-claims (report-only), exit 0:
  • born-false: "Every one of those 1 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 30 body(ies) is either not negated in its own prose, or negated only in an ASPECT of it that may legitimately hold still";
  • the standing notice "83 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. No pending changeset quotes either tombstone string or either describe string; the one textual hit, "truthiness-tests" in 6940-rowactions-boolean-mirror.md, is prose, not a quote.
• pnpm check:control-bytes, exit 0: "check-control-bytes: OK (scanned 9125 tracked text file(s); skipped 85 binary)."
• pnpm check:new-line-citations, exit 0: "VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0".
• Also run: the governed-surface predicate over the 90 paths, exit 0: "NOT GOVERNED — 90 path(s) checked against 5 governed surface(s); none matched." (lit control AGENTS.md: exit 3).

Tests, through the shared verify lock.

• Red, reproduced first.
  • layout-default-jsdoc-7361 on d21aeb0f6 itself gives VERDICT command-exit 1, Tests 1 failed | 74 passed (75): "expected '/**\n * Text variant/style. …' to contain '6942'".
  • cellClassNameCensusProse-6921: its d21aeb0f6 copy was checked out over this tree and run. ObjectGrid.tsx and the census changesets it reads are identical at d21aeb0f6 and here. Result: Tests 2 failed | 3 passed (5), on /objectui#6882|#6882/ and /REDUNDANT since objectui#6882/. The file was then restored with git checkout HEAD --, checked by blob hash against HEAD, and git diff HEAD came back empty.
• Green, on this head ae0b81089: layout-default-jsdoc-7361, cellClassNameCensusProse-6921, action-callback-retired-7068, data-table-declared-keys-6882, tombstone-discriminator-agreement-9684 and zod-mirror-parity give Test Files 6 passed (6), Tests 181 passed (181).
  • The run was the last part of the locked batch, so its exit is the one the lock's VERDICT batch-last-exit 0 reports.

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 43 of the 48 touched files is identical to main, and the other 5 differ only by the listed literal edits. Every test that anchors on a changed string or comment was found by the anchor sweep (Special cases 10) and run above. CI runs the full farm.

Acceptance notes

1. The remainder rides this card, unchanged (seat amendment 5860244997, Q2 = A). Of the 83 numbers PR objectui#10869's Acceptance notes item 1 lists, this PR carries the first 30 in ascending order. The other 53 are: 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 occurs in any hunk of this diff.
2. The C0 bare-number 404s, for later batches (sites at e32dae160, lines / files):
   • New to the family: [finding] CloudDeploymentConfig.environment 手写第三套环境拼写('development'|'staging'|'production'),与 spec 两个枚举均不吻合 #3720 (5 / 3), [cross-repo] Studio's designer save→publish loop should state ?package= on publish, now that the framework publish route accepts it #5420 (1 / 1), fix(plugin-charts): put the chart min-height floor on the element Recharts measures #5503 (1 / 1), Studio metadata forms: no errors before input, translated help text, and a publish button clear of the toast #5506 (1 / 1), feat(core,react): declare record.* the row-predicate canon and warn on the two deprecated spellings #5737 (4 / 4), R2 of the unused-code program (#4806): promote the unused-IMPORT subclass of no-unused-vars to error and clear the measured 114 sites #6467 (1 / 1), fix(types): one authority for ActionSchema and the Breadcrumb pair #6936 (1 / 1), feat(types): declare the 13 renderer-read keys that no shipped type declared #6945 (1 / 1), fix(dashboard): retire the dashboard-root title read on all five surfaces #7622 (1 / 1), fix(types): SchemaRegistry's kanban entry stops describing a component it cannot name #7662 (1 / 1), fix(types): ChartDataSeriesSchema declares the six series keys the renderer reads (objectui#7546) #7684 (2 / 2).
     • feat(core,react): declare record.* the row-predicate canon and warn on the two deprecated spellings #5737, feat(types): declare the 13 renderer-read keys that no shipped type declared #6945, fix(dashboard): retire the dashboard-root title read on all five surfaces #7622, fix(types): SchemaRegistry's kanban entry stops describing a component it cannot name #7662 and fix(types): ChartDataSeriesSchema declares the six series keys the renderer reads (objectui#7546) #7684 are written "PR #N". A later batch can look for each one's squash commit, as batch 3 did for 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.
     • The [finding] CloudDeploymentConfig.environment 手写第三套环境拼写('development'|'staging'|'production'),与 spec 两个枚举均不吻合 #3720 sites are in ObjectGrid.tsx, rowCrudAffordances.ts and ListView.tsx. ObjectGrid.tsx is also held by open PR objectui#10278.
   • Already on the family list: date has the same two-convention split datetime just had: data-table's date-only cell keeps a year that formatDate drops #7620, types: the triggerIcon tombstone's rationale contradicts mobile.ts's own retire-vs-remove discriminator, and its tripwire comment overclaims #7678 and 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. They have bare sites too, which the printed instrument counts.
   • Not read: the 22 distinct bare numbers above 10900 (budget). Nothing here re-derives whether any of them is dead.
3. Published or shipped text outside the two in-scope classes still names some of these numbers. It is untouched by scope, as another class the triage split did not scope here:
   • content/docs: enhanced-actions.mdx and schema-overview.md say the callbacks were "RETIRED (objectui#7068)" in prose, not as verbatim quotes of the runtime string; plugin-form.mdx names objectui#6958.
   • The private @object-ui/test-support README names objectui#6923 and 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.
   • Published CHANGELOG.md history, which is never re-addressed. It includes a bare "framework PR TextSchema.variant is a nine-value enum that the ui:text renderer never reads — declared-but-unenforced, and it refuses 5 catalog entries #6942" in @object-ui/app-shell's.
   • In tests: action-callback-retired-7068.test.ts's test names and four @ts-expect-error comments reading "RETIRED (objectui#7068)"; layout-default-jsdoc-7361.test.ts's header-table comment naming objectui#6942; and the test names and comments in cellClassNameCensusProse-6921.test.ts that name [Decision] Declare renderCellEditor and schema-level cellClassName on DataTableSchema? — the two live undeclared keys the #6459 census measured #6882. Only anchors moved (ruling 5861900779).
   • Carrier: none.
4. Filenames are not citations. Pending changeset and test 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, docs: cite landing commits where pending changesets and source comments name fourteen objectui issues that answer 404 (objectui#10803) #10854 and docs: cite landing commits where pending changesets and source comments name 32 objectui issues that answer 404 (objectui#10803, batch 3) #10869.

---

Generated by Claude Code

[github-actions]

changeset-claim-re-read

⚠️ 83 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/10337-widget-input-serializer-key-list.md

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

  Clause 2 of the WidgetInput docblock said sdui-parser's manifest serializer forwards six keys per input and listed them without of. manifestFromConfigs has forwarded of since objectui#8067, so a reader of the published declaration learned that of is not published when it is. The clause now reads "a fixed key list per input, of included since objectui#8067" and lists all of them, the uncounted wording ComponentInput's own docblock in base.ts already uses. The clause's conclusion is unchanged: none of the five tombstoned ComponentInput keys is on that list. Comment only, with no type or runtime change.

.changeset/4730-retire-dead-locale-key-batch.md

• names ObjectGrid.tsx → packages/plugin-grid/src/ObjectGrid.tsx — edited by this change

  • Superseded twin vocabularies. cellRender.* and rowAction.* duplicated a grid.* vocabulary that won. RowActionMenu.tsx is fully i18n-wired and reads grid.openMenu / grid.edit / grid.delete; ObjectGrid.tsx reads grid.empty / grid.yes / grid.no / grid.systemFields. The twins had no reader on either side. - Labels that outlived their control. calendar.agenda labelled a view mode b55a34647 retired from CalendarViewMode (now 'month' | 'week' | 'day'). home.quickActions.createApp*, layout.systemNav.createApp, actionDialog.defaultActionTitle / .ok and grid.bulk.selectPlaceholder sit in namespaces whose consumers are live and wired but demonstrably read other siblings. - Surfaces that left the product. map.* is the strongest form: @object-ui/plugin-map declares no @object-ui/i18n dependency and contains no t() call at all, so it cannot consume a locale string. home.stats.* and recordDetail.viewersTooltip name surfaces nothing renders.

.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/5674-retire-plugin-component-input.md

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

  Migration. Replace PluginComponentInput with ComponentInput — they have named the identical declaration since objectui#4972 converged the plugin-scoped interface onto base.ts, so this is a rename with no shape change:

.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/5905-componentinput-inputtype-tombstone.md

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

  Stale wording corrected in the same pass, because this change falsifies it: base.ts and zod/base.zod.ts both said the fork was "recorded for a ruling; until then this stays a live, writable key", and widget.ts called it "the open fork". All three now record the ruling. A reader who greps the source instead of the card thread was meeting an open fork that no longer existed.

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

  Stale wording corrected in the same pass, because this change falsifies it: base.ts and zod/base.zod.ts both said the fork was "recorded for a ruling; until then this stays a live, writable key", and widget.ts called it "the open fork". All three now record the ruling. A reader who greps the source instead of the card thread was meeting an open fork that no longer existed.

.changeset/5905-componentinput-retire-constraint-keys.md

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

  The retirement kit: ?: never on the interface (packages/types/src/base.ts), so authoring one is a tsc error at the registration site; retirementTombstone() on the Zod mirror (packages/types/src/zod/base.zod.ts), so an authored value is REFUSED at parse time with code: 'invalid_type', the key named in the issue path, and the migration note as the message. Deleting the members outright was the option NOT taken: ComponentInputSchema is a non-strict z.object, which strips an undeclared key silently — one silent no-op traded for another. Pinned in packages/types/src/__tests__/component-input-retired-constraint-keys.test.ts.

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

  The retirement kit: ?: never on the interface (packages/types/src/base.ts), so authoring one is a tsc error at the registration site; retirementTombstone() on the Zod mirror (packages/types/src/zod/base.zod.ts), so an authored value is REFUSED at parse time with code: 'invalid_type', the key named in the issue path, and the migration note as the message. Deleting the members outright was the option NOT taken: ComponentInputSchema is a non-strict z.object, which strips an undeclared key silently — one silent no-op traded for another. Pinned in packages/types/src/__tests__/component-input-retired-constraint-keys.test.ts.

.changeset/5926-empty-action-visible-when.md

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

  emptyAction was the one authored-node exception in the tree. The empty-state CTA slot resolved the registry directly — ComponentRegistry.get(node.type) — and mounted the result itself, so the node never passed through SchemaRenderer and its visibleWhen was never evaluated. @objectstack/spec accepts the key (SchemaNodeSchema carries visibleWhen, and data-display.zod.ts types emptyAction as a SchemaNode), so an author wrote a gate, the platform took it, and nothing enforced it — declared-not-enforced, the same class c86185eb5 closed for record:alert, one level down.

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

  The fix is a route, not a new check: no visibleWhen test was added to data-table.tsx. A local check on this slot would have been a fourth evaluator, which is the drift page:tabs' item-level predicate already records on this card. The slot now mounts its authored node exactly the way the empty renderer's action slot always has.

.changeset/5928-classname-style-props-rename.md

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

  Why the name had to move. The const declares exactly two keys — className and style, the CSS passthrough attributes a node exposes. The TypeScript StyleProps (base.ts) is the Tailwind-SCALE vocabulary: padding, margin, gap, backgroundColor, textColor, borderWidth, borderColor, borderRadius. Measured on this branch's base with an AST read of both files: 2 keys against 8, sharing ZERO keys. In this package the …Schema suffix otherwise means "runtime mirror of the like-named declaration", so the shared name asserted a mirror relationship that does not exist — and building objectui#5684's parity registry by name pairing duly put the two together and reported drift on a pair that has no counterpart at all.

.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/6067-component-meta-derive-from-canonical.md

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

  packages/core/src/registry/Registry.ts declared its own ComponentMeta: thirteen keys, of which nine were restated from @object-ui/types' base.ts, four were registry-only (tier, namespace, skipFallback, labelling), and tags / description were absent — although both are declared on the canonical type and on the ComponentMetaSchema zod mirror. Two of the three authorities agreed and the registration surface did not, so those two keys were unwritable at exactly the declaration most component registrations import. That is the same two-key delta objectui#5893 had just closed inside @object-ui/types, arriving a third time on a third declaration, and objectui#5671 had already made the identical move for the sibling type ComponentInput in this very file.

.changeset/6150-undeclared-but-consumed-keys.md

• names renderers/basic/text.tsx → packages/components/src/renderers/basic/text.tsx — edited by this change

  | type | key | declared as | read at | |---|---|---|---| | TextSchema | content | string | renderers/basic/text.tsx — {schema.content \|\| schema.value} | | CarouselSchema | opts | RecordANGLE-BRACKETS(string, unknown) | complex/carousel.tsx — opts={schema.opts} | | CarouselSchema | orientation | 'horizontal' \| 'vertical' | complex/carousel.tsx | | CarouselSchema | itemClassName | string | complex/carousel.tsx — per-slide class | | FilterBuilderSchema | wrapperClass | string | complex/filter-builder.tsx | | TreeViewSchema | nodes | TreeNode[] | data-display/tree-view.tsx | | TreeViewSchema | title | string | data-display/tree-view.tsx | | TreeViewSchema | onNodeClick | (node: TreeNode) => void | data-display/tree-view.tsx — INVOKED | | CheckboxSchema | required | boolean | form/checkbox.tsx — drives the * marker | | FileUploadSchema | buttonText | string | form/file-upload.tsx | | FileUploadSchema | wrapperClass | string | form/file-upload.tsx | | HoverCardSchema | align | OverlayAlignment | overlay/hover-card.tsx | | ContextMenuSchema | trigger | SchemaNode \| SchemaNode[] | overlay/context-menu.tsx |

.changeset/6169-chatbot-authoring-face-type.md

• names packages/plugin-chatbot/src/renderer.tsx → packages/plugin-chatbot/src/renderer.tsx — edited by this change

  ChatbotSchema (@object-ui/types) now declares ten keys that previously existed ONLY inside an anonymous inline intersection local to packages/plugin-chatbot/src/renderer.tsx's chatbot registration, invisible to anything outside that one file:

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

  • showTimestamp, userAvatarUrl, userAvatarFallback, assistantAvatarUrl, assistantAvatarFallback, maxHeight — display fields. - autoResponse, autoResponseText, autoResponseDelay — the local auto-response (demo/playground) fields, already live via a real consumer (packages/app-shell/src/console/ai/AiChatPage.tsx). - onSend — the send-callback, now typed on the published authoring face rather than against the plugin's internal runtime message type. Its messages element is the authoring ChatMessage widened by the three runtime-only approval states a chat runtime hands back (objectui#10018).

.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/6349-types-internal-name-collisions-batch-1.md

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

  ActionSchema — renamed, because the two shapes are unrelated. crud.ts and ui-action.ts both declared it. Measured member-by-member they share 9 keys out of 28 each: crud.ts extends BaseSchema and pins type: 'action' (a UI node — a button in a component tree), ui-action.ts extends nothing and types type as ActionType (a spec-v2 action definition, with name, locations, params, target). Re-pointing either at the other would silently hand a consumer a different type, so this took the rename branch (objectui#5044 is the precedent for choosing the surviving name). ui-action.ts's declaration is now spelled UIActionSchema — the name src/index.ts has always PUBLISHED it under, via export type { ActionSchema as UIActionSchema }, which is now a plain re-export. The package's public surface is unchanged: ActionSchema still means crud.ts's legacy shape and UIActionSchema still means ui-action.ts's, exactly as before. Nothing outside ui-action.ts imported the old spelling — there is no ./ui-action subpath in exports, so the old name was never reachable from outside the package.

• 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 fieldRules.ts → packages/core/src/evaluator/fieldRules.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/6597-retire-fieldmeta-referenceto.md

• names plugin-grid/src/ObjectGrid.tsx → packages/plugin-grid/src/ObjectGrid.tsx — edited by this change

  No authoring story survived the search either. ObjectGrid's own relational-meta pass-through (applyRelationalMeta, plugin-grid/src/ObjectGrid.tsx) copies reference_to / reference / display_field / etc. from the SCHEMA field def only, at all three of its call sites — never from an authored column override. No doc, example, or fixture in this repo shows a table column pinning a lookup's target away from what its schema field already says. Under the maintainer's standing startup-stage rule (2026-08-27: deprecated/alias spellings retire immediately, no transition windows), no measured demand selects withdraw.

.changeset/6625-retire-fieldmeta-decimals.md

• names fields/src/index.tsx → packages/fields/src/index.tsx — edited by this change

  buildFieldMeta computed decimals: overrides.decimals ?? meta?.decimals ?? meta?.scale on every call and the value reached nothing. Re-measured on this branch's base (efdc6c62): zero .decimals member reads across @object-ui/fields, @object-ui/i18n, @object-ui/components, @object-ui/core and plugin-dashboard itself — the only non-comment occurrence was the write being removed here. The positive control in the same query shape fires: .scale member reads hit NumberField.tsx, GridField.tsx and fields/src/index.tsx. So the zero is a finding, not a broken query. The overrides.decimals ?? head of that chain had already lost its only feeder when objectui#6425's ruling removed the authored read from ObjectDataTable.enrich(); RecordDetailDrawer, the only other buildFieldMeta caller, passes no overrides at all. Both halves retire together, so the key leaves in one move.

.changeset/6661-app-launcher-nav-menu-renderers.md

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

  Three new strings — the launcher's and the menu's accessible names, and the menu's empty state — are declared under console.nav in en.ts and its nine sibling packs. An inline defaultValue alone is not a fix: it renders English at one call site and leaves the string untranslatable everywhere (objectui#3517).

.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/6687-chatbot-surface-authorable.md

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

  Measured on both declaration faces before the fix, each with a control that had to hit: schema.surface appeared 0 times in renderer.tsx against schema.placeholder at 3 (one per registration) and schema.processVisibility at 1; and ChatbotSchema (packages/types/src/complex.ts) declared 34 keys, not this one. Two faces agreeing is what made the zero a reading rather than a bad query.

.changeset/6694-dashboard-lookup-reference-meta.md

• names packages/fields/src/index.tsx → packages/fields/src/index.tsx — edited by this change

  ⚠️ The copy set is three keys where ObjectGrid's RELATIONAL_META_KEYS is nine, and the difference is measured per key, not preferred. The grid's cells are EDITABLE, so its extra keys drive the inline picker's query (LookupField / UserField read id_field, description_field, lookup_filters, lookupFilters); these two widgets are read-only and their render path ends at a cell renderer. packages/fields/src/index.tsx reads exactly reference_to, reference and display_field off a cell's field prop; titleFormat is never read off a field meta at all (its readers take it off the object schema, which arrives here through useRefObjectSchema(reference_to)), and reference_to_field has zero member reads anywhere in the repo. Copying the other six would mint six members written on every call and read by nothing — precisely what objectui#6625 (decimals) and objectui#6597 (referenceTo) retired from this same file.

.changeset/6783-readprops-degenerate-config-bag.md

• names metadata-viewer.tsx → packages/components/src/renderers/basic/metadata-viewer.tsx — edited by this change

  Five modules under packages/components/src/renderers/basic/ — elements.tsx, data-list.tsx, text-input.tsx, record-picker.tsx, metadata-viewer.tsx — each carried a copy of the same reader, { ...(schema?.props ?? {}), ...(schema?.properties ?? {}) }. ?? only replaces null/undefined, so a non-object bag went into the object spread and came back out as indexed keys: for properties: 'not-a-bag', the config bag a renderer received was { '0': 'n', '1': 'o', … '8': 'g' } — nine keys nobody authored. The five copies are now one readProps (renderers/basic/readProps.ts) that asks isConfigBag, and a degenerate bag on either side contributes no keys.

.changeset/6837-reference-to-arm-deletion.md

• names fields/src/index.tsx → packages/fields/src/index.tsx — edited by this change

  Three readers were deliberately left alone. LookupCellRenderer (fields/src/index.tsx), LookupField and UserField read FieldMetadata — ObjectUI's OWN contract, whose LookupFieldMetadata declares reference_to and never declares reference. They are fed by the emitters above and by published example schemas (examples/schema-catalog/src/schemas/fields-lookup/*.json), so narrowing them would break in-repo producers, and plugin-grid's relationalMetaCopySet.derivation.test.ts re-derives its read set from exactly those three sources — where reference_to is recorded with verdict adapter-stamped. DetailViewFieldSchema is likewise untouched.

.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 widgets/toDomProps.ts → packages/fields/src/widgets/toDomProps.ts — edited by this change

  Its props are FieldWidgetComponentProps — the controlled-input keys intersected with FieldWidgetDomProps, AriaAttributes and the open data- family — so a host could always pass id, name, autoFocus, tabIndex, onBlur, onFocus, onClick, any aria-* and any data-* with no type error. The body then destructured five keys and rendered the widget with those, so autoFocus was the ONLY survivor of the whole block and everything else was silently dropped. That is this package's own first-class defect class, named in widgets/toDomProps.ts: a key that type-checks, reads as supported, and silently never reaches the element (objectui#3290's aria-required, objectui#3222's validation slot).

• names toDomProps.ts → packages/fields/src/widgets/toDomProps.ts — edited by this change

  The fix hands the widget toDomProps(props) — this package's own executor — rather than a second key list written out in the factory. That reuse is the guard: toDomProps.ts's direction-2 assertion already makes keyof FieldWidgetDomProps extends DomPassThroughKey a compile error to violate, so a key added to the declared DOM block now reaches the widget through this factory automatically. One mechanism, one judge — a private list here would have been free to drift, which is how the factory came to deliver one key out of seven.

• 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.ts → packages/types/src/complex.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/6951-text-value-retired.md

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

  Two published faces, one retirement. The TypeScript interface TextSchema (@object-ui/types, layout.ts) declares value?: never; the Zod mirror TextSchema (@object-ui/types/zod, layout.zod.ts) declares value as a retirementTombstone(), so the key stays DECLARED and is refused BY NAME — a plain deletion would have let an authored value ride BaseSchema's .passthrough() into a silent blank, which is worse than the tolerated fallback it replaces. The value?: string members of TextSpanSchema and TabsSchema in the same file are other schemas' contracts and are unchanged.

.changeset/6951-tree-view-data-retired.md

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

  Two published faces, one retirement — and why a tombstone, not a deletion. The TypeScript interface TreeViewSchema (@object-ui/types, data-display.ts) declares data?: never; the Zod mirror TreeViewSchema (@object-ui/types/zod, data-display.zod.ts) declares data as a retirementTombstone(). BaseSchema already declares data?: any (z.any().optional() on the mirror), so DELETING the member would not have refused the key — it would have ADMITTED it, unvalidated, through the base member, and the renderer would have drawn an empty tree. The tombstone on the extended schema shadows the base member on both faces; the pin measures the base accepting the very document the extended schema refuses.

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

  Two published faces, one retirement — and why a tombstone, not a deletion. The TypeScript interface TreeViewSchema (@object-ui/types, data-display.ts) declares data?: never; the Zod mirror TreeViewSchema (@object-ui/types/zod, data-display.zod.ts) declares data as a retirementTombstone(). BaseSchema already declares data?: any (z.any().optional() on the mirror), so DELETING the member would not have refused the key — it would have ADMITTED it, unvalidated, through the base member, and the renderer would have drawn an empty tree. The tombstone on the extended schema shadows the base member on both faces; the pin measures the base accepting the very document the extended schema refuses.

.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/7081-overlay-trigger-union.md

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

  This is a widening, not a replacement: every singular trigger keeps type-checking unchanged. The Zod mirror is untouched — zod/overlay.zod.ts already spelled every one of these keys z.union([SchemaNodeSchema, z.array(SchemaNodeSchema)]) — and so is the runtime: every overlay renderer hands schema.trigger to renderChildren, whose Array.isArray branch has served the array form all along, and every registration's defaultProps.trigger ships as an array. What changes is that the TypeScript face stops under-reporting an accept set that already ships: copying a renderer's own default into a typed document is no longer a type error against the type that shipped it. The seven docs pages' trigger rows follow the declaration.

.changeset/7122-capability-manage-org-presentation.md

• names useFieldTranslation.ts → packages/fields/src/widgets/useFieldTranslation.ts — edited by this change

  The label is the spec artifact's own (Manage Organization Presentation), read off the installed build rather than invented, and it is authored everywhere the widget's docblock requires of any edit to that list: useFieldTranslation.ts and all ten locale packs. Each non-English string is composed from that pack's own established sibling vocabulary (manage_org_users, manage_platform_settings) rather than machine-translated; a native review pass is welcome on the nine, and nothing about the capability's behaviour depends on the wording.

.changeset/7166-retire-inert-fieldmeta-copies.md

• names packages/fields/src/index.tsx → packages/fields/src/index.tsx — edited by this change

  applyRelationalMeta writes the copy set onto the fieldMeta that generateColumns hands to ANGLE-BRACKETS(CellRenderer) as the field prop — six JSX passes across the three column-building paths, and nowhere else. For a relational column that resolves to LookupCellRenderer, which reads exactly reference_to, reference, display_field, displayField, reference_field and options; a user column resolves to UserCellRenderer, which destructures { value } and reads no field meta at all. Measured by receiver rather than by count: packages/fields/src/index.tsx, the file holding every cell renderer, contains zero occurrences of the three retired keys, against a control of 22 occurrences of the display_field / displayField / reference_to spellings the cell does read.

.changeset/7295-chat-message-avatar-keys.md

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

  packages/plugin-chatbot/src/index.tsx:173–178 reads message.avatar || userAvatarUrl and message.avatarFallback || userAvatarFallback (and the assistant twins), the authoring-to-runtime seam spreads every unlisted key through (chatMessageAdapter.ts, ...passthrough), and the SDUI renderer feeds the authored messages[] straight in — a per-message avatar override renders, is documented, and no authoring-facing type declared it. ChatMessage in packages/types/src/complex.ts has no index signature (objectui#5155, deliberately — none is added here), so an author annotating ChatbotSchema.messages was told a value that renders is an error (TS2353); the zod mirror ChatMessageSchema is a plain strip-mode z.object, so the value parsed green and was silently DROPPED from the parsed output.

.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).

.changeset/7493-componentinput-retire-label-defaultvalue-advanced.md

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

  The retirement kit: ?: never on ComponentInput (packages/types/src/base.ts), so authoring one is a tsc error at the registration site; retirementTombstone() on ComponentInputSchema (packages/types/src/zod/base.zod.ts), so an authored value is REFUSED at parse time with code: 'invalid_type', the key named in the issue path, and the migration note as the message (one string, both channels). Pinned in packages/types/src/__tests__/component-input-retired-keys-7493.test.ts, which also holds a tree-scoped absence census over every inputs: array under packages/** and apps/**.

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

  The retirement kit: ?: never on ComponentInput (packages/types/src/base.ts), so authoring one is a tsc error at the registration site; retirementTombstone() on ComponentInputSchema (packages/types/src/zod/base.zod.ts), so an authored value is REFUSED at parse time with code: 'invalid_type', the key named in the issue path, and the migration note as the message (one string, both channels). Pinned in packages/types/src/__tests__/component-input-retired-keys-7493.test.ts, which also holds a tree-scoped absence census over every inputs: array under packages/** and apps/**.

.changeset/7530-predicate-envelope-declared.md

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

  • ExpressionWire (type, main entry) — the TypeScript wire union, in packages/types/src/expression.ts. - ExpressionWireSchema (@object-ui/types/zod) — its runtime twin, hoisted out of zod/form.zod.ts (where it was module-private) into zod/expression.zod.ts and imported by both base.zod.ts and form.zod.ts. One envelope type, reused by reference; no second spelling.

.changeset/7654-floating-chatbot-trigger-icon-tombstone.md

• names packages/plugin-chatbot/src/renderer.tsx → packages/plugin-chatbot/src/renderer.tsx — edited by this change

  It is also absent from the chatbot-floating registration's inputs AND from its defaultProps (packages/plugin-chatbot/src/renderer.tsx), both re-confirmed here. No designer control ever offered it and no designer-created node carries it, so TypeScript was the only way to reach the key. That is what makes this half of objectui#7654 an ordinary retirement; the card's other key, displayMode, is seeded into defaultProps and is NOT touched here.

.changeset/7694-chart-series-chart-type-alias-refusal.md

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

  • Before: series: [{ name: 'revenue', chartType: 'line' }] validated green through @object-ui/types/zod (safeValidateSchema, objectui check / objectui validate, any pipeline that keeps parse()'s output) — and the key was gone from the output, so a consumer of the parse result drew that series in the chart's own family, precisely what the author was overriding. On the TypeScript face the key was merely an excess property on a fresh literal; a widened object carrying it assigned structurally. - After: the same document REFUSES at series[i].chartType (issue code invalid_type) with one message on both channels — the parse-time issue and the .describe() metadata: Unrecognized key(s) on this chart series: \chartType`. Did you mean `chartType` → `type`? …followed by the reason and the remedy. Writetype: 'bar' | 'line' | 'area'. On the TypeScript face ChartDataSeries.chartTypeis a?: nevertombstone, so both the fresh literal and the widened assignment aretsc errors. - **Both written** ({ type: 'bar', chartType: 'line' }) is refused at chartTypealone — the key is not folded ontotypeand no precedence is minted between the two spellings. - **Which documents to scan.** The narrowing does not stop atChartDataSeriesSchema; it reaches every document through the parents that embed it — ChartSchema.series (zod/data-display.zod.ts, z.array(ChartDataSeriesSchema)) and, one level further out, ReportSectionSchema.chart (zod/reports.zod.ts, ChartSchema.optional()). Authors meet it through safeValidateSchema() (zod/index.zod.ts, which parses AnyComponentSchema) and through the CLI's objectui validate command (packages/cli/src/cli.ts). In practice: every chartnode'sseries[], and every report section whose chart` carries one.

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

• names packages/plugin-chatbot/src/renderer.tsx → packages/plugin-chatbot/src/renderer.tsx — edited by this change

  Re-measured on this branch's base (21d7989fb, i.e. after objectui#7708's fence landed as PR fix(plugin-chatbot): fence chatbot-floating's raw props spread #8077) rather than inherited from the card: one schema.KEY count per ComponentRegistry.register(...) body of packages/plugin-chatbot/src/renderer.tsx, the file split at the three register calls.

• names packages/types/src/complex.ts → packages/types/src/complex.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/7704-schema-registry-chatbot-keys.md

• names packages/plugin-chatbot/src/renderer.tsx → packages/plugin-chatbot/src/renderer.tsx — edited by this change

  packages/plugin-chatbot/src/renderer.tsx registers three components — chatbot, chatbot-enhanced and chatbot-floating — and SchemaRegistry mapped one of them. Since ComponentType = keyof SchemaRegistry is the published union, a consumer discriminating on it was told two registered keys do not exist: an author narrowing a node by ComponentType, or writing a RecordANGLE-BRACKETS(ComponentType, …) table, had no arm for either. The asymmetry that showed which half was wrong is that packages/cli/src/utils/known-schema-types.ts keeps its own parallel list containing both keys, precisely because this map did not.

.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/7762-object-grid-export-options-bare-array-refusal.md

• names ObjectGrid.tsx → packages/plugin-grid/src/ObjectGrid.tsx — edited by this change

  What was measured, on this branch's base. The mirror declared NO exportOptions member at all, and BaseSchema is .passthrough(), so ObjectGridSchema.safeParse({ type: 'object-grid', objectName: 'accounts', exportOptions: ['csv', 'xlsx'] }) returned success: true with the array back VERBATIM — as did { formats: ['csv', 'pdf'], compression: 'gzip' }. Nothing on the render path parses, and ObjectGrid.tsx reads schema.exportOptions?.formats and only that, so the authored array then lost SILENTLY to the ['csv', 'json'] default: the useEffect that warns about dropped formats reads .formats too and returns early when it is absent, while !!schema.exportOptions kept the export button on screen. An author declared ['csv', 'xlsx'] and got csv/json with no error, no warning and no console line. The two authoring faces disagreed in the direction opposite to objectui#6956's: the TypeScript interface already declared the object form only, so TS refused what zod admitted.

.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/7918-zod-lazy-getter-identity.md

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

  The card that found this did not claim the ten were wrong. It asked whether the spelling was buying a temporal-dead-zone dodge, and that check is what shipped. Each of the ten was rewritten in place to const inner = ANGLE-BRACKETS(body); z.lazy(() => inner), the package rebuilt, and the built barrel imported in a fresh process. Eight refuse to load. Seven name the very const being declared (children: z.array(TreeNodeSchema) sits inside TreeNodeSchema's own initialiser); SchemaNodeSchema names BaseSchemaCore, which base.zod.ts declares below it. For those eight the z.lazy is load-bearing, so ActionSchema, AppMenuItemSchema, FilterGroupSchema, MenuItemSchema, NavLinkSchema, NavigationMenuItemSchema, SchemaNodeSchema and TreeNodeSchema keep the spelling they have. The two that loaded clean are memoised: FilterBuilderConditionSchema is not recursive at all, and NavigationItemSchema already defers its self-reference through an inner z.lazy(() => NavigationItemSchema) on children.

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

  ⚠️ Also settled while locating the ten: AppMenuItemSchema has no declaration of its own — it is the barrel alias of app.zod.ts's MenuItemSchema, while the barrel's own MenuItemSchema is overlay.zod.ts's. Two different schemas, so the list really is ten entries and not nine.

.changeset/8166-record-scope-data-root.md

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

  The fault is loud, not fatal. The verdict a faulting predicate resolves to is unchanged: visibleWhen still fails OPEN, readonlyWhen / requiredWhen still fail permissive (@object-ui/core's fieldRules.ts; the direction is objectui#8069's open question, not this change's). So a record form renders exactly as before except that the console now names the root. Nothing throws.

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

• names packages/types/src/__tests__/layout-default-jsdoc-7361.test.ts → packages/types/src/__tests__/layout-default-jsdoc-7361.test.ts — edited by this change

  The pin packages/types/src/__tests__/layout-default-jsdoc-7361.test.ts grows from 15 rows to 24, both sides derived off disk as before.

.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/8344-node-recursion-point-redirect.md

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

  Two mechanical notes for anyone editing the wiring. AnyComponentSchema is built in zod/index.zod.ts from all 13 category modules and 14 modules import zod/base.zod.ts, so the arm cannot be an import — z.lazy defers evaluation, not the module graph. It is a written option slot that index.zod.ts fills inside AnyComponentSchema's own initializer, and it is a z.union option rather than a z.lazy holder because z.lazy memoises its getter: a holder would let whichever module graph parsed first decide the accept set for the whole process. Both constraints are measured, and the reasoning lives on defineNodeComponentUnion in zod/base.zod.ts.

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

  ⛔ It is NOT closed here, and the reason is measured rather than argued. The route that closes it by binding the union inside SchemaNodeSchema's z.lazy getter was implemented and pushed, and CI refused it: Build Docs failed with ReferenceError: Cannot access 'BaseSchema' before initialization out of packages/types/dist/zod/app.zod.js, because that import makes base.zod.ts depend on the barrel and a bundler is free to evaluate the resulting cycle category-module-first. Reproduced locally in one line — importing dist/zod/app.zod.js throws with the binding in place and loads clean without it. The other three candidates were measured too: a narrowed sideEffects array is not a legal declaration for this package (one gate requires every entry form to be named, another refuses a named entry with no load-time effect, and this package's entry forms are pure), a bare top-level call is dropped by the same flag, and dropping the flag costs 16,078 gzipped bytes on the console framework chunk and moves a workspace census a guard pins.

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

• names complex.ts → packages/types/src/complex.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 packages/types/src/zod/overlay.zod.ts → packages/types/src/zod/overlay.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/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).

.changeset/8802-8257-8008-kanban-gantt-family-retirement.md

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

  What each retirement was, measured. Three of the four were registration-only: no schema face in @object-ui/types ever declared kanban-ui, kanban-enhanced or gantt as a component node type, so unregistering is the whole retirement. The bare kanban key was the exception — it had a declared arm on both faces (KanbanSchema in complex.ts and its Zod mirror), and a plain deletion there would have been the objectui#7664 failure: BaseSchema is .passthrough(), so a document naming a dropped key validates green and renders nothing. It therefore retires as a named refusal: the Zod union keeps an arm claiming the literal and answers a { "type": "kanban" } document with a message naming object-kanban as the remedy, while the TypeScript half is the absence of the arm from ComplexSchema and of the key from SchemaRegistry, so tsc refuses it at the authoring site.

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

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

  Accept-set change, deliberately. A page document carrying breadcrumbs used to parse GREEN and render nothing. PageNodeSchema never declared the key and no renderer ever read it, so the array survived purely through BaseSchema's .passthrough(). On the TypeScript face, tsc previously accepted it too, through BaseSchema's own [key: string]: any index signature (the [key: string]: any member of BaseSchema in packages/types/src/base.ts) — the same open door the zod mirror walked through at runtime.

• 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.

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

• 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/9162-node-slot-guard-class-closure.md

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

  What leaked. {schema.footer && ANGLE-BRACKETS(CardFooter)…ANGLE-BRACKETS(/CardFooter)} does not evaluate to false when the slot is falsy — it evaluates to the slot, and React renders numbers. A node slot's published zod face carries a z.number() arm (nodeUnionOptions, packages/types/src/zod/base.zod.ts), so footer: 0 is legal authored input, and it painted a stray 0 into the DOM. NaN painted three characters. The && also short-circuits, so renderChildren's own if (!children) return null first leg was never reached — which is why the objectui#8908 bridge repair could not cover any of these sites.

.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/9365-bridgelistview-present-tense.md

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

  base.ts stated the factual basis of objectui#4580's revised Q1 ruling in the PRESENT tense — "that is what a spec producer already writes into this slot: bridgeListView assigns node.label = spec.label", and the same shape one slot over for description. Both sentences were TRUE when PR fix(types): one SchemaNode and one label vocabulary — the union wins, labels resolve where the locale lives (#4580) #4608 wrote them on 2026-08-13: at that commit packages/react/src/spec-bridge/bridges/list-view.ts exported bridgeListView and carried if (spec.label) node.label = spec.label; and if (spec.description) node.description = spec.description; at exactly the addresses cited. objectui#6366 (PR refactor(react): retire the spec-bridge — SpecBridge, bridgeListView, bridgeFormView (#6366) #6632, 2026-08-29) then removed the WHOLE spec-bridge — SpecBridge, bridgeListView, bridgeFormView — from @object-ui/react as a declared BREAKING CHANGE, and the producer, its module and those addresses went with it.

.changeset/9375-base-i18n-vocabulary-docblock.md

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

  base.ts said of the INLINE locale map (label / description) and the KEYED bundle reference (ariaLabel) that they "each accept the other's shape vacuously", and the label docblock said the same thing one property over ("a keyed ref typed into this slot is accepted only vacuously"). That was true when objectui#4580 Q2-B wrote it; the installed pin has since closed it, and the sentence now reads as live in published .d.ts bytes while the tree says the opposite.

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

• names crud.ts → packages/types/src/crud.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/crud.zod.ts → packages/types/src/zod/crud.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/9628-kanban-column-collapsed-honoured.md

• names complex.ts → packages/types/src/complex.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/9659-node-recursion-point-inert-clause.md

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

  What was there. defineNodeComponentUnion (zod/base.zod.ts) installed the component union into the node slot WRAPPED in a superRefine clause that re-issued the node-slot's own refusal under body for a chatbot node. spec(types): redirect the node recursion point from BaseSchemaCore to AnyComponentSchema — measured at 9 newly-refused documents, and it drops 118 phantom strict refusals #8344 needed it because ChatbotSchema.body was then a record — the one redeclaration across the arms that was WIDER than the base key it restated — so installing the union bare would have narrowed at 108 child slots and widened at one.

.changeset/9722-bulk-executor-datasource-face.md

• names ObjectGrid.tsx → packages/plugin-grid/src/ObjectGrid.tsx — edited by this change

  • ObjectGrid.tsx → RecordDetailPanel: removing it type-checks GREEN. It was paying for nothing — both sides already declare the same DataSource | undefined from @object-ui/types. Removed outright. - ObjectGrid.tsx → BulkActionDialog: removing it reddens, and it was paying for TWO things at once — the optional-vs-required arm (the grid declares dataSource?: DataSource, the dialog demands one) AND the bulk-door contravariance. Only the first still needs erasing, so it is now a non-null assertion: today's runtime behaviour is preserved exactly, and any future drift of the face reddens at that site instead of passing silently.

.changeset/9853-grid-non-positive-page-size.md

• names ObjectGrid.tsx → packages/plugin-grid/src/ObjectGrid.tsx — edited by this change

  Refuse a non-positive pageSize at all three of ObjectGrid.tsx's read points, instead of giving two different answers for one authored value (objectui#9853).

.changeset/calendar-readme-schema-keys-5045.md

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

  README.md's "Schema API / CalendarView" block described a CalendarViewSchema that does not exist. Measured against the interface itself (packages/types/src/complex.ts) and its zod mirror: events — the schema's only required key besides type — was published as events?, so a reader following the README omits it and TypeScript rejects the node; defaultDate was string where the schema says string | Date; and onDateClick was listed as a schema key when it is a CalendarViewProps component prop, sending readers to a different package's surface for a key calendar-view does not have (the schema's key is onDateChange). The block also listed 6 of the schema's 13 keys with nothing saying it was a summary (objectui#5045).

.changeset/component-meta-converge-and-deprecate-alias-5893.md

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

  @object-ui/types published ComponentMeta twice, from two different declarations: base.ts and plugin-scope.ts (the latter published as PluginComponentMeta). They were structural copies, not an alias pair. plugin-scope.ts' ComponentMeta is now export type { ComponentMeta } from './base.js' — the disposition objectui#4580 ruled for the identical shape, a structural copy would reproduce the defect the moment either side moved, and the same move objectui#5671 made for the sibling type ComponentInput in the same file.

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

  Either side had already moved. base.ts declared eleven keys; the plugin-scoped copy declared nine — the same nine, minus tags and description. So a plugin author typing against the plugin-facing declaration could not write two keys the main surface advertises, and which the runtime validator already accepted: ComponentMetaSchema in zod/base.zod.ts declares all eleven, so two of the three authorities agreed and the plugin-facing one did not. resizeConstraints' six members were identical in both, so the delta was exactly those two keys.

.changeset/componentinput-reexport-4972.md

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

  @object-ui/core's ComponentInput (registry/Registry.ts) and @object-ui/types' plugin-scoped ComponentInput (plugin-scope.ts, published as PluginComponentInput) were structural copies of the interface in @object-ui/types' base.ts. Both are now re-exports of that one declaration, which is the disposition objectui#4580 ruled for the identical shape — a structural copy would reproduce the defect the moment either side moved — and the way core/src/types/index.ts already handles SchemaNode.

.changeset/console-formpage-visible-predicates-5594.md

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

  objectui#2212 recorded this exact symptom and PR fix(form): evaluate view-level FormField.visibleOn with the canonical CEL engine #2214 fixed it — in a different chain: ModalForm → resolveFormViewLayout → @object-ui/plugin-form sectionFields.ts → @object-ui/components renderers/form/form.tsx. FormPage.tsx is on that chain at no point, and Form-view FormField.visibleOn (CEL) is never evaluated — conditional fields always render #2212's regression pin lives with the chain it fixed, so nothing in the suite could see this copy. One contract, two implementations, each only ever checked against itself.

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

  The wiring is Form-view FormField.visibleOn (CEL) is never evaluated — conditional fields always render #2212's ruling applied verbatim rather than a second predicate semantics invented for this renderer, because two form renderers disagreeing about what visibleWhen means would be a worse defect than one renderer ignoring it. The predicate goes through the canonical engine — evalFieldPredicate (@object-ui/core, evaluator/fieldRules.ts) — so the accepted wire shapes (bare CEL string and { dialect, source }), the bound scope (record.* = the live input values, previous.* = the stored record an edit form started from), and the fail-open-but-loud behaviour on an unevaluable predicate are the shared ones by construction. Resolution is canonical-first, visibleWhen ?? visibleOn, matching both sibling readers: sectionFields.ts and app-shell's readVisibility.

.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/default-children-retired-5051.md

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

  If you author plugins against the published register-meta table, drop the key. It is gone from skills/objectui/guides/plugin-development.md, which had been teaching it. A meta that still declares it stays valid: ComponentMetaSchema is a plain z.object, and measured on zod 4.4.3 that STRIPS unknown keys rather than rejecting them — so the key is silently dropped from the parse output instead of failing validation. TypeScript authors get the loud signal instead: all three ComponentMeta declarations (@object-ui/types base.ts and plugin-scope.ts, @object-ui/core Registry.ts) no longer offer it, so re-declaring it is now a compile error.

.changeset/issue-5373-retire-crud-schema.md

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

  crud had four declaration faces and no registered renderer, for the whole life of the key: the TS interface (packages/types/src/crud.ts), the zod mirror (packages/types/src/zod/crud.zod.ts), a dedicated branch in validateSchema that affirmatively PASSED it, and CRUDBuilder in @object-ui/core. A node spelling it painted the OBJUI-001 "Unknown component type" panel, and content/docs/api/schema-reference.md published it as reference material — so a reader (or an AI author) who copied the page got a red panel.

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

  crud had four declaration faces and no registered renderer, for the whole life of the key: the TS interface (packages/types/src/crud.ts), the zod mirror (packages/types/src/zod/crud.zod.ts), a dedicated branch in validateSchema that affirmatively PASSED it, and CRUDBuilder in @object-ui/core. A node spelling it painted the OBJUI-001 "Unknown component type" panel, and content/docs/api/schema-reference.md published it as reference material — so a reader (or an AI author) who copied the page got a red panel.

.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.

.changeset/palette-canonical-discussion-5495.md

• names public-blocks.ts → packages/core/src/registry/public-blocks.ts — edited by this change

  The two spellings are one renderer under two names — @object-ui/plugin-detail registers both against RecordChatterRenderer — and the palette deliberately carries one entry per renderer. It carried the wrong one. record:discussion is the canonical spelling: @object-ui/core's public-blocks.ts records record:chatter as that same block "under a Salesforce-familiar name, kept for schemas", app-shell's own page synthesiser (buildDefaultPageSchema) has emitted the canonical name all along, and the console's AI block vocabulary already leaves the alias uncurated for exactly this reason. The palette was the last surface still pointing at the alias, and it did so only because the @objectstack/spec build pinned when the entry was written had no canonical member to offer; the currently pinned build declares both. The author-facing label moves "Chatter feed" → "Discussion". Maintainer ruling 2026-08-22 on objectui#5495.

.changeset/param-dialog-title-fallback-4282.md

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

  title is declared on no action surface in the ecosystem: it is absent from @objectstack/spec's ActionSchema (44 keys walked at spec 17.0.0), from @object-ui/core's ActionDef and its pinned ACTION_DEF_KEYS / SPEC_ACTION_KEYS inventories, and from @object-ui/types' renderer view (ui-action.ts) and crud.ts ActionSchema / BaseSchema. None of the four action renderers — action:button, action:icon, action:group, action:menu — forwards it either. So the right-hand side of that || could not be reached by authored metadata: a fallback that cannot fire, which is the "declared is not enforced" shape objectstack#4075 exists to reduce. Nothing a user hits changes; the line now reads exactly one key, matching the description line directly below it.

.changeset/plugin-component-input-deprecate-5674.md

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

  @object-ui/types' entry point publishes ComponentInput as PluginComponentInput. Until objectui#4972 that alias pointed at a genuinely different declaration: plugin-scope.ts restated its own nine-key ComponentInput. objectui#5671 converged that declaration onto base.ts, so the alias became a second published name for the same type, carrying no information the first does not. Two published names for one type is a shape that costs readers a step and gives AI-authored code a coin-flip between spellings.

.changeset/plugin-form-readme-classname-quantifier-5131.md

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

  README.md's "Not a FormField key" table said a field-level className is "read on exactly one pseudo-field, type: 'section-divider'". That quantifier holds only for the renderer's explicit read — className={fp.className} on the section-divider branch of packages/components/src/renderers/form/form.tsx. The same renderer forwards every key it did not destructure, and className is not among the names taken off the field config, not among the ones stripRendererOnlyProps removes, and so rides {...fieldProps} into renderFieldComponent, whose built-in input branch spreads it onto ANGLE-BRACKETS(Input). A field-level className therefore lands visibly on ordinary built-in controls, and a reader taking "exactly one" literally concludes the opposite of what the code does (objectui#5131).

.changeset/record-detail-param-dialog-title-5610.md

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

  title is declared on no action surface in the ecosystem: it is absent from @objectstack/spec's ActionSchema (44 keys walked at spec 17.0.0), from @object-ui/core's ActionDef and its pinned ACTION_DEF_KEYS / SPEC_ACTION_KEYS inventories, and from @object-ui/types' renderer view (ui-action.ts) and crud.ts ActionSchema / BaseSchema. None of the four action renderers — action:button, action:icon, action:group, action:menu — forwards it either. So the right-hand side of that || could not be reached by authored metadata: a fallback that cannot fire, which is the "declared is not enforced" shape objectstack#4075 exists to reduce. Nothing a user hits changes; the line now reads exactly one key, matching the description line directly below it.

.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).

.changeset/text-input-description-aria-describedby-5735.md

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

  Before this the paragraph and the input were siblings with no programmatic relationship: a screen reader moving to the field announced the label and the value and never the helper text. The label half of the same block was already wired (htmlFor against the input's id), which is what made the gap specific to description rather than a general absence of a11y wiring — and the identical key authored on a field INSIDE renderers/form/form.tsx has been announced all along, so one authoring key behaved two ways depending on which container the author reached for. It no longer does.

.changeset/zod-base-schema-mirror-parity-4605.md

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

  The new pin is DERIVED rather than a hand-written key list: it reads the mirror's own .shape and compares each key against the declaration, so the next widening of base.ts that forgets this file turns it red with no list to maintain. It reads .shape and not keyof z.inputANGLE-BRACKETS(…) because that spelling was measured vacuous — .passthrough() collapses the inferred key union to bare string, and a pin written over it resolved never while five keys were demonstrably narrow. Two guards pin the derivation against both degenerations (never and string).

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 c6678b1bd (merge-base with origin/main): 48 file(s) changed outside .changeset/, read against 1620 pending declaration(s) that publish a body (2200 pending in total). · run

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3086.5 KB	3104.5 KB
Main entry chunk (gzip)	148.5 KB	350 KB
Entry file	index-Cdjv-zpi.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.00KB	62.52KB
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: d21aeb0f6bb55e7d771c5287185d96336356a11f

① Derived judgments

Blocking: CI is red. Three source-text pins quote comment citations this PR re-points. The dev's quote search covered only tests quoting the changed RUNTIME strings. These three tests read the source file and pin the citation token inside a comment. All three are final failures on the head:

• layout-default-jsdoc-7361.test.ts, row 5: toContain('6942') over the TextSchema.variant docblock in layout.ts, which now reads "the whole point of 57f9b077b". This fails Test (shard 6/8).
• cellClassNameCensusProse-6921.test.ts (plugin-grid): toMatch(/objectui#6882|#6882/) over the cellClassName census entry in ObjectGrid.tsx, which now reads "declared by the same bf97b98c8". This fails Test (shard 8/8).
• The same file: toMatch(/REDUNDANT since objectui#6882/) over the ObjectGridDataTableSchemaHolds.cellClassName docblock, which now reads "REDUNDANT since bf97b98c8". This fails Test (shard 8/8).
• Every other non-comment test line naming one of the 30 numbers is a title, a message or a testid, and none asserts on changed text. No script gate pins these comments.
• Neither the order nor ruling 5861129870 settles this class; it is the seat's to rule.

Mapping: 18 of 30 sampled, each against git show. The sha carries the sentence:

• fix(plugin-timeline): judge gantt dates by TYPE — string, finite number, or Date #6905 85f6a6097; 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 7fc5c3c12; [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 d3bf4fa6f ("Per the 2026-08-31 ruling"); 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 78e98bf44; Studio: render advisories on the BATCH publish door ("publish whole app") — blocked until objectstack#9343 stops discarding them server-side #6965 ce986aafc.
• 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 85b495795 plus a5d55472b, each carrying the half its sentence names.
• finding(plugin-timeline): spellGanttDateValue's Array.isArray is the last non-total operation on the gantt date path — a revoked Proxy crashes it #7036 869b876c8, and 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 2760075ff: the "card behind" form is correct.
• @object-ui/types' Phase-2 ActionCallback surface is a third onSuccess meaning — declared, zod-mirrored, doc-advertised, zero producers #7068 6bca0e4e8; objectui#6942 57f9b077b; [Decision] Declare renderCellEditor and schema-level cellClassName on DataTableSchema? — the two live undeclared keys the #6459 census measured #6882 bf97b98c8; 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 c0c436db8; finding(types): 18 schemas narrow inherited disabled to boolean while 0 narrow its twin visible — no ruling says which is intended #7087 c93b4d5f3; 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 3619792bf; 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 320374d2a; finding(fields): FieldEditWidget still drops the DECLARED non-DOM host-plumbing keys — error, dataSource, dependentValues, dependsOn, dependsOnLabels, emptyHint, onUploadingChange, onSelectRecord, onCreateNew #7008 f08bcd9af.
• 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, named by role, is true.
• 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 8063bcbdc is right at the confirm, static-column, TableSchema, timeline, overlay and union-arm sites.

Wrong: a neighbouring change (the #5738 class).

• The MarkdownSchema docblock in zod/data-display.zod.ts reads "Both refuse BY NAME through retirementTombstone() (8063bcbdc)".
• That commit never touched MarkdownSchema: its data-display diff has 0 hits for markdown or sanitize.
• sanitize and components were retired, and this docblock was written, by 446d93d4e (objectui#6972) five days later. The pointer only means the convention.

objectstack#6942: confirmed. It is a closed PR: "the ADR-0045 publish gate gets its own machine-managed key — app.hidden goes back to meaning navigation (#4829)". That is exactly the _unpublished / hidden heading it sits under.

The deviation is correct. PR objectui#10038 is the squash PR of ce986aafc, and PR #7024 is the squash PR of 78e98bf44; both answer 200. Each sentence therefore still cites the landing that preference 1 names, and swapping in the sha would give two pointers to one landing. Non-blocking nit: three app-shell sites spell this landing as the PR while their siblings use ce986aafc.

All 24 shas are ancestors of main 309d17b30, and --short=9 matches for each.

Runtime strings: correct.

• ADR-0049 is measured from the retirement itself: the zod comment above the keys opens "ADR-0049 RETIREMENT TOMBSTONES"; .changeset/action-callback-retired-7068.md says "ADR-0049 enforce-or-remove"; each string already ends "Retired under ADR-0049".
• Only the listed text moved (2 plus 2 tombstone lines, and 2 describe lines). The pinning test asserts the full literals by toBe, and its remedy anchors are byte-unchanged.
• No test, doc or changeset quotes either string verbatim.

Census: reproduced. 170 at e32dae160 and at main 309d17b30; 0 at the head; 0 on the merge-tree with 309d17b30. Unfiltered, the head shows 7 lines, all live objectstack#6888 ×5 and objectstack#6942 ×2. Other spellings of the 30 hit only filenames and SVG coordinates.

C0: sane.

• 1002 distinct numbers reproduced, 980 of them at or below 10900.
• [finding] CloudDeploymentConfig.environment 手写第三套环境拼写('development'|'staging'|'production'),与 spec 两个枚举均不吻合 #3720, feat(core,react): declare record.* the row-predicate canon and warn on the two deprecated spellings #5737 and fix(types): one authority for ActionSchema and the Breadcrumb pair #6936 re-read: 404 as an issue and as a pull, and the site counts match.
• Controls finding(plugin-timeline): non-string gantt dates that coerce to the epoch (0, false, []) still draw a 649-column 1970 axis with no diagnostic #6781, test(test-support): one enum-options walk for the top-level reader family (#6924) #7024 and feat(data-objectstack,app-shell): route "publish whole app" through the advisory reporting seam (objectui#6965) #10038 answer 200.
• framework#N is excluded by design.

Changesets.

• 40 of 40 frontmatters are byte-identical (scripted md5).
• Both new changesets are true against the head.
• Optional nits:
  • 7004-cli-root-path-line.md says "(the mechanical half)", which has no referent once the card is gone.
  • "(slice 2)" / "(slice 3)" in the vi-mock changesets have the same problem.

② Semver level

• '@object-ui/types': patch is right: only parse-message and .describe() text moves.
• The sweep changeset is empty, which is right.
• No major. Clause-②: no is right.

③ Boundary flags

• CI on d21aeb0f6 (final, 43 runs): 37 success, 3 skipped, and 3 failure (Test shard 6/8, Test shard 8/8, and the Test shard-reader gate). Type Check, Lint, Build & E2E, dist pins, every Changeset gate, the Line Citation Gate and the Governed Surface Queue Guard are all success.
• git merge-tree against main 309d17b30: clean. The PR is 1 commit behind (PR objectui#10871).
• Open PRs:
  • fix(types,cli): the three plugin-ai node types validate, and a ratchet counts the registered types objectui validate refuses (objectui#10859, batch 1) #10870 (zod/base.zod.ts): disjoint hunks.
  • feat(components,types)!: a list item and a tabs item draw content only, and both item faces refuse body by name (objectui#9590) #10714: disjoint.
  • feat(plugin-grid): one display page size read from the spec, and a distinct fetch batch (objectui#9853) #10278 (ObjectGrid.tsx): conflicts identically against main alone.
  • refactor(fields): the record picker calls core's withoutDeniedFields, the last copy of the field-read rule (objectui#10594) #10876: no shared file.
• check-governed-merges: NOT governed (0 of 88 paths).
• Draft, assigned to os-elon-musk, commit trailers model-free.

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

VERDICT: FAIL

1. Green the three pins. The seat picks the route.
   • Route (a), recommended: extend ruling 5861129870's follower rule to tests that pin comment text, and move the three anchors to 57f9b077b / bf97b98c8.
   • Route (b): restore the three pinned phrases, and hold them with the census at 3.
2. The MarkdownSchema docblock in zod/data-display.zod.ts. Replace "Both refuse BY NAME through retirementTombstone() (8063bcbdc), with the remedy in the message," with "Both refuse BY NAME through retirementTombstone(), the spelling 8063bcbdc made uniform, with the remedy in the message,". The PR body's 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 mapping row notes this site.

Optional, same round:

• Drop " (the mechanical half)" from .changeset/7004-cli-root-path-line.md.
• Merge main with a merge commit (no force-push), and re-read the census on the merged head.

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3087.5 KB	3104.5 KB
Main entry chunk (gzip)	148.4 KB	350 KB
Entry file	index-O3LKSIY9.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.59KB	133.61KB
core (index.js)	9.93KB	3.94KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	225.00KB	62.52KB
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)	161.21KB	41.41KB
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.90KB	22.06KB
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: ae0b81089e50bf66a2ce3066cbc58745a357c6ff

A narrow re-review of the patch-round-1 delta d21aeb0f6..ae0b81089 against the FAIL record 5861897723 and seat ruling 5861900779 (route a), run in-seat. The delta is one fix commit, 914f9104b (4 files, +7 / −7), plus the merge ae0b81089 of main de1b879a6. Everything the record found sound stands: the 30-number mapping (18 sampled), the 24 shas, the runtime strings, the census, C0, the 40 frontmatters and semver.

① Derived judgments

• Item 1, the three pins (route a): applied, anchor only.
  • layout-default-jsdoc-7361.test.ts: toContain('6942') becomes toContain('57f9b077b').
  • cellClassNameCensusProse-6921.test.ts: /objectui#6882|#6882/ becomes /bf97b98c8/, and /REDUNDANT since objectui#6882/ becomes /REDUNDANT since `bf97b98c8`/.
  • Titles, messages and comments in those tests are unchanged.
  • The dev reproduced the red first: layout-default-jsdoc-7361 on d21aeb0f6 gives 1 failed of 75, and the d21aeb0f6 copy of the census test over this tree gives 2 failed of 5. It shows them green at head: the six named files give 181 of 181.
• The gap is closed. A sweep over every literal in the 3814 test and script files under packages/ and scripts/ looked for anchors whose occurrence count drops between main and head in the 90 changed files. The only specific anchors are these three. The tombstone-discriminator-agreement-9684 note search reads mobile.ts only, and that file is untouched.
• Item 2, the MarkdownSchema docblock: applied verbatim. It reads "through retirementTombstone(), the spelling 8063bcbdc made uniform, with the remedy in the message". The sha is now cited only for the convention it did set. This is a comment, so the file's C4 print is unchanged.
• The optional nit: taken. .changeset/7004-cli-root-path-line.md ends "sits at the document root.", and its frontmatter is byte-identical at d21aeb0f6 and head.
• Census: 0 at head, and 0 on the merge-tree with main c6678b1bd.

② Semver level

Unchanged: '@object-ui/types': patch, and an empty-frontmatter sweep changeset. Clause-②: no. Nothing is major.

③ Boundary flags

• The merge is a merge commit (no rebase, no force-push). The branch is 1 behind main c6678b1bd (PR objectui#10870), and git merge-tree against it is clean.
• Open PRs: fix(types,components,docs): correct the texts objectui#6771 left false about body (objectui#8284) #10879, feat(plugin-grid): server-side grid grouping — group headers from the query, rows paged per group (objectui#7189) #10878, feat(components,types)!: a list item and a tabs item draw content only, and both item faces refuse body by name (objectui#9590) #10714 and feat(plugin-grid): one display page size read from the spec, and a distinct fetch batch (objectui#9853) #10278 share files, but no changed line sits inside or beside their hunks. feat(plugin-grid): one display page size read from the spec, and a distinct fetch batch (objectui#9853) #10278 conflicts identically against main alone.
• Commit trailers are model-free.
• CI on the head: the landing waits for all of it to be final green.

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

VERDICT: PASS