@salsita-ai/sdk 0.50.0-develop.bb71259564 → 0.50.0-develop.bc204720a8

package/dist/docs/fabs/basic.mdx

@@ -16,15 +16,13 @@ For this you can use the following on-scene controls:
 - `sceneEntityDeleteFab` - to delete an entity
 - `sceneEntityAddFab` - to add an entity using a recipe
 
-(or the `Object` variants of each: `sceneEntityObjectSelectHotspot`, `sceneEntityObjectDeleteFab`, `sceneEntityObjectAddFab`)
-
 Note that `sceneEntitySelectHotspot` is described in a [separate story](./?path=/docs/selection-highlight-hotspots--docs) and here we focus solely on the `sceneEntityDeleteFab` and `sceneEntityAddFab` controls.
 
 - Give every icon-only or otherwise unlabeled FAB a title so Phoenix shows a tooltip. Prefer a visible label when the action has room for one.
 
 ## Code
 
-Like any other on-scene control (fab or hotspot), the attached component lets you specify position of the control relative to the entity (or its object for the `Object` variants): `offsetX`, `offsetY` and `offsetZ` properties. The values are scaled by the unit specified in the `unit` property to the scene's coordinate space.
+Like any other on-scene control (fab or hotspot), the attached component lets you specify position of the control relative to the entity: `offsetX`, `offsetY` and `offsetZ` properties. The values are in the application's distance data unit, see [Dimension Data Unit](?path=/docs/dimensions-basic-concepts-dimension-data-unit--docs).
 
 ```yaml
 components:
@@ -51,10 +49,9 @@ Additionally, the on-scene controls support various dynamic visibility condition
   - `sceneEntityDeleteFab` - `['selected']`
   - `sceneEntityAddFab` - `['selected']`
 
-Both controls are represented by a floating action button that can optionally take a tooltip `title`, `label`, and PHX `icon` name. Both
-these properties are localizable. When specifying a `label` the button will be displayed in an "extended" variant (see the live example).
+Both controls are represented by a floating action button that can optionally take a tooltip `title` and a PHX `icon` name. Both also take a `label`; `title` and `label` are localizable. When specifying a `label` the button will be displayed in an "extended" variant (see the live example).
 
-Lastly as both `sceneEntityDeleteFab` and `sceneEntityAddFab` are controls that modify state of the configuration, they allow filtering out of certain violation types so that the error message tooltip is not too crowded:
+Lastly as both controls modify state of the configuration, they allow filtering out of certain violation types so that the error message tooltip is not too crowded:
 
 - `hiddenViolations` - an array of violation types to hide from the error message tooltip
 
@@ -66,7 +63,7 @@ All on-scene controls allow definition of `azimuthAngleLimits`, `polarAngleLimit
 - `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.
+All three limits can be used separately or combined. The angle limits are in radians and the distance limits are in the application's distance data unit, like the offsets.
 
 #### Displaying Tooltips
 
@@ -81,7 +78,7 @@ All on-scene controls allow definitions of `title` and `tooltipVisibility` prope
 
 ### Delete Fab
 
-The `sceneEntityDeleteFab` accepts `icon` to replace its built-in trash icon. Its `Object` variant keeps the built-in icon.
+The `sceneEntityDeleteFab` accepts `icon` to replace its built-in trash icon.
 
 ### Add Entity Fab
 
@@ -151,7 +148,7 @@ Here you can see the live example!
     - This should be disabled when there's 5 holes in the plate already.
     - Clicking it should directly add a new hole to the plate.
 - There should be a selection hotspot over each hole.
-- After selecting a hole through the hotspot, a delete button with `Trash` icon should appear.
+- After selecting a hole through the hotspot, a delete button with the `X` icon should appear.
   - This should be disabled for the top-right hole as that is a special glorified hole.
   - Clicking it should delete the selected hole and cause no errors in the console :-)
 - Toggle tooltip visibility to control the tooltip on the `+` Fab
@@ -393,7 +390,6 @@ invariants:
 
 ```ts
 import { createPlate } from '../../../../common/plate-rendering.js'
-import { phx } from '../../.phoenix/phx.js'
 
 export default phx.domain.implementCustomExpressions({
   Hole: {
@@ -458,8 +454,6 @@ export default phx.domain.implementCustomExpressions({
 ### ./src/invariants/invariants.ts
 
 ```ts
-import { phx } from '../../.phoenix/phx.js'
-
 export default phx.domain.implementCustomInvariants({
   Plate: {
     one54: s => s.$features.filter(phx.domain.model.Hole54.is).length === 1,

package/dist/docs/fabs/layout.mdx

@@ -346,7 +346,6 @@ invariants:
 
 ```ts
 import { getConsoleRenderingComponents } from '../../../../common/console-rendering.js'
-import { phx } from '../../.phoenix/phx.js'
 
 export default [...getConsoleRenderingComponents('ConsoleUnit', phx.domain.attachComponent)]
 ```
@@ -356,8 +355,6 @@ export default [...getConsoleRenderingComponents('ConsoleUnit', phx.domain.attac
 ```tsx
 import { Paper, Typography } from '@mui/material'
 
-import { phx } from '../../.phoenix/phx.js'
-
 export default phx.frontend.createCustomPhoenixEntityElement('LabelHotspot', ({ entityId }) => (
   <Paper
     sx={{
@@ -375,8 +372,6 @@ export default phx.frontend.createCustomPhoenixEntityElement('LabelHotspot', ({
 ### ./src/expressions/expressions.ts
 
 ```ts
-import { phx } from '../../.phoenix/phx.js'
-
 export default phx.domain.implementCustomExpressions({
   ConsoleUnit: {
     $newConsoleRecipes: () => {
@@ -396,8 +391,6 @@ export default phx.domain.implementCustomExpressions({
 ### ./src/invariants/invariants.ts
 
 ```ts
-import { phx } from '../../.phoenix/phx.js'
-
 export default phx.domain.implementCustomInvariants({
   Scene: {
     maxOneConsoleUnit: s => s.$consoleUnits.length <= 1,

package/dist/docs/index.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-10-19T10:55:27.402Z",
+  "generatedAt": "2026-10-31T06:44:53.401Z",
   "categories": [
     {
       "name": "Phoenix",
@@ -236,7 +236,7 @@
         },
         {
           "title": "SDK Builder Workflow",
-          "description": "An SDK-builder workspace lets you build one configurator from the application spec and develop and deploy it from your terminal. You don't need a repository, a CI pipeline, project keys or a...",
+          "description": "An SDK-builder workspace lets you build configurators from application specs and develop and deploy them from your terminal. You don't need a repository, a CI pipeline, project keys or a development...",
           "path": "docs/phoenix/sdk-builder-workflow.mdx",
           "category": [
             "Phoenix",
@@ -296,7 +296,7 @@
         },
         {
           "title": "Webhooks",
-          "description": "To support project specific finalization workflows, authentication and custom integrations, platform provides a way to define webhooks. These webhooks are deployed on aws lambda and can be triggered...",
+          "description": "To support project specific finalization workflows, authentication and custom integrations, the platform runs a project webhook: one bundle, deployed as a cloud function (AWS Lambda), that the...",
           "path": "docs/phoenix/webhooks.mdx",
           "category": [
             "Phoenix",
@@ -1212,7 +1212,7 @@
         },
         {
           "title": "Text Input",
-          "description": "Describe the use case for this story. What problem does it solve? When should this pattern be used?",
+          "description": "Let the user type free text that becomes part of the configuration: a name for the design, an engraving on a heater panel, a signature on a guitar, a monogram on a bag. The text is stored in a string...",
           "path": "docs/controls/text-input.mdx",
           "category": [
             "Controls",
@@ -2879,7 +2879,7 @@
         },
         {
           "title": "Navigation Guard",
-          "description": "Describe the use case for this story. What problem does it solve? When should this pattern be used?",
+          "description": "Ask the user to confirm a navigation before it happens, when it would cost them work. A stepped configurator, such as a kitchen planner whose first step picks the room shape and whose later steps...",
           "path": "docs/complex-use-cases/navigation-guard.mdx",
           "category": [
             "Complex Use Cases",
@@ -2889,7 +2889,7 @@
         },
         {
           "title": "Navigation Reset Selection",
-          "description": "The `createResetSelectionOnNavigationTransformer` automatically deselects entities when the user navigates to specific steps. This clears the active selection when entering certain workflow phases,...",
+          "description": "A transformer built with `when.navigated({ to: [...] }).then.deselect()` automatically deselects entities when the user navigates to specific steps. This clears the active selection when entering...",
           "path": "docs/complex-use-cases/navigation-reset-selection.mdx",
           "category": [
             "Complex Use Cases",

package/dist/docs/integrations/lifecycle-providers.mdx

@@ -26,7 +26,6 @@ Read published data, authenticated session data, and web-component properties di
 ```tsx
 import { useWebComponentPropertyValue } from '@salsita-ai/sdk/react'
 
-import { phx } from '../../.phoenix/phx.js'
 import { webComponentProperties } from '../_shared/web-component-options.js'
 
 export default phx.frontend.createOnPublishedDataReadyProvider(({ children }) => {
@@ -49,8 +48,6 @@ The provider must render `children` when validation passes. Returning an empty f
 Use `createOnFrontendDataReadyProvider` to reject an unsupported combination of host inputs before Phoenix sends collected frontend data to the backend. Use `createOnBackendDataReadyProvider` to check a returned price list or permissions before the configurator initializes. Register each provider in its own `src/elements/` file, using the same `children` pattern as the published-data gate. The example's `LifecycleGate` is only a demonstration device; a real gate renders `children` as soon as its check passes.
 
 ```tsx
-import { phx } from '../../.phoenix/phx.js'
-
 export default phx.frontend.createOnFrontendDataReadyProvider(({ children }) => {
   const frontendData = phx.frontend.useFrontendData()
 
@@ -335,7 +332,6 @@ export const webComponentProperties = {
 ```tsx
 import { useState } from 'react'
 
-import { phx } from '../../.phoenix/phx.js'
 import { LifecycleGate } from '../_shared/LifecycleGate.js'
 import { LifecycleLogPanel } from '../_shared/LifecycleLogPanel.js'
 import { resetLifecycleLog } from '../_shared/lifecycle-log.js'
@@ -358,7 +354,6 @@ export default phx.frontend.createOnApplicationStartProvider(({ children }) => {
 ### ./src/elements/OnBackendDataReady.tsx
 
 ```tsx
-import { phx } from '../../.phoenix/phx.js'
 import { LifecycleGate } from '../_shared/LifecycleGate.js'
 
 export default phx.frontend.createOnBackendDataReadyProvider(({ children }) => {
@@ -379,7 +374,6 @@ export default phx.frontend.createOnBackendDataReadyProvider(({ children }) => {
 ### ./src/elements/OnConfiguratorReady.tsx
 
 ```tsx
-import { phx } from '../../.phoenix/phx.js'
 import { LifecycleGate } from '../_shared/LifecycleGate.js'
 
 export default phx.frontend.createOnConfiguratorReadyProvider(({ children }) => {
@@ -400,7 +394,6 @@ export default phx.frontend.createOnConfiguratorReadyProvider(({ children }) =>
 ### ./src/elements/OnFrontendDataReady.tsx
 
 ```tsx
-import { phx } from '../../.phoenix/phx.js'
 import { LifecycleGate } from '../_shared/LifecycleGate.js'
 
 export default phx.frontend.createOnFrontendDataReadyProvider(({ children }) => {
@@ -423,7 +416,6 @@ export default phx.frontend.createOnFrontendDataReadyProvider(({ children }) =>
 ```tsx
 import { useWebComponentPropertyValue } from '@salsita-ai/sdk/react'
 
-import { phx } from '../../.phoenix/phx.js'
 import { LifecycleGate } from '../_shared/LifecycleGate.js'
 import { webComponentProperties } from '../_shared/web-component-options.js'
 
@@ -455,7 +447,6 @@ export default phx.frontend.createOnPublishedDataReadyProvider(({ children }) =>
 ```tsx
 import { useRoutingState } from '@salsita-ai/sdk/react'
 
-import { phx } from '../../.phoenix/phx.js'
 import { LifecycleGate } from '../_shared/LifecycleGate.js'
 
 export default phx.frontend.createOnRoutingReadyProvider(({ children }) => {
@@ -472,7 +463,6 @@ export default phx.frontend.createOnRoutingReadyProvider(({ children }) => {
 ### ./src/elements/OnSessionReady.tsx
 
 ```tsx
-import { phx } from '../../.phoenix/phx.js'
 import { LifecycleGate } from '../_shared/LifecycleGate.js'
 
 export default phx.frontend.createOnSessionReadyProvider(({ children }) => {
@@ -493,7 +483,6 @@ export default phx.frontend.createOnSessionReadyProvider(({ children }) => {
 ### ./src/handlers/collect-frontend-data.ts
 
 ```ts
-import { phx } from '../../.phoenix/phx.js'
 import { appendLifecycleEntry } from '../_shared/lifecycle-log.js'
 
 export default phx.frontend.createCollectFrontendDataHandler(async () => {
@@ -506,7 +495,6 @@ export default phx.frontend.createCollectFrontendDataHandler(async () => {
 ### ./src/handlers/get-web-component-options.ts
 
 ```ts
-import { phx } from '../../.phoenix/phx.js'
 import { webComponentProperties } from '../_shared/web-component-options.js'
 
 export default phx.frontend.createGetWebComponentOptionsHandler(() => ({

package/dist/docs/integrations/onloadprovider.mdx

@@ -65,7 +65,6 @@ import { customSummaryPageComponent, memoEval, propertyPageComponent } from '@sa
 
 import { MockSidebarOne } from '../../../../common/MockSidebar.js'
 import { MockSummary } from '../../../../common/MockSummary.js'
-import { phx } from '../../.phoenix/phx.js'
 
 export default [
   phx.domain.attachComponent
@@ -103,8 +102,6 @@ import { useEffect, useState } from 'react'
 import { useRoutingState } from '@salsita-ai/sdk/react'
 import { Loader } from '@salsita-ai/sdk/ui'
 
-import { phx } from '../../.phoenix/phx.js'
-
 export default phx.frontend.createOnConfiguratorReadyProvider(({ children }) => {
   const [state, setState] = useState('loading')
 

package/dist/docs/integrations/webcomponent-api/basics.mdx

@@ -668,6 +668,8 @@ export const AddToCartButton = () => {
 }
 ```
 
+The example attaches this button as a legacy `finalizeButton` component; a new project declares `finalizeAction` components instead, see [Finalization](?path=/docs/phoenix-finalization--docs).
+
 ### Live preview
 
 ## Client-facing documentation
@@ -684,6 +686,10 @@ If you need a client-facing manual explaining how they can integrate the configu
 ### ./spec/domain.yaml
 
 ```yaml
+availableLocales:
+  - en
+  - cs
+
 model:
   latest:
     entityTypes:
@@ -790,7 +796,6 @@ import {
 import { MockSidebarOne } from '../../../../common/MockSidebar.js'
 import { MockSummary } from '../../../../common/MockSummary.js'
 import { getMockChairComponents } from '../../../../common/mock-chair-model/mock-chair-model-components.js'
-import { phx } from '../../.phoenix/phx.js'
 import { webComponentEvents, webComponentProperties } from '../_shared/web-component-optionts.js'
 
 const pushToECommerce = (_accessToken: string, _cartId: string, _name: string, _price: number) =>
@@ -883,7 +888,6 @@ export default [
 ### ./src/handlers/get-webcomponent-options.ts
 
 ```ts
-import { phx } from '../../.phoenix/phx.js'
 import { webComponentEvents, webComponentProperties } from '../_shared/web-component-optionts.js'
 
 export default phx.frontend.createGetWebComponentOptionsHandler(() => ({

package/dist/docs/integrations/webcomponent-api/preset-tags.mdx

@@ -71,6 +71,10 @@ Alternatively, the `presetTags` HTML attribute can be provided with a comma-sepa
 ### ./spec/domain.yaml
 
 ```yaml
+availableLocales:
+  - en
+  - cs
+
 model:
   latest:
     entityTypes:
@@ -139,7 +143,6 @@ presets:
 
 ```tsx
 import { getMockChairComponents } from '../../../../common/mock-chair-model/mock-chair-model-components.js'
-import { phx } from '../../.phoenix/phx.js'
 
 export default [...getMockChairComponents('Scene', phx.domain.attachComponent)]
 ```

package/dist/docs/integrations/woocommerce/overview.mdx

@@ -13,7 +13,7 @@ It is written in PHP and calls WordPress/WooCommerce helper functions.
 ## Store integration
 
 You will need a configurator web component build. For general information on how to embed the configurator
-into a host application, see [WebComponent API - Basics](/docs/integrations-webcomponent-api-basics--docs).
+into a host application, see [WebComponent API - Basics](?path=/docs/integrations-webcomponent-api-basics--docs).
 Additionally, due to the way WordPress works, there are a few specific steps you need to take to embed the
 configurator into WordPress.
 
@@ -41,7 +41,9 @@ but generally, at least the `session` and `add-to-cart-url` are required. The in
 the values as attributes on the configurator tag.
 
 When the user clicks the cart button in the configurator, the values `session` and `add-to-cart-url` are passed
-in a request to the finalization endpoint on the configurator server. During the finalization process, the cart item
+in a request to the finalization endpoint on the configurator server. The platform sends the plugin's API key to the cart endpoint,
+so the project's webhook builds the absolute URL from the shop's URL, kept in a webhook environment variable, and refuses any
+other origin; see the WooCommerceAddToCart task in [Webhooks](?path=/docs/phoenix-webhooks--docs). During the finalization process, the cart item
 data (eg. name, description, price) is calculated, and at the end a request is made to the plugin endpoint, to add
 the item to the cart.
 

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

@@ -40,7 +40,6 @@ import { useState } from 'react'
 
 import { LayoutSlots } from '@salsita-ai/sdk/configurator'
 
-import { phx } from '../../.phoenix/phx.js'
 import { BottomSheet } from '../_shared/BottomSheet.js'
 import { FullscreenToggle } from '../_shared/FullscreenToggle.js'
 import { MessageToast } from '../_shared/MessageToast.js'
@@ -168,7 +167,7 @@ const ConfiguratorLayout = () => {
 export default phx.frontend.createCustomPhoenixLayoutElement('ConfiguratorLayout', ConfiguratorLayout)
 ```
 
-The components it uses live in `src/_shared/`, which Phoenix does not import by convention, so the layout imports them itself. Application projects receive `phx` as a global. Storybook examples cannot rely on that project environment, so these files import it from `../../.phoenix/phx.js`; leave that import out in a project.
+The components it uses live in `src/_shared/`, which Phoenix does not import by convention, so the layout imports them itself. Application projects receive `phx` as a global. Storybook examples cannot rely on that project environment, so the example's files import it from `../../.phoenix/phx.js`; leave that import out in a project.
 
 ## What the layout has to do
 
@@ -190,7 +189,6 @@ import { Box, Button, Typography } from '@mui/material'
 
 import { detailComponent } from '@salsita-ai/sdk/domain'
 
-import { phx } from '../../.phoenix/phx.js'
 import { EdgeFinishCards } from './EdgeFinishCards.js'
 import { ReviewActions } from './ReviewActions.js'
 
@@ -348,8 +346,6 @@ import type { KeyboardEvent } from 'react'
 
 import type { UseAttributeSelection } from '@salsita-ai/sdk/react'
 
-import { phx } from '../../.phoenix/phx.js'
-
 // Cross-sections of the tabletop's edge, keyed by the option values of the spec.
 const EDGE_PROFILES: Readonly<Record<string, string>> = {
   None: 'M0 4H32V20H0Z',
@@ -488,8 +484,6 @@ import { Button, Tooltip } from '@mui/material'
 
 import { FrontendAnalyticsFactory } from '@salsita-ai/sdk/configurator'
 
-import { phx } from '../../.phoenix/phx.js'
-
 const ENTER_ICON = 'M4 9V4h5M15 4h5v5M20 15v5h-5M9 20H4v-5'
 const EXIT_ICON = 'M9 4v5H4M15 4v5h5M15 20v-5h5M9 20v-5H4'
 
@@ -550,8 +544,6 @@ The customer tries the four finishes against each other, so the layout offers **
 ```tsx
 import { Box, IconButton, Tooltip } from '@mui/material'
 
-import { phx } from '../../.phoenix/phx.js'
-
 const UNDO_ICON = 'M9 14 4 9l5-5M4 9h10.5a5.5 5.5 0 0 1 0 11H11'
 const REDO_ICON = 'M15 14l5-5-5-5M20 9H9.5a5.5 5.5 0 0 0 0 11H13'
 
@@ -625,8 +617,6 @@ import { useEffect, useState } from 'react'
 
 import type { ConfiguratorMessage } from '@salsita-ai/sdk/react'
 
-import { phx } from '../../.phoenix/phx.js'
-
 const VIOLATION_SEVERITY = { fatal: 'error', fixable: 'error', warning: 'warning', notice: 'info' } as const
 const RANK = { info: 0, warning: 1, error: 2 } as const
 const VISIBLE_MS = 6000
@@ -680,8 +670,6 @@ To give the toast something to show, the spec registers one transformer. Choosin
 ```ts
 import { msg } from '@lingui/core/macro'
 
-import { phx } from '../../.phoenix/phx.js'
-
 // A tree-trunk edge is cut by hand; choosing it carries a hint, which reaches the layout as a side-effect message
 export default phx.frontend.transformerBuilder.when
   .entity(['Table'])
@@ -717,8 +705,6 @@ components:
 ```ts
 import { useCallback } from 'react'
 
-import { phx } from '../../.phoenix/phx.js'
-
 // Stands in for the shop's quote service: the request takes a moment, then the panel shows the confirmation
 export default phx.frontend.createPhoenixHandler('requestQuote', () => {
   const navigate = phx.frontend.useNavigate()
@@ -739,8 +725,6 @@ The review step offers the spec's primary finalize action, or the first one when
 ```tsx
 import { Alert, Box, Button, CircularProgress, Typography } from '@mui/material'
 
-import { phx } from '../../.phoenix/phx.js'
-
 const BUTTON_SX = { minBlockSize: 48, borderRadius: 999, textTransform: 'none', fontWeight: 600 } as const
 
 interface ReviewActionsProps {
@@ -1053,7 +1037,6 @@ The element is registered with `phx.frontend.createCustomPhoenixEntityElement` u
 import { Box, ButtonBase, Popover, Tooltip } from '@mui/material'
 import { useState } from 'react'
 
-import { phx } from '../../.phoenix/phx.js'
 import { EdgeFinishCards } from '../_shared/EdgeFinishCards.js'
 
 // The edge profile the button shows, the square edge of the cards' drawings
@@ -1168,8 +1151,6 @@ components:
 ```tsx
 import { Box, Button, Tooltip } from '@mui/material'
 
-import { phx } from '../../.phoenix/phx.js'
-
 // The spec's view states, each with the label of the button that shows it
 const VIEWS = [
   { state: 'overview', label: 'Whole table' },
@@ -1742,8 +1723,6 @@ import type { KeyboardEvent } from 'react'
 
 import type { UseAttributeSelection } from '@salsita-ai/sdk/react'
 
-import { phx } from '../../.phoenix/phx.js'
-
 // Cross-sections of the tabletop's edge, keyed by the option values of the spec.
 const EDGE_PROFILES: Readonly<Record<string, string>> = {
   None: 'M0 4H32V20H0Z',
@@ -1878,8 +1857,6 @@ import { Button, Tooltip } from '@mui/material'
 
 import { FrontendAnalyticsFactory } from '@salsita-ai/sdk/configurator'
 
-import { phx } from '../../.phoenix/phx.js'
-
 const ENTER_ICON = 'M4 9V4h5M15 4h5v5M20 15v5h-5M9 20H4v-5'
 const EXIT_ICON = 'M9 4v5H4M15 4v5h5M15 20v-5h5M9 20v-5H4'
 
@@ -1939,8 +1916,6 @@ import { useEffect, useState } from 'react'
 
 import type { ConfiguratorMessage } from '@salsita-ai/sdk/react'
 
-import { phx } from '../../.phoenix/phx.js'
-
 const VIOLATION_SEVERITY = { fatal: 'error', fixable: 'error', warning: 'warning', notice: 'info' } as const
 const RANK = { info: 0, warning: 1, error: 2 } as const
 const VISIBLE_MS = 6000
@@ -1994,7 +1969,6 @@ import { Box, Button, Typography } from '@mui/material'
 
 import { detailComponent } from '@salsita-ai/sdk/domain'
 
-import { phx } from '../../.phoenix/phx.js'
 import { EdgeFinishCards } from './EdgeFinishCards.js'
 import { ReviewActions } from './ReviewActions.js'
 
@@ -2122,8 +2096,6 @@ export const ProductPanel = ({ collapsed = false, inSheet = false }: ProductPane
 ```tsx
 import { Alert, Box, Button, CircularProgress, Typography } from '@mui/material'
 
-import { phx } from '../../.phoenix/phx.js'
-
 const BUTTON_SX = { minBlockSize: 48, borderRadius: 999, textTransform: 'none', fontWeight: 600 } as const
 
 interface ReviewActionsProps {
@@ -2174,8 +2146,6 @@ export const ReviewActions = ({ onBack }: ReviewActionsProps) => {
 ```tsx
 import { Box, Button, Tooltip } from '@mui/material'
 
-import { phx } from '../../.phoenix/phx.js'
-
 // The spec's view states, each with the label of the button that shows it
 const VIEWS = [
   { state: 'overview', label: 'Whole table' },
@@ -2269,8 +2239,6 @@ export const SceneControls = ({ compact = false, resetOnly = false }: SceneContr
 ```tsx
 import { Box, IconButton, Tooltip } from '@mui/material'
 
-import { phx } from '../../.phoenix/phx.js'
-
 const UNDO_ICON = 'M9 14 4 9l5-5M4 9h10.5a5.5 5.5 0 0 1 0 11H11'
 const REDO_ICON = 'M15 14l5-5-5-5M20 9H9.5a5.5 5.5 0 0 0 0 11H13'
 
@@ -2338,7 +2306,6 @@ import { useState } from 'react'
 
 import { LayoutSlots } from '@salsita-ai/sdk/configurator'
 
-import { phx } from '../../.phoenix/phx.js'
 import { BottomSheet } from '../_shared/BottomSheet.js'
 import { FullscreenToggle } from '../_shared/FullscreenToggle.js'
 import { MessageToast } from '../_shared/MessageToast.js'
@@ -2472,7 +2439,6 @@ export default phx.frontend.createCustomPhoenixLayoutElement('ConfiguratorLayout
 import { Box, ButtonBase, Popover, Tooltip } from '@mui/material'
 import { useState } from 'react'
 
-import { phx } from '../../.phoenix/phx.js'
 import { EdgeFinishCards } from '../_shared/EdgeFinishCards.js'
 
 // The edge profile the button shows, the square edge of the cards' drawings
@@ -2531,8 +2497,6 @@ export default phx.frontend.createCustomPhoenixEntityElement('EdgeFinishHotspot'
 ### ./src/expressions/table.ts
 
 ```ts
-import { phx } from '../../.phoenix/phx.js'
-
 const EDGE_FINISH_SURCHARGE = { None: 0, Facet: 90, Round: 120, TreeTrunk: 340 }
 
 export default phx.domain.implementCustomExpressions({
@@ -2558,8 +2522,6 @@ export default phx.domain.implementCustomExpressions({
 ```ts
 import { useCallback } from 'react'
 
-import { phx } from '../../.phoenix/phx.js'
-
 // Stands in for the shop's quote service: the request takes a moment, then the panel shows the confirmation
 export default phx.frontend.createPhoenixHandler('requestQuote', () => {
   const navigate = phx.frontend.useNavigate()
@@ -2578,8 +2540,6 @@ export default phx.frontend.createPhoenixHandler('requestQuote', () => {
 ```ts
 import { msg } from '@lingui/core/macro'
 
-import { phx } from '../../.phoenix/phx.js'
-
 // A tree-trunk edge is cut by hand; choosing it carries a hint, which reaches the layout as a side-effect message
 export default phx.frontend.transformerBuilder.when
   .entity(['Table'])

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

@@ -300,8 +300,6 @@ import { Stack, Typography, styled } from '@mui/material'
 
 import { customPriceFooterComponent, memoEval } from '@salsita-ai/sdk/domain'
 
-import { phx } from '../../.phoenix/phx.js'
-
 const Row = styled('div')(() => ({
   display: 'flex',
   justifyContent: 'space-between',

package/dist/docs/layouts/custom-theme-handler.mdx

@@ -29,8 +29,6 @@ import { standardWebComponentProperties } from '@salsita-ai/sdk/domain'
 import { useWebComponentPropertyValue } from '@salsita-ai/sdk/react'
 import { desktopStyles, pxToRem } from '@salsita-ai/sdk/ui'
 
-import { phx } from '../../.phoenix/phx.js'
-
 const createCustomThemeOptions = (htmlFontSize: number): ThemeOptions => ({
   palette: {
     primary: { main: '#01483E', contrastText: '#FFFFFF' },
@@ -136,8 +134,6 @@ import { standardWebComponentProperties } from '@salsita-ai/sdk/domain'
 import { useWebComponentPropertyValue } from '@salsita-ai/sdk/react'
 import { desktopStyles, pxToRem } from '@salsita-ai/sdk/ui'
 
-import { phx } from '../../.phoenix/phx.js'
-
 const createCustomThemeOptions = (htmlFontSize: number): ThemeOptions => ({
   components: {
     MuiButton: {