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

[objectstack-fleet]

Part of #10803
Clause-②: no

Dispatched implementation of the domain:ui seat 2 claim (comment 5862515185) on objectui#10803, batch 5, 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, all in @object-ui/types: the six ChatbotSchema tombstone guidance strings open RETIRED (ADR-0049) — (rulings 5861129870 and 5861311219), the page node's actions refusal, an ADR-0049 tombstone too, cites (ADR-0049) in place of its dead card (ruling 5861129870, as measured in patch round 1), and the ChartDataSeriesSchema.variant description drops its pointer (amendment 5860244997, Q1 = A). Two tests that pin changed text follow it, anchor only (ruling 5861900779, route a).

Patch round 1 answers the contract review's one FAIL item on afed8aa6b: Special cases 7 had read the actions refusal as not ADR-0049 from a proxy (the breadcrumbs changeset, which only says the 2026-09-09 RULING is not borrowed). Measured from the retirement itself, it is an ADR-0049 tombstone, so under the seat's option (a) its string now reads "never was (ADR-0049): no renderer reads it". The runtime-strings changeset follows, and the sweep changeset notes that @object-ui/types' runtime text is declared separately. One text-only commit, 8255f14f4; no merge, no force-push.

Why Part of, not a closing line

The card stays open for the other 23 numbers of the family remainder (seat amendment 5860244997, Q2 = A), listed in Acceptance notes 1, and for the bare sister-repo numbers the C0 census below lists.

Premise, re-measured

• REST GET /repos/objectstack-ai/objectui/issues/N for each of the 41: all 41 answer 404, and a second read of each answers 404 again (41 of 41). GET .../pulls/N answers 404 for all 41 too. Lit controls: objectui#10533 and objectui#7714 answer 200. No number was dropped from the batch.
• The same 41 in objectstack all answer 200. Three of them are the sites' real subject, read not guessed, and are re-qualified (Zone 1 item 5):
  • objectstack#3720 "列表行级 edit/delete 与批量删除未接入服务端 effective 操作集": the five [#3720] sites in ObjectGrid.tsx, rowCrudAffordances.ts and ListView.tsx describe that gate, and their landing ba4514511 is titled "gate list row Edit/Delete and bulk delete on the effective operation set (objectstack#3720)".
  • objectstack#5506, the "five more hardcoded English chrome strings" card: useDetailTranslation.ts wrote "the SAME key Studio metadata forms: no errors before input, translated help text, and a publish button clear of the toast #5506 gave NavigationOverlay's identical handle", and nine sibling in-scope lines already cite objectstack#5506 for those strings.
  • objectstack#6936, the metadata-admin predicate fail-CLOSED card: predicate.ts wrote "fix(types): one authority for ActionSchema and the Breadcrumb pair #6936's true verdict" one line below "objectstack#6936's unresolved-path ruling".
  • Every other site names an objectui card or pull request, confirmed by its landing commit below (for example objectstack#7853 is a driver-memory finding, while objectui#7853 is the cite-by-content ruling AGENTS.md [WIP] Update documentation for project #11 names).
• Every edited changeset is pending: it is present in .changeset/ on main.
• Branch point: b2683a2c0. main is now 4f8b7f86a; its census still reads 215, and the merge of this head with it reads 0. Not a shallow checkout.

C0: the bare-number remainder (measurement only)

The instrument of PR objectui#10875, at the branch point:

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

• 998 distinct bare numbers at b2683a2c0 (1002 at batch 4's e32dae160): the eight batch 4 re-pointed are gone, and four are new since: finding(plugin-view/types): the pending 9242 changeset and ObjectView's kanban comment say the objectui#8365 stray-groupBy refusal covers BOTH routes, but a named view's listViews.KEY.kanban.groupBy passes safeValidateSchema green #10321, bug(plugin-list): a surviving groupBy in the kanban config OVERRIDES the lane ListView just resolved — measured active, and now unfed #8365 and bug(plugin-view): a stray groupBy in viewOptions.kanban overrides the lane generateViewSchema just resolved — the second route, untouched by objectui#8365 #9242 (at or below 10900, each read once: 200) and #20051.
• Above 10900: 23, batch 4's 22 plus #20051. Each was read once with REST GET .../issues/N: 23 answer 404, and each answered 404 again on a second read (23 of 23); GET .../pulls/N answers 404 for the 18 that are not colours.
• None of them is an objectui citation, and none sits in a sentence or hunk this batch edits, so nothing is folded here:
  • 5 are CSS colours: #334155, #336699, #475569, #737373, #953800.
  • 18 are objectstack numbers, 16 of which answer 200 there with the sites' own subject. #13033 and #13413 answer 404 in objectstack too. Sites (lines / files, at b2683a2c0) are listed in Acceptance notes 2 for later batches.

Census (the enumeration pin for this batch)

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

git grep -nE '(objectui#|#|issues/)(7091|7097|7108|7177|7612|7620|7623|7658|7666|7667|7669|7678|7681|7682|7703|7704|7708|7804|7844|7853|7869|7874|7877|7926|7959|7967|7979|7980|8058|8060|3720|5420|5503|5506|5737|6467|6936|6945|7622|7662|7684)([^0-9]|$)' REF -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | grep -v 'objectstack#' | wc -l

• REF = b2683a2c0 (branch point, and main now): 215 lines, 74 changeset lines in 55 files and 141 src lines in 47 files.
• REF = 8255f14f4 (this head): 0. Round 0's head afed8aa6b also read 0.
• This head merged with a fresh main (4f8b7f86a, git merge-tree --write-tree, clean, tree 08f80168a): 0. REF = 4f8b7f86a alone: 215.
• The filter hid nothing this time. The 18 branch-point lines the grep -v 'objectstack#' drops name only objectstack#6936 or objectstack#5506; with those tokens deleted, none of them matches the instrument (0). Unfiltered, this head reads 26, all live objectstack# lines: the 18, the seven re-qualified here, and the same spelling in the new sweep changeset.
• Lit control, the same printed instrument over live objectui#7714 at this head: 17 lines. Hex-colour false positives (a number followed by a hex letter) at the branch point: 0.
• Out of scope, as it stands (the instrument with the 41 numbers, unfiltered, whole tree at this head): 367 test lines in 98 files, 23 scripts lines in 5 files, 0 .github, 5 governed lines in 4 files (AGENTS.md and three skills/objectui files), and 51 other lines in 18 files: published CHANGELOG.md history (21 lines in 8 files), content/docs (11 in 4), apps/console (7 in 3), eslint-rules (8 in 2) and eslint.config.js (4). See Acceptance notes 4.

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 / docs: cite landing commits where pending changesets and source comments name 30 objectui issues that answer 404 (objectui#10803, batch 4) #10875. All 40 distinct shas in the mapping 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 it 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 (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).
• Where the claim lived only on the dead card (a finding, a ruling, a scope, a comment), the sha only locates it: "the card behind SHA", "the ruling behind SHA" (Special cases 3). 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 (Switch the sharing_rule edit-door client gate on — blocked until #7603 stops the _diagnostics decoration reaching the gate #7612, 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-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(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, and the open finding(types): 39 handler keys a registered renderer READS are declared by no arm — accepted and KEPT by the passthrough, on main today #7804 parent).
• Runtime text carries no sha: see Special cases 7.

Mapping (number to resolution)

Lines / files are the branch-point census for that number. "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
#7091 (a pull request)	969ba84f4	git log --grep: its squash subject ends "(#7091)"	1 / 1	it registers the console app:launcher renderer, which is what made the "not a page" clause false
#7097	3cab5703b; own-card pointer dropped	changeset's adding commit	3 / 3	it adds the 2xl read arm and the literal GRID_COLS_2XL class map, the value-level fix both sentences name
#7108	1267508ea; own-card pointer dropped	changeset's adding commit	3 / 2	it tombstones a deleted record reference in the approvals inbox, the platform-flagged class the sentences name
#7177	own-card pointer dropped (landing ebc05b4d6)	changeset's adding commit	1 / 1	the only site is its own changeset's pointer
#7612	"the 2026-09-20 ruling"; the card by role	git log --grep finds only 2ca238075, the objectui#10150 record of the ruling; the switch, PR objectui#10054, closed unmerged	3 / 2	nothing landed: the ruling was "no". See Special cases 3 and 4
#7620	c15d7eca6; "ruling A behind c15d7eca6" where the sentence cites the ruling; own-card pointer dropped	changeset's adding commit, git log -S	13 / 10	it moves data-table's date-only fallback onto formatDate's default face, and its message records the two-faces fact pattern the sentences cite
#7623	5d0876c5c; own-card pointer dropped	changeset's adding commit	3 / 3	it retires the inert dashboard-root title declaration
#7658	90c6d090d; own-card pointer dropped	changeset's adding commit	2 / 2	it keeps code-span content out of extractToc's HTML strip
#7666	nothing answers: the card by role ("already-filed defect")	git log -S finds only a472b0716, which records it as an already-filed defect	1 / 1	see Special cases 3
#7667	a472b0716; own-card pointer dropped	changeset's adding commit	2 / 2	it gives extractToc's emphasis rules the flanking rule that keeps SCREAMING_SNAKE underscores
#7669 (a pull request)	a3eb5d07a	git log --grep: its squash subject ends "(#7669)"	2 / 2	it retires FloatingChatbotConfig.triggerIcon as the tombstone both sentences name
#7678	5f8190c8c ("in its amended form"); own-card pointers dropped	changeset's adding commit; its body opens "Part of #7678"	21 / 14	it brings every statement of the retire-vs-remove discriminator to the amended form, the surviving-carrier precondition included. See Special cases 6
#7681	01c27c431; own-card pointer dropped	changeset's adding commit	6 / 4	it routes a dataKey-shaped series through normalizeSeries, removing the fast path, so its type override is honoured
#7682	nothing answers: "a separate card"; runtime pointer dropped	git log -S finds only 8fe8e5c16, which defers that decision to it	3 / 3	see Special cases 3
#7703	a4611b3e2; runtime text RETIRED (ADR-0049) —; own-card pointer dropped	changeset's adding commit	15 / 3	it retires the six dark ChatbotSchema keys as ADR-0049 tombstones
#7704	20316bac3; "the card behind 20316bac3" for the scope note; own-card pointer dropped	changeset's adding commit	3 / 2	it adds chatbot-enhanced and chatbot-floating to SchemaRegistry
#7708	d3499b315; PR #8077 kept where it stands beside the dead card; "the card behind d3499b315" for the ruling; own-card and runtime pointers dropped	changeset's adding commit, git log --grep	13 / 6	it fences chatbot-floating's raw props spread through toDomProps at the head of the element
#7804 (the handler-key parent)	per slice, by git blame: 75fca9669 (data-table), 7ca6ddd4b (detail), f1cd29032 (list-view), 5a41ce733 (object-kanban), 8d50bc2bf (objectql.ts), 604476d97 (tree-view); own-card pointers dropped; "the handler-key parent card" where the sentence means the open parent	each slice changeset's adding commit, and git blame per line	49 / 17	each commit declares exactly the handler keys the site's arm or face names
#7844	nothing answers: "their own card"	git log -S finds only c4a1d39fe, which leaves both sub-shapes dark	1 / 1	see Special cases 3
#7853	"the card behind fa7d66c45"	AGENTS.md #11 names fa7d66c45 as its landing	3 / 3	the ruling lived on the card; fa7d66c45 is its one-site landing
#7869	"the finding objectui#8344 discharged" / "the finding this card discharges" (landing 841dd2b7e)	841dd2b7e's message; the live objectui#8344's body, "Discharges the finding #7869"	2 / 2	the measurement lived on the dead finding, and the live card that discharged it restates it
#7874	d9580f464; PR #7887 kept beside the dead card; own-card pointer dropped	changeset's adding commit	3 / 3	it retires the five dead timeline.relative.* rows
#7877	7dcda9cd4	git log -S on the heading	1 / 1	it moves the hand-rolled-table data into hand-rolled-tables.json, the heading's subject
#7926	12b599219; "the 2026-09-09 ruling"; "the actions refusal" by role beside PR #8870; runtime text (ADR-0049); own-card pointer dropped	changeset's adding commit	15 / 6	it refuses actions by name on the page node, measures breadcrumbs at 1 site and leaves it parsing, and pins that
#7959	36fc74629; "the card behind 36fc74629" for its scope restraint	the tests it added are headed "objectui#7959"	8 / 6	it adds readEnvelopeFailureText, the userMessage-first rule on PackagesPage, and the load-failure testid
#7967	own-card pointer dropped (landing 0544ae958)	changeset's adding commit	1 / 1	the only site is its own changeset's pointer
#7979	own-card pointer dropped (landing bfa4fe728)	changeset's adding commit	1 / 1	the only site is its own changeset's pointer
#7980	a810bb2ae; "the card behind a810bb2ae" for its surface and its comment; own-card pointer dropped	changeset's adding commit	4 / 3	it publishes readEnvelopeFailureText from the package entry
#8058	3f4b45886	git log -S storedRelationshipTarget	5 / 2	it adds storedRelationshipTarget, the read door under both spellings, and rewrites the "costs nothing" claim
#8060	7dc31bb8d; "step 1 of the card behind 7dc31bb8d"	git log --grep: its subject names "(#8060)"	8 / 3	it carries a stored type the designer cannot author through verbatim (partitionStoredFields) instead of flattening it to text
#3720 (C0)	re-qualified objectstack#3720	ba4514511's subject; objectstack#3720's subject	5 / 3	see Premise
#5420 (C0)	own-card pointer dropped (landing b470e9150)	the adding commit's subject names "(#5420)"	1 / 1	the only site is its own changeset's heading
#5503 (C0, a pull request)	6f017e99c	its squash subject ends "(#5503)"	1 / 1	it puts the chart min-height floor on the element Recharts measures
#5506 (C0)	re-qualified objectstack#5506	nine sibling in-scope lines already cite it for the same strings	1 / 1	see Premise
#5737 (C0, "PR #5737")	d1ab06f0f	its squash subject ends "(#5737)"	4 / 4	it declares record.* the row-predicate canon and warns on the two deprecated spellings, which is Phase 1
#6467 (C0)	own-card pointer dropped (landing 5ad0641e0)	its subject names "(#6467)" before its own "(#7332)"	1 / 1	the only site is its own changeset's pointer
#6936 (C0)	re-qualified objectstack#6936	the line above already cites it	1 / 1	see Premise
#6945 (C0, "PR #6945")	2c45966ff	its squash subject ends "(#6945)"	1 / 1	it declares the 13 renderer-read keys the sentence says objectui#6150 declared first
#7622 (C0, "PR #7622")	1cca678ba	its squash subject ends "(#7622)"	1 / 1	it retires the dashboard-root title read on all five surfaces
#7662 (C0, "PR #7662")	bc640ec56	its squash subject ends "(#7662)"	1 / 1	it is the change to SchemaRegistry's kanban entry the sentence ascribes to objectui#7645
#7684 (C0, "PR #7684")	"the contract review of 8fe8e5c16's pull request"	its squash subject ends "(#7684)"	2 / 2	the review lived on the dead pull request; the sha only locates it

Special cases (the judgement calls)

1. A dead card beside its own live landing.
   • defaults-table-scan.ts: "rows of objectui#7874 at all (retired in chore(plugin-timeline): retire the five dead timeline.relative.* default rows (objectui#7874) #7887)" becomes "rows at all (retired in chore(plugin-timeline): retire the five dead timeline.relative.* default rows (objectui#7874) #7887)". PR chore(plugin-timeline): retire the five dead timeline.relative.* default rows (objectui#7874) #7887 answers 200 and is d9580f464's pull request.
   • 7703-chatbot-dark-keys-retired.md: "after objectui#7708's fence landed as PR fix(plugin-chatbot): fence chatbot-floating's raw props spread #8077" becomes "after the fence landed as PR fix(plugin-chatbot): fence chatbot-floating's raw props spread #8077". In the same file "until objectui#7708 the chatbot-floating registration ended…" becomes "until PR fix(plugin-chatbot): fence chatbot-floating's raw props spread #8077 the…", and the next sentence's "That card was ruled fence, not declare, and landed as PR fix(plugin-chatbot): fence chatbot-floating's raw props spread #8077" becomes "Its card was ruled fence, not declare, and landed as that PR", so it keeps an antecedent.
   • 8871-page-node-refuses-breadcrumbs.md and layout.zod.ts: "corrects objectui#7926's "1 site"", beside "(PR fix(types,docs): refuse actions by name on the page node, teach the shape that draws (objectui#7926) #8870)", becomes "corrects the actions refusal's "1 site"". The changeset's "objectui#7926's patch does not transfer here" becomes "The actions refusal's patch does not transfer here".
2. The sister-repo numbers. [#3720] becomes [objectstack#3720] at five sites; "Studio metadata forms: no errors before input, translated help text, and a publish button clear of the toast #5506" and "fix(types): one authority for ActionSchema and the Breadcrumb pair #6936's" become objectstack#5506 and objectstack#6936's. See Premise.
3. The card named by role.
   • Switch the sharing_rule edit-door client gate on — blocked until #7603 stops the _diagnostics decoration reaching the gate #7612, clientValidation.ts: "The switch was then put to the maintainer on objectui#7612" becomes "…on its own card". Nothing landed: the ruling said no, and the switch PR closed unmerged. The verbatim ruling quote 「7612 只需要服务端校验」 stays as the maintainer wrote it; it carries no #.
   • 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, 7667-toc-emphasis-flanking.md: "(objectui#7666, a heading extractToc lists…)" becomes "(a heading extractToc lists…)". The sentence already calls it "a different, already-filed defect".
   • 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: "objectui#7682 owns that decision" becomes "a separate card owns that decision" (7546-chart-series-keys-declared.md), and "objectui#7682's decision" becomes "a separate card's decision" (data-display.ts).
   • 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, 8754-… changeset: "the two further sub-shapes objectui#7844 records" becomes "the two further sub-shapes recorded on their own card".
   • finding(types): 39 handler keys a registered renderer READS are declared by no arm — accepted and KEPT by the passthrough, on main today #7804 as the open parent: "whose disposition is still open on objectui#7804" becomes "…on the handler-key parent card" (9447-…); "both are ledgered to objectui#7804, which owns it" becomes "…to the handler-key parent card" (handler-key-reads-follow-cast-receivers.md); crud.zod.ts's "objectui#7804's rows are the handler keys" becomes "the handler-key parent card's rows…".
   • "The card behind SHA", where the sentence rests on something that lived only on the card:
     • date has the same two-convention split datetime just had: data-table's date-only cell keeps a year that formatDate drops #7620's ruling A: "following the maintainer's ruling A on objectui#7620" becomes "…ruling A behind c15d7eca6" in four @object-ui/fields widgets, and GridField's "the split date has the same two-convention split datetime just had: data-table's date-only cell keeps a year that formatDate drops #7620 ruled on" becomes "the split ruling A settled". RelatedList.tsx: "objectui#7443 and objectui#7620 spent two cards" becomes "objectui#7443 and the card behind c15d7eca6 spent two cards".
     • 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's ruling: "objectui#7708 ruled FENCE" becomes "The card behind d3499b315 ruled FENCE", and "That ruling was FENCE" after it becomes "The ruling behind it was FENCE" (complex.ts).
     • 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: "objectui#7853 ruled…" becomes "The card behind fa7d66c45 ruled…" in both [finding] objectui#8047 mechanized the cite-by-content rule for TEST NAMES only, and its carve-out for comments does not hold across files — 10 cross-file path:line citations measured already false, in one PR's blast radius alone #8875 changesets and in defaults-table-scan.ts's list.
     • finding(app-shell): every envelope reader on the package surfaces drops producer-marked text — fetchPackages discards the whole body, apiJson reads no userMessage #7959's scope restraint: "objectui#7959 kept/left it off the public entry as scope restraint — that card's file surface was…" becomes "The card behind 36fc74629 …" (7980-… changeset, app-shell index.ts).
     • finding(console): the agent-key generator reads only error.message, so a marked userMessage and the code never reach the developer #7980: "see objectui#7980 comment 5583988475" becomes "as the card behind a810bb2ae records" (a comment on a dead card resolves nowhere); PackageFormDialog.tsx's "is objectui#7980's surface" becomes "is the surface of the card behind a810bb2ae".
     • finding(types): SchemaRegistry / ComponentType omit chatbot-enhanced and chatbot-floating — two registered keys the layer can now name #7704's scope note (registry.ts) and 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's "step 1" (MetadataFieldsPage.tsx) take the same form.
     • 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: the finding card is dead, and the live objectui#8344 discharged it and restates the measurement, so base.zod.ts reads "That is the finding objectui#8344 discharged: an off-spec size…" and 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's own changeset reads "the finding this card discharges measured…".
4. Rulings by date.
   • Switch the sharing_rule edit-door client gate on — blocked until #7603 stops the _diagnostics decoration reaching the gate #7612: the AUTHOR_SHAPE_ONLY_TYPES heading ends "(the 2026-09-20 ruling)"; 10150-author-shape-header-ruling.md reads "the switch was put to the maintainer, and the 2026-09-20 ruling was option A". Its last sentence, "requires the docblock to name the ruling's card", becomes "…to name the ruling", because the pin it describes now anchors on the ruling (Special cases 8).
   • 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: "objectui#7926's maintainer ruling covers actions" becomes "The 2026-09-09 maintainer ruling covers actions", and "objectui#7926 does not rule on it" becomes "the 2026-09-09 ruling does not cover it" (layout.zod.ts).
5. Own-card pointers that needed a word.
   • 7097-grid-2xl-breakpoint.md: the pointer sat on its own line, so the period moved up with it.
   • 7678-tombstone-discriminator-agreement.md: "the site objectui#7678 was filed about" becomes "the site this card was filed about", the file's own wording two lines earlier.
   • 7804-object-kanban-handler-keys-judged.md: "its KNOWN_UNDECLARED_READS row naming objectui#7804, which stays open and stays the parent" becomes "its KNOWN_UNDECLARED_READS row, which names the parent card".
   • The six 7804-* slice changesets keep "(the … slice)" once the pointer goes, as batch 4 kept "(slice 2)".
6. The discriminator form (types: the triggerIcon tombstone's rationale contradicts mobile.ts's own retire-vs-remove discriminator, and its tripwire comment overclaims #7678). "in the form objectui#7678 amended it to" becomes "in its amended form (5f8190c8c)" at every site; "as amended by objectui#7678" and "amended by objectui#7678" take the same wording; a bare "types: the triggerIcon tombstone's rationale contradicts mobile.ts's own retire-vs-remove discriminator, and its tripwire comment overclaims #7678" in a precedent list becomes 5f8190c8c. mobile.ts's "without the precondition objectui#7678 added" becomes "without the precondition the amendment added", whose antecedent is the preamble's "amended form" two sentences up. 9684-discriminator-cited-once.md: "objectui#7678's amendment had to be applied by hand" becomes "the amendment (5f8190c8c) had to be applied by hand", which is what that commit did.
7. The runtime strings. Only the listed text moves in each.

file	member	before	after
types/src/zod/complex.zod.ts	ChatbotSchema.loading, .showAvatars, .userAvatar, .assistantAvatar, .markdown, .height (tombstones)	"RETIRED (objectui#7703, ADR-0049) — …"	"RETIRED (ADR-0049) — …"
types/src/zod/complex.zod.ts	ChatbotSchema.showAvatars (tombstone)	"… unfiltered props spread — was fenced by objectui#7708. Delete the key: …"	"… unfiltered props spread — was fenced. Delete the key: …"
types/src/zod/layout.zod.ts	PageNodeSchema.actions refusal	"actions is not a key of the page node and never was (objectui#7926): no renderer reads it, …"	"actions is not a key of the page node and never was (ADR-0049): no renderer reads it, …"
types/src/zod/data-display.zod.ts	ChartDataSeriesSchema.variant .describe()	"… the renderer-internal current spelling is not a member (objectui#7682)"	"… the renderer-internal current spelling is not a member"

The ADR-0049 condition, measured from the retirement itself (Zone 1 item 4): the six tombstones already cited ADR-0049 beside the dead card; the zod comment above them opens "ADR-0049 retirement tombstones"; their landing a4611b3e2 is titled "retire six dark ChatbotSchema keys as ADR-0049 tombstones"; and the pending 7703-chatbot-dark-keys-retired.md says "ADR-0049 retirement tombstones". The actions refusal is an ADR-0049 tombstone too, measured the same way: its arm is retirementTombstone(PAGE_ACTIONS_REFUSAL), its landing 12b599219 calls it "an ADR-0049 retirementTombstone arm", and 7926-page-node-refuses-actions.md calls it "an ADR-0049 refusal arm". Its string has no RETIRED opener, so its own parenthetical becomes (ADR-0049), the spelling its breadcrumbs sibling already uses. The TypeScript twins in complex.ts read "ADR-0049 RETIREMENT TOMBSTONE — loading (a4611b3e2)", the comment form.
8. What follows the text, and nothing else in it (ruling 5861900779, route a; ruling 5861129870).

• chatbot-dark-keys-retired-7703.test.ts pins the six guidance strings as full literals. Their openings follow to RETIRED (ADR-0049) — , the showAvatars literal follows "was fenced.", its prescriptive anchor 'was fenced by objectui#7708' becomes 'was fenced.', and toContain('RETIRED (objectui#7703') becomes toContain('RETIRED (ADR-0049) —'). Its test names and @ts-expect-error comments still read "RETIRED (objectui#7703)"; they describe the ?: never TypeScript face and are out of class (Acceptance notes 6).
• clientValidation.authorShapeRuling-10150.test.ts pins that the AUTHOR_SHAPE_ONLY_TYPES header names the ruling and extractDraftBody. Its subject 'objectui#7612' becomes 'the 2026-09-20 ruling'; its message and title are unchanged.
• No test, doc or changeset quotes the actions refusal or the variant description verbatim: a whole-tree search for the old strings returns only the source lines.

9. The anchor sweep (PR objectui#10875 Special cases 10 shape).
   • Instrument: every string, template, numeric and regex literal in all 3822 test and script files under packages/ and scripts/, enumerated with git ls-tree at head and parsed with TypeScript (113091 distinct literals).
   • Test applied to each literal: does its occurrence count DROP between b2683a2c0 and head in any file this PR changes, in raw text or in a comment-flattened form?
   • Run 1, on 8c267051f (the sweep commit, before any test moved): 336 distinct literals drop. Read against the files they sit in, the specific anchors are the two pins in item 8 (the six literals, the prescriptive anchor and the toContain in the first; 'objectui#7612' in the second). Also listed and read: the 'objectui#7804' values of check-handler-key-read-sites's KNOWN_UNDECLARED_READS ledger and its test, which assert over the script's own data and never read a changed file, and tombstone-discriminator-agreement-9684's /RETIRED \(objectui#/, which it applies to mobile.ts alone, untouched here.
   • Everything else is a generic token (whitespace, punctuation, single letters and digits, objectui#, character-class regexes of whole-tree scanners), none an assertion over text this PR changed.
   • Run 2, on round 0's head afed8aa6b: 327 distinct literals; the nine literals the two pins moved are gone from the drop set, nothing new appears, and the only one left naming a batch number is that ledger value.
   • Run 3, patch round 1, over the delta afed8aa6b..8255f14f4: 18 (literal, file) drops, every one a generic token (' is', 'dropped', a /(\w+):/g scanner); no test pins the changed refusal text.

Held

By the serial rule: nothing. Patch round 1 re-read: 8 open besides this PR (objectui#10896, #10891, #10890, #10889, #10888, #10777, #10278 and the release PR #5400; #10886 and #10714 have left the open list). New since round 0, objectui#10896 shares plugin-grid/src/ObjectGrid.tsx and plugin-list/src/ListView.tsx; trial merges of this head with every open head are clean except #10278 (conflicts identical against main alone) and the release PR #5400, which regenerates. The round's one source edit, in layout.zod.ts, is held by no open PR.

Round 0, re-read before its push: 11 open besides this PR. They are objectui#10890, #10889, #10888, #10886, #10884, #10852, #10780, #10777, #10714, #10278 and the release PR #5400.

• Five of them hold files this PR edits:
  • objectui#10890: types/src/ai.ts;
  • objectui#10888: .changeset/8344-node-recursion-point-redirect.md;
  • objectui#10886: types/src/objectql.ts and types/src/zod/objectql.zod.ts;
  • objectui#10714: types/src/data-display.ts, types/src/layout.ts, types/src/zod/data-display.zod.ts and types/src/zod/layout.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 47 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(types)!: the AI node declarations stop offering members no runtime honours (objectui#10874) #10890, fix(types,plugin-designer)!: the app wizard saves a document the spec accepts — a separator without label, branding kept on edit, no Layout control (objectui#10867) #10889, fix(types,cli): 20 of the ADR-0080 public blocks validate, and the ratchet counts the namespaced half (objectui#10872, batch 1) #10888, fix(plugin-calendar,plugin-gantt): show a stored date-only day on that day and write a date field as the calendar day (objectui#10866, sites 1 and 2) #10886, fix(plugin-view): the host delegation reads a named view's remaining protocol members off the named view (objectui#10758) #10884, 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, plugin-grid/README.md and content/docs/plugins/plugin-grid.mdx, and conflicts identically against main alone.
• PR chore: release packages #5400 (Version Packages) regenerates and is not a hold.

Changesets

• .changeset/10803-dead-citation-sweep-fifth-batch.md, EMPTY frontmatter: the comment-only edits in 15 released packages and the private @object-ui/test-support. No published behaviour changes through them. It marks @object-ui/types as the package "whose runtime text is declared separately below" (patch round 1) and points at the second file for it.
• .changeset/10803-fifth-batch-runtime-strings.md, '@object-ui/types': patch: the six tombstones open RETIRED (ADR-0049) — with everything after the dash unchanged except the showAvatars pointer; the actions tombstone cites ADR-0049 in place of its dead card; and the variant description loses its pointer. No key, path, issue code, accept set, refusal or severity moves.

Proof of prose-only (C4), against b2683a2c0, on this head 8255f14f4

• Source. Each of the 49 touched .ts / .tsx files (47 non-test sources and the two pins) was parsed at b2683a2c0 and at this head with TypeScript's createSourceFile and re-printed by createPrinter({ removeComments: true }).
  • 44 of 49 prints are identical.
  • The other 5 are equal once exactly the 19 listed substitutions are applied to the base print, each matched once: complex.zod.ts 7 (six openings and the fence pointer), layout.zod.ts 1 (the pointer becomes (ADR-0049)), data-display.zod.ts 1, chatbot-dark-keys-retired-7703.test.ts 9 (the same seven, the prescriptive anchor and the toContain anchor), clientValidation.authorShapeRuling-10150.test.ts 1.
  • 0 parse diagnostics.
  • Lit controls on the same instrument: dropping "(ADR-0049)" from the loading string moves the print; re-spacing the "ADR-0049 retirement tombstones" comment does not.
• Changesets. The frontmatter block of every one of the 55 edited changesets is byte-identical at b2683a2c0 and this head (55 of 55, by md5). The overwrite gate below agrees.
• Scope of the diff: 106 files: 55 edited and 2 new changesets, 47 non-test source files, and 2 tests.

Gates, on this head 8255f14f4

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

• node scripts/check-changeset-presence.mjs, exit 0: "48 source file(s) of 15 released package(s) changed, and this change declares 2 changeset(s): .changeset/10803-dead-citation-sweep-fifth-batch.md, .changeset/10803-fifth-batch-runtime-strings.md." (48 = the 46 released sources and the 2 tests under released packages' src/; test-support is 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, 55 modified, 0 deleted". declared at base equals declares now for 55 of 55.
• pnpm check:changeset-claims (report-only), exit 0:
  • born-false: "Every one of those 2 address(es) either names the tree it was read from, or points at a line this change does not move";
  • self-contradiction: "Every package declared across those 45 body(ies) is either not negated in its own prose, or negated only in an ASPECT of it that may legitimately hold still";
  • the standing notice "103 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, which reads 0. No pending changeset quotes a changed runtime string.
• pnpm check:control-bytes, exit 0: "check-control-bytes: OK (scanned 9145 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: pnpm check:pending-changeset-literals, exit 0: "No test source names a pending changeset."; the governed-surface predicate over the 106 paths, exit 0: "NOT GOVERNED — 106 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. The branch-point copies of the two pins were written over the committed sweep tree and run: Test Files 2 failed (2), Tests 13 failed | 29 passed (42), for example "expected 'RETIRED (ADR-0049) — never read: chat…' to contain 'RETIRED (objectui#7703'". Both files were then restored with git checkout HEAD --, each checked by blob hash against HEAD, and git diff HEAD came back empty.
• Patch round 1, on this head 8255f14f4: page-actions-refusal-7926 (it pins the message's remedy words actions, children and page:header and that it is not zod's generic text, never the pointer; verified by reading it), page-breadcrumbs-refusal-8871, guide-layout-page-buttons-7926, zod-mirror-parity, chatbot-dark-keys-retired-7703, clientValidation.authorShapeRuling-10150 and tombstone-discriminator-agreement-9684 give Test Files 7 passed (7), Tests 134 passed (134), under VERDICT command-exit 0. A whole-tree search for "never was: no renderer" finds no test or doc quoting it (only the source line and the runtime-strings changeset, both updated); an anchor sweep over the round's delta finds only generic tokens.
• Green, round 0, on afed8aa6b: chatbot-dark-keys-retired-7703, clientValidation.authorShapeRuling-10150, tombstone-discriminator-agreement-9684, page-actions-refusal-7926, page-breadcrumbs-refusal-8871, chart-series-keys-7546, zod-mirror-parity, chatbot-display-mode-retired and schema-registry-chatbot-keys-7704 give Test Files 9 passed (9), Tests 173 passed (173), under VERDICT command-exit 0.

Declared narrowing (per the dispatch: the named checks, not wider sweeps). NOT MEASURED locally: the full suites and type-check of the 15 touched packages, and eslint. Reason: the comment-stripped syntax tree of 44 of the 49 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 9) and run above. CI runs the full farm.

Acceptance notes

1. The remainder rides this card, unchanged (seat amendment 5860244997, Q2 = A). Of the 53 numbers PR objectui#10875's Acceptance notes 1 lists, this PR carries the first 30 in ascending order, plus the 11 C0 404s of its Acceptance notes 2. The other 23 are: 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 numbers above 10900, for later batches (sites at b2683a2c0, lines / files). Each answers 404 as an objectui issue, and none is an objectui citation, so the fix is a re-qualification to objectstack, not a landing sha:
   • written with a word that names the repository but not in repo#N form ("objectstack PR #N", "upstream #N", "framework #N", "spec #N"): feat(plugin-detail,app-shell): a related list inside a record places its child's record_related actions on each row (objectui#11270) #11289 (2 / 2), #11662 (1 / 1), #12616 (1 / 1), #12718 (1 / 1), #13033 (1 / 1), #13413 (1 / 1), #13733 (1 / 1), #13906 (6 / 3), #14274 (1 / 1), #15469 (2 / 2), #20160 (2 / 2);
   • written bare: #13337 (1 / 1), #13632 (3 / 3), #13855 (1 / 1), #14945 (1 / 1), #15948 (1 / 1), #17493 (1 / 1), #20051 (1 / 1);
   • #13033 and #13413 answer 404 in objectstack as well;
   • not citations: #334155, #336699, #475569, #737373, #953800 (CSS colours).
3. A live-but-wrong bare number beside a re-qualified one. rowCrudAffordances.ts cites "(/me/permissions apiOperations, [console] 记录详情页头的 api 动作:target URL 的 {field} 占位符从不插值——record_header 执行器不提供 params._rowRecord,literal {id} 被原样发出 #3391)" at the two sites that now read [objectstack#3720]. objectui#3391 answers 200 with an unrelated subject (a record-header api action placeholder), while objectstack#3391 is the apiMethods whitelist contract card that objectstack#3720's own title names. It is not a 404, so it is outside the family pin and was not touched. Carrier: none.
4. Published or shipped text outside the two in-scope classes still names some of these numbers (counts in Census). It is untouched by scope, as another class the triage split did not scope here: published CHANGELOG.md history (never re-addressed), content/docs (for example the chatbot and layout guides), apps/console (the approvals inbox and the agent-connect section), eslint-rules and eslint.config.js, three skills/objectui files and AGENTS.md (governed). Carrier: none.
5. 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, docs: cite landing commits where pending changesets and source comments name 32 objectui issues that answer 404 (objectui#10803, batch 3) #10869 and docs: cite landing commits where pending changesets and source comments name 30 objectui issues that answer 404 (objectui#10803, batch 4) #10875.
6. Test comments left as they are. chatbot-dark-keys-retired-7703.test.ts's test names and @ts-expect-error comments still read "RETIRED (objectui#7703)", and clientValidation.authorShapeRuling-10150.test.ts's header, title and message still name objectui#7612. Only anchors moved (ruling 5861900779).

---

Generated by Claude Code

[github-actions]

changeset-claim-re-read

⚠️ 103 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/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/4895-retire-block-schema-family.md

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

.changeset/5905-componentinput-inputtype-tombstone.md

• 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/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/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/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:

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

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

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

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

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

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

.changeset/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/6519-retired-field-key-strip.md

• names plugin-designer/src/MetadataFieldsPage.tsx → packages/plugin-designer/src/MetadataFieldsPage.tsx — edited by this change

  Unifying the three retired-key lists on this seam is deliberately not part of this change: it spans plugin-designer/src/MetadataFieldsPage.tsx, which objectui#6489 owns in flight.

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

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

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

.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 GridField.tsx → packages/fields/src/widgets/GridField.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/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/6881-retire-data-table-toolbar.md

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

• names layout.zod.ts → packages/types/src/zod/layout.zod.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/7070-no-invented-gantt-date-fields.md

• names plugin-list/src/ListView.tsx → packages/plugin-list/src/ListView.tsx — edited by this change

  • app-shell/src/views/ObjectView.tsx — the console object page. The inline branch becomes ganttViewOptions, the sibling of calendarViewOptions and timelineViewOptions: the declared block spread whole, title floored at 'name', no date field invented. - plugin-list/src/ListView.tsx — the render branch AND the capability gate. - plugin-view/src/ObjectView.tsx — generateViewSchema, the authored object-view element route, which bypasses ListView entirely.

.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/7087-disabled-twin-symmetry.md

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

  Those 18 redeclarations are removed, on both faces. The interfaces inherit BaseSchema.disabled the way they always inherited visible; the zod mirrors inherit base.zod.ts's z.union([z.boolean(), z.string()]) through .extend()'s merged .shape, so there is no second spelling of the union to drift from — the route ChatbotSchema took in objectui#6169.

.changeset/7113-chart-data-model.md

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

  .extend() with a NEW key still works and preserves the fold and the refinement; .optional(), z.discriminatedUnion, z.toJSONSchema and safeValidateSchema are all unaffected. Nothing in this repository calls the throwing combinators on either const, and the published surface already ships refined mirrors (objectql.zod.ts, complex.zod.ts, form.zod.ts, app.zod.ts), so the class is not new — but it is a real behaviour change on a published export and it belongs in the release note rather than in a reviewer's file.

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

  .extend() with a NEW key still works and preserves the fold and the refinement; .optional(), z.discriminatedUnion, z.toJSONSchema and safeValidateSchema are all unaffected. Nothing in this repository calls the throwing combinators on either const, and the published surface already ships refined mirrors (objectql.zod.ts, complex.zod.ts, form.zod.ts, app.zod.ts), so the class is not new — but it is a real behaviour change on a published export and it belongs in the release note rather than in a reviewer's file.

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

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

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

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

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

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

.changeset/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/7322-object-kanban-group-by-limit.md

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

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

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

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

.changeset/7344-handler-string-any-mirrors.md

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

  The three views.zod.ts z.string() keys that are event NAMES (onViewChange, the two onChange, PR fix(types): the three view handler keys are EVENT NAMES, not callbacks (part of #6124) #6899) are untouched; their describe text says so and the new pin reads it. zod-mirror-parity.test.ts records the three new runtime-slot drift rows; content/docs/core/app-schema.mdx spells its AppAction.onClick row never and drops the string example, the two edits the docs: three pages still teach retired handler keys as authorable props — onColumnAdd/onCardAdd (schema-reference), onSelectChange/onExpandChange (tree-view), onComplete (input-otp) — stale once #6124's tombstones land #7340 docs pin and check:doc-snippets require.

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

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

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

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

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

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

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

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

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

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

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

• 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/7499-gantt-non-axis-floors-omitted.md

• names plugin-list/src/ListView.tsx → packages/plugin-list/src/ListView.tsx — edited by this change

  • plugin-list/src/ListView.tsx — the object-gantt render branch. - plugin-view/src/ObjectView.tsx — generateViewSchema, the authored object-view element route, which bypasses ListView entirely.

.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/7580-responsive-vocabulary-rehome.md

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

  • BreakpointName (xs…2xl) is now declared in @object-ui/types (mobile.ts) instead of re-exported from the spec. No consumer change: same name, same six members, same export sites on @object-ui/types and @object-ui/mobile. Only its provenance moved. - BreakpointColumnMap is now declared in @object-ui/layout (ResponsiveGrid.tsx), verbatim from the retired $strict schema: six optional column counts, no index signature. responsive-grid's columns input and its resolver are unchanged.

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

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

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

.changeset/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/7722-wrapper-class-five-more.md

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

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

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

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

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

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

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

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

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

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

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

.changeset/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/7773-kanban-adapter-groupfield-write.md

• names ListView.tsx → packages/plugin-list/src/ListView.tsx — edited by this change

  Who is NOT affected — the boundary is node-local. Every VIEW-LEVEL groupField read is untouched and still live: it is a legacy alias of the spec's groupByField on the kanban view config, mapped by normalize-list-view.ts, and both adapters still resolve lanes through it (ObjectView.tsx's kanbanCfg.groupField ||, ListView.tsx's groupByField || groupField). Authoring options.kanban.groupField on a list-view or object-view keeps working exactly as documented in packages/plugin-list/README.md. groupField is dead only on the generated object-kanban NODE.

.changeset/7780-object-kanban-record-source.md

• names ListView.tsx → packages/plugin-list/src/ListView.tsx — edited by this change

  groupBy is untouched and stays REQUIRED (objectui#7322, PR feat(types): declare ObjectKanbanSchema.groupBy and .limit, retire groupField on both faces (objectui#7322 item 1) #7774). A record source and a lane key are different questions: every lane-less document above is still refused at groupBy, and the two readings PR feat(types): declare ObjectKanbanSchema.groupBy and .limit, retire groupField on both faces (objectui#7322 item 1) #7774 excluded from counting as a lane-less mode — the dataSource json fragment in content/docs/utilities/data-objectstack.mdx and ListView.tsx's runtime-generated node — are asserted still-refused in the new pin. The retired groupField tombstone is likewise still refused by name.

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

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

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

.changeset/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/7963-alert-dialog-footer-keys-retired.md

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

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

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

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

  Migration. Rewrite data.foo as record.foo on any runtime record surface — the canonical spelling since 83fe6e741, and the only one that reaches the row. The metadata-admin designer is unaffected: its data is the DRAFT under edit (ADR-0089 D3, CANONICAL_ROOT_BY_LAYER = { runtime: 'record', metadata: 'data' }), bound by views/metadata-admin/predicate.ts through its own builder, which takes only the identity roots from this bag and assigns its own data last.

.changeset/8167-conditionbuilder-mount-scope.md

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

  • scope?: 'record' | 'flattened' is now an optional prop, forwarded verbatim to CelPredicateField. Omitting it forwards undefined, so the engine hint is exactly what it was and every mount that passes nothing is unchanged. It deliberately does not derive the scope from subjects.fieldPrefix — that would silently decide the mounts whose tier is still an open question. - An action's Visible when and Disabled when (ActionDefaultInspector) declare scope="record". Conformance: the row-predicate canon in @object-ui/core (rowPredicateCanon.ts) names visible / disabled on an action renderer as a row surface in its own words. - An object validation rule's condition (ObjectValidationsPanel) declares scope="record". The authority there is the server: objectql's rule validator evaluates a script / cross_field condition with { record, previous } and nothing else, and since objectstack#4649 an unevaluable predicate is fail-CLOSED — so a bare reference authored here did not merely fail to match, it rejected every write to the object while the editor linted it green.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

.changeset/8800-retire-ai-insights.md

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

  The retirement's tombstones are the comment standing where the interface was in ai.ts and the comment standing where the barrel re-export was in index.ts; the executable half, including the tree-wide census with its controls, is packages/types/src/__tests__/ai-insights-retired-8800.test.ts. The objectui#8178 exclusion pin that deliberately held AIInsightsSchema.objectName out of that retirement was rewritten by this ruling, which is the only thing that was ever allowed to rewrite it.

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

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

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

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

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

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

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

.changeset/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/8854-app-shell-readme-flow-draft.md

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

  Which door was measured. Not the server, and not the node and edge schemas one at a time: the app-shell metadata admin validates a flow draft client-side by handing the whole draft to the spec's FlowSchema — clientValidation.ts's LOADERS.flow resolves it and ResourceEditPage calls validateMetadataDraft(type, draft) with the editor's entire body. Graded per node and per edge, this block would have reported green while still being refused on save; that is how the identity keys stayed invisible to two previous cards against this same fence.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

• names packages/plugin-list/src/ListView.tsx → packages/plugin-list/src/ListView.tsx — edited by this change

  • packages/plugin-list/src/ListView.tsx generates the node as groupBy: laneField. objectDef loads asynchronously, so laneField is undefined on every load until it lands, and stays undefined whenever the object offers no stageField hint and none of status / stage / state / phase. The renderer serves that node; both published faces refused it. - content/docs/utilities/data-objectstack.mdx documents an object-kanban node that is exactly { type, dataSource }, with no groupBy. ⚠️ This one is weaker and is cited for what it is: that fragment is still refused after this change, at RECORD_SOURCE_REQUIRED, because dataSource is not a rung of the record-source ladder. It shows a lane-less board is a documented authoring; it is not a document this change admits.

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

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

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

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

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

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

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

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

.changeset/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/9309-object-gallery-filter-destination-typed.md

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

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

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

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

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

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

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

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

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

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

• 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/9549-tree-filter-declared.md

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

• 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/action-callback-retired-7068.md

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

  What was measured, on this branch's base (900f8d99). ActionCallback ({ type: 'toast' | 'message' | 'redirect' | 'reload' | 'custom' | 'ajax' | 'dialog', message?, url?, api?, method?, dialog?, handler? }) was declared in crud.ts, mirrored in zod/crud.zod.ts, re-exported by both barrels, and carried on the legacy ActionSchema as onSuccess? / onFailure?. Producers: the package's own phase2-schemas.test.ts fixture and three ts fences in content/docs/core/enhanced-actions.mdx — nothing else (git grep -l ActionCallback over packages content skills hit the five packages/types files; positive control SchemaNodeSchema hit 22). Runtime readers: none — ActionRunner imports UIActionSchema, never this interface, and its own ActionDef.onFailure is a different (runner-native) meaning. It was the THIRD meaning of one key: objectui#5934 had already retired the runner's callback meaning of onSuccess and converged it on the spec's block.

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

  What was measured, on this branch's base (900f8d99). ActionCallback ({ type: 'toast' | 'message' | 'redirect' | 'reload' | 'custom' | 'ajax' | 'dialog', message?, url?, api?, method?, dialog?, handler? }) was declared in crud.ts, mirrored in zod/crud.zod.ts, re-exported by both barrels, and carried on the legacy ActionSchema as onSuccess? / onFailure?. Producers: the package's own phase2-schemas.test.ts fixture and three ts fences in content/docs/core/enhanced-actions.mdx — nothing else (git grep -l ActionCallback over packages content skills hit the five packages/types files; positive control SchemaNodeSchema hit 22). Runtime readers: none — ActionRunner imports UIActionSchema, never this interface, and its own ActionDef.onFailure is a different (runner-native) meaning. It was the THIRD meaning of one key: objectui#5934 had already retired the runner's callback meaning of onSuccess and converged it on the spec's block.

.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 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/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/grid-dom-attribute-whitelist-4787.md

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

  grid.tsx ended in a bare {...gridProps} spread that removed only data-obj-* and style, so everything else SchemaRenderer hands a registered component reached the element. Measured on a canary node, eight attributes leaked: columns="4", gap="4", mdcolumns="2", smcolumns="2", name="grid_node", props="[object Object]", colorvariant="x" (the flattened props container) and an unknown authored zzcanary="leak". A responsive columns object rendered as columns="[object Object]". Layout was unaffected, so every catalog grid example rendered with them — the reason this went unnoticed.

.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/issue-9819-operations-ceiling.md

• names packages/plugin-grid/src/rowCrudAffordances.ts → packages/plugin-grid/src/rowCrudAffordances.ts — edited by this change

  Maintainer ruling of 2026-09-18, ruling batch Complete component documentation coverage for all 76 platform components #162 item 1, letter A, on objectui#9819. rowActions' other ruled power — narrowing INSIDE the ceiling, so naming only edit would withhold an allowed Delete — is NOT part of this change; the section headed "operations is the ceiling" in packages/plugin-grid/src/rowCrudAffordances.ts records what blocks it.

.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/list-user-actions-collision-5398.md

• names ListView.tsx → packages/plugin-list/src/ListView.tsx — edited by this change

  The harvest now reads the object block only. Both userActions read sites in ListView.tsx carry a comment naming the collision, and __tests__/ListView.userActionsCollision.test.tsx pins each clause of it: the two shapes, a producer that manufactures the view one, the harvest's blindness to it, and the projection that must keep the object's operand with a toolbar block — or an empty block — present on the view.

.changeset/listview-comment-pair-4559.md

• names ListView.tsx → packages/plugin-list/src/ListView.tsx — edited by this change

  Two comment corrections in ListView.tsx (objectui#4559, objectui#4966). No runtime behaviour changes and the emitted bundle is byte-identical; the published .d.ts does change, which is why this is a patch rather than an empty frontmatter.

.changeset/lookup-dropdown-cell-renderer-5492.md

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

  Both surfaces now call one shared module — widgets/lookupColumnDisplay.tsx, which owns column normalisation, the field-descriptor enrichment from the referenced object's schema, and the render itself. The picker's own renderCellContent and columnFieldDescriptors are now thin calls into it, so there is a single renderer left to drift from. The dropdown's extra columns are rendered into the option row itself; the row's title keeps the full option label, which is what a truncated label needs, instead of a raw-value dump.

.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-detail-8937-parent-scope-residue.md

• names RelatedList.tsx → packages/plugin-detail/src/RelatedList.tsx — edited by this change

  • packages/plugin-detail/README.md (it is in files[], so it ships). It said the node's filter is AND-combined with { [relationshipField]: parentId }, full stop. Since objectui#7299 the parent condition is compiled to match the relationship field's arity, so a multi-valued relationship gets { [relationshipField]: { $contains: parentId } } instead. The paragraph now states both spellings and names the arbiter (@objectstack/spec/data's isMultiValueField). - The claim that the SQL driver decides arity on that same predicate. It does not: driver-sql gates the equality family on its own storage question, which reads multiple as truthy on ANY type. The two rules therefore disagree for a type outside MULTI_CAPABLE_TYPES carrying multiple: true. objectui#9184 moved the arity compiler into @object-ui/core's parent-scope seam and carried the claim with it, so the correction is recorded there — the seam now states the driver's measured rule, records the divergence as a divergence, and points at the upstream card that owns which of the two rules is right (objectstack#17469). RelatedList.tsx's pointer comment and the objectui#7299 test header carried the same sentence and are corrected to match.

.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/row-predicate-record-canon-5330.md

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

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

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

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

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

.changeset/theme-clientvalidation-dead-entry-5715.md

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

  Removed the dead theme: entry from clientValidation.ts's LOADERS table, which read ThemeSchema off @objectstack/spec/ui — a symbol the spec retired upstream (objectstack#10485 / PR objectstack#10695, which deleted the whole ui/theme.zod.ts module). theme was never a registered metadata type, so metadata-admin never asked for it (objectui#5715).

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

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3095.4 KB	3104.5 KB
Main entry chunk (gzip)	148.4 KB	350 KB
Entry file	index-BDtbBmOu.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.58KB	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.61KB	133.61KB
core (index.js)	9.93KB	3.94KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	226.44KB	63.00KB
fields (index.js)	261.01KB	66.28KB
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)	228.11KB	62.72KB
plugin-kanban (index.js)	48.43KB	15.11KB
plugin-list (index.js)	115.01KB	28.49KB
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

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3095.5 KB	3104.5 KB
Main entry chunk (gzip)	148.5 KB	350 KB
Entry file	index-C9mJOteQ.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.58KB	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.60KB
core (index.js)	9.93KB	3.94KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	226.44KB	63.00KB
fields (index.js)	261.01KB	66.28KB
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.96KB	14.83KB
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)	170.35KB	42.19KB
plugin-grid (index.js)	228.11KB	62.72KB
plugin-kanban (index.js)	48.43KB	15.11KB
plugin-list (index.js)	115.01KB	28.49KB
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)	88.42KB	22.18KB
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: afed8aa6b48cc2111c2c1f9adb539d5fb779753a

① Derived judgments

• Census: reproduced. The printed instrument over the 41 numbers:

  • 215 at the branch point b2683a2c0, and 215 at current main 4f38f3928;
  • 0 at head, and 0 on the head merged with current main.

  Forms the instrument misses were also checked: bare digits, pull/N URLs, and lines hidden by the objectstack# filter. The only hit is a verbatim quote, kept on purpose. Outside the in-scope classes the PR touches only the two anchor-following pins.

• Shas: all 40 distinct shas are ancestors of current main, and the short forms are stable.

• Mapping: 30 of 41 sampled with git show. Every sha carries what its sentence cites it for, and every repaired sentence is true and grammatical. Covered:

  • date has the same two-convention split datetime just had: data-table's date-only cell keeps a year that formatDate drops #7620 ("ruling A behind c15d7eca6": the commit's own comment says "ruled A by the maintainer");
  • types: the triggerIcon tombstone's rationale contradicts mobile.ts's own retire-vs-remove discriminator, and its tripwire comment overclaims #7678 (5f8190c8c, "Part of types: the triggerIcon tombstone's rationale contradicts mobile.ts's own retire-vs-remove discriminator, and its tripwire comment overclaims #7678");
  • finding(types/plugin-chatbot): six ChatbotSchema keys are declared and read by no registration — loading, showAvatars, userAvatar, assistantAvatar, markdown, height #7703;
  • finding(types): 39 handler keys a registered renderer READS are declared by no arm — accepted and KEPT by the passthrough, on main today #7804 (three of six slices checked in full; 8d50bc2bf's nine keys add up);
  • 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 (objectui#8344 "Discharges the finding 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(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 and Switch the sharing_rule edit-door client gate on — blocked until #7603 stops the _diagnostics decoration reaching the gate #7612 (the ruling dates match their commits);
  • fix(types): ChartDataSeriesSchema declares the six series keys the renderer reads (objectui#7546) #7684;
  • [finding] CloudDeploymentConfig.environment 手写第三套环境拼写('development'|'staging'|'production'),与 spec 两个枚举均不吻合 #3720, fix(types): one authority for ActionSchema and the Breadcrumb pair #6936 and Studio metadata forms: no errors before input, translated help text, and a publish button clear of the toast #5506 (each objectstack card IS the cited thing);
  • feat(core,react): declare record.* the row-predicate canon and warn on the two deprecated spellings #5737 and feat(types): declare the 13 renderer-read keys that no shipped type declared #6945;
  • also 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, 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, 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(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, i18n(gate): bring the hand-rolled fallbackT tables into the createSafeTranslation value-compare via a declared registry #7877, 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(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 and fix(plugin-charts): put the chart min-height floor on the element Recharts measures #5503.

• Runtime strings.

  • The six ChatbotSchema tombstones are ADR-0049 retirements, measured from the retirement: the zod comment, a4611b3e2 and the pending 7703-… changeset.
  • Only 9 string lines moved; every other changed line is a comment.
  • The 7703 pin keeps its full-literal toBe(guidance) and all four remedy anchors.
  • The 10150 pin still pins the header's "the 2026-09-20 ruling".

• Blocking: the actions refusal is misclassified.

  • Special cases 7 says it "is NOT an ADR-0049 retirement", resting on 8871-page-node-refuses-breadcrumbs.md. That is a proxy, and it is misread: that changeset only says the 2026-09-09 ruling is not borrowed for breadcrumbs.
  • Measured from the retirement itself (amendment 5861311219), it IS one:
    • the arm is retirementTombstone(PAGE_ACTIONS_REFUSAL);
    • its landing 12b599219 calls it "an ADR-0049 retirementTombstone arm";
    • its own 7926-page-node-refuses-actions.md calls it "an ADR-0049 refusal arm".
  • Under ruling 5861129870 its pointer becomes (ADR-0049), the spelling its breadcrumbs sibling already uses.
  • The PR body's false sentence would land in main's squash message. This is the batch-3 aria error class.

• Deviation on 10150-author-shape-header-ruling.md: true, and within the rule.

• C0: 998 distinct numbers, 23 above 10900. #13632, #13906 and #20051 answer 404 here and 200 in objectstack; #13033 answers 404 in both.

• Changesets:

  • 55 of 55 edited frontmatters byte-identical.
  • The sweep changeset is true. Nit: @object-ui/types is listed as comment-only, though it also carries runtime text.
  • The runtime changeset follows the fix below.

② Semver level

patch for @object-ui/types: only message and description text moves. Clause-②: no stands; the sweep changeset is empty. ⛔ Not major.

③ Boundary flags

• CI on head: 40 success, 3 skipped, 0 failure; final.
• git merge-tree against main 4f38f3928: clean.
• Open PRs:
  • trial merges with objectui#10890, objectui#10888, objectui#10886 and objectui#10891 are clean;
  • objectui#10278's conflicts are the same region as against main alone, outside this diff's lines.
• check-governed-merges --pr was refused with HTTP 403 on page 2 of the file list (as in batch 3). The same predicate via --test over the 106 paths: NOT GOVERNED, with a lit control.
• Draft, assigned to os-elon-musk.
• The commit trailers carry no model identifier.

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

VERDICT: FAIL

The actions refusal takes (ADR-0049) (the seat rules option (a)), with the runtime changeset and the PR body's Special cases 7 following. The optional package-list nit rides the same commit.

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 8255f14f475331b51951f23e46a3641aab316f7b

This is an in-seat delta review of fix round 1 (afed8aa6b to 8255f14f4, one text-only commit), against record 5863489805 (FAIL, one item).

① Derived judgments

• The actions refusal: fixed, as the seat ruled (option a). PAGE_ACTIONS_REFUSAL in layout.zod.ts now reads "never was (ADR-0049): no renderer reads it", the spelling its breadcrumbs sibling already uses. It is measured from the retirement itself:
  • the retirementTombstone arm;
  • the landing 12b599219;
  • 7926-page-node-refuses-actions.md.
• .changeset/10803-fifth-batch-runtime-strings.md carries the ruling's exact wording in both sentences: "the six tombstones keep ADR-0049 … the actions tombstone cites ADR-0049 in its place, and the one description simply drops its pointer", and the actions bullet. The frontmatter md5 is unchanged.
• The optional package-list nit: taken. @object-ui/types is marked "(whose runtime text is declared separately below)", with frontmatter unchanged.
• Nothing else moved: 3 files, 9 insertions and 6 deletions.
  • page-actions-refusal-7926 pins only remedy words ('actions', 'children', 'page:header'), and the dev read it rather than assuming. No test or doc quotes "never was: no renderer".
  • The seven related pin files pass (134 tests).
  • C4 still reads 44 identical plus 5 equal after 19 listed substitutions.
  • The census is 0 at head and 0 merged with current main.
• The PR body r2 (applied with this landing) carries Special cases 7 in the seat's text, the table's "after" cell with (ADR-0049), and a re-read census and Held section. Line 1 is Part of #10803, and there is no closing keyword.

② Semver level

patch for @object-ui/types (message text only), and an empty sweep changeset. Clause-②: no. ⛔ Not major.

③ Boundary flags

• CI: the landing waits for every check-run on this head to be final and green, and re-runs git merge-tree against current main first.
• Open PRs: trial merges are clean with every one except objectui#10278, whose conflicts are the same region as against main alone. New objectui#10896 shares ObjectGrid.tsx and ListView.tsx and merges clean. No open PR holds layout.zod.ts.
• NOT GOVERNED (--test over the 106 paths).
• Draft, assigned to os-elon-musk.

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

VERDICT: PASS