@cratis/stage.runtime 4.228.0 → 5.0.0

package/dist/src/App.d.ts

@@ -1,6 +1,6 @@
 import '@cratis/showrunner.notes.react/styles';
 import { type ApplicationStructure, type DialogTemplate, type InstanceContribution, type Layout, type NavigationModel, type SceneElement, type Screen, type ScreenTemplate, type Theme, type UiProfile, type ExposureDeclaration } from '@cratis/scene.model';
-import type { EffectiveNavItem, PackageCatalog } from '@cratis/scene.engine';
+import type { EffectiveNavItem, OutletLevel, PackageCatalog } from '@cratis/scene.engine';
 import { type ComponentRegistry } from '@cratis/scene.react';
 import { type CompositionOptions } from '@cratis/scene.blueprint.default';
 import '@cratis/components/tokens';
@@ -29,6 +29,8 @@ export interface StageSceneApplication {
     structure?: ApplicationStructure;
     /** The JSON schema of every modeled command, by name, which a toolbar slice's task dialog reads its fields from. */
     commandSchemas?: Record<string, string>;
+    /** The outlets the modules, features and slices refine or contribute to, from the top down. */
+    outletLevels?: OutletLevel[];
     responseContracts?: StageResponseContracts;
 }
 /**

package/dist/src/StageChrome.d.ts

@@ -1,5 +1,6 @@
 import { type ReactNode } from 'react';
 import type { ComponentRegistry, RegisteredComponentProps } from '@cratis/scene.react';
+import { StageSlot } from './stageSlot';
 /** What the Stage's own components need that the document itself does not carry. */
 export interface StageChromeState {
     locales: string[];
@@ -30,15 +31,7 @@ export declare function StageThemeToggle({ element }: RegisteredComponentProps):
  * as the model nests them, each entry linking to the screen it opens.
  */
 export declare function StageNavigationTree({ element }: RegisteredComponentProps): import("react").JSX.Element;
-/**
- * The `core:outlet` the Stage renders: the screen the Scene navigation host placed in the named outlet, drawn
- * inside the Stage's own data scope so its queries, selections and commands work as they do on a primary screen.
- *
- * Scene's own outlet renders the placed screen in a scope of its own, which cannot see what the Stage resolves
- * queries and selections with, so the Stage draws the same region itself - including the `Close` button of an outlet the host
- * put in a slot the shell declares (`slot side`).
- */
-export declare function StageOutlet({ element }: RegisteredComponentProps): import("react").JSX.Element;
+export { StageSlot };
 /** What the last interaction did, or could not do. */
 export declare function StageActivity(): import("react").JSX.Element | null;
 /**