@salsita-ai/sdk 0.50.0-develop.ae52227c7e → 0.50.0-develop.ae9a830ef0

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/index.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-10-13T19:44:25.844Z",
+  "generatedAt": "2026-10-14T16:30:09.091Z",
   "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...",