@proveanything/smartlinks 2.0.38 → 2.0.40

package/dist/headless.d.ts

@@ -8,12 +8,26 @@ export interface HeadlessValidation {
     ok: boolean;
     errors: HeadlessIssue[];
     warnings: HeadlessIssue[];
-    /** The read recipe for each type: the declared one, else the standard one for its storage. */
+    /**
+     * The read recipe for each type: the declared one, else the standard one for its storage — plus what
+     * the call returns and where an item's fields are. Those two always come from the storage kind (the
+     * platform's response shape), never from the app, so a custom recipe can't leave them out.
+     */
     recipes: Record<string, {
         list: string;
         get?: string;
+        returns: string;
+        item: string;
     }>;
 }
+/**
+ * What a type's read calls return, and where one item's declared fields live — fixed by the storage
+ * kind (see app-objects.md "Paginated List Responses"). Sites must read items from `response.data`.
+ */
+export declare function responseShape(type: AppDataType): {
+    returns: string;
+    item: string;
+};
 /** The standard SDK read calls for a type, from how it's stored. `appId` / `collectionId` are the caller's variables. */
 export declare function standardRecipe(type: AppDataType): {
     list: string;

package/dist/headless.js

@@ -18,13 +18,36 @@ const PLATFORM_REFS = new Set(['product', 'contact', 'proof']);
 const SEO_HELPERS = new Set(['faqPage', 'product', 'article', 'breadcrumbs', 'organization', 'localBusiness']);
 const STORAGE_KINDS = new Set(['record', 'case', 'thread', 'config']);
 const SEMVER = /^\d+\.\d+\.\d+(?:[-+][0-9A-Za-z.-]+)?$/;
+/**
+ * What a type's read calls return, and where one item's declared fields live — fixed by the storage
+ * kind (see app-objects.md "Paginated List Responses"). Sites must read items from `response.data`.
+ */
+export function responseShape(type) {
+    const s = type.storage;
+    const first = Object.keys(type.fields || {})[0] || 'field';
+    const paged = (name) => `list → { data: ${name}[], pagination: { total, limit, offset, hasMore } }. The items are in response.data (not response.items / response.records); page with offset/limit while pagination.hasMore. get → one ${name}.`;
+    switch (s && s.kind) {
+        case 'record':
+            return { returns: paged('AppRecord'), item: `Each record's declared fields are in record.data (e.g. record.data.${first}); record.id, record.productId, record.status, record.createdAt are top-level.` };
+        case 'case':
+            return { returns: paged('AppCase'), item: `Each case's declared fields are in case.data (e.g. case.data.${first}); id, status, category and dates are top-level.` };
+        case 'thread':
+            return { returns: paged('AppThread'), item: `Each thread's declared fields are in thread.data (e.g. thread.data.${first}); replies are in thread.replies.` };
+        case 'config': {
+            const key = s.key;
+            return { returns: "The app's configuration object for the collection.", item: key ? `The items are in config.${key}; each item's fields are its declared fields.` : 'The declared fields are top-level properties of the config object.' };
+        }
+        default:
+            return { returns: '(unknown storage)', item: '' };
+    }
+}
 /** The standard SDK read calls for a type, from how it's stored. `appId` / `collectionId` are the caller's variables. */
 export function standardRecipe(type) {
     const s = type.storage;
     switch (s && s.kind) {
         case 'record':
             return {
-                list: `SL.app.records.list(collectionId, appId, { recordType: '${s.recordType}', limit: 50 })  // → { data: AppRecord[] }; fields in record.data`,
+                list: `SL.app.records.list(collectionId, appId, { recordType: '${s.recordType}', limit: 50 })`,
                 get: 'SL.app.records.get(collectionId, appId, recordId)',
             };
         case 'case':
@@ -179,7 +202,8 @@ export function validate(manifest, opts = {}) {
             if (samples && samples.length)
                 checkItems('real item', typeId, type, samples, { errors, warnings });
             const std = standardRecipe(type);
-            recipes[typeId] = Object.assign({ list: (type.read && type.read.list) || std.list }, ((type.read && type.read.get) || std.get ? { get: (type.read && type.read.get) || std.get } : {}));
+            const get = (type.read && type.read.get) || std.get;
+            recipes[typeId] = Object.assign(Object.assign({ list: (type.read && type.read.list) || std.list }, (get ? { get } : {})), responseShape(type));
         }
     }
     // ---- headless

package/dist/openapi.yaml

@@ -26623,8 +26623,24 @@ components:
           type: object
           additionalProperties: true
       required:
-        - id
         - appId
+    EnsureInteractionTypeInput:
+      type: object
+      properties:
+        appId:
+          type: string
+        key:
+          type: string
+        permissions:
+          $ref: "#/components/schemas/InteractionPermissions"
+        display:
+          $ref: "#/components/schemas/InteractionDisplay"
+        data:
+          type: object
+          additionalProperties: true
+      required:
+        - appId
+        - key
     UpdateInteractionTypeBody:
       type: object
       properties:

package/dist/types/interaction.d.ts

@@ -195,10 +195,25 @@ export interface InteractionTypeList {
     limit: number;
     offset: number;
 }
+/**
+ * Body for interactions.create(). The SERVER mints the type's id (a UUID) — read it from the
+ * returned record. Prefer interactions.ensureType(), which also finds an existing type by its key.
+ */
 export interface CreateInteractionTypeBody {
-    id: string;
+    /** @deprecated Ignored — the server mints the id. Use the `id` of the returned record (or ensureType). */
+    id?: string;
+    appId: string;
+    permissions?: InteractionPermissions;
+    data?: Record<string, unknown>;
+}
+/** Input for interactions.ensureType(): find this app's type by `key`, or create it. */
+export interface EnsureInteractionTypeInput {
     appId: string;
+    /** Your readable, stable name for the type, e.g. 'vote' — stored as data.interactionType. NOT the id. */
+    key: string;
     permissions?: InteractionPermissions;
+    display?: InteractionDisplay;
+    /** Extra definition data (e.g. effects); merged under data alongside interactionType/display. */
     data?: Record<string, unknown>;
 }
 export interface UpdateInteractionTypeBody {

package/docs/API_SUMMARY.md

@@ -1,6 +1,6 @@
 # Smartlinks API Summary
 
-Version: 2.0.38  |  Generated: 2026-10-05T12:10:36.598Z
+Version: 2.0.40  |  Generated: 2026-10-05T14:51:09.158Z
 
 This is a concise summary of all available API functions and types.
 
@@ -26,6 +26,12 @@ For detailed guides on specific features:
 - **[iframe Responder](iframe-responder.md)** - iframe integration and cross-origin communication (incl. hand-rolled streaming protocol)
 - **[Utilities](utils.md)** - Helper functions for building portal paths, URLs, and common tasks
 - **[UI Utils](ui-utils.md)** - Reusable, themeable admin UI React component library for microapps
+- **[Headless Providers](headless-providers.md)** - Declaring an app's content for other sites: the manifest `data` + `headless` blocks (types, storage, public fields, examples, read recipes, categories), `SL.headless.validate`, `smartlinks-headless`, and the procedure for adding a headless mode
+- **[Websites: SEO + GEO](site-seo.md)** - For apps served as websites: platform-generated robots/sitemap/llms.txt, canonical addresses, `SL.seo.head` / `SL.seo.jsonLd` / `SL.seo.schema.*`, `SL.site.ready()`, routes in `sitemap-paths.txt`
+- **[Agent Tools](agent-tools.md)** - Exposing app functions as AI agent tools
+- **[Host Dependency Contract](host-dependency-contract.md)** - The shared dependencies (React, the SDK…) the host provides, and what an app must externalise
+- **[Theme Tokens](theme-tokens.md)** - The `--sl-*` semantic token contract hosts set and apps bind to (`theme.css`)
+- **[CSS Baseline](css-baseline.md)** - The frozen `sl-*` structural helper classes hosts guarantee
 - **[Caching](caching.md)** - Multi-tier caching strategy (in-memory, SessionStorage, IndexedDB) used by the SDK
 - **[Native Facade](native-facade.md)** - Contract layer for accessing device capabilities (share, NFC, haptics) across host shells
 - **[i18n](i18n.md)** - Internationalization and localization
@@ -7269,13 +7275,24 @@ interface InteractionTypeList {
 **CreateInteractionTypeBody** (interface)
 ```typescript
 interface CreateInteractionTypeBody {
-  id: string
+  id?: string
   appId: string
   permissions?: InteractionPermissions
   data?: Record<string, unknown>
 }
 ```
 
+**EnsureInteractionTypeInput** (interface)
+```typescript
+interface EnsureInteractionTypeInput {
+  appId: string
+  key: string
+  permissions?: InteractionPermissions
+  display?: InteractionDisplay
+  data?: Record<string, unknown>
+}
+```
+
 **UpdateInteractionTypeBody** (interface)
 ```typescript
 interface UpdateInteractionTypeBody {
@@ -11192,22 +11209,22 @@ The release channel a call targets, or undefined for "the collection's installed
 **functionPath**(surface: 'public' | 'admin', collectionId: string, name: string, opts: FunctionCallOptions = {}) → `string`
 The API path a function call goes to (exported for hosts/tests that need the exact URL).
 
-**siteUrl**(collection: { siteHost?: string | null } | string,
-    name: string,
+**siteUrl**(collection: { siteHost?: string | null } | string,
+    name: string,
     opts: FunctionSiteUrlOptions & { appId?: string } = {}) → `string`
 The PUBLIC address of an app function on the collection's own site — what you give a third party as a webhook URL, or call from the collection's public pages: `https://<siteHost>/_fn/<appId>[/<channel>]/<name>[/<path>]`. Every HTTP method the function declares works there, with the raw body for signature checks. Pass the collection (or its siteHost). This address is for public/integration calls; signed-in calls from your app keep using {@link call} / {@link callAdmin}, so the user's SmartLinks session never goes to a tenant hostname. const col = await SL.collection.get(collectionId) const hookUrl = SL.functions.siteUrl(col, 'stripeWebhook', { appId: 'my-shop' }) // → https://acme.smartlinks.host/_fn/my-shop/stripeWebhook
 
-**call**(collectionId: string,
-    name: string,
-    body: Record<string, any> = {},
+**call**(collectionId: string,
+    name: string,
+    body: Record<string, any> = {},
     opts: FunctionCallOptions = {}) → `Promise<T>`
-Call a PUBLIC app server function inline (surface `'public'`). App-scoped: `POST /public/collection/:c/app/:appId/functions/:name`. // App calling its own function (appId from initializeApi({ appId })): const { value } = await SL.functions.call<{ value: number }>(collectionId, 'pressCounter') // Or address another app explicitly: await SL.functions.call(collectionId, 'pressCounter', {}, { appId: 'my-counter-app' })
+Call a PUBLIC app server function inline (surface `'public'`). App-scoped: `POST /fn/public/collection/:c/app/:appId/functions/:name`. // App calling its own function (appId from initializeApi({ appId })): const { value } = await SL.functions.call<{ value: number }>(collectionId, 'pressCounter') // Or address another app explicitly: await SL.functions.call(collectionId, 'pressCounter', {}, { appId: 'my-counter-app' })
 
-**callAdmin**(collectionId: string,
-    name: string,
-    body: Record<string, any> = {},
+**callAdmin**(collectionId: string,
+    name: string,
+    body: Record<string, any> = {},
     opts: FunctionCallOptions = {}) → `Promise<T>`
-Call an ADMIN app server function (surface `'admin'`; requires an admin session). App-scoped: `POST /admin/collection/:c/app/:appId/functions/:name`.
+Call an ADMIN app server function (surface `'admin'`; requires an admin session). App-scoped: `POST /fn/admin/collection/:c/app/:appId/functions/:name`.
 
 **list**(collectionId: string, opts: FunctionCallOptions = {}) → `Promise<FunctionListResponse>`
 List the public functions available for a collection (discovery). Scoped to one app when an appId is given (or set as the SDK app context): `GET /public/collection/:c[/app/:appId]/functions`.
@@ -11319,36 +11336,40 @@ POST /api/v1/public/collection/:collectionId/interactions/submit Submits an inte
     query: ListInteractionTypesQuery = {}) → `Promise<InteractionTypeList>`
 POST /api/v1/public/collection/:collectionId/interactions/submit Submits an interaction event from a public/client-side context. `interactionId` must reference an existing interaction type definition. This endpoint does not create interaction definitions. When the interaction has `allowAnonymousSubmit: true`, neither `userId` nor `contactId` is required. Pass `anonId` inside `metadata` to enable device-level deduplication via `uniquePerAnonId`.
 
+**ensureType**(collectionId: string,
+    input: EnsureInteractionTypeInput) → `Promise<InteractionTypeRecord>`
+Find this app's interaction type by its readable `key` (data.interactionType), or create it. Returns the type record — its `id` is the server-minted UUID every event must use. ADMIN only (run it in your admin/setup screen), then store the id in your app config so public code can read it: `interactionIds: { vote: type.id }`. Safe to run on every setup. const vote = await SL.interactions.ensureType(collectionId, { appId: 'my-app', key: 'vote', permissions: { allowPublicSubmit: true, uniquePerUser: true }, }) // vote.id → '52bab6fa-…' — store it in config; never hardcode 'vote' as an interactionId
+
 **get**(collectionId: string,
     id: string) → `Promise<InteractionTypeRecord>`
-POST /api/v1/public/collection/:collectionId/interactions/submit Submits an interaction event from a public/client-side context. `interactionId` must reference an existing interaction type definition. This endpoint does not create interaction definitions. When the interaction has `allowAnonymousSubmit: true`, neither `userId` nor `contactId` is required. Pass `anonId` inside `metadata` to enable device-level deduplication via `uniquePerAnonId`.
+Find this app's interaction type by its readable `key` (data.interactionType), or create it. Returns the type record — its `id` is the server-minted UUID every event must use. ADMIN only (run it in your admin/setup screen), then store the id in your app config so public code can read it: `interactionIds: { vote: type.id }`. Safe to run on every setup. const vote = await SL.interactions.ensureType(collectionId, { appId: 'my-app', key: 'vote', permissions: { allowPublicSubmit: true, uniquePerUser: true }, }) // vote.id → '52bab6fa-…' — store it in config; never hardcode 'vote' as an interactionId
 
 **update**(collectionId: string,
     id: string,
     patchBody: UpdateInteractionTypeBody) → `Promise<InteractionTypeRecord>`
-POST /api/v1/public/collection/:collectionId/interactions/submit Submits an interaction event from a public/client-side context. `interactionId` must reference an existing interaction type definition. This endpoint does not create interaction definitions. When the interaction has `allowAnonymousSubmit: true`, neither `userId` nor `contactId` is required. Pass `anonId` inside `metadata` to enable device-level deduplication via `uniquePerAnonId`.
+Find this app's interaction type by its readable `key` (data.interactionType), or create it. Returns the type record — its `id` is the server-minted UUID every event must use. ADMIN only (run it in your admin/setup screen), then store the id in your app config so public code can read it: `interactionIds: { vote: type.id }`. Safe to run on every setup. const vote = await SL.interactions.ensureType(collectionId, { appId: 'my-app', key: 'vote', permissions: { allowPublicSubmit: true, uniquePerUser: true }, }) // vote.id → '52bab6fa-…' — store it in config; never hardcode 'vote' as an interactionId
 
 **remove**(collectionId: string,
     id: string) → `Promise<void>`
-POST /api/v1/public/collection/:collectionId/interactions/submit Submits an interaction event from a public/client-side context. `interactionId` must reference an existing interaction type definition. This endpoint does not create interaction definitions. When the interaction has `allowAnonymousSubmit: true`, neither `userId` nor `contactId` is required. Pass `anonId` inside `metadata` to enable device-level deduplication via `uniquePerAnonId`.
+Find this app's interaction type by its readable `key` (data.interactionType), or create it. Returns the type record — its `id` is the server-minted UUID every event must use. ADMIN only (run it in your admin/setup screen), then store the id in your app config so public code can read it: `interactionIds: { vote: type.id }`. Safe to run on every setup. const vote = await SL.interactions.ensureType(collectionId, { appId: 'my-app', key: 'vote', permissions: { allowPublicSubmit: true, uniquePerUser: true }, }) // vote.id → '52bab6fa-…' — store it in config; never hardcode 'vote' as an interactionId
 
 **publicCountsByOutcome**(collectionId: string,
     body: PublicInteractionsCountsByOutcomeRequest,
     authToken?: string) → `Promise<OutcomeCount[]>`
-POST /api/v1/public/collection/:collectionId/interactions/submit Submits an interaction event from a public/client-side context. `interactionId` must reference an existing interaction type definition. This endpoint does not create interaction definitions. When the interaction has `allowAnonymousSubmit: true`, neither `userId` nor `contactId` is required. Pass `anonId` inside `metadata` to enable device-level deduplication via `uniquePerAnonId`.
+Find this app's interaction type by its readable `key` (data.interactionType), or create it. Returns the type record — its `id` is the server-minted UUID every event must use. ADMIN only (run it in your admin/setup screen), then store the id in your app config so public code can read it: `interactionIds: { vote: type.id }`. Safe to run on every setup. const vote = await SL.interactions.ensureType(collectionId, { appId: 'my-app', key: 'vote', permissions: { allowPublicSubmit: true, uniquePerUser: true }, }) // vote.id → '52bab6fa-…' — store it in config; never hardcode 'vote' as an interactionId
 
 **publicMyInteractions**(collectionId: string,
     body: PublicInteractionsByUserRequest,
     authToken?: string) → `Promise<InteractionEventRow[]>`
-POST /api/v1/public/collection/:collectionId/interactions/submit Submits an interaction event from a public/client-side context. `interactionId` must reference an existing interaction type definition. This endpoint does not create interaction definitions. When the interaction has `allowAnonymousSubmit: true`, neither `userId` nor `contactId` is required. Pass `anonId` inside `metadata` to enable device-level deduplication via `uniquePerAnonId`.
+Find this app's interaction type by its readable `key` (data.interactionType), or create it. Returns the type record — its `id` is the server-minted UUID every event must use. ADMIN only (run it in your admin/setup screen), then store the id in your app config so public code can read it: `interactionIds: { vote: type.id }`. Safe to run on every setup. const vote = await SL.interactions.ensureType(collectionId, { appId: 'my-app', key: 'vote', permissions: { allowPublicSubmit: true, uniquePerUser: true }, }) // vote.id → '52bab6fa-…' — store it in config; never hardcode 'vote' as an interactionId
 
 **publicList**(collectionId: string,
     query: ListInteractionTypesQuery = {}) → `Promise<InteractionTypeList>`
-POST /api/v1/public/collection/:collectionId/interactions/submit Submits an interaction event from a public/client-side context. `interactionId` must reference an existing interaction type definition. This endpoint does not create interaction definitions. When the interaction has `allowAnonymousSubmit: true`, neither `userId` nor `contactId` is required. Pass `anonId` inside `metadata` to enable device-level deduplication via `uniquePerAnonId`.
+Find this app's interaction type by its readable `key` (data.interactionType), or create it. Returns the type record — its `id` is the server-minted UUID every event must use. ADMIN only (run it in your admin/setup screen), then store the id in your app config so public code can read it: `interactionIds: { vote: type.id }`. Safe to run on every setup. const vote = await SL.interactions.ensureType(collectionId, { appId: 'my-app', key: 'vote', permissions: { allowPublicSubmit: true, uniquePerUser: true }, }) // vote.id → '52bab6fa-…' — store it in config; never hardcode 'vote' as an interactionId
 
 **publicGet**(collectionId: string,
     id: string) → `Promise<InteractionTypeRecord>`
-POST /api/v1/public/collection/:collectionId/interactions/submit Submits an interaction event from a public/client-side context. `interactionId` must reference an existing interaction type definition. This endpoint does not create interaction definitions. When the interaction has `allowAnonymousSubmit: true`, neither `userId` nor `contactId` is required. Pass `anonId` inside `metadata` to enable device-level deduplication via `uniquePerAnonId`.
+Find this app's interaction type by its readable `key` (data.interactionType), or create it. Returns the type record — its `id` is the server-minted UUID every event must use. ADMIN only (run it in your admin/setup screen), then store the id in your app config so public code can read it: `interactionIds: { vote: type.id }`. Safe to run on every setup. const vote = await SL.interactions.ensureType(collectionId, { appId: 'my-app', key: 'vote', permissions: { allowPublicSubmit: true, uniquePerUser: true }, }) // vote.id → '52bab6fa-…' — store it in config; never hardcode 'vote' as an interactionId
 
 ### jobs
 

package/docs/headless-providers.md

@@ -50,6 +50,14 @@ Site builders (the Forge agent included) read these declarations to decide "inst
 | `thread` | App threads: discussions, Q&A, reviews | `SL.app.threads.list / get` |
 | `config` (+ optional `key`) | App configuration: settings, small fixed lists | `SL.appConfiguration.getConfig({ collectionId, appId })` |
 
+**What the read calls return.** This is fixed by the storage kind, so a provider never needs to describe it, and site builders get it from the checker and `forge-cms describe`:
+
+- **`record`, `case`, `thread`:** `list` returns `{ data: Item[], pagination: { total, limit, offset, hasMore } }`.
+  - The items are in **`response.data`**, never `response.items` or `response.records`.
+  - Each item's declared fields are in **`item.data`** (e.g. `record.data.question`). `id`, `status`, `productId` and the dates are top-level.
+  - Page with `offset` / `limit` while `pagination.hasMore`. `get` returns one item.
+- **`config`:** the configuration object. Items are in `config.<key>` when the type names a `key`.
+
 Products, contacts and proofs are platform data. Reference them with `ref` fields (`"to": "product"`); never redeclare them.
 
 **Field types:** `string`, `text`, `richtext` (HTML), `markdown`, `number`, `boolean`, `date` (YYYY-MM-DD), `datetime`, `enum` (+ `options`), `url`, `image` and `file` (a URL or `{ url, ... }`), `ref` and `ref[]` (+ `to`: a declared type id, or `product` / `contact` / `proof`), `string[]`, `json` (avoid where a typed field fits).

package/docs/interactions.md

@@ -12,43 +12,50 @@ Interactions have two distinct layers:
 
 | Layer | Purpose |
 |-------|---------|
-| **Interaction Types** | Definitions stored in the database — configure an interaction's ID, permissions, and display metadata once per collection |
-| **Interaction Events** | Individual event records logged each time a user performs that interaction |
+| **Interaction Types** | Definitions stored in the database, once per collection: permissions, display metadata, effects. **The server mints each type's `id` (a UUID).** |
+| **Interaction Events** | Individual event records logged each time a user performs that interaction. Each event's `interactionId` is a type's minted `id`. |
 
-Critical rule: event `interactionId` values must reference an existing interaction type definition in that collection. Do not generate random IDs in app code and submit events against them.
+## The one rule: create in admin → store the id in config → read it everywhere
 
-```text
-┌──────────────────────────────────────────────────────────────────┐
-│ Your App                                                         │
-│                                                                  │
-│  1. Create type once:  interactions.create(collectionId, {       │
-│       id: 'vote', permissions: { uniquePerUser: true } })        │
-│       -> definition exists in platform                           │
-│                                                                  │
-│  2. Log events:        interactions.appendEvent(collectionId, {  │
-│       interactionId: 'vote', outcome: 'option-a', userId })      │
-│       (must match the created definition ID)                     │
-│                                                                  │
-│  3. Read results:      interactions.countsByOutcome(collectionId, │
-│       { interactionId: 'vote' })                                 │
-│       → [{ outcome: 'option-a', count: 42 }, ...]               │
-└──────────────────────────────────────────────────────────────────┘
+**You never choose an interaction id, and you never write one as a string literal.** You choose a readable *key* (e.g. `'vote'`); the server mints the *id* (e.g. `'52bab6fa-…'`). Events must carry the id.
+
+```typescript
+// 1. ADMIN / setup screen — find-or-create the type by your key, then store its minted id in app config.
+const vote = await SL.interactions.ensureType(collectionId, {
+  appId: 'my-app',
+  key: 'vote',                                            // your readable name — NOT the id
+  permissions: { allowPublicSubmit: true, uniquePerUser: true },
+  display: { title: 'Vote' },
+});
+const config = await SL.appConfiguration.getConfig({ collectionId, appId: 'my-app', admin: true });
+await SL.appConfiguration.setConfig({
+  collectionId, appId: 'my-app', admin: true,
+  config: { ...config, interactionIds: { ...config?.interactionIds, vote: vote.id } },
+});
+
+// 2. ANYWHERE ELSE (public widget, container, server function) — read the id from config.
+const { interactionIds } = await SL.appConfiguration.getConfig({ collectionId, appId: 'my-app' });
+await SL.interactions.submitPublicEvent(collectionId, {
+  appId: 'my-app',
+  interactionId: interactionIds.vote,                     // the minted id, from config
+  outcome: 'option-a',
+});
 ```
 
-### Required Workflow (Do Not Invent IDs)
+Why it's split this way:
 
-1. Create an interaction type definition (admin endpoint) before recording any events.
-2. Reuse that same definition ID for every `appendEvent` / `submitPublicEvent` call.
-3. Treat unknown IDs as configuration errors, not as values your app should auto-create.
+- **Types can only be created on the admin surface.** Public code (widgets, the portal) can submit events but can't create types — so the public side can only learn the id from somewhere admin put it. App config is that place.
+- **`ensureType` is safe to re-run.** It returns the existing type when one with that `key` exists for your app, so run it every time your setup screen saves.
+- **Unknown ids are configuration errors.** If `interactionIds.vote` is missing, the app hasn't been set up in this collection: show "not configured", don't submit, and never fall back to a literal like `'vote'`. (`interactions.create()` exists too, but it ignores any `id` you pass — read `id` from the record it returns.)
 
-If your app currently hardcodes strings like `"poll"` or `"entry"`, make sure those IDs are actually created as interaction types during setup.
+The examples below use `interactionIds` — the map you read from config in step 2.
 
 ---
 
 ## Common Use Cases
 
-| Use Case | `interactionId` example | `outcome` example |
-|----------|-------------------------|-------------------|
+| Use Case | type `key` (for `ensureType`) | `outcome` example |
+|----------|-------------------------------|-------------------|
 | Competition entry | `competition-entry` | `"entered"` |
 | Voting / polling | `vote` | `"option-a"` |
 | Mailing list signup | `newsletter-signup` | `"subscribed"` |
@@ -62,12 +69,14 @@ If your app currently hardcodes strings like `"poll"` or `"entry"`, make sure th
 
 Interaction types are defined once per collection and control permissions, display metadata, and uniqueness constraints.
 
-### Create a Type
+### Create a Type (find-or-create)
+
+Admin only. Returns the type record; its `id` is the minted UUID — store it in app config (see [the one rule](#the-one-rule-create-in-admin--store-the-id-in-config--read-it-everywhere)).
 
 ```typescript
-await SL.interactions.create(collectionId, {
-  id: 'vote',
+const vote = await SL.interactions.ensureType(collectionId, {
   appId: 'my-app',
+  key: 'vote',                       // stored as data.interactionType; how ensureType finds it again
   permissions: {
     allowPublicSubmit: true,
     uniquePerUser: true,
@@ -75,35 +84,34 @@ await SL.interactions.create(collectionId, {
     endAt: '2026-06-30T23:59:59Z',
     allowPublicSummary: true,
   },
-  data: {
-    display: {
-      title: 'Vote',
-      description: 'Cast your vote for the competition.',
-    },
+  display: {
+    title: 'Vote',
+    description: 'Cast your vote for the competition.',
   },
 });
+// vote.id → '52bab6fa-d868-4616-9342-6731b0f332b2'
 ```
 
 ### Update / Delete a Type
 
 ```typescript
 // Update permissions or display
-await SL.interactions.update(collectionId, 'vote', {
+await SL.interactions.update(collectionId, interactionIds.vote, {
   permissions: { endAt: '2026-07-15T23:59:59Z' },
 });
 
-// Delete the definition (does not delete existing events)
-await SL.interactions.remove(collectionId, 'vote');
+// Delete the definition (does not delete existing events) — and remove it from your config
+await SL.interactions.remove(collectionId, interactionIds.vote);
 ```
 
 ### List / Get Types
 
 ```typescript
-// Admin: list all types for an app
+// Admin: list all types for an app (each has data.interactionType = its key)
 const { items } = await SL.interactions.list(collectionId, { appId: 'my-app' });
 
 // Admin: get a single type
-const type = await SL.interactions.get(collectionId, 'vote');
+const type = await SL.interactions.get(collectionId, interactionIds.vote);
 
 // Public: list available types (respects permissions)
 const { items } = await SL.interactions.publicList(collectionId, { appId: 'my-app' });
@@ -113,7 +121,7 @@ const { items } = await SL.interactions.publicList(collectionId, { appId: 'my-ap
 
 ## Logging Events
 
-Before logging events, ensure the referenced interaction type already exists. Event ingestion is not intended to create new interaction definitions.
+Every `interactionId` below is a minted type id read from your app config (`interactionIds`, see [the one rule](#the-one-rule-create-in-admin--store-the-id-in-config--read-it-everywhere)). Events never create types: an id that isn't a type defined for this collection and app is a configuration error.
 
 ### Admin Event Append
 
@@ -122,7 +130,7 @@ Use on the server side or in admin flows. Requires `userId` **or** `contactId`.
 ```typescript
 await SL.interactions.appendEvent(collectionId, {
   appId: 'my-app',
-  interactionId: 'vote',
+  interactionId: interactionIds.vote,
   outcome: 'option-a',      // The result / choice — used by countsByOutcome()
   userId: 'user_abc123',    // One of userId or contactId is required
   productId: 'prod_xyz',    // Optional — scope to a specific product
@@ -139,7 +147,7 @@ Use in client-side app code. Hits the public endpoint and respects interaction p
 // Authenticated submission
 await SL.interactions.submitPublicEvent(collectionId, {
   appId: 'my-app',
-  interactionId: 'competition-entry',
+  interactionId: interactionIds.competitionEntry,
   outcome: 'entered',
   contactId: currentUser.contactId,
   metadata: { answer: 'Paris' },
@@ -148,7 +156,7 @@ await SL.interactions.submitPublicEvent(collectionId, {
 // Anonymous submission (interaction must have allowAnonymousSubmit: true)
 const response = await SL.interactions.submitPublicEvent(collectionId, {
   appId: 'my-app',
-  interactionId: 'nps-score',
+  interactionId: interactionIds.npsScore,
   outcome: '9',
   metadata: {
     anonId: SL.utils.getAnonId(),  // device-level dedup signal
@@ -169,7 +177,7 @@ if (!response.success) {
 ```typescript
 await SL.interactions.updateEvent(collectionId, {
   eventId: 'evt_abc123',    // Required — the event to update
-  interactionId: 'vote',
+  interactionId: interactionIds.vote,
   userId: 'user_abc123',
   outcome: 'option-b',      // Override the outcome
   status: 'deleted',        // Soft-delete the event
@@ -180,7 +188,7 @@ await SL.interactions.updateEvent(collectionId, {
 
 | Field | Type | Required | Description |
 |-------|------|----------|-------------|
-| `interactionId` | string | ✅ | Existing interaction type ID (must already be defined in this collection) |
+| `interactionId` | string | ✅ | The type's minted `id` (from `ensureType`, stored in app config) — never a literal you made up |
 | `userId` or `contactId` | string | ✅ (one of) | The actor. `appendEvent` / `updateEvent` require one of these |
 | `appId` | string | ❌ | Scopes the event to your app |
 | `outcome` | string | ❌ | The result or choice — what `countsByOutcome()` aggregates |
@@ -205,7 +213,7 @@ The primary analytics function — returns how many times each outcome was recor
 // Admin (full access, deduplication options)
 const results = await SL.interactions.countsByOutcome(collectionId, {
   appId: 'my-app',
-  interactionId: 'vote',
+  interactionId: interactionIds.vote,
   scope: 'round-1',       // Optional — filter by scope
   from: '2026-06-01',     // Optional — date range
   to: '2026-06-30',
@@ -216,7 +224,7 @@ const results = await SL.interactions.countsByOutcome(collectionId, {
 // Public (respects allowPublicSummary permission)
 const results = await SL.interactions.publicCountsByOutcome(
   collectionId,
-  { appId: 'my-app', interactionId: 'vote' },
+  { appId: 'my-app', interactionId: interactionIds.vote },
   authToken     // Optional — pass if user is authenticated
 );
 ```
@@ -228,7 +236,7 @@ Flexible admin query for raw interaction events:
 ```typescript
 const events = await SL.interactions.query(collectionId, {
   appId: 'my-app',
-  interactionId: 'vote',
+  interactionId: interactionIds.vote,
   userId: 'user_abc123',      // Filter by user
   outcome: 'option-a',        // Filter by outcome
   from: '2026-06-01T00:00Z',
@@ -247,7 +255,7 @@ Lets authenticated users see their own events:
 ```typescript
 const myEvents = await SL.interactions.publicMyInteractions(
   collectionId,
-  { appId: 'my-app', interactionId: 'vote' },
+  { appId: 'my-app', interactionId: interactionIds.vote },
   authToken
 );
 ```
@@ -290,7 +298,7 @@ Platform emits event to Journey trigger
 Journey step runs: send confirmation email, update CRM, award points, etc.
 ```
 
-When defining a journey trigger, reference the `interactionId` that should fire it. The interaction `outcome` and `metadata` are available as variables in journey steps.
+When defining a journey trigger, reference the interaction type (its minted `id`) that should fire it. The interaction `outcome` and `metadata` are available as variables in journey steps.
 
 ---
 
@@ -316,9 +324,9 @@ A failure in one effect is logged and swallowed; subsequent effects still run.
 Pass `data.effects` when creating or updating an interaction type:
 
 ```typescript
-await SL.interactions.create(collectionId, {
-  id: 'donation',
+await SL.interactions.ensureType(collectionId, {
   appId: 'my-app',
+  key: 'donation',
   permissions: { allowPublicSubmit: true },
   data: {
     effects: [
@@ -351,7 +359,7 @@ All effect `config` values support `{{token}}` interpolation resolved from the e
 | `{{eventId}}` | BigQuery event UUID |
 | `{{collectionId}}` | Collection / brand ID |
 | `{{appId}}` | App ID that submitted the event |
-| `{{interactionId}}` | Interaction definition ID |
+| `{{interactionId}}` | Interaction type id (the minted UUID) |
 | `{{contactId}}` | Contact UUID (if resolved) |
 | `{{userId}}` | Firebase UID (if authenticated) |
 | `{{productId}}` | Product ID (if provided with event) |
@@ -496,7 +504,8 @@ import type {
   InteractionPermissions,         // Full permissions config shape
   InteractionTypeRecord,          // Definition record from create() / get()
   InteractionTypeList,            // { items, limit, offset }
-  CreateInteractionTypeBody,      // Body for create()
+  CreateInteractionTypeBody,      // Body for create() — the server mints the id
+  EnsureInteractionTypeInput,     // Input for ensureType() — { appId, key, permissions?, display?, data? }
   UpdateInteractionTypeBody,      // Body for update()
   AdminInteractionsQueryRequest,  // query() filter options
   AdminInteractionsCountsByOutcomeRequest,
@@ -520,7 +529,8 @@ import type {
 
 ## Best Practices
 
-- Use descriptive `interactionId` values: `warranty-registration`, `competition-entry`, `newsletter-vote`
+- Never hardcode an `interactionId`: create types with `ensureType` in admin, keep their ids in app config (`interactionIds.<key>`), read them everywhere else
+- Use descriptive type keys: `warranty-registration`, `competition-entry`, `newsletter-vote`
 - Use `outcome` to capture the choice — it's the key field that `countsByOutcome()` aggregates on
 - Include `metadata` for richer analytics and debugging (`source`, `device`, `region`, etc.)
 - Use `uniquePerUser: true` for actions that should only happen once (votes, registrations)

package/docs/overview.md

@@ -280,7 +280,7 @@ See `docs/ai.md` for complete documentation.
 
 The `SL.interactions` namespace tracks user engagement — competition entries, votes, form submissions, warranty registrations. Events can trigger automated journeys and communications.
 
-Important: create interaction type definitions first, then submit events using those existing IDs. Do not invent `interactionId` values in client code.
+**The one rule:** you never choose an interaction id. In admin, `SL.interactions.ensureType(collectionId, { appId, key: 'vote', … })` finds-or-creates the type and returns its server-minted `id`; store it in app config (`interactionIds: { vote: type.id }`); everywhere else — public widgets included — read `interactionIds.vote` from config and pass that as `interactionId`. Never write an interactionId as a string literal.
 
 Key functions: `submitPublicEvent()`, `appendEvent()` (admin), `countsByOutcome()`, `query()`.
 

package/docs/site-seo.md

@@ -8,9 +8,10 @@ get all of this from Hub.
 - **`/robots.txt`, `/sitemap.xml`, `/llms.txt`** are generated on the site's own address. Don't ship
   `robots.txt` or `sitemap.xml`: one build serves many sites, and sitemap URLs must be absolute on
   the site's host, which the build can't know.
-- **Declare your routes** in `public/sitemap-paths.txt`, one path per line (`/`, `/menu`,
-  `/book`). They go into the sitemap and `llms.txt` on the right host. Pre-rendered pages
-  (`about/index.html`) are found automatically.
+- **List every page** in `public/sitemap-paths.txt`, one `<path> [Title]` per line, in menu order
+  (`/ Home`, `/menu Menu`, `/book Book a table`). They go into the sitemap and `llms.txt` (titled)
+  on the right host, and Forge's preview uses the same list as its page menu. Keep it in step with
+  the router. Pre-rendered pages (`about/index.html`) are found automatically.
 - **Canonical address.** A site can answer on its automatic address, a chosen name and a custom
   domain. Every page gets `Link: <https://{canonical}{path}>; rel="canonical"`, so search engines
   consolidate on one: the custom domain, else the chosen name, else the automatic address. Don't set