Studio Engine State Isolation

This file keeps its historical filename for existing doc links. The state model now uses Studio Engine language.

Product Rule

Each Studio Engine is an independent renderer scope. Desktop Runtime, Atlas Studio, Grid Studio, Ops Studio, and local-only development engines under /dev/studios/* must not leak app window or surface state into each other by accident.

Current State Model

Window instances still include a desktopId field for compatibility with the existing window manager. In Studio language, that field is the local engine scope for the window runtime.

WindowInstance
  appId
  spaceId
  desktopId
  layout
  route

Desktop Runtime continues to own the mature window runtime and Studio-local Scene model. Other Studio Engines use their own local surface state and can open apps through the desktop window runtime while their projection models mature.

Dock Boundary

The Dock is Desktop Runtime chrome. It should not appear in Atlas, Grid, Ops, or any local-only development Studio unless a future engine intentionally defines its own equivalent. Those engines can expose their own launchers, sidebars, cards, rails, palettes, node panels, forms, dashboards, or focus controls.

RuntimeCommandStrip keeps global controls such as Studio Engine switching, search, Alma, profile, settings, and the Global Command Surface.

App Launch Boundary

Launching from a non-Desktop Runtime Engine may still open the App through the desktop window runtime in v0. The projection contract decides whether the capability appears as a window, page, frame, mobile screen, widget, block, node, card, panel, admin section, or thumbnail.

When the workspace column becomes narrow, the window runtime clamps window position and size against the current workspace bounds instead of reusing an old wide-viewport center point.

Future Work

• Persist layouts per Studio.
• Add per-engine pinned apps, widgets, blocks, nodes, and cards.
• Add backend layout snapshots for public and team Studios.
• Teach install destinations to target a Studio scope explicitly.