@pygmalionjs/pygmalion 0.2.40 → 0.2.41

package/README.md

@@ -224,6 +224,38 @@ Screen recipes support `click`, `fill`, `check`, `press`, `wait`, and `storage`
 steps. Use deterministic recipes and assertions so each frame represents a
 repeatable application state.
 
+Keep user journeys explicit instead of relying only on source navigation
+inference. Paths expand into adjacent graph edges, and source-discovered edges
+are still merged underneath them:
+
+```tsx
+const storyboard = {
+  startScreenIds: ['screen:entry'],
+  paths: [
+    {
+      id: 'checkout',
+      label: 'Checkout',
+      screenIds: ['screen:entry', 'screen:cart', 'screen:confirmation'],
+    },
+  ],
+};
+
+<PygmalionEditor storyboard={storyboard} />
+```
+
+Every id is checked against the resolved screen catalog. Unknown endpoints and
+unreachable screens stay visible as graph diagnostics instead of disappearing
+from the sidebar. Code-only redirects or fixtures can be classified through
+`nonVisualScenarioIds` with ids created by
+`createStoryboardRouteScenarioId(route)`.
+
+The editor shell and frame geometry mount before storyboard discovery finishes.
+Cached or live route content remains gated until baseline environment and source
+digests settle, so immediate canvas paint cannot consume a provisional preview
+identity. Selecting an already visible frame in the sidebar preserves the
+camera; an offscreen frame is revealed with the smallest pan possible and never
+changes the user's zoom.
+
 ## Capture artifact lifecycle
 
 Import the reusable capture primitives from