fix(app-shell): the metadata editor page tells its scoped inspector why it is read-only - #29203

Requested by Steedos · project thread

Fixes #29079

Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么:元数据编辑页(Setup 的条目页，以及 Studio「全部元数据」下的 /studio/包/metadata/flow/名称)现在会把「为什么只读」告诉右侧的节点属性栏。属性栏显示的原因，就是编辑器上方提示条对当前原因说的那句话：只读软件包、锁定、缺少 manage_metadata 能力、代码包提供的条目、运行时只读的类型，以及安全目录的隔离墙。没有新增文案。
• 为什么改:Studio flow node inspector: on a read-only package every control is disabled with no reason on hover, keyboard focus or to assistive tech #28985 之后，Studio 自动化页的流程节点属性栏会解释灰掉的控件，但同一个属性栏放在元数据编辑页上时，宿主不传原因，控件仍然灰着却没有任何说明。
• 风险与回滚:低。只多传一个可选属性 readOnlyReason,且只传给按选中项打开的属性栏;可写时不传，渲染与之前相同。未选中时的默认属性栏不变。回滚即还原本 PR。
• 先看:ResourceEditPage.tsx 中 formReadOnly 下方新增的 inspectorReadOnlyReason(原因的先后顺序与上方提示条一致),以及 InspectorComponent 调用处新增的一行。
• 两分钟验证:在 ui/ 下运行 pnpm exec vitest run packages/app-shell/src/views/metadata-admin/ResourceEditPage.inspectorReadOnlyReason-29079.test.tsx,预期 6 个测试全绿;去掉调用处那一行后 5 个变红。
• 需要你做的:无，席位落地。

What changes

• ResourceEditPage derives inspectorReadOnlyReason next to formReadOnly and passes it to the scoped inspector (InspectorComponent) as readOnlyReason, the prop Studio flow node inspector: on a read-only package every control is disabled with no reason on hover, keyboard focus or to assistive tech #28985 added to MetadataInspectorProps. The sentence is the one the page's own notice gives for the cause in force, in the notices' order:
  1. the walled security catalog: engine.catalog.readOnly.walled;
  2. a read-only package (Studio's "All metadata" area): engine.studio.pkg.readonlyHint, the sentence Studio's Automations pillar passes;
  3. a lock: the lock banner's title, then the lockReason the server serves;
  4. a declaration-only catalog: its engine.catalog.declaredOnly.hint sentence;
  5. a caller without manage_metadata: engine.edit.capabilityReadOnly;
  6. an item a code package ships: engine.edit.artifactLockedBanner;
  7. a type that is read-only at runtime: engine.edit.readOnlyTypeBanner.
     An editable page passes none.
• No string is new, so no i18n pack changes: every sentence is an existing key the page already shows above the editor.
• The no-selection default inspector is unchanged. MetadataDefaultInspectorProps declares no readOnlyReason, and widening it is outside this card.

Deviations

The card asks for three causes on the node inspector: no write access, a pending walled decision, and view mode pointing at Edit. Measured on main 87d6baef, only the first can reach the flow node inspector on this page:

• Walled applies only to the security catalog types (position, permission, capability), and none of them registers a scoped inspector. The page still names the wall first, so an inspector a host registers for one of those types gets the right sentence and not the capability one. The test pins that through a host inspector registered for position.
• View mode does not reach a scoped inspector. The inspector renders only beside a designer canvas. A designer type enters editing as soon as the item can be written (the designer auto-on effect), stays in editing after save and reset, and has no Edit button (the Edit button renders only when there is no preview). A sentence pointing at Edit would point at nothing, so view mode passes no reason. The seat accepted this shape before code.

Tests

• New: ResourceEditPage.inspectorReadOnlyReason-29079.test.tsx, 6 cases. The real page, gates and FlowInspector → FlowNodeInspector; only the canvases (to emit a selection) and the data reads are stubbed. Each case opens the item, selects on the canvas and reads the accessible description of the node inspector's reason group:
  • a writable flow: no reason group, and Remove node is enabled;
  • a read-only package's area, a caller without manage_metadata, a locked item with a served reason, and a flow a code package ships: each shows its own sentence;
  • the walled catalog: a host inspector registered for position receives readOnly and the wall's sentence.
• Red on main: the same file on 87d6baef reads 5 failed, 1 passed (only the writable control passes).
• Ablation: deleting the readOnlyReason={inspectorReadOnlyReason} line through scripts/ablation-replace.mjs reads 5 failed, 1 passed; restored, blob equals HEAD and git diff HEAD is empty.

Verification

All readings on head 162f85c0, base 87d6baef.

Generated by Claude Code