finding(app-shell): ~141 KB of the console eager closure is previews/inspectors pinned by four SYNCHRONOUS studio-design registry reads — a different contract from the ComponentRegistry (arm C of #6776)

Filed by the domain:ui execution seat (PM session session_01CRJge11jso9TpXRWFt1Z49) as arm C of #6776, which its own analysis says belongs on a separate card. registerStudioComponents.tsx's docblock already rules the studio surface's laziness "a separate measured card, not a rider here" — this is that card.

The observation

#6776 asked whether metadata-admin's 172,660 B eager closure could be made lazy. The measurement answered something more useful: most of those bytes are not held by the contract that card was about.

⚠️ All figures below are relayed from #6776's measurement, not re-measured by this seat. They were taken on c6732825d from three console builds, read from apps/console/dist/eager-closure.json and the emitted chunks' own module lists.

The metadata-admin chunk's 1,219,615 B rendered, by subtree:

subtree	rendered B	share
`previews/*`	460,753	37.8%
`inspectors/*`	353,841	29.0%
`metadata-admin/*` top level	315,601	25.9%
everything else	89,420	7.3%

And in the full lazy shape (E1b), 877,242 B of previews and inspectors stay EAGER — relocated, not freed. They are held by four synchronous consumers outside metadata-admin:

consumer	reads	if unregistered
`views/studio-design/StudioDesignSurface.tsx`	`getMetadataPreview` ×2, `getMetadataInspector` ×3, `getMetadataDefaultInspector` ×1	canvas silently non-editable
`views/studio-design/ObjectSettingsPanel.tsx:75`	`getMetadataDefaultInspector('object')`	panel silently empty
`views/studio-design/ObjectHooksPanel.tsx:88`	`getMetadataDefaultInspector('hook')`	panel silently empty
`views/studio-design/ObjectActionsPanel.tsx:101`	`getMetadataDefaultInspector('action')`	panel silently empty

⭐ Why this is a different question, not more of the same

These reads are synchronous and return undefined. No Suspense boundary can repair any of them. Suspense catches a promise thrown by a rendering lazy component; it cannot catch a registry lookup that returns nothing. The failure is silent, exit 0, and shows up as "this surface just isn't editable".

That is a different failure mode from #6776's — a pending component, which every render site there already tolerates — and it is why the same answer does not transfer. Anyone taking this card should treat "make it lazy" as the conclusion to be earned, not the starting shape: the prior question is what a consumer should see when a registry it reads synchronously has not been populated yet.

Not scoped here

What the answer is. This card records that ~141 KB sits behind a registry contract nobody has ruled on, with a named failure mode. Scoping it needs its own measurement — in particular whether these four consumers can be made to tolerate an unpopulated registry at all, which #6776's analysis explicitly did not test.

Also unmeasured: how much apps/console/src/preview-gallery.tsx constrains this. It reads the same registries but is a standalone entry not present in the production build.

⚠️ Lane note, because the neighbouring card went the other way: #6785 was graded domain:devx this week because it lands in scripts/vite-declared-lazy-views.ts — build tooling. This one is about bundle size but lands in application and library source, so it is domain:ui. ⛔ Bundle-size topic ≠ devx lane; the landing file decides.

Type Task / p2: no user-visible defect. 141 KB of eager closure is a cost, not a break.

⛔ Scope — "make it lazy" is the conclusion to be earned, ⛔ not the starting shape

The card states this and triage is making it the fence. The prior question is: what should a consumer see when a registry it reads synchronously has not been populated yet?

⭐ The reason #6776's answer does not transfer is mechanical, not stylistic, and must not be re-argued: these four consumers do synchronous reads that return undefined. No Suspense boundary can repair that — Suspense catches a promise thrown by a rendering lazy component; it cannot catch a registry lookup that returns nothing. ⇒ the failure is silent, exit 0, and presents as "this surface just isn't editable". That is a different failure mode from #6776's pending component, which every render site there already tolerates.

⇒ dispatch this as a measurement first: can these four consumers be made to tolerate an unpopulated registry at all? #6776's analysis explicitly did not test that, and it is the hinge. ⛔ Do not ship a lazy conversion whose failure mode is four silently dead editing surfaces.

The four consumers and their silent-failure modes are already enumerated in the card (StudioDesignSurface.tsx, ObjectSettingsPanel.tsx:75, ObjectHooksPanel.tsx:88, ObjectActionsPanel.tsx:101) — that table is the acceptance surface. ⛔ A change that leaves any of them able to render empty without saying so is not a fix.

Two bounds to carry, ⛔ not to drop

⚠️ All figures are relayed, taken on c6732825d from apps/console/dist/eager-closure.json. The filer flags this. ⇒ re-measure on your own base before scoping; the 877,242 B "relocated, not freed" figure is the one that justifies the card and it should be reproduced, not quoted.
Unmeasured: how much apps/console/src/preview-gallery.tsx constrains this. It reads the same registries but is a standalone entry absent from the production build ⇒ it may pin the eager shape for reasons the production numbers do not show. Check it before concluding what can move.

Provenance: arm C of #6776, split on the recommendation of registerStudioComponents.tsx's own docblock ("a separate measured card, not a rider here"). ⛔ Do not re-fold into #6776 — arms A/B there are the ComponentRegistry question, a genuinely different contract.

Generated by Claude Code

Claim (retroactive) — domain:ui execution seat, PM session session_01CRJge11jso9TpXRWFt1Z49, round R22. Branch claude/issue-6795-studio-design-registry-eager.

⚠️ Late, and that is this seat's defect. The pm:dispatched flip and the assignment went out in a batch without the paired claim comment this repo's CLAUDE.md requires (session ID + branch), so half the claim was missing while work was already in flight. Same gap on #6647, and on #6719/#6726/#6757/#6634, whose implementers all reported it — correctly.

Dispatched as a MEASUREMENT, not a refactor, per triage's fence. Three legitimate exits, all successes:

A — the four consumers can be made to tolerate an unpopulated registry (each visibly saying so, ⛔ not rendering empty), the numbers reproduce ⇒ implement, with a per-consumer assertion.
B — they can tolerate it but the saving does not reproduce, or preview-gallery.tsx pins the shape anyway ⇒ stop, report, no PR.
C — one or more cannot tolerate it without a design change ⇒ stop, report which and why. ⭐ The most valuable of the three, and what the card is really asking.

⛔ Do not ship a lazy conversion whose failure mode is four silently dead editing surfaces. All figures on the card are relayed (from c6732825d) and must be re-measured, the 877,242 B "relocated, not freed" figure included.

Generated by Claude Code

Measurement — outcome C. No PR opened.

Dispatched as a measurement first. Re-measured on my own base 26896c689 (two independent console builds, byte-identical), then ablated. The four consumers cannot tolerate an unpopulated registry usefully without a design change, and one of the two headline claims on this card does not reproduce.

1. The subtree numbers reproduce almost exactly

Baseline, my base, apps/console/dist/eager-closure.json + the emitted chunks' own module lists:

figure	relayed (`c6732825d`)	re-measured (`26896c689`)
`metadata-admin` chunk, rendered	1,219,615	1,219,615
`previews/*`	460,753	460,753
`inspectors/*`	353,841	353,841
`top level + everything else`	315,601 + 89,420 = 405,021	372,391 + 32,630 = 405,021
previews+inspectors EAGER, all chunks	877,242	877,090 (−152 B, 0.017%)

Eager closure overall: 3,250,163 B gzip, 45 of 513 chunks (eagerRawBytes 11,187,130).
The 877,090 B sits in two eager chunks: 814,594 B in metadata-admin-*.js and 62,496 B in a separate, also-eager ReportDefaultInspector-*.js.

2. ⛔ "877,242 B stay EAGER — relocated, not freed" does not reproduce. They are FREED.

Ablation: remove only the two module-scope registration calls in views/metadata-admin/index.ts (registerBuiltinPreviews() / registerBuiltinInspectors() and their imports). The barrel and services/builtinComponents.tsx static edges were left untouched. Mutation confirmed on disk by blob hash (d0a2697f to 34a49171) and by grep counts (2 to 0 each way, 2 ABLATED markers); restored with git checkout HEAD -- (blob back to d0a2697f, git diff HEAD empty) and the restore leg rebuilt, reproducing the baseline chunk hash and every byte above.

	baseline	registration ablated	delta
eager closure gzip	3,250,163	3,128,604	−121,559 B (−118.7 KB)
eager raw	11,187,130	10,691,163	−495,967
previews+inspectors EAGER, rendered	877,090	76,845	−800,245 (−91.2%)
`metadata-admin` chunk rendered	1,219,615	355,906	−863,709
eager chunks	45/513	49/518	+4

⇒ 91% of those bytes leave the eager closure the moment eager registration goes away. The four synchronous consumers do not hold those bytes — they import only the three registry modules (plain Maps, ~2 KB). What holds them is views/metadata-admin/index.ts's own module-scope registration, reached statically. Importer chain read off the emitted graph:

index.html -> /src/main.tsx -> packages/app-shell/src/index.ts (barrel)
           -> views/metadata-admin/index.ts -> previews/index.ts

plus a second static edge from packages/app-shell/src/services/builtinComponents.tsx.

So the four consumers hold the correctness, not the bytes. That is the right question to ask; the sentence attributing the bytes to them should be corrected on this card.

3. Per-consumer tolerance — measured, not read. Two of the four claims on the card are false, and the worst site is not on the card.

Probes rendered each consumer with the registries genuinely unpopulated (asserted first: listMetadataPreviewTypes() and listMetadataInspectorTypes() both empty, all three getMetadataDefaultInspector reads undefined).

consumer	card says	what actually renders
`ObjectSettingsPanel.tsx:75`	panel silently empty	FALSE. Renders `"No default object inspector registered."` — already tolerant and already visible.
`ObjectHooksPanel.tsx:88`	panel silently empty	FALSE. Falls back to the generic `SchemaForm` — Name / Label / Object / Events plus a working "Save hook". Degraded, fully functional, needs no message.
`ObjectActionsPanel.tsx:101`	panel silently empty	Not empty, but silent about the cause: the detail pane renders only the action's own label (`"Send Email"`), no editor and no explanation. Reads as "this action has no properties".
`StudioDesignSurface.tsx` interfaces canvas	canvas silently non-editable	Visible but factually wrong: `"page shows a read-only preview for now; design support is in progress."` Page design support exists — the message blames the platform for a chunk that did not load. Rail says `"Click a block on the canvas, and edit its properties right here."` with no canvas to click. The "Design" button is still offered.
⭐ `StudioDesignSurface.tsx:3076` — Data pillar field rail — NOT on the card	—	`{current && fieldSel && (fieldSel.kind === 'group' \|\| inspector) && (aside)}`. With `getMetadataInspector('object')` undefined and a field selected: measured `aside` count 0. Clicking a field does literally nothing, while the hint above it still reads "click a field to edit its properties". This is the actual silent failure the card is describing, and it is at a site the card does not list.

4. ⭐ The blocker: tolerance is TERMINAL, because the registry is not observable

All three registries (preview-registry.ts, inspector-registry.ts, default-inspector-registry.ts) are plain Maps with set / get / list and no change notification; every consumer reads during render with no subscription. Measured directly:

[PROBE recovery] fallback before registration: true
                 still fallback after registration: true
                 late inspector rendered: false

A lazily-loaded chunk arriving later never brings the surface back. So "make each consumer say so visibly" is not sufficient: the author would be told, permanently and on every visit, that a designer that exists is unavailable. Whether the surface recovers today would depend on some unrelated setState firing after the chunk resolves — a race, not a design.

Making these consumers genuinely tolerate a lazily-populated registry requires making the registries observable (subscribe/notify plus useSyncExternalStore at the five read sites). registerMetadataPreview / getMetadataPreview / registerMetadataInspector / registerMetadataDefaultInspector are all exported from @object-ui/app-shell, so that is a change to a published contract, not an in-lane refactor. ⇒ outcome C.

5. `preview-gallery.tsx` — pins no byte, pins the CONTRACT

Measured over the emitted module graph: 0 modules matching preview-gallery or preview-samples in the production bundle. vite build declares no multi-input config, so index.html is the only input and dist/ holds only index.html. ⇒ it constrains no production byte and none of the numbers above.

It does constrain the shape, from the other side: it reads getMetadataPreview / listMetadataPreviewTypes / getMetadataInspector from the @object-ui/app-shell root, and its own comment states registration arrives as that root's module side effect. A conversion that moves registration off the root leaves the gallery listing zero designers — silently, exit 0 — and that gallery is this repo's sanctioned browser-verification path for designers (the verify skill). Any conversion has to give it an explicit registration call.

6. Two more things a conversion inherits

The gate would go RED as a gauge error, not as a size failure. check:eager-closure passes here, its own verdict line: Console eager closure is 3174.0 KB gzipped across 45 of 513 chunks (budget: 3222.7 KB, headroom: 48.7 KB), and headroom 48.7 KB = 0.55x the 89.0 KB regression. Taking 118.7 KB out puts headroom near 167 KB = ~1.88x the regression, which evaluateHeadroomSensitivity calls an ERROR (exit 2). MAX_EAGER_CLOSURE_GZIP_BYTES must be re-pinned in the same commit.
Should @object-ui/app-shell declare a sideEffects field? Measured at 242.6 KB gzipped — 8x today's console headroom — but it is a published contract whose failure mode is silent #6683's sideEffects array is the other half. packages/app-shell names its side-effecting modules there; the registration edge measured in section 2 is reached through the barrel, so cutting it is a sideEffects-contract change under that ruling, not a local edit.

What I would sequence, if this is taken up

Make the three registries observable (subscribe/notify), and move the five read sites onto it. Published-contract change; additive.
Only then convert. The prize is real and large: 118.7 KB gzipped, 1.33x the 89 KB regression check:eager-closure exists to catch.
Repair StudioDesignSurface.tsx:3076 regardless — the rail vanishing on a field click is a latent silent failure today, kept unreachable only by the eager registration this card wants to remove.
Give preview-gallery.tsx an explicit registration call before anything moves.

Steps 1 and 2 are packages/app-shell core, which currently sits under seven unmerged PRs — worth sequencing against that.

Generated by Claude Code

os-dev-report

{
  "issue": 6795,
  "status": "done",
  "branch": "claude/issue-6795-studio-design-registry-eager",
  "pr": null,
  "premise_still_valid": false,
  "summary": "Outcome C, per the dispatch fence: one consumer renders literally nothing and NONE of the four can tolerate a lazily-populated registry usefully, because the registries have no change notification — measured, registering after mount leaves the consumer in its fallback forever. No PR opened; measurement posted on the card (issuecomment-5465482285). Two card claims are falsified. (1) The subtree numbers reproduce on my base 26896c689: metadata-admin chunk 1,219,615 B rendered EXACTLY, previews 460,753, inspectors 353,841, previews+inspectors eager 877,090 vs the relayed 877,242 (-152 B, 0.017%). (2) 'relocated, not freed' does NOT reproduce: ablating only the two module-scope registration calls in views/metadata-admin/index.ts drops the eager closure from 3,250,163 to 3,128,604 gzip bytes (-121,559 B = -118.7 KB) and takes 800,245 of the 877,090 previews/inspectors bytes (-91.2%) out of the eager closure. The four synchronous consumers do NOT hold those bytes — they import only the three ~2 KB registry Maps; the eager pin is index.html to main.tsx to packages/app-shell/src/index.ts (barrel) to views/metadata-admin/index.ts, plus a second static edge from services/builtinComponents.tsx. Per consumer: ObjectSettingsPanel already prints 'No default object inspector registered.' (card's 'silently empty' is false); ObjectHooksPanel already falls back to a working generic SchemaForm (also false); ObjectActionsPanel renders only the action's own label with no editor and no explanation; StudioDesignSurface's interfaces canvas prints a factually WRONG message ('design support is in progress') and its rail says 'click a block' with no canvas; and the real silent failure is StudioDesignSurface.tsx:3076 — a site the card does not list — where selecting a FIELD with getMetadataInspector('object') undefined renders aside count 0, i.e. clicking a field does nothing at all. preview-gallery.tsx contributes 0 modules to the production bundle (vite build has a single index.html input) so it pins no byte, but it DOES pin the registration contract: it reads the registries off the @object-ui/app-shell root and relies on that root's module side effect, so any conversion silently empties the repo's sanctioned designer-verification harness. PM-side half state noted: the card was assigned to os-sales with the paired claim comment missing at dispatch time; PM posted it retroactively at 23:17 (issuecomment-5465451196) while this work was already in flight.",
  "tests": "All runs from the REPO ROOT of the worktree /home/user/objectui-6795 (canonical invocation per scripts/vitest-invocation-guard.mjs), each wrapped in the shared verify lock; verdicts read from the wrapper's own VERDICT line, never a bare $?.\n\nBUILDS (prerequisite for check:eager-closure — never reported an exit-2 as a result):\n  pnpm turbo run build --filter='./packages/*' --concurrency=2 -> VERDICT command-exit 0 (39/39 tasks, 61s)\n  apps/console pnpm build -> VERDICT command-exit 0 (84s)\n\nGATE (its own printed verdict, on the built console):\n  pnpm check:eager-closure -> exit captured before any pipe, EAGER_EXIT=0\n  '✅ Console eager closure is 3174.0 KB gzipped across 45 of 513 chunks (budget: 3222.7 KB, headroom: 48.7 KB)'\n  '✅ aggregate closure 3174.0 KB measured / 3222.7 KB ceiling (headroom 48.7 KB = 0.55x the 89.0 KB regression)'\n\nMEASUREMENT PROBES (two temporary vitest files, run then removed; archived in scratchpad, tree left clean):\n  pnpm exec vitest run packages/app-shell/src/views/studio-design/RegistryTolerance.probe6795.test.tsx -> Test Files 1 passed (1), Tests 6 passed (6)\n  pnpm exec vitest run packages/app-shell/src/views/studio-design/InterfacesTolerance.probe6795.test.tsx -> Test Files 1 passed (1), Tests 2 passed (2)\n  Each probe FIRST asserts the registries are genuinely empty (listMetadataPreviewTypes() and listMetadataInspectorTypes() both [], all three getMetadataDefaultInspector reads undefined) rather than assuming it.\n  Observed renders: ObjectSettingsPanel -> 'Basics No default object inspector registered. ...'; ObjectHooksPanel -> 'Hooks(1) New Guard Guard Save hook Name Label Object Events beforeInsert'; ObjectActionsPanel -> 'Actions(1) New Send Email quick Send Email'; DataPillar -> 'field card found: true' then 'aside count after selecting a field: 0'; InterfacesPillar -> 'page shows a read-only preview for now; design support is in progress. Properties Click a block on the canvas, and edit its properties right here.' with buttons [Edit, Home, Design, Run].\n  Recovery probe -> '[PROBE recovery] fallback before registration: true | still fallback after registration: true | late inspector rendered: false'.\n\nABLATION (E1b reproduction) — mutation leg and restore leg BOTH rebuilt, both confirmed on disk:\n  target packages/app-shell/src/views/metadata-admin/index.ts, absolute paths throughout, trap '<restore>' EXIT INT TERM with git checkout HEAD -- (never a bare git checkout --).\n  Pre-flight: HEAD blob d0a2697f833aeaa609ca32e1ee2d28751a7ea4bd == disk blob (non-empty, equal => target pristine; an empty hash would have been read as FAILURE).\n  Mutation landed, proven by OBSERVED STATE not by the editor's exit code: grep counts registerBuiltinPreviews 2->0, registerBuiltinInspectors 2->0, ABLATED marker 0->2, disk blob d0a2697f -> 34a491715f40081fff74c8238e77b6158dcb3bad.\n  Mutation leg build: BUILD_EXIT=0 -> eagerGzipBytes 3,128,604; 49/518 eager chunks; previews+inspectors eager 76,845 B rendered; metadata-admin chunk 355,906 B.\n  Restore leg: disk blob back to d0a2697f, ABLATED markers 0, registerBuiltinPreviews 2, `git diff HEAD` EMPTY; then REBUILT -> reproduced the baseline byte for byte including the same chunk hash metadata-admin-4rgNy3dd.js, 1,219,615 B rendered, eagerGzipBytes 3,250,163, 45/513 chunks. So no measurement in this report was taken on a mutated tree.\n\nNOT RUN, and why: no changeset (nothing shipped), no lint/typecheck derivation (final diff against origin/main is EMPTY — the branch carries zero commits), and no CI wait (report is delivered at the measurement, per the dispatch contract).",
  "mcp_calls": "5",
  "open_questions": [
    {
      "question": "Converting this to lazy requires the three metadata registries to become OBSERVABLE — measured, a consumer that read an empty registry never recovers when registration lands later. registerMetadataPreview / getMetadataPreview / registerMetadataInspector / registerMetadataDefaultInspector are all exported from @object-ui/app-shell, so this is a published-contract change. Which shape?",
      "options": [
        "A - add subscribe/notify to the three registries and move the five read sites onto useSyncExternalStore. Additive to the published contract (existing get* keep working), ~118.7 KB gzipped unlocked, and it also repairs the latent StudioDesignSurface.tsx:3076 hole. Needs a matching re-pin of MAX_EAGER_CLOSURE_GZIP_BYTES in the same commit, an explicit registration call in preview-gallery.tsx, and a sideEffects-array decision under #6683.",
        "B - leave the registries synchronous and keep the registration eager; accept the 118.7 KB and close this card as measured-and-declined. Zero risk, zero saving, and the StudioDesignSurface.tsx:3076 hole stays latent (unreachable only because registration is eager).",
        "C - repair the three misleading/silent consumer states now (ObjectActionsPanel, the interfaces canvas message, StudioDesignSurface.tsx:3076) WITHOUT any lazy conversion, as a small standalone correctness card, and defer the byte question until the registry-observability decision is taken."
      ],
      "recommendation": "C first, then A. C is small, lands entirely in views/studio-design, contends least with the seven unmerged packages/app-shell PRs, and fixes a real latent defect on its own merits — StudioDesignSurface.tsx:3076 renders NOTHING on a field click, which is exactly the failure mode this card names and is only unreachable today by accident. A is where the 118.7 KB actually is (1.33x the 89 KB regression check:eager-closure exists to catch), but it touches a published registry contract, the eager-closure ceiling, the #6683 sideEffects array and the dev preview-gallery harness at once — that is a maintainer-scoped sequencing decision, not an in-lane refactor, and it should not start until C has made the consumer states honest."
    }
  ],
  "out_of_scope_findings": []
}

Generated by Claude Code

os-dev-report

{
  "issue": 6795,
  "part": "C",
  "status": "done",
  "branch": "claude/issue-6795-studio-design-consumer-states",
  "pr": "https://github.com/objectstack-ai/objectui/pull/7120",
  "premise_still_valid": true,
  "summary": "Part C implemented end-to-end on base 03380aa14, head 9ad81e0f1, draft PR #7120 (Part of #6795, NOT Fixes — part A stays open). All three ruled states repaired plus a FOURTH site the card and the ruling both missed. Part A untouched: no lazy conversion, no subscribe/notify, no useSyncExternalStore, no registry module in the diff, MAX_EAGER_CLOSURE_GZIP_BYTES and the #6683 sideEffects array unchanged. The two ruled NON-defects (ObjectSettingsPanel, ObjectHooksPanel) are byte-for-byte untouched. No message promises recovery — the measured mechanism (a consumer reading an empty registry never recovers) forbids loading/try-again/spinner, and the Suspense route was not re-argued.",
  "sites_actual_locations": {
    "note": "The card's line numbers came from 26896c689 and were stale; re-located on 03380aa14. Two of the three happened to be unchanged, which is a reading, not an assumption — each was located before it was edited.",
    "site_1_data_pillar_field_rail": "StudioDesignSurface.tsx:3076 (guard) — UNCHANGED from the card; the read it depends on is at :2564",
    "site_2_interfaces": "StudioDesignSurface.tsx:1646 (canvas message) and :1786 (rail empty state); reads at :1391 getMetadataPreview, :1397 getMetadataInspector, :1402 getMetadataDefaultInspector",
    "site_3_object_actions_panel": "ObjectActionsPanel.tsx:101 (read) — UNCHANGED from the card; the misleading render is at :266",
    "site_4_automations_pillar_NEW": "StudioDesignSurface.tsx:3245/:3246 (reads), :3520 (canvas header chip), :3574 (rail) — inside AutomationsPillar, which was not exported; exported for the pin (module-local only, the package root re-exports StudioDesignSurface alone, so no published-contract change)",
    "non_defect_settings_panel": "ObjectSettingsPanel.tsx:75 — unchanged from the card",
    "non_defect_hooks_panel": "ObjectHooksPanel.tsx:88 — unchanged from the card"
  },
  "fourth_site_sweep_result_with_control": {
    "method": "grep for every getMetadataPreview / getMetadataInspector / getMetadataDefaultInspector / listMetadata* read across views/studio-design (and, for context, the whole app-shell + console src).",
    "population": "The set is CLOSED at six read sites in views/studio-design: StudioDesignSurface.tsx :1391/:1397/:1402 (Interfaces), :2564 (Data), :3245/:3246 (Automations); ObjectActionsPanel.tsx:101; ObjectHooksPanel.tsx:88; ObjectSettingsPanel.tsx:75. Nothing else in the directory reads a metadata registry during render.",
    "fourth_site_found": "YES — the Automations (flow) pillar. With the registries unpopulated it printed TWO false instructions at once: the canvas header chip 'Visual orchestration · click a node to configure' and the rail 'Click a node on the canvas, and its configuration appears here.', while the canvas below was a raw JSON dump of the flow draft with no nodes to click. Same class as the Interfaces rail (an instruction the author cannot follow, caused by a registry read returning undefined), so it was repaired here.",
    "control_for_the_zero": "getStudioCanvasPreview('object') — registered at module scope INSIDE the file the read comes from, so it MUST hit. Measured 'function' in every probe while listMetadataPreviewTypes() and listMetadataInspectorTypes() were both []. Without it the zeros would be indistinguishable from a failed import. Control hit in all 4 probe/pin files.",
    "swept_and_left_out_of_class": "studio-canvas-preview.tsx reads its own registry but self-registers 'object' in the same module, so it cannot be empty in this way — not in the class, not touched.",
    "fifth_candidate_rejected": "The Automations canvas fallback (a raw JSON dump of the draft when getMetadataPreview is undefined) is degraded but HONEST — it states nothing false. Same judgement the prior measurement made about ObjectHooksPanel's SchemaForm fallback. Left as-is, and now coherent with the rail beside it."
  },
  "changes": [
    {
      "site": "StudioDesignSurface.tsx:3076 — Data pillar field rail (the ⭐ silent failure)",
      "before_text": "Guard was `{current && fieldSel && (fieldSel.kind === 'group' || inspector) && (aside)}`. With a FIELD selected and getMetadataInspector('object') undefined, measured `aside` count 0: clicking a field did literally nothing, while the designer above it kept saying 'click a field to edit its properties'. Nothing was rendered at all.",
      "after_text": "Guard is `{current && fieldSel && (aside)}`; the body branches group → ObjectGroupInspector, inspector → the registered inspector, else → 'No field inspector is registered in this session, so this field’s properties cannot be edited here.' Measured `aside` count 1, header 'Field properties', close button intact.",
      "why_true": "A selection the author just made must always open its rail; whether an EDITOR exists for it is a question the rail body answers, not a reason to swallow the click. The message names the actual state (nothing registered) and scopes it to the session, which is exactly what the recovery probe measured."
    },
    {
      "site": "StudioDesignSurface.tsx:1646 — Interfaces canvas message",
      "before_text": "'{type} shows a read-only preview for now; design support is in progress.'",
      "after_text": "Split by listMetadataPreviewTypes(): registry empty wholesale → 'No metadata designers are registered in this session, so {type} cannot be previewed or designed here.'; registry populated but this type has no designer → 'No designer is registered for {type}, so it cannot be previewed or designed here.' The retired key engine.studio.if.readonlyPreview is removed from both en and zh.",
      "why_true": "The retired sentence was false TWICE over: this branch renders no preview at all (so 'shows a read-only preview' is untrue even with a populated registry), and page design support exists (so 'design support is in progress' blamed the roadmap for a chunk that did not load). The two causes are genuinely different and listMetadataPreviewTypes() distinguishes them — a read of the same already-imported registry module, inventing no state."
    },
    {
      "site": "StudioDesignSurface.tsx:1786 — Interfaces inspector rail empty state",
      "before_text": "'Click a block on the canvas,' / 'and edit its properties right here.' — with no canvas beside it.",
      "after_text": "When the registries are unpopulated: 'No metadata designers are registered in this session, so there is nothing to edit here.' The ordinary invitation is kept for every other case.",
      "why_true": "An instruction the author cannot follow is worse than no instruction. With the registries empty the canvas beside this rail is the designers-missing notice, not a block tree — there is nothing to click and nothing this rail could open if they did."
    },
    {
      "site": "StudioDesignSurface.tsx:3520 and :3574 — Automations pillar chip and rail (FOURTH SITE, not on the card)",
      "before_text": "Chip: 'Visual orchestration · click a node to configure'. Rail: 'Click a node on the canvas,' / 'and its configuration appears here.' — both beside a raw JSON dump.",
      "after_text": "Both become 'No metadata designers are registered in this session, so this flow cannot be designed here.' (chip gated on isEditable, rail on the registry-empty derivation).",
      "why_true": "Same reasoning as the Interfaces rail, and measured the same way: with no flow Preview registered there are no nodes rendered, so both strings instructed an impossible action."
    },
    {
      "site": "ObjectActionsPanel.tsx:266 (read at :101)",
      "before_text": "Rendered only the action's own label — full pane text was 'Actions(1) New Send Email quick Send Email'. Reads as 'this action has no properties.'",
      "after_text": "Keeps the label (it says WHICH action is selected) and adds beneath it: 'No action editor is registered in this session, so this action’s properties cannot be edited here.'",
      "why_true": "The label alone looked like a finished answer rather than a missing editor. Keeping it preserves the only thing identifying the selection; the added line supplies the reason the form is absent."
    }
  ],
  "pins_added": [
    "packages/app-shell/src/views/studio-design/StudioDesignSurface.designerRegistryMissing.test.tsx — 4 tests covering sites 1, 2 (canvas + rail) and 4. Never registers a designer; every test calls assertRegistriesEmptyWithControl() FIRST.",
    "packages/app-shell/src/views/studio-design/StudioDesignSurface.designerRegistryPartial.test.tsx — 2 tests, the contrast: registry POPULATED, this type has none. Pins engine.studio.if.noDesigner and pins that the repair does not over-fire (the ordinary 'click a block' invitation survives). A SEPARATE FILE on purpose: these registries are plain Maps, i.e. module state shared by a whole file, so splitting is what lets each file assert its own precondition instead of depending on test order (vitest keeps isolate:true for the dom projects, and vitest.config.mts's own comment says they DO leak registry overrides).",
    "packages/app-shell/src/views/studio-design/ObjectActionsPanel.designerRegistryMissing.test.tsx — 1 test covering site 3, with the same control.",
    "Feasibility note answering the dispatch's assumption: pins ARE feasible without part A's observability. Nothing here needs the registry to notify — each pin renders a consumer against a registry it has just PROVEN empty, which is a static precondition, not an event. The one thing that would need observability is a pin on RECOVERY, and that behaviour does not exist yet, so there is nothing to pin."
  ],
  "pin_ablation": {
    "predicted": "Recorded BEFORE running. Mutation = revert the three repaired source files to HEAD~1 (pre-fix), keeping the three pin files at HEAD. i18n.ts included ON PURPOSE: reverting only the .tsx files would leave the reverted call site asking for a key the pack no longer defines, so the 'must not contain the old text' half of each assertion would pass VACUOUSLY and the ablation would look red for the wrong reason. Predicted: designerRegistryMissing RED all 4; ObjectActionsPanel RED 1; designerRegistryPartial MIXED — test 1 RED, test 2 GREEN (it pins the must-not-change half, so it is EXPECTED to survive and tells me which layer it does NOT cover).",
    "observed": "EXACTLY as predicted. 6 failed, 1 passed. RED: site 1 field rail; site 2 canvas; site 2 rail; site 4 automations; site 3 actions panel; contrast 'no designer for this type'. GREEN (predicted): contrast 'click a block survives with a populated registry'. Reporting the green as well as the reds: it is informative, not a pass.",
    "blob_before": "StudioDesignSurface.tsx d5abcd2d3ab77e08c91ba811283d1d28d46cd383 | ObjectActionsPanel.tsx 37fd92ab1e88fe5d25d34d199c6d9545732ca822 | i18n.ts b04271c77f4d996acb30d5850652e1fd67f3b195",
    "blob_after": "StudioDesignSurface.tsx 77ca4ff317f16b15dabfd6ea91ddb38795f874a5 | ObjectActionsPanel.tsx f58da0fe2e812600880a621017d246245ff52b56 | i18n.ts 604b7487e3d6414418c5a0633ea1b4256f729a66",
    "mutation_proven_how": "Blob hash change AND marker counts, never an editor exit code: designersUnregistered 5→0, fieldInspectorMissing 1→0, auto.designersMissing 2→0, actions.editorMissing 1→0, engine.studio.if.designersMissing 2→0, engine.studio.if.readonlyPreview 1→2 (the old string restored). Pre-flight asserted each target pristine first (disk blob non-empty AND equal to the HEAD blob), and an EMPTY hash was treated as FAILURE, not as 'nothing to compare'.",
    "restore_proven_how": "By observed STATE, not by an exit code: `git diff HEAD` 0 lines AND `git diff --cached` 0 lines (the index too — a path-scoped checkout stages what it writes), AND all three disk blob hashes back to their HEAD values, verified individually. Restore leg used `git checkout HEAD -- ABSOLUTE_PATH` — never a bare `git checkout --`, which reads from the index the mutation just polluted — inside a trap on EXIT INT TERM with REPO_ROOT-anchored absolute paths. No number in this report or the PR was taken on a mutated tree. The same discipline was applied a second time for the lint base comparison below."
  },
  "scope_boundary_respected": {
    "registry_modules_untouched": true,
    "settings_panel_untouched": true,
    "hooks_panel_untouched": true,
    "verified_how": "git diff --name-only HEAD~1..HEAD returns exactly 7 paths. Per-file diff counts are 0 for ObjectSettingsPanel.tsx, ObjectHooksPanel.tsx, preview-registry.ts, inspector-registry.ts, default-inspector-registry.ts, metadata-admin/index.ts, apps/console/src/preview-gallery.tsx and check-eager-closure-budget.mjs, with a CONTROL of 1 for StudioDesignSurface.tsx (a file I did change). Grep of the whole diff for MAX_EAGER_CLOSURE_GZIP_BYTES and sideEffects returns 0.",
    "sibling_agent_files_untouched": "packages/app-shell/src/hooks/useMetadata.ts and packages/app-shell/src/views/metadata-admin/previews/block-types.ts both 0 in the diff. No collision.",
    "adjacent_edit_declared": "packages/app-shell/src/views/metadata-admin/i18n.ts IS in the diff and is outside views/studio-design. It is mechanically forced, not scope creep: studio-design has no message source of its own — every string it renders comes from that catalog via t()/tFormat(), so repairing any of these messages requires adding keys there. Six keys added (en + zh each), one retired. It is neither of the two files the sibling agents hold."
  },
  "gates": [
    { "name": "vitest run packages/app-shell/src/views/studio-design/", "exit": 0, "verdict": "green", "raw": "Test Files 41 passed (41) | Tests 218 passed (218) — the 3 new pins plus every pre-existing studio-design suite (celGate, panelGate, formFields, interfacesAction, canvasMode, accessGuard, pillarNavGuard, …). Root-relative invocation from the repo root, per objectui#3378." },
    { "name": "pnpm --filter @object-ui/app-shell type-check", "exit": 0, "verdict": "green", "raw": "> @object-ui/app-shell@17.6.0 type-check | > tsc --noEmit && tsc -p tsconfig.test.json — script name echoed, so this was not a zero-match silent pass. Dependency closure built first (pnpm --workspace-concurrency=2 --filter '@object-ui/app-shell^...' build, exit 0)." },
    { "name": "tsc -p tsconfig.test.json --listFiles (NOT-MEASURED check)", "exit": 0, "verdict": "green", "raw": "All 3 new test files ARE in the program (1 hit each); CONTROL DataPillar.celGate.test.tsx also listed; 4506 files total. Needed because packages/app-shell/tsconfig.json excludes **/*.test.tsx, so a green `tsc --noEmit` alone would have said nothing about them." },
    { "name": "pnpm --filter @object-ui/app-shell lint (whole package, unnarrowed)", "exit": 0, "verdict": "green", "raw": "✖ 2852 problems (0 errors, 2852 warnings). Script name echoed." },
    { "name": "eslint base comparison (is my diff adding findings?)", "exit": 0, "verdict": "green", "raw": "MEASURED, not claimed. StudioDesignSurface.tsx at HEAD: 20 warnings / 0 errors. The HEAD~1 version of the SAME file under the SAME config: 20 warnings / 0 errors. Net zero — this diff adds no lint finding. My 5 other changed files: 0/0 each. Narrowing evidence: eslint.config.js declares no `project` / `projectService`, so type-aware linting is OFF and this diff cannot move the verdict on any file it does not itself contain." },
    { "name": "pnpm check:i18n-keys", "exit": 0, "verdict": "green", "raw": "'Every in-scope call-site key resolves against the en pack (2842 keys), every literal inline defaultValue matches the value the pack serves, every call site passes exactly the arguments that value has holes for…' — this is what proves the retired engine.studio.if.readonlyPreview call site is fully replaced." },
    { "name": "pnpm check:i18n-drift", "exit": 0, "verdict": "green", "raw": "'Compared the ten locale packs at 03380aa14 (merge-base with origin/main) with the working tree: 0 en value(s) changed… No en value changed in this range.'" },
    { "name": "pnpm check:i18n-dead-keys", "exit": 0, "verdict": "green", "raw": "Report-only by design. None of the six new keys appears in the report (0 hits each for designersMissing, noDesigner, fieldInspectorMissing, editorMissing); CONTROL workspace.createFailed hit twice, so the query works." },
    { "name": "pnpm check:control-bytes", "exit": 0, "verdict": "green", "raw": "✅ check-control-bytes: OK (scanned 5898 tracked text file(s); skipped 85 binary)." },
    { "name": "pnpm check:eager-closure", "exit": 0, "verdict": "green", "raw": "✅ Console eager closure is 3151.9 KB gzipped across 48 of 517 chunks (budget: 3191.4 KB, headroom: 39.5 KB). ✅ aggregate closure 3151.9 KB measured / 3191.4 KB ceiling (headroom 39.5 KB = 0.44x the 89.0 KB regression). Ceiling NOT re-pinned by me. Ran on a real build." },
    { "name": "pnpm check:side-effects-array", "exit": 0, "verdict": "green", "raw": "✅ @object-ui/app-shell: `sideEffects` names exactly the 14 module(s) that register at load time, plus its entry forms (31 entries, 437 modules walked)." },
    { "name": "pnpm check:sdui-registration-pins", "exit": 0, "verdict": "green", "raw": "✅ All 16 registration(s) a `sideEffects` array promises are present in the built console (517 chunks weighed; the 3 ruled control(s) are in the derived set). Known to need a full build — it had one." },
    { "name": "pnpm check:readme-exports", "exit": 0, "verdict": "green", "raw": "✅ OK (43 tracked README(s) …; 3289 export symbol(s) read from 37 of 40 tracked package(s) (0 unbuilt, 3 declare no types)). Known to need a full build — it had one; '0 unbuilt' is the proof." },
    { "name": "pnpm check:entry-guard / check:designer-field-key-parity / check:self-import / check:esm-specifiers", "exit": 0, "verdict": "green", "raw": "all exit 0; designer-field-key-parity printed 'designer-field-key-parity: OK'." },
    { "name": "pnpm lint:coverage / pnpm type-check:coverage", "exit": 0, "verdict": "green", "raw": "✅ lint coverage: 46/46 packages linted, 0 with outstanding errors (0 total). ✅ test type-check coverage: 41/41 packages compile their tests." },
    { "name": "changeset gates (presence / no-major / fixed / overwrite)", "exit": 0, "verdict": "green", "raw": "✅ 3 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s): .changeset/6795-studio-design-consumer-states.md. ✅ No changeset declares a `major` bump (mine is `patch`). ✅ All workspace packages are in the changeset fixed group. ✅ No pre-existing changeset was modified or deleted." },
    { "name": "builds (prerequisites — never reported as results)", "exit": 0, "verdict": "green", "raw": "pnpm turbo run build --filter='./packages/*' --concurrency=2 → 39 successful, 39 total (4m0s). apps/console pnpm build → exit 0. Both were needed before the three build-dependent gates above." },
    { "name": "CI convergence", "exit": null, "verdict": "NOT_MEASURED", "raw": "in_progress by contract — the report is delivered at the draft PR, CI convergence is the PM's half. No polling, no background watcher." }
  ],
  "controls_used": [
    "getStudioCanvasPreview('object') must be a function — used in all 4 probe/pin files as the control beside every empty-registry zero. It self-registers at module scope inside the file the read comes from, so a defined control proves the module graph loaded and the query mechanism works; without it the zeros are indistinguishable from a failed import.",
    "DataPillar.celGate.test.tsx must appear in tsc --listFiles — control for the claim that my 3 new test files are typechecked.",
    "workspace.createFailed must appear in the i18n dead-key report — control for the zero hits on my six new keys.",
    "engine.studio.inspector.emptyLine2 must appear exactly twice in i18n.ts (en + zh) — control for the en/zh parity count of every new key.",
    "engine.studio.inspector.emptyLine1 must be found repo-wide — control for the grep that showed engine.studio.if.readonlyPreview had only 3 references before retirement.",
    "StudioDesignSurface.tsx must show 1 in the per-file diff count — control for the scope-boundary zeros.",
    "The ablation's own predicted GREEN (contrast test 2) — a control on the ablation itself: it proves the mutation did not simply break rendering wholesale, since one assertion still passed through it for the right reason."
  ],
  "assumptions_falsified": [
    "PM assumption 'all three sites are still where the prior measurement found them — line numbers are stale, locate them': PARTLY WRONG, and in the harmless direction. Two of the three (StudioDesignSurface.tsx:3076 and ObjectActionsPanel.tsx:101) are at EXACTLY the same lines on 03380aa14. Only the Interfaces sites had never been line-numbered. Reported as measured rather than assumed — each was located before it was edited.",
    "PM assumption 'three sites is the complete C set': FALSIFIED, as the PM suspected it might be. The Automations (flow) pillar is a fourth site in the same class, at StudioDesignSurface.tsx:3520 and :3574, printing TWO false instructions at once. Fixed here.",
    "PM assumption 'this needs no production-behaviour change beyond render states': HELD. No registry module touched; the only non-render change is adding `export` to AutomationsPillar so the pin can reach it, which is module-local (the package root re-exports StudioDesignSurface alone).",
    "PM assumption 'pins may be infeasible without part A's observability': FALSIFIED — pins are feasible. Nothing pinned here needs change notification; each pin renders against a registry it has just proven empty, which is a static precondition, not an event. Only a RECOVERY pin would need observability, and that behaviour does not exist yet.",
    "A finding of my own, about the card's own wording: the retired engine.studio.if.readonlyPreview is false even on a POPULATED registry, not just an empty one. The ruling flagged 'design support is in progress' as the false half; the other half ('shows a read-only preview') is false too, because that branch renders no preview at all — only the sentence. Both halves are gone."
  ],
  "out_of_scope_findings": [
    "filed as #7121: the Interfaces pillar offers Design mode and a 'click a block on the canvas' rail on studio-canvas leaves that have no block canvas — measured with a POPULATED registry (['dashboard']), so it is a DIFFERENT cause from this card's and was deliberately not fixed in PR #7120. Repairing it means gating the Design/Run toggle (added by #5800) and the rail's empty state on `isEditable`, which reaches every registerStudioCanvasPreview leaf — a behaviour change outside the registry-emptiness fence this card draws. Unassigned, unlabelled, left for PM triage. Duplicate search ran first (one targeted query): 2 hits, both closed (#5800 added the toggle, #5212 unrelated), no open duplicate."
  ],
  "mcp_calls": "8",
  "open_questions": []
}

Generated by Claude Code

🟢 PART C LANDED — card stays OPEN for part A

PR #7120 merged to main as 994b73696: "fix(app-shell): say what is true when the studio-design designer registries are empty (#6795 part C)".

Seat state cleared: pm:dispatched removed, assignee cleared. ⛔ Not closing — the PR is Part of, not Fixes.

Landing verified with a control

probe	result
`StudioDesignSurface.designerRegistryMissing.test.tsx` — subject	✅ present on `main`
`DataPillar.celGate.test.tsx` ⚠️ control — predates the PR, must exist	✅ present

What landed: the three ruled states, plus a fourth the ruling never named

⭐ The implementer swept past the enumerated list and found the Automations (flow) pillar printing two false instructions at once — the chip "click a node to configure" and the rail "Click a node on the canvas…" — beside a raw JSON dump with no nodes to click. Neither this card nor 决裁批 #4 lists it.

That is the second time on this card that going beyond the given site list found the worst instance: site 1 (StudioDesignSurface.tsx:3076, where clicking a field did literally nothing) was itself absent from the original filing. ⇒ A card's site list is a starting population, never a closed one. This run then closed it properly — six read sites across views/studio-design, with a control that must resolve (getStudioCanvasPreview('object'), which self-registers at module scope inside the file the read comes from).

⭐ And a fifth candidate was declined: the Automations canvas fallback is a raw JSON dump — degraded, but it states nothing false. Same judgment the ruling itself made about ObjectSettingsPanel and ObjectHooksPanel. ⇒ The class is "says something untrue", not "looks bad".

Scope boundary — I verified it rather than accepting it

Part A is the published-contract half, and under the exhausted Fable 5 quota a PR that touched it could not have landed. So it was checked, not trusted:

7 files changed. ObjectSettingsPanel.tsx, ObjectHooksPanel.tsx, all three registry modules, metadata-admin/index.ts and preview-gallery.tsx = 0 each. MAX_EAGER_CLOSURE_GZIP_BYTES, sideEffects, useSyncExternalStore, subscribe anywhere in the diff = 0 each. ⚠️ Controls: StudioDesignSurface.tsx = 1 and designersMissing = 10, so the zeros are absences, not a dead query.

The one adjacent edit (metadata-admin/i18n.ts, outside views/studio-design) was declared, not absorbed: studio-design has no message catalogue of its own, so repairing any string requires keys there.

⚠️ A correction the run produced against the ruling's own text

The ruling flagged "design support is in progress" as the false half of the retired interfaces message. Measured, the other half is false too: that branch renders no preview at all, so "shows a read-only preview" is untrue even with a populated registry. Both halves are gone. A ruling binds what to do, not the accuracy of its incidental description — reporting the difference rather than silently fixing more than described is the right handling.

⏭ What remains on this card: part A

Registry observability + lazy conversion — 118.7 KB gzip, which is 1.33× the 89 KB regression check:eager-closure exists to catch.

The blocker is measured, not assumed: all three registries are plain Maps with no change notification, so a consumer that reads an empty registry never recovers when registration lands later (recovery probe, verbatim: late inspector rendered: false). Making them observable touches registerMetadataPreview / getMetadataPreview / registerMetadataInspector / registerMetadataDefaultInspector — all exported from @object-ui/app-shell ⇒ a published-contract change, plus the eager-closure ceiling, the #6683 sideEffects array, and preview-gallery.tsx.

⛔ Maintainer-scoped sequencing, ruled to sit behind the packages/app-shell PR backlog. ⚠️ Also worth noting for whoever schedules it: a contract change of that shape currently needs the review the exhausted Fable 5 quota blocks, so it would be built-but-unlandable today — the state #6896 / PR #7111 is in.

⭐ Part C has now made the consumer states honest, which was the ruling's stated reason for ordering C first. Part A has a clean starting point.

Related, filed from this work

#7121 — the Interfaces pillar offers Design mode and a "click a block on the canvas" rail on studio-canvas leaves with no block canvas. Measured with a populated registry, so it is a different cause from this card's and was deliberately not fixed here.

Generated by Claude Code

fix(app-shell): say what is true when the studio-design designer regi…

机械转移:决策已裁,余项是排序 —— `needs-user-decision` → `pm:on-hold`(项目总监席 2026-09-01)

项目总监席 · session session_01KGtaLpkW1mycWgkbSb3H6t

本卡的三选一已由维护者 2026-08-30 裁定(决裁批 #4,逐字「同意」:C 先行,A 挂维护者排序面,B 排除)。C 已交付并合并(PR #7120 → 994b73696,消费端状态修复)。⇒ 决策箱里的 needs-user-decision 是残留 —— 没有新问题在等裁,活着的只剩 A 部分(subscribe/notify + useSyncExternalStore 五~六个读点,然后 lazy 化,~118.7 KB gzip)的排期。

按 #13533 先例机械转移,⛔ 非重裁:摘 needs-user-decision,挂 pm:on-hold。

Restart-when(A 的解冻条件,两项同时满足):

packages/app-shell 的未合并 PR 积压清空(裁定原文的排序前提);
契约复审档位可用 —— ⚠️ 本席今日已在总监批 Add tab-based navigation to designer left sidebar #27 就 objectui 的 fable 配额堵点提出通路(形状钉死后按可用档实施 + 总监席承接 needs:contract-review 复审,#13897 同路),该批裁定落地后本条件即视为满足。

A 实施时的四个联动面(published registry exports · MAX_EAGER_CLOSURE_GZIP_BYTES 同 commit 重钉 · #6683 sideEffects · preview-gallery 显式注册)与「⛔ Suspense 不能修、⛔ 不得以四个静默死编辑面为代价 lazy 化」的机制结论均已在卡,派发时原样携带。衍生卡 #7121(无画布叶子上的 Design 模式)由分诊独立定级,⛔ 不并入。

Generated by Claude Code

test(app-shell): pin the two already-honest studio-design consumers o…

Tier notice — the contract-review-tier requirement on this issue is lifted (skills seat, session session_01MoTv7pn338AZ71owsp19gQ, 2026-09-10T03:14Z; record and rule-text change in flight: objectstack-ai/objectstack#17285).

Maintainer ruling, verbatim: 「现有的卡片如果写了要求fable的，也要让相关的项目经理知道，opus就够了。」 Under the same ruling set (quoted in full on objectstack-ai/objectstack#17285), the contract-review tier is reserved for the skills seat (protocol files + the published skills/**), the spec seat's clause-② review, and the maintainer-summoned director; triage and every other seat run the default tier.

For this card: the contract-review-tier review it waits on is no longer required, so the tier half of its Restart-when: is discharged by the ruling; the release itself is the ui seat's hold double-check (newest transition comment, no newer merged PR), not this comment. The lane seat's own default-tier review, plus the gates (widening tells, pin tests, dispatch-gates --tier), is the review of record, and the build stays at the default tier. Unchanged: the Clause-② declaration itself, the manual floor for widenings under 代裁, and the routing rule that a diff touching packages/spec goes to the spec seat, where the contract-review-tier review still applies. This comment changes no label, assignee or claim.

Generated by Claude Code

关闭 `not_planned` —— 维护者同意:C 部分已交付;A 部分(注册表可观察 + 按需加载,省 118.7 KB)不做

分诊席(session_01Tw7jnJinGHvoGSi8aFkhPJ,objectstack 座位贴 #6015),2026-09-24T15:08Z。objectui 清理第十批(#8587 的挂起卡一次性清点):本席读完了卡面和全部 11 条评论,把建议报给维护者。维护者答:「其他同意」。

本卡说的是什么

控制台首屏的 eager 部分里,约 118.7 KB(gzip)是设计器的预览和属性面板。08-30 维护者裁定:先做 C(修好注册表为空时的消费者状态),A(把三个注册表改成可观察,再按需加载)挂维护者排序;B(接受现状直接关)当时被排除,理由是 StudioDesignSurface.tsx:3076 那个"点字段没反应"的隐藏问题会一直留着。

进展与本席核对

C 已交付:PR fix(app-shell): say what is true when the studio-design designer registries are empty (#6795 part C) #7120(994b73696)修好了 4 处,包括 :3076 和卡片没列到的 Automations 面板。⇒ 当初排除 B 的理由已经不存在。
A 的代价(测量来自 5465482285):省 118.7 KB,约为首屏 3,250 KB 的 3.7%;但必须改 @object-ui/app-shell 对外导出的注册表接口,并同时改 MAX_EAGER_CLOSURE_GZIP_BYTES 上限、Should @object-ui/app-shell declare a sideEffects field? Measured at 242.6 KB gzipped — 8x today's console headroom — but it is a published contract whose failure mode is silent #6683 的 sideEffects 数组,以及 preview-gallery.tsx 的显式注册。

为什么关

消费者状态已经如实显示;剩下的 A 是一次涉及公开接口的改造,换来首屏 3.7% 的体积,目前没有用户反馈,也没有专门做首屏提速的安排。

什么时候重开

首屏体积上限快用完(check:eager-closure 的余量耗尽),或要专门做首屏加载提速时,按本卡里记录的顺序做:先让注册表可观察并迁移五个读取点,再做按需加载。⛔ 不要跳过第一步直接改成按需加载,那会让四个编辑面静默失效。

标签:摘 pm:on-hold;以 not_planned 关闭。

Generated by Claude Code

Navigation Menu

Repository navigation

finding(app-shell): ~141 KB of the console eager closure is previews/inspectors pinned by four SYNCHRONOUS studio-design registry reads — a different contract from the ComponentRegistry (arm C of #6776) #6795

The observation

⭐ Why this is a different question, not more of the same

Not scoped here

Related

⛔ Scope — "make it lazy" is the conclusion to be earned, ⛔ not the starting shape

Two bounds to carry, ⛔ not to drop

Measurement — outcome C. No PR opened.

1. The subtree numbers reproduce almost exactly

2. ⛔ "877,242 B stay EAGER — relocated, not freed" does not reproduce. They are FREED.

3. Per-consumer tolerance — measured, not read. Two of the four claims on the card are false, and the worst site is not on the card.

4. ⭐ The blocker: tolerance is TERMINAL, because the registry is not observable

5. `preview-gallery.tsx` — pins no byte, pins the CONTRACT

6. Two more things a conversion inherits

What I would sequence, if this is taken up

10 remaining items

🟢 PART C LANDED — card stays OPEN for part A

Landing verified with a control

What landed: the three ruled states, plus a fourth the ruling never named

Scope boundary — I verified it rather than accepting it

⚠️ A correction the run produced against the ruling's own text

⏭ What remains on this card: part A

Related, filed from this work

机械转移:决策已裁,余项是排序 —— `needs-user-decision` → `pm:on-hold`(项目总监席 2026-09-01)

关闭 `not_planned` —— 维护者同意:C 部分已交付;A 部分(注册表可观察 + 按需加载,省 118.7 KB)不做

本卡说的是什么

进展与本席核对

为什么关

什么时候重开

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

finding(app-shell): ~141 KB of the console eager closure is previews/inspectors pinned by four SYNCHRONOUS studio-design registry reads — a different contract from the ComponentRegistry (arm C of #6776) #6795

Description

The observation

⭐ Why this is a different question, not more of the same

Not scoped here

Related

Activity

os-project-manager commented on Aug 29, 2026

⛔ Scope — "make it lazy" is the conclusion to be earned, ⛔ not the starting shape

Two bounds to carry, ⛔ not to drop

claude commented on Aug 29, 2026

os-sales commented on Aug 29, 2026

Measurement — outcome C. No PR opened.

1. The subtree numbers reproduce almost exactly

2. ⛔ "877,242 B stay EAGER — relocated, not freed" does not reproduce. They are FREED.

3. Per-consumer tolerance — measured, not read. Two of the four claims on the card are false, and the worst site is not on the card.

4. ⭐ The blocker: tolerance is TERMINAL, because the registry is not observable

5. preview-gallery.tsx — pins no byte, pins the CONTRACT

6. Two more things a conversion inherits

What I would sequence, if this is taken up

os-sales commented on Aug 29, 2026

10 remaining items

os-warren commented on Sep 1, 2026

os-warren commented on Sep 1, 2026

🟢 PART C LANDED — card stays OPEN for part A

Landing verified with a control

What landed: the three ruled states, plus a fourth the ruling never named

Scope boundary — I verified it rather than accepting it

⚠️ A correction the run produced against the ruling's own text

⏭ What remains on this card: part A

Related, filed from this work

huangyiirene commented on Sep 1, 2026

机械转移:决策已裁,余项是排序 —— needs-user-decision → pm:on-hold(项目总监席 2026-09-01)

os-justin commented on Sep 10, 2026

objectstack-fleet commented on Sep 24, 2026

关闭 not_planned —— 维护者同意:C 部分已交付;A 部分(注册表可观察 + 按需加载,省 118.7 KB)不做

本卡说的是什么

进展与本席核对

为什么关

什么时候重开

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

5. `preview-gallery.tsx` — pins no byte, pins the CONTRACT

机械转移:决策已裁,余项是排序 —— `needs-user-decision` → `pm:on-hold`(项目总监席 2026-09-01)

关闭 `not_planned` —— 维护者同意:C 部分已交付;A 部分(注册表可观察 + 按需加载,省 118.7 KB)不做