@salsita-ai/sdk 0.50.0-develop.71209819cd → 0.50.0-develop.780177b115

package/dist/configurator/ui/preset-layout/PresetUi.js

@@ -1 +1 @@
-import{jsx as e}from"react/jsx-runtime";import{createCustomPhoenixLayoutElement as t}from"#package/domain";import{PhoenixLayoutElement as r}from"#package/react-sdk";import{CategoryPresetUi as o}from"./CategoryPresetUi.js";let a="PresetUi";export const createPresetUi=e=>t(a,e);let s="PresetPageAction";export const createPresetPageAction=e=>t(s,e);let l="PresetDeviceNotSupported";export const createPresetDeviceNotSupported=e=>t(l,e);let n=()=>e(r,{name:s,elementProps:{},defaultSlot:()=>null}),p=()=>e(r,{name:l,elementProps:{},defaultSlot:()=>null}),c=()=>e(o,{action:e(n,{}),overlay:e(p,{})});export const PresetUi=()=>e(r,{name:a,elementProps:{},defaultSlot:c});
+import{jsx as e}from"react/jsx-runtime";import{createCustomPhoenixLayoutElement as t}from"#package/domain";import{PhoenixLayoutElement as r}from"#package/react-sdk";import{PresetDeviceNotSupportedName as o,PresetPageActionName as s}from"../../preset-screen-elements/index.js";let c="PresetUi";export const createPresetUi=e=>t(c,e);export const createPresetPageAction=e=>t(s,e);export const createPresetDeviceNotSupported=e=>t(o,e);export const PresetUi=()=>e(r,{name:c,elementProps:{}});

package/dist/configurator/ui/save-message-snackbars/SaveMessageSnackbars.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Shows the save messages of `useConfiguratorMessages` as snackbars: a `saveError` as an error snackbar that stays
+ * until it is dismissed or a later save succeeds, and a `saveRecovery` as an informational one. Mounted wherever a
+ * layout mounts its message services: `LayoutSlots.Services`, the legacy layouts' overlays and the `custom` owner UI.
+ * In read mode, from the access or the web component's `readonly`, nothing is saved: an error snackbar left from
+ * owner mode is closed and no message is shown. The read UIs that replace an owner UI in read mode
+ * (`SummaryReadLayout`, the `custom` read UI) mount it too, since the owner UI's instance unmounts before it can close
+ * the snackbar.
+ */
+export declare const SaveMessageSnackbars: () => null;

package/dist/configurator/ui/save-message-snackbars/SaveMessageSnackbars.js

@@ -0,0 +1 @@
+import{jsx as r}from"react/jsx-runtime";import{Trans as e}from"@lingui/react";import{Button as s}from"@mui/material";import{useSnackbar as i}from"notistack";import{useEffect as t}from"react";import{useApplicationRuntime as o,useApplicationRuntimeSelector as a,useConfiguratorMessages as n}from"#package/react-sdk";let m="phx-configuration-persist-system-failure";export const SaveMessageSnackbars=()=>{let c=a(o().selectors.domainContext.configurator.getInitializationState).isViewMode,{enqueueSnackbar:d,closeSnackbar:p}=i();return t(()=>{c&&p(m)},[c,p]),n(i=>{c||("saveError"===i.kind&&d(r(e,{id:"sdk.persist.system.error.message",message:"An error occured when trying to update a configuration"}),{variant:"error",key:m,persist:!0,preventDuplicate:!0,action:i=>r(s,{color:"inherit",size:"small",onClick:()=>{p(i)},children:r(e,{id:"sdk.persist.system.error.dismiss",message:"Dismiss"})})}),"saveRecovery"===i.kind&&(p(m),d(r(e,{id:"sdk.persist.system.error.recovered",message:"Configuration updated"}),{variant:"info"})))}),null};

package/dist/configurator/ui/save-message-snackbars/index.d.ts

@@ -0,0 +1 @@
+export { SaveMessageSnackbars } from './SaveMessageSnackbars.js';

package/dist/configurator/ui/save-message-snackbars/index.js

@@ -0,0 +1 @@
+export{SaveMessageSnackbars}from"./SaveMessageSnackbars.js";

package/dist/docs/complex-use-cases/filtered-controls-with-fix-dialog.mdx

@@ -46,25 +46,22 @@ countersinkNotAvailable:
 ```
 
 ```ts
-const violationExpressions = invariantBuilder
-  .withInvariants(
-    implementCustomInvariants({
-      Plate: {
-        finishNotAvailable: s => {
-          return availableMaterials.some(state => state.material === s.material && state.finish === s.finish)
-        },
-        thicknessNotAvailable: s => {
-          return availableMaterials.some(
-            state => state.material === s.material && state.finish === s.finish && state.thickness === s.thickness
-          )
-        },
-        countersinkNotAvailable: s => {
-          return !s.someCounterSinkAdded || counterSinkThicknesses.includes(s.thickness)
-        },
-      },
-    })
-  )
-  .buildViolationExpressions()
+// src/invariants/invariants.ts
+export default phx.domain.implementCustomInvariants({
+  Plate: {
+    finishNotAvailable: s => {
+      return availableMaterials.some(state => state.material === s.material && state.finish === s.finish)
+    },
+    thicknessNotAvailable: s => {
+      return availableMaterials.some(
+        state => state.material === s.material && state.finish === s.finish && state.thickness === s.thickness
+      )
+    },
+    countersinkNotAvailable: s => {
+      return !s.someCounterSinkAdded || counterSinkThicknesses.includes(s.thickness)
+    },
+  },
+})
 ```
 
 With following control structure. Note the hierarchy of `fixableViolations`. The top input "fixes" all violations as it should never be disabled.

package/dist/docs/complex-use-cases/focus-mode.mdx

@@ -69,6 +69,8 @@ components:
 
 The toolMenuFab is scene HTML rendered at the entity's position in the 3D scene. It supports positioning properties (`offsetX`, `offsetY`, `offsetZ`) and appearance properties like opacity and visibility.
 
+The FAB and its menu are the entity element `ToolMenuFab`. A project replaces them by registering its own with `phx.frontend.createToolMenuFab`, which receives the `options` and `onSelectTool(toolState)`. See [Configurator Interface → In-Scene Controls](?path=/docs/phoenix-configurator-interface--docs#in-scene-controls).
+
 ### Step 3: Add exitToolModeFab component
 
 The `exitToolModeFab` component renders a button in the call to action layout slot, providing a clear way to exit the current tool mode. This appears in the UI chrome, not in the scene:

package/dist/docs/complex-use-cases/sketching.mdx

@@ -669,44 +669,6 @@ import { Model, attachComponent, configuratorBuilder } from './domain/index.js'
 // ... identical to the Code section above ...
 ```
 
-### Domain Setup (`domain/index.ts`)
-
-```typescript
-import { memoEval } from '@salsita-ai/sdk/domain'
-
-import { adminDomainBuilder } from './__generated/admin-implementation.js'
-import { generatedConfiguratorBuilder } from './__generated/configurator-builder.js'
-import {
-  domainBuilder,
-  implementCustomExpressions,
-  implementCustomInvariants,
-  invariantBuilder,
-} from './__generated/implementation.js'
-
-const violationExpressions = invariantBuilder.withInvariants(implementCustomInvariants({})).buildViolationExpressions()
-
-const customExpressions = implementCustomExpressions({
-  // ... as shown in Code section ...
-})
-
-const domainFactory = domainBuilder.withExpressions(violationExpressions).withExpressions(customExpressions).build()
-const adminDomainFactory = adminDomainBuilder.build()
-
-export const configuratorBuilder = generatedConfiguratorBuilder
-  .withDomainFactory(domainFactory)
-  .withAdminDomainFactory(adminDomainFactory)
-
-export * as AdminEnhancedDomain from './__generated/admin-enhanced-model.js'
-export * as AdminModel from './__generated/admin-model/index.js'
-export * as ApplicationTypes from './__generated/application-types.js'
-export * as EnhancedDomain from './__generated/enhanced-model.js'
-export * as Model from './__generated/model/index.js'
-
-export { attachAdminComponent, createAdminRecipe } from './__generated/admin-implementation.js'
-export { attachComponent, createRecipe } from './__generated/implementation.js'
-export { createPresets } from './__generated/presets.js'
-```
-
 ### Domain Configuration (`domain/domain.yaml`)
 
 ```yaml

package/dist/docs/controls/select-attribute/cardselect.mdx

@@ -99,19 +99,15 @@ components:
 Optionally disable specific options using invariants. The control performs a dry run for each option and disables those that would violate your rules. Provide a clear message; if multiple violations apply, messages are concatenated.
 
 ```typescript
-// domain/index.ts (extract)
-const violationExpressions = invariantBuilder
-  .withInvariants(
-    implementCustomInvariants({
-      Table: {
-        trunkDisabled: s =>
-          s.edgeFinish === 'TreeTrunk'
-            ? [{ type: 'trunkDisabled', severity: 'fatal', message: 'TreeTrunk finish is disabled because stuff!' }]
-            : [],
-      },
-    })
-  )
-  .buildViolationExpressions()
+// src/invariants/trunk-disabled.ts
+export default phx.domain.implementCustomInvariants({
+  Table: {
+    trunkDisabled: s =>
+      s.edgeFinish === 'TreeTrunk'
+        ? [{ type: 'trunkDisabled', severity: 'fatal', message: 'TreeTrunk finish is disabled because stuff!' }]
+        : [],
+  },
+})
 ```
 
 Register the invariant type in YAML so the system knows about it.

package/dist/docs/controls/select-child-entity/cardselect.mdx

@@ -189,6 +189,7 @@ interface ChildEntityCardSelectorSchema {
 interface ChildEntitySelectionComponentState {
   value: { $read: string } // Read-only - system manages DomainEntityId updates
   options: { $read: string } // Expression returning ChildEntitySelectionOption[]
+  keepChildren?: boolean // Keep the children of the replaced entity; by default they are deleted
 }
 
 // Each selectable option configuration

package/dist/docs/dimensions/3d-scene-integration/dimension-indicators.mdx

@@ -572,9 +572,9 @@ export type DimensionIndicatorState = {
    */
   readonly labelFontStyle?: 'normal' | 'italic'
   /**
-   * Font weight, which can be a numeric value, 'normal', or 'bold'.
+   * Font weight: a number, or a keyword such as 'normal' or 'bold'.
    */
-  readonly labelFontWeight?: number | 'normal' | 'bold'
+  readonly labelFontWeight?: number | string
   /**
    * Spacing between letters. Default is 0.
    */

package/dist/docs/dimensions/3d-scene-integration/editable-angle-indicator.mdx

@@ -131,7 +131,7 @@ export type EditableAngleIndicatorComponentState = AngleIndicatorBaseState &
     /** The instance name of the angleDimension component that will be used to update the angle. */
     readonly targetDimension: string
     /** An array of fixable violations. They will be ignored in the violation hint. */
-    readonly fixableViolations?: string[]
+    readonly fixableViolations?: readonly string[]
     /** The label of the input field. */
     readonly inputLabel?: Localizable
     /** The title of the modal. */

package/dist/docs/dimensions/3d-scene-integration/editable-distance-dimension-indicator.mdx

@@ -330,7 +330,7 @@ export type EditableDistanceDimensionIndicatorComponentState = DimensionIndicato
     /**
      * An array of fixable violations. They will be ignored in the violation hint.
      */
-    readonly fixableViolations?: string[]
+    readonly fixableViolations?: readonly string[]
     /**
      * The label of the input field.
      */

package/dist/docs/dimensions/3d-scene-integration/list-selector-dimension-indicator.mdx

@@ -365,7 +365,7 @@ export type ListSelectorDimensionIndicatorComponentState = DimensionIndicatorSta
     /**
      * An array of fixable violations. They will be ignored in the violation hint.
      */
-    readonly fixableViolations?: string[]
+    readonly fixableViolations?: readonly string[]
     /**
      * The title of the modal.
      */

package/dist/docs/drag-and-drop/drag-handle.mdx

@@ -71,7 +71,7 @@ export type DragHandleComponentState = {
    * It is defined in hessian normal form: `normal.x * x + normal.y * y + normal.z * z + constant = 0`
    * see https://threejs.org/docs/#api/en/math/Plane
    */
-  readonly surfaces: DraggableSurface[]
+  readonly surfaces: readonly DraggableSurface[]
 
   /**
    * The x property to be updated when the drag handle is dragged.

package/dist/docs/drag-and-drop/hotspot-handle.mdx

@@ -120,7 +120,7 @@ export type HotspotDragHandleComponentState = SceneEntityHtmlPositionState &
      * It is defined in hessian normal form: `normal.x * x + normal.y * y + normal.z * z + constant = 0`
      * see https://threejs.org/docs/#api/en/math/Plane
      */
-    readonly surfaces: DraggableSurface[]
+    readonly surfaces: readonly DraggableSurface[]
     /**
      * Instance name of hotspot binding. All hotspots which instance name is the same as the target will be dragged when the hotspot drag handle is dragged.
      */

package/dist/docs/drag-and-drop/planes.mdx

@@ -76,7 +76,7 @@ export type DragHandleComponentState = {
    * It is defined in hessian normal form: `normal.x * x + normal.y * y + normal.z * z + constant = 0`
    * see https://threejs.org/docs/#api/en/math/Plane
    */
-  readonly surfaces: DraggableSurface[]
+  readonly surfaces: readonly DraggableSurface[]
 
   /**
    * The x property to be updated when the drag handle is dragged.

package/dist/docs/drag-and-drop/rotatable.mdx

@@ -154,9 +154,9 @@ export type RotationHandleComponentState = {
 ```typescript
 export type RotatableSurface = {
   /**
-   * Unique identifier for the surface.
+   * Identifier of the surface.
    */
-  readonly key: string
+  readonly key?: string
 
   /**
    * The widget rotation axis in normal form. Usually corresponds to the target object's rotation axis.

package/dist/docs/fabs/basic.mdx

@@ -62,8 +62,8 @@ Lastly as both `sceneEntityDeleteFab` and `sceneEntityAddFab` are controls that
 
 All on-scene controls allow definition of `azimuthAngleLimits`, `polarAngleLimits` and `distanceLimits` properties to limit the visibility of the control based on the camera position. These properties optionally take an object with the following properties:
 
-- `min`, `max` - the range of the angle or distance where the control is visible
-- `minOpacity` - the opacity of the control when the camera is out of the range (default is `0.15`)
+- `min`, `max` (both required) - the range of the angle or distance where the control is visible
+- `minOpacity` - the opacity of the control when the camera is out of the range (default is `0`)
 - `smoothZone` - zone that eats from both sides of the range, where the opacity is interpolated from `minOpacity` to `1.0` (default is `(max - min) / 8`)
 
 All three limits can be used separately or combined. The angle limits are in radians and the distance limits respect the `unit` defined on the component.
@@ -131,6 +131,10 @@ components:
           - non-existent
 ```
 
+### Your own FABs
+
+The FABs are the entity elements `DeleteEntityFab` and `AddEntityFab`. A project replaces their look by registering its own with `phx.frontend.createDeleteEntityFab` or `phx.frontend.createAddEntityFab`; the spec's settings and positions above still apply. The delete FAB's replacement gets `onDelete`, `disabled` and `disabledHint`; the add FAB's reads its recipes with `phx.frontend.useGroupedRecipeOptions`. See [Configurator Interface → In-Scene Controls](?path=/docs/phoenix-configurator-interface--docs#in-scene-controls).
+
 ## Example
 
 Here you can see the live example!

package/dist/docs/index.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-10-13T16:11:48.414Z",
+  "generatedAt": "2026-10-16T16:48:27.223Z",
   "categories": [
     {
       "name": "Phoenix",
@@ -164,6 +164,16 @@
           ],
           "source": "storybook-root"
         },
+        {
+          "title": "Layout Slots",
+          "description": "A project layout registered as `ConfiguratorLayout` builds its UI from its own components and from the pieces of the built-in layout it wants to keep. Those pieces are the members of `LayoutSlots`,...",
+          "path": "docs/phoenix/layout-slots.mdx",
+          "category": [
+            "Phoenix",
+            "Layout Slots"
+          ],
+          "source": "storybook-root"
+        },
         {
           "title": "Localization",
           "description": "Phoenix provides a localization system built on **Lingui** that enables multi-language support across your configurator. The system handles React components and server-side webhook processing,...",
@@ -264,6 +274,16 @@
           ],
           "source": "storybook-root"
         },
+        {
+          "title": "Testing",
+          "description": "A project's tests check its own logic, such as an expression on a preset, a transformer that completes an edit, a Blender projection or a migration, against the application the project ships. They...",
+          "path": "docs/phoenix/testing.mdx",
+          "category": [
+            "Phoenix",
+            "Testing"
+          ],
+          "source": "storybook-root"
+        },
         {
           "title": "Webhook Membership",
           "description": "Build component controls with React and browser SDKs without pulling them into the server webhook bundle. Phoenix keeps user-authored components and handlers in the frontend unless a file explicitly...",
@@ -686,6 +706,16 @@
           ],
           "source": "storybook-example"
         },
+        {
+          "title": "Custom Layout",
+          "description": "Make the configurator look like the brand's own product page. A furniture shop wants its table configurator to read like the rest of its site: a floating panel on the left with the product's name,...",
+          "path": "docs/layouts/custom-layout.mdx",
+          "category": [
+            "Layouts",
+            "Custom Layout"
+          ],
+          "source": "storybook-example"
+        },
         {
           "title": "Custom Price",
           "description": "The custom price footer component replaces the standard price display in the sidebar footer with a fully customizable React component. This allows you to create custom pricing interfaces, add...",
@@ -804,6 +834,17 @@
               ],
               "source": "storybook-example"
             },
+            {
+              "title": "In a Custom Layout",
+              "description": "A project wants the configurator arranged differently, for example with the sidebar on the left, but the sidebar itself is right as it is: the spec's tabs, property pages and sidebar footer, with...",
+              "path": "docs/layouts/sidebar/in-a-custom-layout.mdx",
+              "category": [
+                "Layouts",
+                "Sidebar",
+                "In a Custom Layout"
+              ],
+              "source": "storybook-example"
+            },
             {
               "title": "General",
               "description": "The sidebar is the primary navigation and control interface in Phoenix configurators. It provides a flexible container for property pages, tabs, summary views, and other interactive components that...",
@@ -840,6 +881,23 @@
           ],
           "subcategories": []
         },
+        {
+          "name": "Gallery",
+          "docs": [
+            {
+              "title": "Kestrel Kettle",
+              "description": "Sell a small product from one calm page that looks like the shop's own. A specialty-coffee shop, Aldermoor Coffee, sells its Kestrel pour-over kettle in three finishes, two handle woods and with or...",
+              "path": "docs/layouts/gallery/kestrel-kettle.mdx",
+              "category": [
+                "Layouts",
+                "Gallery",
+                "Kestrel Kettle"
+              ],
+              "source": "storybook-example"
+            }
+          ],
+          "subcategories": []
+        },
         {
           "name": "Header",
           "docs": [

package/dist/docs/integrations/woocommerce/local-development.mdx

@@ -133,7 +133,7 @@ The value of `WOOCOMMERCE_API_KEY` must correspond to the value of the 'API key'
 settings page and `WOOCOMMERCE_PRODUCT_NAME` must correspond to the name of the product template you created.
 
 - run development server (from this repo): `pnpm dev:server`
-- prepare local deployment (from the implementation project): `pnpm deployment:prepare-local`
+- prepare local deployment (from the implementation project): `pnpm phoenix deployment:prepare-local`
 - start the dev process (from the implementation project): `pnpm dev`
 - run bundle build (from the implementation project): `pnpm build`