@salsita-ai/sdk 0.50.0-develop.7d4723b0a5 → 0.50.0-develop.9cf426b400

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,5 +1,5 @@
1
1
  {
2
- "generatedAt": "2026-10-08T23:11:35.723Z",
2
+ "generatedAt": "2026-10-09T05:36:29.197Z",
3
3
  "categories": [
4
4
  {
5
5
  "name": "Phoenix",
@@ -421,7 +421,7 @@ export const handler = webhookBuilder
421
421
 
422
422
  The publishing workflow validates admin state, transforms entities, and stores JSON to S3. Configurators access published data via `ctx.publishedData` in expressions.
423
423
 
424
- For implementation examples, see `packages/demos/demo-finalize/src/handlers/map-published-revision-data.ts`.
424
+ For implementation examples, see `packages/demos/demo-catalog-builder/src/handlers/map-published-chunked-data.ts`.
425
425
 
426
426
  For technical details about data transformation and storage, see [Data Sources - Published Data](?path=/docs/phoenix-data-sources--docs#published-data).
427
427
 
@@ -515,4 +515,4 @@ Ready to implement admin functionality in your Phoenix project? Here's what to e
515
515
  - **[Sessions and Access](?path=/docs/phoenix-sessions-and-access--docs)** - Understand admin authentication and permissions
516
516
  - **[Connected Data Sources](?path=/docs/phoenix-connected-data-sources--docs)** - Wire `$data` entries to Google Sheets or Excel; requires the embedded admin mode
517
517
 
518
- For hands-on examples, check out the finalize demo (`packages/demos/demo-finalize/`) which shows spec-driven admin using `createAdminPages` for presets and recipes. This demo demonstrates the YAML-based admin approach with publishing workflows rather than custom admin UI components.
518
+ For hands-on examples, check out the Catalog Builder demo (`packages/demos/demo-catalog-builder/`), which shows spec-driven admin pages over connected and generated data, custom catalog pages beside them, admin model migrations, and the publishing workflow.
@@ -355,4 +355,4 @@ Now that you understand finalization workflows, explore these related topics:
355
355
  - **[Admin](?path=/docs/phoenix-admin--docs)** - Learn about admin finalization and published data generation
356
356
  - **[Best Practices](?path=/docs/phoenix-best-practices--docs)** - Follow proven patterns for finalization implementation
357
357
 
358
- For hands-on practice, explore the finalize demo in the **[Quickstart](?path=/docs/phoenix-quickstart--docs)** guide.
358
+ For hands-on practice, explore the Precision demo (`packages/demos/demo-precision/`) for finalization resources — PDF, CSV, images, email attachments and callbacks — and the Catalog Builder demo (`packages/demos/demo-catalog-builder/`) for the finalization data lifecycle and access links.
@@ -51,11 +51,11 @@ For details on the server-side token exchange, see [Authentication](?path=/docs/
51
51
 
52
52
  The `power` attribute controls the configurator's state:
53
53
 
54
- | Value | Behavior |
55
- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
56
- | `"off"` | Completely inactive. No rendering, no session, no network requests beyond loading the bundle. |
57
- | `"standby"` | Session initialized, assets preloaded (3D models, textures), but not rendered. Faster power-on, but consumes bandwidth and counts toward session quotas. |
58
- | `"on"` | Fully active and visible. |
54
+ | Value | Behavior |
55
+ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
56
+ | `"off"` | Completely inactive. No rendering, no session, no network requests beyond loading the bundle. |
57
+ | `"standby"` | Session initialized and any textures listed in `resourcesConfig.prefetchTextureUrls` prefetched; nothing is rendered and no models are loaded. Faster power-on, but consumes bandwidth and counts toward session quotas. |
58
+ | `"on"` | Fully active and visible. |
59
59
 
60
60
  A typical flow: power on at login (`"standby"`), then toggle between `"on"` and `"standby"` as the user opens and closes the configurator. Use `"off"` only before the user has authenticated.
61
61
 
@@ -28,11 +28,11 @@ The configurator fills its parent container. Set a height on the element or a wr
28
28
 
29
29
  The `power` attribute controls whether the configurator is active. It accepts three values:
30
30
 
31
- | Value | Behavior |
32
- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
33
- | `"off"` | Configurator is completely inactive. No rendering, no session initialization, no network requests beyond loading the bundle. Lowest resource usage. |
34
- | `"standby"` | Configurator initializes its session and preloads assets (3D models, textures), but does not render. Subsequent power-on is faster, but consumes bandwidth and counts toward monthly session quotas. |
35
- | `"on"` | Configurator is fully active and visible. |
31
+ | Value | Behavior |
32
+ | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
33
+ | `"off"` | Configurator is completely inactive. No rendering, no session initialization, no network requests beyond loading the bundle. Lowest resource usage. |
34
+ | `"standby"` | Configurator initializes its session and prefetches any textures listed in `resourcesConfig.prefetchTextureUrls`, but does not render or load models. Subsequent power-on is faster, but consumes bandwidth and counts toward monthly session quotas. |
35
+ | `"on"` | Configurator is fully active and visible. |
36
36
 
37
37
  ### Choosing the Initial Power
38
38
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@salsita-ai/sdk",
3
- "version": "0.50.0-develop.7d4723b0a5",
3
+ "version": "0.50.0-develop.9cf426b400",
4
4
  "description": "TypeScript SDK and CLI for building, running, and deploying Phoenix configurator applications.",
5
5
  "keywords": [
6
6
  "salsita",
@@ -295,8 +295,8 @@
295
295
  "yaml": "2.9.0",
296
296
  "yargs": "17.7.2",
297
297
  "zod": "3.25.76",
298
- "@salsita-ai/contracts": "0.50.0-develop.7d4723b0a5",
299
- "@salsita-ai/common": "0.50.0-develop.7d4723b0a5"
298
+ "@salsita-ai/common": "0.50.0-develop.9cf426b400",
299
+ "@salsita-ai/contracts": "0.50.0-develop.9cf426b400"
300
300
  },
301
301
  "devDependencies": {
302
302
  "@clerk/clerk-react": "5.61.8",