@salsita-ai/sdk 0.50.0-develop.dbf0122072 → 0.50.0-develop.dd7119ab25

package/dist/application-spec/assistant/generate-assistant-prompt.d.ts

@@ -1,13 +0,0 @@
-import type { AssistantManifest } from '#package/domain';
-/**
- * The part of the assistant's system prompt that explains how to read the generated GraphQL schema.
- * It is generated here, by the SDK that also runs in the browser, and stored with the deployment,
- * because the conventions it describes belong to this SDK version and not to the server. The part
- * about changes is left out when the schema has no `Mutation` type, the part about adding
- * entities when it has no `addChild` mutation, the part about replacing them when it has no
- * `replaceEntity` mutation, the part about the choices of a field when it has
- * no options edge, and the part about custom changes when the manifest exposes no action. The last two sections explain the
- * `query` and `apply` tools, which every run registers whatever the schema holds, and the change
- * record the `AssistantSystem` attaches to every user message.
- */
-export declare const generateAssistantPrompt: (assistant: AssistantManifest) => string;

package/dist/application-spec/assistant/generate-assistant-prompt.js

@@ -1 +0,0 @@
-let e=["How to read the GraphQL schema of this configurator:","- A configuration is a set of entities. `root` is the root entity, `entities` lists every entity or the ones with the given ids, and `selectedEntity` is the entity the user has selected, or the root entity when nothing is selected.","- Every entity has an `id` of the form `<Type>-<number>`, for example `Table-1`, and a `type` with its entity type name. Ids are assigned by the configurator: read them from the configuration and never make one up.","- A field whose name starts with `_` is computed by the configurator from other values. It can be read like any other field and never written.","- Numbers are in the units the configuration stores them in. A field description names the unit when the product defines one.",'- A text field that only takes fixed values lists them in its description as "One of: ...". Use exactly those values.',"- A field typed as another entity type or as a list of one is a relation: select fields on it to read the related entities.","- Field and type descriptions come from the team that built the configurator and say what a value means for the product."],t=["How changes work:","- Every field of the `Mutation` type is one change. Its description says what it changes and what it returns.","- The configurator checks the whole configuration after each change. A change that would leave it invalid fails with an error that names the entities at fault, and it is not applied. Later changes of the same request are then not run.","- The configurator may adjust other values in response to a change, so read what a mutation returns instead of assuming the values you sent."],a=["How to add entities:","- Entities are added from recipes, the same ones the configurator offers the user. An entity type that can take children has a `meta` field; `meta { childRecipes }` lists its recipe groups and their recipes.","- List the recipes of the group first, pick one by its `key`, then call `addChild` with the id of the parent, the `groupId` and the `key`. Keys change with the configuration and the language, so never reuse one from memory.","- `dryRun` on a recipe shows what adding it would do without adding it: whether it is `ok`, the `changedEntities` it would add or modify, the `deletedEntityIds` it would remove, the `sideEffects` the configurator says it would have, and the `errors` when it cannot be added. An entity whose id the configuration does not have yet is new. It is costly, so select it only on the recipes you are deciding between.","- Put each `addChild` in its own operation. The recipes of a group and what they add depend on the configuration before them, so after adding something, list the group again before adding from it once more."],n=["How to replace entities:","- An entity is replaced from recipes, the same ones the configurator offers the user. An entity type that can be replaced has a `meta` field; `meta { replaceRecipes }` lists its replace recipe groups and what the entity can be replaced with.","- List the recipes of the group first, pick one by its `key`, then call `replaceEntity` with the id of the entity, the `groupId` and the `key`. `dryRun` on a replace recipe shows what replacing would do without doing it: the replacement and everything else that changes are under `changedEntities`, and the replaced entity is among the `deletedEntityIds`.","- The replacement is a new entity with a new id, and its field values come from the recipe, so they can differ from those of the entity it replaces. Read the ids and values `replaceEntity` returns, and never use the old id again.","- Put each `replaceEntity` in its own operation. The recipes of a group and what they do depend on the configuration before them, so after replacing something, list the group of the replacement again before replacing once more."],o=["How to find the values a field can take:","- Some fields store a key whose choices the configurator holds elsewhere. Such a field has an edge under `meta` named after it: `meta { <field>Options }` lists its choices, each with the `value` to write and the `name` the user sees.","- Read the choices before you write such a field or name a choice to the user, and write the `value`, not the `name`. A value outside the list is rejected unless the edge description says the field is not checked.","- `dryRun` on an option shows what writing its value would do without writing it: whether it is `ok`, the `changedEntities` it would add or modify, the `deletedEntityIds` it would remove, the `sideEffects` the configurator says it would have, and the `errors` when the value cannot be written. It is costly, so select it only on the options you are deciding between. It is null when the edge description says the options cannot be dry-run.","- The choices can depend on the entity and on its current state. Read them again after a change, unless the edge description says they are the same for all instances or do not change."],i=["How the custom changes of this configurator work:","- Besides the generic changes, the `Mutation` type has fields the team built for this product. Each runs one domain operation the configurator itself uses, so prefer it over composing the same change from generic mutations. Its description says what it does and what its arguments mean.","- Its arguments are checked against what the operation declares; an argument that does not fit, or a change the product does not allow, fails the field with a message that says what to send instead.","- It returns an object whose fields the description names; a field typed as an entity reads that entity after the change."],s=["How to use the `query` and `apply` tools:","- Both take `operations`, a list of GraphQL documents that run in order. Each document holds exactly one operation. To do several things, send several items in one call instead of several calls.","- Write values into the document as literals. Use `variables` only for a value that cannot be written as a literal.","- Select only the fields you need: results are returned whole.","- The result has one GraphQL result per operation, in the order sent. When an operation fails, its `errors` say why and the operations after it are not run.","- `query` reads the configuration the user has open and never changes it. Call it before you say anything about the configuration."],h=["- This configurator exposes no changes, so there is nothing for `apply` to run. Say so when the user asks you to change the configuration."],r=['- Mutations inside `query` answer "what if" questions. Each operation sees the changes of the ones before it, so a mutation followed by a query shows the configuration as it would be. Nothing is kept and the user sees no change.',"- `apply` makes the changes the user asked for. It is all or nothing: when any operation fails, nothing is changed; when all succeed, the user gets them as one undo step.","- `committed` in the result says whether the changes were kept. When it is false although no operation failed, `message` says why: the changes may be waiting for the approval of the user, the user may have changed the configuration meanwhile, or this session may not change the configuration at all. Without a `message`, the operations changed nothing. Never tell the user a change was made unless `committed` is true.","- `sideEffects` in the result lists what the configurator did beyond what the operations asked for, such as parts it added or replaced to keep the configuration valid, in its own words. Tell the user about them when the changes were kept. When they were not, or in `query`, it lists what the mutations that succeeded would do. `dryRun` has the same list for a single recipe or option."],d=["How to read the change record:","- Every user message starts with a change record of the configuration since your previous action. It is the complete list of the entities that were added or deleted, of the stored fields of this schema that changed, and of the selection and navigation changes, so update your picture from it and do not query those again when it does not mention them.","- Fields whose name starts with `_` are computed and are never listed. Read them again when the record lists a change they may depend on.","- `[changes: none]`: nothing changed. Do not query again what you already know.","- `[changes]` is followed by one line per change. `selected`, `navigationState`, `viewState` and `toolState` lines show `<old> -> <new>` of what `selectedEntity` and `navigation` return, with `none` for an empty value. `A <id>` is an added entity and `D <id>` a deleted one. `M <id>` is a modified entity, followed by one `<field>: <old> -> <new>` line per changed field, under the name the field has in this schema. A `reset: undo/redo` line says the user undid or redid changes.","- The `#` comment at the end of a line names the control, the transformer or the explanation of the last change to that line.","- `[changes: unavailable]`: the page was loaded since your previous action, so earlier values may be stale. `[changes: too many (n)]`: n entities changed and are not listed. In both cases query what you need."],c=["- Changes you applied are not in the record, except those that were waiting for the approval of the user: they appear in it once approved."];export const generateAssistantPrompt=l=>{let u=/^type Mutation\b/m.test(l.sdl);return[e,...u?[t]:[],.../^\s+addChild\(/m.test(l.sdl)?[a]:[],.../^\s+replaceEntity\(/m.test(l.sdl)?[n]:[],.../^type FieldOption\b/m.test(l.sdl)?[o]:[],...Object.keys(l.actions??{}).length>0?[i]:[],[...s,...u?r:h],[...d,...u?c:[]]].map(e=>e.join("\n")).join("\n\n")};

package/dist/application-spec/assistant/index.d.ts

@@ -1 +0,0 @@
-export { generateAssistantPrompt } from './generate-assistant-prompt.js';

package/dist/application-spec/assistant/index.js

@@ -1 +0,0 @@
-export{generateAssistantPrompt}from"./generate-assistant-prompt.js";

package/dist/application-spec/core/eval-to-constant.d.ts

@@ -1,14 +0,0 @@
-import type { EvalExpressionParser } from './eval-expression-parser.js';
-type FoldedValue = string | number | boolean | null | undefined | readonly FoldedValue[] | {
-    readonly [key: string]: FoldedValue;
-};
-interface EvalToConstantSuccess {
-    readonly ok: true;
-    readonly value: FoldedValue;
-}
-interface EvalToConstantFailure {
-    readonly ok: false;
-}
-type EvalToConstantResult = EvalToConstantSuccess | EvalToConstantFailure;
-export declare const evalToConstant: (code: string, parseExpression: EvalExpressionParser) => EvalToConstantResult;
-export {};

package/dist/application-spec/generate-application/code/templates/env-ci.d.ts

@@ -1 +0,0 @@
-export declare const generateApplicationSpecEnvCi: () => string;

package/dist/application-spec/generate-application/code/templates/env-ci.js

@@ -1,25 +0,0 @@
-export const generateApplicationSpecEnvCi=()=>`# CI Environment Configuration
-#
-# This file is used to initialize environment variables in CI pipelines with mock data.
-# It allows the frontend and webhooks to be built without requiring actual credentials.
-# These values are sufficient for builds. DEPLOYMENT_ID also supports local-storage runtime;
-# server-backed runtime operations still require real deployment credentials.
-#
-# To use: run 'pnpm run prepare:ci' to copy this file to .env
-
-# Frontend
-DEPLOYMENT_ID=will-not-work-but-will-initialize
-SERVER_URL=http://not.valid
-FRONTEND_URL=http://not.valid
-RESOURCES_URL=http://not.valid
-CLERK_PUBLISHABLE_KEY=will-not-work-but-will-initialize
-GTM_ID=GTM-XXXXXX
-DATADOG_CLIENT_TOKEN=XXXXXX
-DATADOG_SITE=XXX
-SERVICE_NAME=project-template
-
-# Webhook
-AWS_S3_PUBLIC_RESOURCES_BUCKET=private
-AWS_S3_PRIVATE_RESOURCES_BUCKET=public
-AWS_S3_RESOURCES_REGION=eu-central-1
-`;

package/dist/application-spec/generate-application/code/templates/env-example.d.ts

@@ -1 +0,0 @@
-export declare const generateApplicationSpecEnvExample: () => string;

package/dist/application-spec/generate-application/code/templates/env-example.js

@@ -1,90 +0,0 @@
-export const generateApplicationSpecEnvExample=()=>`# This file documents developer-supplied Phoenix variables. Copy the values you
-# need into an untracked .env; never commit .env.
-# phoenix dev, deployment:prepare-dev, and deployment:prepare-local write
-# server-generated values to .env.generated; do not maintain them here.
-
-# ============================================================================
-# Development environment (phoenix dev and deployment:prepare-dev)
-# ============================================================================
-# Not needed when you are signed in with phoenix login. Otherwise create a
-# development environment in PHX Studio and paste its block here.
-#
-# SERVER_URL=http://localhost:3000
-# PROJECT_SLUG=<project-slug>
-# ENVIRONMENT_SLUG=<development-environment-slug>
-# DEVELOPMENT_KEY=<development-key>
-
-# ============================================================================
-# Shared-server access (deployment:prepare-local and CI commands only)
-# ============================================================================
-# Ask DevOps for these values when using the legacy prepare-local or CI flows.
-# SERVER_URL=https://phoenix.example.com
-# ENVIRONMENT_API_KEY=<shared-server-api-key>
-# PROJECT_KEY=<shared-server-project-key>
-# PROJECT_SLUG=<project-slug>
-# ENVIRONMENT_SLUG=<environment-slug>
-# LAMBDA_URL=http://localhost:8080
-
-# ============================================================================
-# Dev Configuration (phoenix dev)
-# ============================================================================
-# Override these to run multiple projects simultaneously.
-# Ports auto-increment if occupied, but setting explicit values avoids surprises.
-#
-# EDITOR_WS_PORT=3020
-# ENABLE_EDITOR=true
-# Enable Lingui extraction and compilation during dev. Phoenix warns when this is disabled.
-# WITH_LINGUI=false
-# DEBUG=false
-# FORCE_REBUILD=false
-# USE_APPLICATION_SPEC=true
-# IS_DEV=true
-#
-# Persistence mode controls how configurator state is stored.
-# Options: 'server' (default), 'local-storage', 'memory'
-# PERSISTENCE_MODE=server
-
-# deployment:prepare-dev and deployment:prepare-local output and behavior overrides:
-# OUT_FILE=.env.generated
-# SKIP_UPLOAD also applies to the deployment phoenix dev prepares at startup.
-# SKIP_UPLOAD=false
-# OVERRIDE_SCHEMA=true
-
-# ============================================================================
-# Project-Specific Environment Variables
-# ============================================================================
-# Additional environment variables can be defined in spec/application.yaml
-# under the 'env.frontend' and 'env.webhook' sections.
-#
-# These are useful for project-specific needs such as:
-# - Third-party API keys (e.g., salesforce)
-# - External service URLs
-# - Feature flags
-# - Custom configuration values
-#
-# Example in spec/application.yaml:
-#   env:
-#     frontend:
-#       SALESFORCE_CLIENT_ID:
-#         type: str
-#         devDefault: pk_test_xxx
-#     webhook:
-#       SALESFORCE_CLIENT_SECRET:
-#         type: str
-#       SALESFORCE_REDIRECT_URI:
-#         type: str
-#
-# These will be automatically validated and available in your code via
-# the generated frontend.config.ts and webhooks.config.ts files.
-#
-# IMPORTANT: If you add required custom environment variables (without defaults),
-# remember to also add them to .env.ci with mock values so CI builds can succeed.
-
-# ============================================================================
-# Generated environment
-# ============================================================================
-# Deployment variables (DEPLOYMENT_ID, RESOURCES_URL, and related values)
-# are auto-generated by the PHX server and written to .env.generated when you run
-# phoenix dev, deployment:prepare-dev, or deployment:prepare-local. Development
-# environment settings can be managed via PHX Studio.
-`;

package/dist/application-spec/generate-application/code/templates/nvmrc.d.ts

@@ -1 +0,0 @@
-export declare const generateApplicationSpecNvmrc: () => string;

package/dist/application-spec/generate-application/code/templates/nvmrc.js

@@ -1,2 +0,0 @@
-export const generateApplicationSpecNvmrc=()=>`v24.14.1
-`;

package/dist/application-spec/generate-application/code/templates/package-json.d.ts

@@ -1,10 +0,0 @@
-interface GenerateApplicationSpecPackageJsonProps {
-    readonly sdkVersion: string;
-    readonly useWorkspace: boolean;
-    readonly useClerk?: boolean;
-    readonly name?: string;
-    readonly description?: string;
-    readonly existingContent?: string;
-}
-export declare const generateApplicationSpecPackageJson: (props: GenerateApplicationSpecPackageJsonProps) => string;
-export {};

package/dist/application-spec/generate-application/code/templates/package-json.js

@@ -1 +0,0 @@
-let e=["@salsita-ai/platform-project-sdk","@salsita-ai/platform-common","@salsita-ai/platform-contracts","@salsita-ai/common","@salsita-ai/contracts"],t=(e,t)=>e>t?1:e<t?-1:0,r={private:!0,type:"module",packageManager:"pnpm@11.1.3",engines:{node:"24.14.1",pnpm:"11.1.3"}},i={"babel-plugin-macros":"3.1.0",vite:"6.4.3","@vitejs/plugin-react":"5.2.0","@swc/cli":"0.8.1","@swc/core":"1.15.40",typescript:"npm:@typescript/typescript6@6.0.2","@lingui/cli":"5.9.5","@types/lodash-es":"4.17.12","@lingui/macro":"5.9.5","@lingui/swc-plugin":"5.11.0","@types/node":"24.12.2","@types/react":"18.3.8","@types/react-dom":"18.3.0","@types/three":"0.160.0","@typescript/native":"npm:typescript@7.0.2",envalid:"8.1.1",eslint:"9.39.4",prettier:"3.8.3",vitest:"4.1.11"},n={build:"phoenix build",clean:"phoenix clean",dev:"phoenix dev","dev:local":"phoenix dev --persistence local-storage",sync:"phoenix sync",check:"phoenix check",fix:"phoenix fix","verify:fix":"phoenix build && phoenix fix && phoenix check --types",test:"vitest --passWithNoTests run","test:watch":"vitest","prepare:ci":"phoenix prepare:ci","deployment:prepare-local":"phoenix deployment:prepare-local"},s=["environment:create","environment:list","deployment:register","deployment:register:skip","lint:check","prettify:check","ts:check","lint:fix","prettify:fix"],c=e=>"object"==typeof e&&null!==e&&!Array.isArray(e),o=e=>{if(!c(e))return;let t=[];for(let[r,i]of Object.entries(e)){if("string"!=typeof i)return;t.push([r,i])}return Object.fromEntries(t)},a=e=>e.replace(/^[\^~]/,""),p=(r,i)=>{let n={};for(let[e,t]of Object.entries(r))n[e]=a(t);if(i)for(let[e,t]of Object.entries(i))e in n||(n[e]=a(t));return Object.fromEntries(Object.entries(n).filter(([t])=>!e.includes(t)).sort(([e],[r])=>t(e,r)))};export const generateApplicationSpecPackageJson=e=>{let{sdkVersion:a,useWorkspace:l,useClerk:f=!1,name:m,description:d,existingContent:u}=e,y=(e=>{if(!e)return{};try{let t=JSON.parse(e);if(c(t))return t}catch{}return{}})(u),h=p({...f?{"@clerk/clerk-react":"5.61.8"}:{},"camera-controls":"2.4.2","lodash-es":"4.18.1",react:"18.3.1","react-dom":"18.3.1","@emotion/react":"11.11.3","@emotion/styled":"11.11.0","@mui/material":"5.15.5","@mui/system":"5.16.7","@lingui/core":"5.9.5","@lingui/react":"5.9.5",three:"0.160.1","@react-three/fiber":"8.15.16","@react-three/drei":"9.97.6","@react-three/postprocessing":"2.16.3",motion:"12.34.0","@tanstack/react-query":"5.100.14",rxjs:"7.8.2",uuid:"14.0.0","ts-pattern":"5.9.0","@salsita-ai/sdk":l?"workspace:^":a,zod:"3.25.76"},o(y.dependencies)),g=p(i,o(y.devDependencies)),x=((e,r)=>{let i={};for(let[t,r]of Object.entries(e))i[t]=r;if(r)for(let[e,t]of Object.entries(r))e in i||(i[e]=t);return Object.fromEntries(Object.entries(i).filter(([e])=>!s.includes(e)).sort(([e],[r])=>t(e,r)))})({...n,...l?{dev:"phoenix dev --local"}:{}},o(y.scripts)),v=y.name,b=m?m.toLowerCase().replace(/[^a-z0-9-]/g,"-"):"string"==typeof v?v:"project-name",j={...y,name:b,...r,scripts:x,dependencies:h,devDependencies:g};return void 0!==d&&(j.description=d),JSON.stringify(j,null,2)+"\n"};

package/dist/application-spec/generate-application/code/templates/prettier-ignore.d.ts

@@ -1 +0,0 @@
-export declare const generateApplicationSpecPrettierIgnore: () => string;

package/dist/application-spec/generate-application/code/templates/prettier-ignore.js

@@ -1,6 +0,0 @@
-export const generateApplicationSpecPrettierIgnore=()=>`/dist
-**/__generated
-**/locales/**/*
-pnpm-lock.yaml
-.linguirc
-.nvmrc`;

package/dist/application-spec/generate-application/code/templates/private-assets-readme.d.ts

@@ -1 +0,0 @@
-export declare const generateApplicationSpecPrivateAssetsReadme: () => string;

package/dist/application-spec/generate-application/code/templates/private-assets-readme.js

@@ -1,24 +0,0 @@
-export const generateApplicationSpecPrivateAssetsReadme=()=>`# Private Assets
-
-This folder contains private environment resources that will be uploaded to S3 and made available only to your webhooks with authentication.
-
-## Usage
-
-1. Place any private assets in this folder
-2. Files uploaded here will require authentication to access
-3. These assets are typically used in webhook implementations for server-side operations
-
-## Examples
-
-- Private configuration files
-- Server-side resources
-- Blender scripts
-
-## Deployment
-
-When you run \`pnpm run deployment:prepare-local\`, all files in this folder will be:
-
-- Uploaded to S3 with private access control
-- Only accessible by authenticated webhook requests
-- Available via signed URLs
-`;

package/dist/application-spec/generate-application/code/templates/public-assets-readme.d.ts

@@ -1 +0,0 @@
-export declare const generateApplicationSpecPublicAssetsReadme: () => string;

package/dist/application-spec/generate-application/code/templates/public-assets-readme.js

@@ -1,24 +0,0 @@
-export const generateApplicationSpecPublicAssetsReadme=()=>`# Public Assets
-
-This folder contains public environment resources that will be uploaded to S3 and made available to your configurator and webhooks.
-
-## Usage
-
-1. Place any public assets (images, 3D models, textures, etc.) in this folder
-2. Files uploaded here will be publicly accessible via S3 URLs
-3. These assets can be referenced in your configurator frontend and webhook implementations
-
-## Examples
-
-- Product images
-- Icons and logos
-- Public configuration files
-
-## Deployment
-
-When you run \`pnpm run deployment:prepare-local\`, all files in this folder will be:
-
-- Uploaded to S3
-- Made publicly accessible
-- Available via the configured CDN/S3 URL
-`;

package/dist/application-spec/generate-application/code/templates/readme.d.ts

@@ -1 +0,0 @@
-export declare const generateApplicationSpecReadme: (projectName?: string) => string;

package/dist/application-spec/generate-application/code/templates/readme.js

@@ -1,23 +0,0 @@
-export const generateApplicationSpecReadme=(e="project-template")=>{let t=e.toLowerCase().replace(/[^a-z0-9]+/g,"-");return`# configurator-${t}
-
-This repository is built on top of PHX platform and uses @salsita-ai/sdk packages to build the configurator experience.
-
-## To run this project
-
-1. \`pnpm install\` (you need access to @salsita-ai organization)
-2. \`pnpm run sync\`
-3. Sign in with \`pnpm phoenix login <workspace>\`. Or, to develop against a Studio development environment, create one in PHX Studio and paste its \`SERVER_URL\`, \`PROJECT_SLUG\`, \`ENVIRONMENT_SLUG\`, and \`DEVELOPMENT_KEY\` block into \`.env\`.
-4. Make sure the target PHX server is running.
-5. Run \`pnpm run dev\`. It prepares the development deployment, writes \`.env.generated\`, and starts the development servers.
-
-## Useful scripts
-
-\`pnpm run check\` - runs TypeScript, ESLint, and Prettier checks
-\`pnpm run fix\` - runs ESLint and Prettier fixes for auto-fixable issues. Run this before pushing to CI.
-\`pnpm run build\` - builds the project for production
-\`pnpm run clean\` - cleans build artifacts, reinstalls dependencies, and rebuilds specs
-
-## Deployment
-
-Run \`pnpm phoenix deploy\` to build and deploy the project to your workspace, or connect the repository to the deployment pipeline that comes with your workspace. Studio shows the deployments, their logs and the live URL of every environment.
-`};

package/dist/application-spec/generate-application/code/templates/skills/agents-md.d.ts

@@ -1 +0,0 @@
-export declare const generateAgentsMd: () => string;

package/dist/application-spec/generate-application/code/templates/skills/agents-md.js

@@ -1,2 +0,0 @@
-import{sdkGuidanceSections as e}from"./sdk-content.js";export const generateAgentsMd=()=>`${[e.projectIntro,e.buildCommands,e.doNotEdit,"Phoenix SDK guidance lives in the `phoenix`, `phoenix-cli`, `phoenix-create-configurator`, `phoenix-feedback`, `phoenix-review` and `phoenix-variants` skills under `.claude/skills/` and `.agents/skills/`. Phoenix rewrites them on every sync, removes anything else inside their folders and removes other `phoenix`-prefixed skill folders, so to customise a skill, copy it to a folder whose name does not start with `phoenix`."].join("\n\n")}
-`;

package/dist/application-spec/generate-application/code/templates/webhook-implementation.d.ts

@@ -1 +0,0 @@
-export declare const generateApplicationSpecWebhookImplementation: () => string;

package/dist/application-spec/generate-application/code/templates/webhook-implementation.js

@@ -1,7 +0,0 @@
-export const generateApplicationSpecWebhookImplementation=()=>`// A webhook needs at least one handler; anonymous auth stays inert until spec/application.yaml sets useAuthHook
-const authHandler = phx.webhooks.authHandlerBuilder
-  .withAnonymousHandler(async () => ({ success: true, data: {}, role: 'anonymous' }))
-  .build()
-
-export default phx.webhooks.webhookBuilder.withAuthHook(authHandler).build()
-`;

package/dist/configurator/common/frontend-analytics.d.ts

@@ -1,46 +0,0 @@
-import { type EntityId } from '#package/domain';
-declare const CloseConfiguratorClicked: () => import("#package/domain").UserActionEvent;
-declare const PreviousStepButtonClicked: () => import("#package/domain").UserActionEvent;
-declare const NextStepButtonClicked: () => import("#package/domain").UserActionEvent;
-declare const FinalizeButtonClicked: () => import("#package/domain").UserActionEvent;
-declare const SummaryButtonClicked: () => import("#package/domain").UserActionEvent;
-declare const TopNavigationStepClicked: (step: string) => import("#package/domain").UserActionEvent;
-declare const HorizontalTabClicked: (tab: string) => import("#package/domain").UserActionEvent;
-declare const GoToProductsClicked: () => import("#package/domain").UserActionEvent;
-declare const ExpandedViewClosed: () => import("#package/domain").UserActionEvent;
-declare const ProductSelected: (productType: string, productName: string) => import("#package/domain").UserActionEvent;
-declare const SelectionHotspotClicked: (id: string) => import("#package/domain").UserActionEvent;
-declare const RedoButtonClicked: () => import("#package/domain").UserActionEvent;
-declare const UndoButtonClicked: () => import("#package/domain").UserActionEvent;
-declare const GlobalDimensionsButtonClicked: (dimensionUnit: string) => import("#package/domain").UserActionEvent;
-declare const MeasurementsMenuToggled: () => import("#package/domain").UserActionEvent;
-declare const MeasurementsMenuClosed: () => import("#package/domain").UserActionEvent;
-declare const DimensionIndicatorsToggled: () => import("#package/domain").UserActionEvent;
-declare const FullScreenModeToggled: () => import("#package/domain").UserActionEvent;
-declare const HelpDialogOpened: () => import("#package/domain").UserActionEvent;
-declare const HelpDialogClosed: () => import("#package/domain").UserActionEvent;
-declare const EntityDeleteHotspotClicked: (id: EntityId) => import("#package/domain").UserActionEvent;
-export declare const FrontendAnalyticsFactory: {
-    CloseConfiguratorClicked: typeof CloseConfiguratorClicked;
-    PreviousStepButtonClicked: typeof PreviousStepButtonClicked;
-    NextStepButtonClicked: typeof NextStepButtonClicked;
-    FinalizeButtonClicked: typeof FinalizeButtonClicked;
-    SummaryButtonClicked: typeof SummaryButtonClicked;
-    TopNavigationStepClicked: typeof TopNavigationStepClicked;
-    HorizontalTabClicked: typeof HorizontalTabClicked;
-    GoToProductsClicked: typeof GoToProductsClicked;
-    ProductSelected: typeof ProductSelected;
-    SelectionHotspotClicked: typeof SelectionHotspotClicked;
-    RedoButtonClicked: typeof RedoButtonClicked;
-    UndoButtonClicked: typeof UndoButtonClicked;
-    GlobalDimensionsButtonClicked: typeof GlobalDimensionsButtonClicked;
-    MeasurementsMenuToggled: typeof MeasurementsMenuToggled;
-    MeasurementsMenuClosed: typeof MeasurementsMenuClosed;
-    DimensionIndicatorsToggled: typeof DimensionIndicatorsToggled;
-    FullScreenModeToggled: typeof FullScreenModeToggled;
-    HelpDialogOpened: typeof HelpDialogOpened;
-    HelpDialogClosed: typeof HelpDialogClosed;
-    EntityDeleteHotspotClicked: typeof EntityDeleteHotspotClicked;
-    ExpandedViewClosed: typeof ExpandedViewClosed;
-};
-export {};

package/dist/configurator/common/frontend-analytics.js

@@ -1 +0,0 @@
-import{AnalyticsEventFactory as e,domainEntityTypeFromId as t,isVirtualEntityId as o}from"#package/domain";export const FrontendAnalyticsFactory={CloseConfiguratorClicked:()=>e.UserActionEvent({section:"topNavigation",element:"button",action:"click",result:"User requested to close the configurator."}),PreviousStepButtonClicked:()=>e.UserActionEvent({section:"sidebar",element:"previousStepButton",action:"click",result:"User clicked on previous step button."}),NextStepButtonClicked:()=>e.UserActionEvent({section:"sidebar",element:"nextStepButton",action:"click",result:"User clicked on next step button."}),FinalizeButtonClicked:()=>e.UserActionEvent({section:"sidebar",element:"finalizeButton",action:"click",result:"User clicked on finalize button."}),SummaryButtonClicked:()=>e.UserActionEvent({section:"sidebar",element:"summaryButton",action:"click",result:"User clicked go to summary button."}),TopNavigationStepClicked:t=>e.UserActionEvent({section:"topNavigation",element:"step",action:"click",result:"User clicked on top navigation step.",data:{step:t}}),HorizontalTabClicked:t=>e.UserActionEvent({section:"topNavigation",element:"horizontalTab",action:"click",result:"User clicked on horizontal tab.",data:{tab:t}}),GoToProductsClicked:()=>e.UserActionEvent({section:"topNavigation",element:"button",action:"click",result:"User requested to go to the product page."}),ProductSelected:(t,o)=>e.UserActionEvent({section:"productPage",element:"selectCardButton",action:"click",data:{productType:t,productName:o},result:"User has selected a product."}),SelectionHotspotClicked:t=>e.UserActionEvent({section:"canvas",element:"selectionHotspot",action:"click",result:"User clicked on selection hotspot of an entity.",data:{id:t}}),RedoButtonClicked:()=>e.UserActionEvent({section:"bottomToolbar",element:"redoButton",action:"click",result:"User clicked on redo button."}),UndoButtonClicked:()=>e.UserActionEvent({section:"bottomToolbar",element:"undoButton",action:"click",result:"User clicked on undo button."}),GlobalDimensionsButtonClicked:t=>e.UserActionEvent({section:"bottomToolbar",element:"measurementUnitButton",action:"click",data:{dimensionUnit:t},result:"Global measurement units were changed."}),MeasurementsMenuToggled:()=>e.UserActionEvent({section:"bottomToolbar",element:"measurementsMenu",action:"click",result:"User opened the measurements menu."}),MeasurementsMenuClosed:()=>e.UserActionEvent({section:"bottomToolbar",element:"measurementsMenu",action:"click",result:"User closed the measurements menu."}),DimensionIndicatorsToggled:()=>e.UserActionEvent({section:"bottomToolbar",element:"dimensionIndicatorsToggle",action:"click",result:"User toggled dimension indicators visibility."}),FullScreenModeToggled:()=>e.UserActionEvent({section:"bottomToolbar",element:"fullscreenButton",action:"click",result:"User toggled fullscreen mode."}),HelpDialogOpened:()=>e.UserActionEvent({section:"bottomToolbar",element:"helpButton",action:"click",result:"Help dialog opened."}),HelpDialogClosed:()=>e.UserActionEvent({section:"bottomToolbar",element:"helpDialog",action:"click",result:"Help dialog closed."}),EntityDeleteHotspotClicked:n=>{let i=o(n)?"":t(n);return e.UserActionEvent({section:"canvas",element:"deleteEntityHotspot",action:"click",data:{id:n,type:i},result:"User has deleted an entity."})},ExpandedViewClosed:()=>e.UserActionEvent({section:"topNavigation",element:"button",action:"click",result:"User requested to close the expanded view."})};

package/dist/domain/actions/action-factory.d.ts

@@ -1,10 +0,0 @@
-import type { ActionImplementations, ActionTypes } from '../core/action.js';
-import type { $DomainEntity, DomainEntity } from '../core/model.js';
-/**
- * Creates the `implementActions` factory the generated `domain-spec.ts` exposes as
- * `phx.domain.implementActions`. A module in `src/actions/` implements any subset of the declared
- * actions and gets each parameter and result typed from the spec; a name the spec does not declare
- * is a type error, since its implementation would have to be `never`. The generated barrel merges
- * the modules and checks that every declared action is implemented.
- */
-export declare const createActionFactory: <ENTITIES extends DomainEntity<string>, ALLOWED_ROOT_ENTITIES extends ENTITIES, $MAP extends Record<ENTITIES['type'], $DomainEntity<ENTITIES>>, PUBLISHED_DATA extends Record<string, unknown>, SESSION_DATA extends Record<string, unknown>, FRONTEND_DATA extends Record<string, unknown>, NAVIGATION_STATES extends string, VIEW_STATES extends string, TOOL_STATES extends string, EXPORT_STATES extends string, ACTION_TYPES extends ActionTypes>() => <IMPLEMENTATIONS extends Partial<ActionImplementations<ENTITIES, ALLOWED_ROOT_ENTITIES, $MAP, PUBLISHED_DATA, SESSION_DATA, FRONTEND_DATA, NAVIGATION_STATES, VIEW_STATES, TOOL_STATES, EXPORT_STATES, ACTION_TYPES>>>(implementations: IMPLEMENTATIONS & Readonly<Record<Exclude<keyof IMPLEMENTATIONS, keyof ACTION_TYPES>, never>>) => IMPLEMENTATIONS;

package/dist/domain/actions/prepare-action-implementations.d.ts

@@ -1,15 +0,0 @@
-import type { ActionDefinitions, AnyActionImplementations } from '../core/index.js';
-/** The declared actions that have no implementation, and the implementations of undeclared names. */
-export interface ActionImplementationConflicts {
-    readonly missing: readonly string[];
-    readonly extra: readonly string[];
-}
-/** Compares the names of the declared actions with the implemented ones. */
-export declare const findActionImplementationConflicts: (declared: readonly string[], implementations: AnyActionImplementations) => ActionImplementationConflicts;
-/**
- * Validates the implemented actions against the declared ones, as `prepareDomainExpressions` does
- * for expressions: a declared action without an implementation throws, so the domain is not
- * instantiated with an action that can only fail when it is called; an implementation of an
- * undeclared name is logged. Returns the implementations unchanged.
- */
-export declare const prepareActionImplementations: (definitions: ActionDefinitions, implementations: AnyActionImplementations) => AnyActionImplementations;

package/dist/domain/actions/prepare-action-implementations.js

@@ -1,5 +0,0 @@
-export const findActionImplementationConflicts=(e,n)=>{let t=Object.keys(n);return{missing:e.filter(e=>!t.includes(e)),extra:t.filter(n=>!e.includes(n))}};export const prepareActionImplementations=(e,n)=>{let{missing:t,extra:i}=findActionImplementationConflicts(Object.values(e).map(e=>e.name),n);if(0===t.length&&0===i.length)return n;let o=Error("Domain cannot be instantiated because there are conflicts between declared and implemented actions."+(t.length>0?`
-
-Missing actions: ${t.join(", ")}. Add each to a default export of phx.domain.implementActions({ ... }) in src/actions/.`:"")+(i.length>0?`
-
-Extra actions: ${i.join(", ")}. Declare each under "actions" in a spec file or remove its implementation.`:"")+"\n");if(t.length>0)throw o;return console.error(o),n};

package/dist/domain/application/element-registration.d.ts

@@ -1,105 +0,0 @@
-import type { SvgIconProps } from '@mui/material';
-import type { PropsWithChildren, ReactNode } from 'react';
-import type { ExtendedJsonSchema } from '@salsita-ai/common/utils';
-import type { DomainEntityId } from '../core/index.js';
-export interface PhoenixEntityElementProps {
-    entityId: DomainEntityId<string>;
-    children?: ReactNode;
-}
-export type PhoenixEntityElementRegistration = {
-    type: 'entity';
-    name: string;
-    element: (props: PhoenixEntityElementProps) => JSX.Element;
-};
-export type PhoenixLayoutElementRegistration = {
-    type: 'layout';
-    name: string;
-    element: (props: PropsWithChildren) => JSX.Element;
-};
-export type PhoenixIconRegistration = {
-    type: 'icon';
-    elements: ReadonlyArray<(props: SvgIconProps) => JSX.Element>;
-};
-export type ElementRegistration = PhoenixEntityElementRegistration | PhoenixLayoutElementRegistration | PhoenixIconRegistration;
-export interface CustomPhoenixEntityElementProps {
-    entityId: DomainEntityId<string>;
-    children?: ReactNode;
-}
-export interface SystemElementRegistry {
-    layoutElements: Record<string, (props: PropsWithChildren) => JSX.Element>;
-    entityElements: Record<string, (props: CustomPhoenixEntityElementProps) => JSX.Element>;
-}
-/**
- * Internal registry for system-level elements registered at import time
- * via createPhoenixLayoutElement / createPhoenixEntityElement.
- */
-export declare const systemElementRegistry: SystemElementRegistry;
-type SchemaOfPhoenixLayoutElement<SCHEMA extends {
-    kind: string;
-    props?: Record<string, unknown>;
-}> = {
-    type: 'object';
-    properties: {
-        kind: {
-            type: 'string';
-            enum: [SCHEMA['kind']];
-        };
-        props?: {
-            type: 'object';
-            properties: Record<keyof SCHEMA['props'], any>;
-        };
-    };
-} & ExtendedJsonSchema;
-export interface PhoenixLayoutElementDefinition<SCHEMA extends {
-    kind: string;
-    props?: Record<string, unknown>;
-}> {
-    schema: SchemaOfPhoenixLayoutElement<SCHEMA>;
-    component: React.FunctionComponent<SCHEMA['props'] & {
-        children?: ReactNode;
-    }>;
-}
-/**
- * For internal use in PHX only.
- */
-export declare const createPhoenixLayoutElement: <SCHEMA extends {
-    kind: string;
-    props?: Record<string, unknown>;
-} = never>(element: PhoenixLayoutElementDefinition<SCHEMA>) => import("react").FunctionComponent<SCHEMA["props"] & {
-    children?: ReactNode;
-}>;
-export declare const createCustomPhoenixLayoutElement: (name: string, element: (props: PropsWithChildren) => JSX.Element) => PhoenixLayoutElementRegistration;
-export type CreateCustomPhoenixLayoutElement = (name: string, element: (props: PropsWithChildren) => JSX.Element) => PhoenixLayoutElementRegistration;
-type SchemaOfPhoenixElement<SCHEMA extends {
-    kind: string;
-    props?: Record<string, unknown>;
-}> = {
-    type: 'object';
-    properties: {
-        kind: {
-            type: 'string';
-            enum: [SCHEMA['kind']];
-        };
-        props?: {
-            type: 'object';
-            properties: Record<keyof SCHEMA['props'], any>;
-        };
-    };
-} & ExtendedJsonSchema;
-export interface PhoenixEntityElementDefinition<SCHEMA extends {
-    kind: string;
-    props?: Record<string, unknown>;
-}> {
-    schema: SchemaOfPhoenixElement<SCHEMA>;
-    component: React.FunctionComponent<SCHEMA['props'] & CustomPhoenixEntityElementProps>;
-}
-/**
- * For internal use in PHX only.
- */
-export declare const createPhoenixEntityElement: <SCHEMA extends {
-    kind: string;
-    props?: Record<string, unknown>;
-} = never>(element: PhoenixEntityElementDefinition<SCHEMA>) => import("react").FunctionComponent<SCHEMA["props"] & CustomPhoenixEntityElementProps>;
-export declare const createCustomPhoenixEntityElement: (name: string, element: (props: CustomPhoenixEntityElementProps) => JSX.Element) => PhoenixEntityElementRegistration;
-export type CreateCustomPhoenixEntityElement = (name: string, element: (props: CustomPhoenixEntityElementProps) => JSX.Element) => PhoenixEntityElementRegistration;
-export {};

package/dist/domain/application/element-registration.js

@@ -1 +0,0 @@
-export const systemElementRegistry={layoutElements:{},entityElements:{}};export const createPhoenixLayoutElement=e=>(systemElementRegistry.layoutElements[e.schema.properties.kind.enum[0]]=e.component,e.component);export const createCustomPhoenixLayoutElement=(e,t)=>({type:"layout",name:e,element:t});export const createPhoenixEntityElement=e=>(systemElementRegistry.entityElements[e.schema.properties.kind.enum[0]]=e.component,e.component);export const createCustomPhoenixEntityElement=(e,t)=>({type:"entity",name:e,element:t});

package/dist/domain/application/handler-registration.d.ts

@@ -1,29 +0,0 @@
-export type PhoenixHandlerDefinition = {
-    handler: () => Promise<void>;
-};
-export type SystemPhoenixHandlerDefinition<P, R> = {
-    handler: (props: P) => R;
-};
-export type SystemPhoenixAsyncHandlerDefinition<P, R> = {
-    handler: (props: P) => Promise<R>;
-};
-export type SystemPhoenixHandlerRegistration<P, R> = {
-    type: 'system';
-    name: string;
-    handler: () => SystemPhoenixHandlerDefinition<P, R>;
-};
-export type SystemPhoenixAsyncHandlerRegistration<P, R> = {
-    type: 'system-async';
-    name: string;
-    handler: () => SystemPhoenixAsyncHandlerDefinition<P, R>;
-};
-export type PhoenixHandlerRegistration = {
-    type: 'phoenix';
-    name: string;
-    handler: () => PhoenixHandlerDefinition;
-};
-export type HandlerRegistration<P, R> = SystemPhoenixHandlerRegistration<P, R> | SystemPhoenixAsyncHandlerRegistration<P, R> | PhoenixHandlerRegistration;
-export declare const createPhoenixHandler: (name: string, handler: () => PhoenixHandlerDefinition) => PhoenixHandlerRegistration;
-export type CreatePhoenixHandler = (name: string, handler: () => PhoenixHandlerDefinition) => PhoenixHandlerRegistration;
-export declare const createSystemPhoenixHandler: <P, R>(name: string, handler: () => SystemPhoenixHandlerDefinition<P, R>) => SystemPhoenixHandlerRegistration<P, R>;
-export declare const createSystemPhoenixAsyncHandler: <P, R>(name: string, handler: () => SystemPhoenixAsyncHandlerDefinition<P, R>) => SystemPhoenixAsyncHandlerRegistration<P, R>;

package/dist/domain/application/handler-registration.js

@@ -1 +0,0 @@
-export const createPhoenixHandler=(e,t)=>({type:"phoenix",name:e,handler:t});export const createSystemPhoenixHandler=(e,t)=>({type:"system",name:e,handler:t});export const createSystemPhoenixAsyncHandler=(e,t)=>({type:"system-async",name:e,handler:t});

package/dist/domain/application/resolve-imported-transformers.d.ts

@@ -1,13 +0,0 @@
-import type { $DomainEntity, DomainEntity } from '../core/model.js';
-import type { DomainContextSystems } from '../domain-context/domain-context-systems.js';
-import type { Transformers } from '../domain-context/store-system/store-system.js';
-import type { ImportedTransformer, SpecTransformer } from './application-config.js';
-/**
- * Resolves imported transformer modules against spec transformer declarations.
- * Each imported transformer is registered/executed with the domain context,
- * then matched by name against spec entries to apply priority ordering.
- *
- * Used both at build time (via withTransformers) and at hot-reload time
- * (via domain-context subscription to registry changes).
- */
-export declare const resolveImportedTransformers: <ENTITIES extends DomainEntity<string>, ALLOWED_ROOT_ENTITIES extends ENTITIES, $MAP extends Record<ENTITIES['type'], $DomainEntity<ENTITIES>>, NAVIGATION_STATES extends string, VIEW_STATES extends string, TOOL_STATES extends string, EXPORT_STATES extends string>(importedTransformers: ReadonlyArray<ImportedTransformer<ENTITIES, ALLOWED_ROOT_ENTITIES, $MAP, NAVIGATION_STATES, VIEW_STATES, TOOL_STATES, EXPORT_STATES>>, specTransformers: readonly SpecTransformer[], ctx: DomainContextSystems<ENTITIES, ALLOWED_ROOT_ENTITIES, $MAP, NAVIGATION_STATES, VIEW_STATES, TOOL_STATES, EXPORT_STATES>) => Transformers<ENTITIES>;

package/dist/domain/application/resolve-imported-transformers.js

@@ -1 +0,0 @@
-export const resolveImportedTransformers=(r,e,t)=>{let o=r.flatMap(({name:r,transformer:e})=>{if(Array.isArray(e))return e.map((e,o)=>{if("register"in e)return e.register(t);if("function"==typeof e)return{priority:1/0,transformer:e(t),name:`${r}[${o}]`};throw Error(`Transformer '${r}[${o}]' must be either a RegistrableTransformer (with register method) or a TransformerFactory (function)`)});if("register"in e)return e.register(t);if("function"==typeof e)return{priority:1/0,transformer:e(t),name:r};throw Error(`Transformer '${r}' must be either a RegistrableTransformer (with register method) or a TransformerFactory (function)`)}),n=[];for(let r of e){let e=o.find(e=>e.name===r.name);if(!e){let e=o.map(r=>r.name).filter(Boolean).join(", ");throw Error(`Transformer '${r.name}' not found in imported transformer files. Available transformers: ${e||"none"}`)}n.push({priority:r.priority??1/0,transformer:e.transformer,name:r.name})}return n};

package/dist/domain/application/resource-builder.d.ts

@@ -1,13 +0,0 @@
-import type { ClientGeneratedImageResource, CsvResource, ExistingImageResource, FinalizeTaskResource, GeneratedImageResource, LinkResource, PdfResource } from '@salsita-ai/contracts/webhook';
-export declare class ResourceBuilder<RESOURCE extends string = never> {
-    private readonly _resources;
-    private readonly _resourceNames;
-    constructor(_resources?: Array<FinalizeTaskResource<RESOURCE>>, _resourceNames?: RESOURCE[]);
-    addClientGeneratedImage<const NEW_RESOURCE extends string>(resource: ClientGeneratedImageResource<NEW_RESOURCE>): ResourceBuilder<RESOURCE | NEW_RESOURCE>;
-    addExistingImage<const NEW_RESOURCE extends string>(resource: ExistingImageResource<NEW_RESOURCE>): ResourceBuilder<RESOURCE | NEW_RESOURCE>;
-    addGeneratedImage<const NEW_RESOURCE extends string>(resource: GeneratedImageResource<NEW_RESOURCE>): ResourceBuilder<RESOURCE | NEW_RESOURCE>;
-    addLink<const NEW_RESOURCE extends string>(resource: LinkResource<NEW_RESOURCE>): ResourceBuilder<RESOURCE | NEW_RESOURCE>;
-    addPdf<const NEW_RESOURCE extends string>(resource: PdfResource<NEW_RESOURCE>): ResourceBuilder<RESOURCE | NEW_RESOURCE>;
-    addCsv<const NEW_RESOURCE extends string>(resource: CsvResource<NEW_RESOURCE>): ResourceBuilder<RESOURCE | NEW_RESOURCE>;
-    build(): Array<FinalizeTaskResource<RESOURCE>>;
-}

package/dist/domain/application/resource-builder.js

@@ -1 +0,0 @@
-export class ResourceBuilder{_resources;_resourceNames;constructor(e=[],r=[]){this._resources=e,this._resourceNames=r}addClientGeneratedImage(e){if(this._resources.some(r=>r.name===e.name))throw Error(`Resource with name ${e.name} already exists!`);return new ResourceBuilder([...this._resources,e],[...this._resourceNames,e.name])}addExistingImage(e){if(this._resources.some(r=>r.name===e.name))throw Error(`Resource with name ${e.name} already exists!`);return new ResourceBuilder([...this._resources,e],[...this._resourceNames,e.name])}addGeneratedImage(e){if(this._resources.some(r=>r.name===e.name))throw Error(`Resource with name ${e.name} already exists!`);return new ResourceBuilder([...this._resources,e],[...this._resourceNames,e.name])}addLink(e){if(this._resources.some(r=>r.name===e.name))throw Error(`Resource with name ${e.name} already exists!`);return new ResourceBuilder([...this._resources,e],[...this._resourceNames,e.name])}addPdf(e){if(this._resources.some(r=>r.name===e.name))throw Error(`Resource with name ${e.name} already exists!`);return new ResourceBuilder([...this._resources,e],[...this._resourceNames,e.name])}addCsv(e){if(this._resources.some(r=>r.name===e.name))throw Error(`Resource with name ${e.name} already exists!`);return new ResourceBuilder([...this._resources,e],[...this._resourceNames,e.name])}build(){return this._resources}}