docs(types,components): date the dead bridgeListView producer evidence instead of letting it read as live (#9365)

[os-sales]

Fixes #9365

Clause-②: no

Three docblocks described bridgeListView — a producer objectui#6366 retired as a declared BREAKING CHANGE — in the PRESENT tense (assigns, already writes), one of them as the stated factual basis of objectui#4580's revised Q1 ruling. Nothing re-derives those sentences and nothing can, which is the shape AGENTS.md #9 forbids. This is a paper-trail repair: nothing executable moves and objectui#4580 is not re-litigated.

Per-site verdict — established at the WRITE-TIME ref, per SITE

git log -S named one write-time ref for all three sentences: c1d939f7f — "fix(types): one SchemaNode and one label vocabulary" (#4580, PR #4608), 2026-08-13. Reading the tree AT that ref is what rules BORN FALSE out, and it rules it out byte-exactly.

site (addressed by symbol)	verdict	established at which ref, and on what reading	repair taken
BaseSchema.label docblock — packages/types/src/base.ts	ROTTED	c1d939f7f: that tree carries export const bridgeListView in packages/react/src/spec-bridge/bridges/list-view.ts, and the cited line is exactly if (spec.label) node.label = spec.label;	sentence KEPT, quoted and dated to its write-time ref, followed by a dated note naming the falsifier; the assertion now points at an instrument
BaseSchema.description docblock — same file	ROTTED	c1d939f7f: the cited line in the same module is exactly if (spec.description) node.description = spec.description;	same
header docblock of packages/components/src/__tests__/inline-locale-label-read-sites.test.tsx	ROTTED	c1d939f7f — the same commit wrote all three sentences	same
the column-spelling comment in packages/plugin-grid/src/ObjectGrid.tsx	NOT ROTTED — measured, not assumed	read WHOLE on 20b5e361e	none. "The one in-repo producer that spoke it, bridgeListView in @object-ui/react, was migrated in the same PR" is a PAST-tense account of objectui#5068's migration. It was true when written and it is true now.
the retired-witness comment at the tail of packages/plugin-grid/src/__tests__/gridNonAuthorKeys.test.tsx	CORRECT	read WHOLE on 20b5e361e	none. It already records the objectui#6366 retirement in the past tense.

⇒ the card's "three rotted / two probably fine" split — which the card itself flagged as a one-line-of-grep-context reading — survives a whole-docblock re-read. None of the five is BORN FALSE, and all three repairs are the ROTTED route (keep + date + name the falsifier), not the correction route.

The falsifier, dated: bf283414f — "refactor(react): retire the spec-bridge — SpecBridge, bridgeListView, bridgeFormView (#6366) (#6632)", 2026-08-29. .changeset/retire-spec-bridge-6366.md declares it BREAKING and removes the public exports outright, so the producer, its module and the addresses the sentences cite are all gone.

What the docblocks assert now. The declared face is re-derived on every run by inline-locale-declared-face-9092.test.ts in packages/types (both tsc -p packages/types/tsconfig.test.json and vitest read it); the read side by the renderer pins in @object-ui/components and @object-ui/plugin-dashboard. No figure is written down — the instrument is named instead (AGENTS.md #9). ⛔ No new gate, probe or citation was added: the only path:line addresses in the diff are the two the dead sentences already carried, kept verbatim inside the quotation.

Measurement — the quotation trap, taken head on

⭐ A count is invariant under quotation, and the ROTTED route quotes what it retires. So the token and the rot PHRASE were each read in ASSERTION position and in QUOTED position, separately, with a whitespace-tolerant scanner over whole file contents (* prefixes stripped, line wraps joined) rather than a line-anchored git grep. Corpus: every git-tracked file under packages/, CHANGELOG.md excluded.

reading (source files, CHANGELOG excluded)	BEFORE (assertion / quoted)	AFTER (assertion / quoted)
token bridgeListView	5 / 0	5 / 3
phrase "bridgeListView assigns" (wrap-tolerant)	3 / 0	0 / 3
phrase "producer already writes" (wrap-tolerant)	2 / 0	0 / 2
LIT CTRL token SchemaRenderer, same instrument, same corpus	3473 / 5	3473 / 5
ABSENT CTRL a minted token	0 / 0	0 / 0

Read the bare token row as the trap it is: it goes UP, because the repair's own dated notes name the three retired exports. The reading that answers the card is the PHRASE in ASSERTION position: 3 to 0 and 2 to 0, with every one of those occurrences still present in quoted position, which is the ROTTED route working as intended.

⚠️ And the wrap-tolerance is load-bearing rather than ceremonial: the test-header sentence wraps between bridgeListView and assigns, so a line-anchored probe reads 2 where the truth is 3.

Whole-tree population. 11 mentions across 5 files, not the card's 5 across 4. The extra six are all in packages/react/CHANGELOG.md — published release history, past tense, CORRECT, and ⛔ untouched.

Gates and tests — every exit code captured to a file BEFORE any pipe

run	exit	reading
check-changeset-presence	0	"2 source file(s) of 2 released package(s) changed, and this change declares 1 changeset(s)"
check-changeset-overwrite · check:changeset-claims · check:pending-changeset-literals · check-changeset-no-major · check-changeset-fixed	0 each	—
check:control-bytes	0	—
check:new-line-citations	0	"VERDICT new-cross-file-line-citations: 0 new citation(s)" — the quoted addresses are byte-identical, so the multiset does not move
check-governed-queue-guard --self-test	0	and --test on the three paths: "NOT GOVERNED — 3 path(s) checked against 5 governed surface(s); none matched"
check:doc-component-types	0	it reads packages/types/src/base.ts; "Every documented component type is registered"
pnpm --filter @object-ui/types type-check	0	tsc --noEmit + tsconfig.examples.json + tsconfig.test.json
pnpm --filter @object-ui/types test	0	Test Files 203 passed (203) · Tests 4762 passed (4762)
pnpm --filter @object-ui/components type-check	0	tsc --noEmit + tsconfig.test.json, after building that package's dependency closure
pnpm exec vitest run packages/components/src/__tests__/inline-locale-label-read-sites.test.tsx	0	Test Files 1 passed (1) · Tests 9 passed (9)
the three scripts/__tests__/ suites that read either changed file	0	Test Files 3 passed (3) · Tests 57 passed (57)

Every heavy run went through the container's shared verify lock; each one printed VERDICT command-exit 0.

NOT MEASURED, with reasons. check:doc-example-types exited 2 = PREREQUISITE NOT MET: it needs every package's dist on disk (a whole-monorepo turbo build). It is a repo-level scan and CI's run; a comment-only diff moves no type it reads. @object-ui/types's dependency closure build is empty — pnpm --filter "@object-ui/types^..." build selects no workspace package with a build script — so step ① is a no-op for that package and was run for real for @object-ui/components.

Declared narrowings. eslint --no-inline-config was run on the two changed files only, from the flat config that owns the population (eslint.config.js, whose lint population is **/*.{ts,tsx} minus its ignores block): 2 files linted (count read from --format json), 0 errors, 21 warnings, ALL of them pre-existing @typescript-eslint/no-explicit-any — base.ts reads 20 warnings both on origin/main and here. No type-aware linting is configured (no project / projectService in eslint.config.js), so a comment-only diff cannot move the verdict on any file it does not touch. Repo-wide pnpm lint is CI's run. The full @object-ui/components suite is likewise CI's; the changed file there is a header comment and the file itself was run.

⚠️ One declared deviation from the dispatch word — the changeset is patch, not empty

The dispatch asked for EMPTY frontmatter on the ground that no package moves. Measured, it does. @object-ui/types publishes files: ["dist", ...], and after pnpm --filter @object-ui/types build the repaired prose is in packages/types/dist/base.d.ts (2 hits for the new dated note; POSITIVE CONTROL: 2 hits for neighbouring prose known to ship; ABSENT CONTROL: a minted token, 0 hits, exit 1). Published bytes therefore move, and .changeset/9375-base-i18n-vocabulary-docblock.md — the same file, the same class of comment-only repair — graded itself patch for exactly this reason. So this PR declares '@object-ui/types': patch and states the conflict rather than picking a side quietly. The components-side change is a test header, which reaches no tarball (tsconfig.json excludes **/__tests__/**), and is owed no declaration of its own.

Out of scope, deliberately

• ⛔ The bridgeFormView / SpecBridge sweep the card names as the obvious next question was not run and is not widened into here.
• ⛔ packages/react/CHANGELOG.md is untouched.
• ⛔ No label was added, removed or changed on this PR or on the card.

---

Generated by Claude Code

[github-actions]

changeset-claim-re-read

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

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

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

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

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

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

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

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

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

.changeset/6067-component-meta-derive-from-canonical.md

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

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

.changeset/7088-hidden-jsdoc-single-hide-path.md

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

  Why a comment was worth a changeset: the JSDoc is the authority a later docs correction is measured against, and this one nearly propagated. While splitting the schema-reference hidden row, a reader checked it against base.ts and almost "corrected" the table's "Inverse of visible" — the half that describes shipped behaviour — toward the declaration. That row is unchanged and stays. SchemaRenderer.hiddenVisibleSynonymy.test.tsx now pins the claim the comment makes: the two keys produce the same rendered output, and hidden: true leaves no node that could carry a visibility style.

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

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

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

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

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

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

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

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

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

.changeset/componentinput-reexport-4972.md

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

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

.changeset/default-children-retired-5051.md

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

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

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

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

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

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

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

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

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

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

Not covered, stated so nobody reads this as more: a claim that was born false (a changeset this change adds is excluded by construction), 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 20b5e361e (merge-base with origin/main): 2 file(s) changed outside .changeset/, read against 1132 pending declaration(s) that publish a body (1645 pending in total). · run

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3049.2 KB	3104.5 KB
Main entry chunk (gzip)	145.7 KB	350 KB
Entry file	index-DnyzLIkC.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.69KB	6.21KB
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)	25.05KB	9.16KB
auth (AuthContext.js)	0.31KB	0.24KB
auth (AuthGuard.js)	2.07KB	1.00KB
auth (AuthProvider.js)	40.18KB	10.59KB
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.41KB	1.23KB
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.46KB	3.43KB
auth (index.js)	3.19KB	1.44KB
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)	26.08KB	7.56KB
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)	545.93KB	130.69KB
core (index.js)	8.94KB	3.59KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	215.98KB	59.97KB
fields (index.js)	249.27KB	62.92KB
i18n (LocalizationContext.js)	1.76KB	0.96KB
i18n (builtinAggregateLabels.js)	0.86KB	0.49KB
i18n (currency.js)	1.22KB	0.64KB
i18n (fallbackInterpolation.js)	6.25KB	2.77KB
i18n (i18n.js)	8.87KB	3.64KB
i18n (index.js)	5.22KB	2.26KB
i18n (pickLocalized.js)	9.86KB	3.95KB
i18n (provider.js)	32.15KB	10.49KB
i18n (useDisplayLocale.js)	2.85KB	1.45KB
i18n (useObjectLabel.js)	34.34KB	9.17KB
i18n (useSafeTranslation.js)	5.60KB	2.33KB
layout (index.js)	38.83KB	10.95KB
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)	2.53KB	0.85KB
mobile (useResponsive.js)	0.72KB	0.42KB
mobile (useSpecGesture.js)	4.39KB	1.66KB
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.39KB	3.10KB
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)	14.81KB	3.63KB
plugin-calendar (index.js)	49.92KB	14.22KB
plugin-charts (index.js)	71.49KB	19.99KB
plugin-chatbot (index.js)	195.34KB	46.51KB
plugin-dashboard (index.js)	131.44KB	34.65KB
plugin-designer (index.js)	215.94KB	44.33KB
plugin-detail (index.js)	253.29KB	65.88KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	136.71KB	34.16KB
plugin-gantt (index.js)	167.62KB	41.26KB
plugin-grid (index.js)	212.64KB	57.91KB
plugin-kanban (index.js)	48.10KB	14.94KB
plugin-list (index.js)	112.73KB	27.69KB
plugin-map (index.js)	21.48KB	6.99KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	43.41KB	11.93KB
plugin-timeline (index.js)	30.07KB	8.74KB
plugin-tree (index.js)	10.58KB	3.72KB
plugin-view (index.js)	85.04KB	21.01KB
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.66KB	3.50KB
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)	104.82KB	34.67KB
react (data-invalidation.js)	5.05KB	2.08KB
react (index.js)	4.63KB	2.18KB
react (schema-input.js)	4.25KB	2.04KB
react (spec-input.js)	0.20KB	0.18KB
sdui-parser (codegen.js)	6.58KB	2.74KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	5.66KB	2.50KB
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.66KB	1.82KB
sdui-parser (types.js)	0.28KB	0.23KB
sdui-parser (validate.js)	14.82KB	4.99KB
types (ai.js)	4.11KB	2.06KB
types (api-types.js)	0.20KB	0.18KB
types (app.js)	2.87KB	1.00KB
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.25KB
types (layout.js)	0.20KB	0.18KB
types (managed-by.js)	0.19KB	0.18KB
types (mobile.js)	4.73KB	2.28KB
types (navigation.js)	0.20KB	0.18KB
types (objectql.js)	0.20KB	0.18KB
types (overlay.js)	0.20KB	0.18KB
types (permissions.js)	0.20KB	0.18KB
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)	14.04KB	5.36KB
types (system-fields.js)	3.33KB	1.54KB
types (theme.js)	6.28KB	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