@salsita-ai/sdk 0.49.0 → 0.50.0-develop.03ef51a292

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

@@ -104,106 +104,92 @@ All inputs include countersinkNotAvailable, as that is fixable by auto fix dialo
 And corresponding transformers
 
 ```typescript
-configuratorBuilder
-  .withTransformers(() => [
-    {
-      priority: 3,
-      transformer: (updates, currentState) => {
-        if (updates.length > 1) {
-          return updates
-        }
-
-        const materialUpdate = updates.find(
-          (u): u is ComponentModification<MaterialSwatchComponent> =>
-            u.kind === 'modifyComponent' && u.updateTag === 'selectSwatch-material'
-        )
-
-        if (!materialUpdate) {
-          return updates
-        }
-
-        const plate = currentState.domainState.entities.find(Plate.is)!
-        const newMaterial = materialUpdate.writableState.selectedSwatchKey
-
-        const isAvailable = availableMaterials.some(
-          state =>
-            state.material === newMaterial && state.finish === plate.finish && state.thickness === plate.thickness
-        )
-
-        if (isAvailable) {
-          return updates
-        }
-
-        const similarMaterial = availableMaterials.find(m => m.material === newMaterial)
-
-        if (!similarMaterial) {
-          return updates
-        }
-
-        const fixUpdate = updateFactory.DomainEntityModification({
-          entityId: plate.id,
-          stateDelta: {
-            material: similarMaterial.material,
-            finish: similarMaterial.finish,
-            thickness: similarMaterial.thickness,
-          },
-          updateTag: 'fix.material',
-        })
-
-        return [fixUpdate]
+// src/transformers/fix-finish.ts
+import { availableMaterials } from '../_shared/available-materials.js'
+
+export default phx.frontend.transformerBuilder.when
+  .entity(['Plate'])
+  .modified({ atFields: ['finish'] })
+  .then.overrideMatchingUpdate(({ update, getOld$Entity }) => {
+    const plate = getOld$Entity()
+    const newFinish = update.stateDelta.finish
+
+    const isAvailable = availableMaterials.some(
+      state => state.material === plate.material && state.finish === newFinish && state.thickness === plate.thickness
+    )
+
+    if (isAvailable) {
+      return [update]
+    }
+
+    const similarMaterial = availableMaterials.find(m => m.finish === newFinish && m.material === plate.material)
+
+    if (!similarMaterial) {
+      return [update]
+    }
+
+    const fixUpdate = phx.frontend.updates.DomainEntityModification({
+      entityId: plate.id,
+      stateDelta: {
+        material: similarMaterial.material,
+        finish: similarMaterial.finish,
+        thickness: similarMaterial.thickness,
       },
-    },
-    {
-      priority: 3.1,
-      transformer: (updates, currentState) => {
-        if (updates.length > 1) {
-          return updates
-        }
-
-        const materialUpdate = updates.find(
-          (u): u is ComponentModification<AttributeSelectionComponent> =>
-            u.kind === 'modifyComponent' &&
-            u.updateTag === 'AttributeSelect.update' &&
-            (u.componentInstance.instanceName as string) === 'finish'
-        )
-
-        if (!materialUpdate) {
-          return updates
-        }
-
-        const plate = currentState.domainState.entities.find(Plate.is)!
-        const newFinish = materialUpdate.writableState.value
-
-        const isAvailable = availableMaterials.some(
-          state =>
-            state.material === plate.material && state.finish === newFinish && state.thickness === plate.thickness
-        )
-
-        if (isAvailable) {
-          return updates
-        }
-
-        const similarMaterial = availableMaterials.find(m => m.finish === newFinish && m.material === plate.material)
-
-        if (!similarMaterial) {
-          return updates
-        }
-
-        const fixUpdate = updateFactory.DomainEntityModification({
-          entityId: plate.id,
-          stateDelta: {
-            material: similarMaterial.material,
-            finish: similarMaterial.finish,
-            thickness: similarMaterial.thickness,
-          },
-          updateTag: 'fix.brushed',
-        })
-
-        return [fixUpdate]
+      updateTag: 'fix.brushed',
+    })
+
+    return [fixUpdate]
+  })
+  .build('fix-finish')
+```
+
+```typescript
+// src/transformers/fix-material.ts
+import { availableMaterials } from '../_shared/available-materials.js'
+
+export default phx.frontend.transformerBuilder.when
+  .entity(['Plate'])
+  .modified({ atFields: ['material'] })
+  .then.overrideMatchingUpdate(({ update, getOld$Entity }) => {
+    const plate = getOld$Entity()
+    const newMaterial = update.stateDelta.material
+
+    const isAvailable = availableMaterials.some(
+      state => state.material === newMaterial && state.finish === plate.finish && state.thickness === plate.thickness
+    )
+
+    if (isAvailable) {
+      return [update]
+    }
+
+    const similarMaterial = availableMaterials.find(m => m.material === newMaterial)
+
+    if (!similarMaterial) {
+      return [update]
+    }
+
+    const fixUpdate = phx.frontend.updates.DomainEntityModification({
+      entityId: plate.id,
+      stateDelta: {
+        material: similarMaterial.material,
+        finish: similarMaterial.finish,
+        thickness: similarMaterial.thickness,
       },
-    },
-  ])
-  .buildConfig()
+      updateTag: 'fix.material',
+    })
+
+    return [fixUpdate]
+  })
+  .build('fix-material')
+```
+
+Each file in `src/transformers/` default-exports one transformer and is picked up by its location. The `transformers` section of the spec turns it on by name. For a transformer made with `build(name)` that is the name passed to `build(...)`, which must match the file name with case and dashes ignored (`fix-finish.ts` and `fixFinish` match). For a plain-function export it is the file name:
+
+```yaml
+# spec/application.yaml
+transformers:
+  - name: fix-finish
+  - name: fix-material
 ```
 
 And FilteredControls

package/dist/docs/complex-use-cases/navigation-reset-selection.mdx

@@ -18,7 +18,7 @@ The `createResetSelectionOnNavigationTransformer` automatically deselects entiti
 
 ## Guide
 
-The `createResetSelectionOnNavigationTransformer` is added through the `.withTransformers()` method. It automatically injects a deselect update when navigating to specified states.
+The `createResetSelectionOnNavigationTransformer` is added as a file in `src/transformers/`. It automatically injects a deselect update when navigating to specified states.
 
 ### Step 1: Import the transformer
 
@@ -28,19 +28,25 @@ Import the transformer function from the domain package:
 import { createResetSelectionOnNavigationTransformer } from '@salsita-ai/sdk/domain'
 ```
 
-### Step 2: Add the transformer to your config
+### Step 2: Add the transformer to your project
 
-Use the `.withTransformers()` method on the builder:
+Create the transformer in a file under `src/transformers/`:
 
 ```typescript
-const config = configuratorBuilder
-  .withTransformers(ctx => [
-    {
-      priority: 32,
-      transformer: createResetSelectionOnNavigationTransformer([ApplicationTypes.NavigationState.SecondStep], ctx),
-    },
-  ])
-  .buildConfig()
+// src/transformers/reset-selection.ts
+import { createResetSelectionOnNavigationTransformer } from '@salsita-ai/sdk/domain'
+
+export default phx.frontend.createTransformer(ctx =>
+  createResetSelectionOnNavigationTransformer([phx.applicationTypes.NavigationState.SecondStep], ctx)
+)
+```
+
+Each file in `src/transformers/` default-exports one transformer and is picked up by its location. The `transformers` section of the spec turns it on by name. For a transformer made with `build(name)` that is the name passed to `build(...)`, which must match the file name with case and dashes ignored (`fix-finish.ts` and `fixFinish` match). For a plain-function export it is the file name:
+
+```yaml
+# spec/application.yaml
+transformers:
+  - name: reset-selection
 ```
 
 The transformer takes two arguments:
@@ -97,7 +103,7 @@ When the transformer triggers, any selected entity is deselected automatically.
  *
  * @param navigationStates - Array of navigation state names that trigger deselection
  * @param ctx - Domain context providing access to the navigation system
- * @returns Update transformer that can be registered in withTransformers
+ * @returns Update transformer to return from a transformer file in src/transformers/
  *
  * @example
  * // Deselect when entering the summary step

package/dist/docs/index.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-10-08T08:51:36.828Z",
+  "generatedAt": "2026-10-13T08:01:20.023Z",
   "categories": [
     {
       "name": "Phoenix",
@@ -26,7 +26,7 @@
         },
         {
           "title": "Best Practices",
-          "description": "1. **YAML is king** - 99% of configuration should be in spec/\\*.yaml files 2. **Custom code locations** (in order of preference): - `src/expressions/` - Computed/derived properties -...",
+          "description": "1. **YAML is king** - 99% of configuration should be in spec/\\*.yaml files 2. **Custom code locations** (in order of preference): - `src/expressions/` - Computed/derived properties - `src/actions/` -...",
           "path": "docs/phoenix/best-practices.mdx",
           "category": [
             "Phoenix",
@@ -2479,6 +2479,16 @@
           ],
           "source": "storybook-example"
         },
+        {
+          "title": "Domain Actions",
+          "description": "A plate carries holes, and a hole can be nudged by an offset as long as it stays on the plate. The arrow buttons of a selected hole and the AI assistant both make this change, so the rule (\"stay on...",
+          "path": "docs/other-features/domain-actions.mdx",
+          "category": [
+            "Other features",
+            "Domain Actions"
+          ],
+          "source": "storybook-example"
+        },
         {
           "title": "Not Found (404)",
           "description": "Error page that is displayed when the configuration is not accesible.",

package/dist/docs/layouts/custom-price.mdx

@@ -78,24 +78,22 @@ Your custom component has full access to the Material-UI theme and SDK utilities
 
 ### Step 3: Attach the component to your entity
 
-Use the configurator builder to attach your custom price component to the root entity:
+Attach your custom price component to the root entity in a file under `src/components/`. The generated code picks the
+file up by its location and registers its default export:
 
 ```typescript
-const config = configuratorBuilder
-  .withComponentOptics([
-    attachComponent
-      .withEntity('Scene')
-      .withComponent(customPriceFooterComponent, 'default')
-      .attach(
-        memoEval(
-          (s) => [s.$price],
-          (price) => ({
-            node: <AppPrice price={price} />,
-          })
-        )
-      ),
-  ])
-  .buildConfig()
+// src/components/custom-price.tsx
+export default phx.domain.attachComponent
+  .withEntity('Scene')
+  .withComponent(customPriceFooterComponent, 'default')
+  .attach(
+    memoEval(
+      (s) => [s.$price],
+      (price) => ({
+        node: <AppPrice price={price} />,
+      })
+    )
+  )
 ```
 
 The `memoEval` function takes two arguments:

package/dist/docs/layouts/sidebar/tabs.mdx

@@ -179,27 +179,30 @@ When a selected entity has no `sidebarTabs`, its property pages replace the root
 You can use transformers to automatically navigate to specific tabs when entities are selected or deselected:
 
 ```typescript
-const config = configuratorBuilder
-  .withTransformers(ctx => {
-    return [
-      // Navigate to BuckyBall's first tab when selected
-      phx.frontend.transformerBuilder.when
-        .entity(['BuckyBall'])
-        .selected()
-        .then.navigateTo('BuckyBallTab1')
-        .build('Navigate to BuckyBallTab1')
-        .register(ctx),
-
-      // Return to global tab1 when BuckyBall is deselected
-      phx.frontend.transformerBuilder.when
-        .entity(['BuckyBall'])
-        .deselected()
-        .then.navigateTo('tab1')
-        .build('Navigate to Tab1')
-        .register(ctx),
-    ]
-  })
-  .buildConfig()
+// src/transformers/bucky-ball-tab.ts
+export default phx.frontend.transformerBuilder.when
+  .entity(['BuckyBall'])
+  .selected()
+  .then.navigateTo('BuckyBallTab1')
+  .build('buckyBallTab')
+```
+
+```typescript
+// src/transformers/tab.ts
+export default phx.frontend.transformerBuilder.when
+  .entity(['BuckyBall'])
+  .deselected()
+  .then.navigateTo('tab1')
+  .build('tab')
+```
+
+Each file in `src/transformers/` default-exports one transformer and is picked up by its location. The `transformers` section of the spec turns it on by name. For a transformer made with `build(name)` that is the name passed to `build(...)`, which must match the file name with case and dashes ignored (`fix-finish.ts` and `fixFinish` match). For a plain-function export it is the file name:
+
+```yaml
+# spec/application.yaml
+transformers:
+  - name: buckyBallTab
+  - name: tab
 ```
 
 This creates smooth navigation flows where selecting specific entities automatically switches to their relevant tabs, and deselecting returns to a default tab state.

package/dist/docs/layouts/toolbar.mdx

@@ -81,6 +81,12 @@ Phoenix provides built-in toolbar buttons for common operations:
   `props.showIndicatorSwitch: false` to hide the Dimension indicators switch. When omitted, the prop falls back to
   `applicationConfig.indicatorSwitch`, then `true`.
 - `helpToolbarButton` - Show help content (supports custom children)
+- `assistantToolbarButton` - Open and close the built-in assistant panel. It renders only in a project whose
+  application spec has an `assistant` section. `props.showTitle` defaults to `true`; the label shows on a
+  desktop-sized layout only. The default toolbar includes it, in a group of its own, when the spec has an
+  `assistant` section. Only the universal layout carries the panel, and the button does not hide itself in a
+  layout without it. A custom layout that renders the toolbar therefore defines a `toolbar` component without the
+  button, because the default toolbar would add it.
 
 ### Mobile Toolbar Configuration