@pygmalionjs/pygmalion 0.18.0 → 0.20.0

package/README.md

@@ -396,6 +396,62 @@ 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.
 
+### Declare catalog conditions
+
+A product is often several products at once: a color scheme, an account level
+or a feature entitlement decides which screens exist and how every one of them
+looks. A session preset is one runtime choice for the whole catalog, and a
+preview environment control only dresses the live preview. Independent flags
+are condition axes:
+
+```tsx
+const conditionAxes = [
+  {
+    id: 'theme',
+    label: 'Theme',
+    defaultValue: 'authored',
+    options: [
+      { value: 'authored', label: 'Auto' },
+      { value: 'dark', label: 'Dark', environment: { localStorage: { 'app:theme': 'dark' } } },
+    ],
+  },
+  {
+    id: 'tier',
+    label: 'Plan tier',
+    options: [{ value: 'basic', label: 'Basic' }, { value: 'plus', label: 'Plus' }],
+  },
+];
+
+<PygmalionEditor conditionAxes={conditionAxes} />
+```
+
+The Conditions panel lists every axis. The effective value is the explicit
+choice, then `defaultValue`, then nothing: an axis without a default constrains
+nothing until chosen, the same way the Default session shows every runtime.
+
+Each option's `environment` joins the storyboard baseline underneath every
+frame's own declared environment, in declared axis order and on top of the
+selected session preset. Capture fingerprints, flow sessions and Application
+runs already derive from that baseline, so choosing a value re-resolves the
+catalog under it instead of reusing frames captured under the previous one. An
+option without an environment is a pure catalog choice and leaves existing
+capture identities intact; a default with an environment participates from the
+start.
+
+A screen names the values it exists under with `conditions`; an axis it does
+not name means every value:
+
+```tsx
+{ id: 'billing', route: '/billing', conditions: { tier: ['plus'] } }
+```
+
+Unknown axis ids or values never widen the catalog: the revision catalog
+validator rejects them, and at runtime such a screen is hidden and reported by
+`conditionDeclarationIssues`. Frame-level condition axes from
+`screenStateAxes` stay frame states and are not promoted to catalog filters. The
+core evaluates the declarations; which product screens exist under which values,
+and what each value means to the application, remain host declarations.
+
 ## Capture artifact lifecycle
 
 Import the reusable capture primitives from
@@ -574,10 +630,31 @@ entries use a bounded cache. Dispose the runtime when its font environment ends.
 Mixed text, bidi, connected/repeated content, unresolved typography and
 source-rendered text return named diagnostics in this first measurement API.
 
-These snapshots do not yet drive Workspace selection handles, parent layout or
-the built-in multiline exporter. Callers must preserve the captured lifetime and
-apply scene transforms and clips when consuming them. Measurement never rewrites
-canonical width/height, adds an undo entry or changes source files.
+When both font capabilities are supplied, Workspace shares a disposable measured
+scene between the canvas, selection handles, snapping, guides, alignment and
+prototype wiring. Auto-height text keeps its authored minimum height when its
+width changes; auto-width text owns both dimensions. Inspector sizes follow the
+measured scene and derived dimensions cannot be overwritten by resize controls.
+Pending or unavailable derived bounds stay unavailable to geometry commands.
+Changing the document, page, source, mode or font registration cancels stale
+geometry work and gestures. Late measurements never reset a camera the user moved.
+
+This integration supports plain text under the existing bounded layout solver.
+Non-start constraints under text-resized ancestors, mixed text and dynamic
+prototype playback still need additional geometry integration. The built-in
+multiline exporter is also separate work. Measurement never rewrites canonical
+width/height, adds an undo entry or changes source files.
+
+### Inspect an existing variable binding
+
+`resolveVariableModeForNode` and `resolveVariableModeForInstance` return the
+requested collection mode and the scope that supplied it. Instance addresses
+use the existing opaque override address; consumers do not reconstruct paths.
+`planVariableOccurrence` captures one actual bound occurrence, its token
+resolution (including the authored mode), scalar value and literal patch without
+refreshing unrelated nodes. `projectVariableScalar` exposes the same validation
+and own-node or sparse-override projection used by refresh. These reads do not
+write either document or enable variable-library clipboard transfer.
 
 ## Local development
 

package/dist-lib/{CameraLayer-Clqgdcjb.js → CameraLayer-DXeRJvoy.js}

@@ -1,5 +1,5 @@
 import { jsx as p } from "react/jsx-runtime";
-import { n as C, R as g, aM as P, ck as R, cl as k, Y as E, cm as I, a7 as m, a4 as b } from "./runtime-B8Qu1ung.js";
+import { n as C, R as g, aM as P, ck as R, cl as k, Y as E, cm as I, a7 as m, a4 as b } from "./runtime-DcPbR8PS.js";
 import { useRef as L, useLayoutEffect as h } from "react";
 function v(n) {
   return `translate(${n.panX}px, ${n.panY}px) scale(${n.zoom})`;