Studio diagnostics · activation policy

Surface diagnostics

Prove activation policy: manifest-declared surfaces must pass slot, kind, capability, registry trust, render, and host-action telemetry gates before product apps rely on them.

Open live shell Stream workbench

Live diagnostics

Mounted and rejected Homestead surfaces

Booting

This page boots a tiny diagnostics runtime: one internal trusted surface should mount, one registry-validated external surface should render, one trusted executable fixture should fail rendering audibly, and one external unregistered surface should be rejected as untrusted-plugin.

Expected proof

  • mount studio-surface-diagnostics in streams
  • render external-validated-surface with registry: validated
  • fail failing-surface-diagnostics with render: failed
  • reject untrusted-plugin with registry: unregistered
  • action click the diagnostics surface action to emit requested/failed telemetry
  • audit telemetry visible through Homestead inspector helpers