@proveanything/smartlinks 2.0.39 → 2.0.41

package/dist/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/dist/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/dist/docs/server-functions.md

@@ -324,6 +324,40 @@ name (a first-party builtin still wins). Always prefer an appId.
 
 ---
 
+## Inputs — data handed to your function
+
+Declare what your function needs and the platform fetches it **before** the run: read it from `ctx.inputs` instead of calling `ctx.sl` first. One less round trip — and for functions running in the isolated runner, one less network hop.
+
+```jsonc
+// app.manifest.json → functions.definitions[]
+{
+  "name": "onProductChanged",
+  "trigger": { "type": "event", "eventTypes": ["product.updated"] },
+  "capabilities": ["sl:products:read", "sl:data:read"],
+  "inputs": { "appConfig": true }            // entity is on by default for event triggers
+}
+```
+
+```js
+export async function onProductChanged(ctx, event) {
+  const product = ctx.inputs.entity                     // the product that changed
+  const { interactionIds } = ctx.inputs.appConfig || {} // this app's config for the collection
+}
+```
+
+| Input | What you get | Needs | Triggers |
+|---|---|---|---|
+| `entity` | The record the event is about: the product, your app's record, or the interaction event. **On by default**; `"entity": false` opts out. | read on that resource (`sl:products:read`, `sl:records:read`) | event |
+| `collection` | The collection's public record | — | all |
+| `appConfig` | Your app's config for this collection (where setup like `interactionIds` lives) | `sl:data:read` | all |
+| `product` | A product named by the request: `{ "from": "body.productId" }`, `"query.<field>"` or `"path"` | `sl:products:read` | http |
+
+- **Same rules as `ctx.sl`.** Inputs are fetched with your function's authority and capabilities, scoped to the collection it runs in — a product from another collection is never fetched.
+- **Never an error.** Not found, not allowed or larger than 256 KB → that input is `null`. Check before you use it.
+- **Current state.** Event inputs are fetched when your function runs, so you see the record as it is now; `event` still carries the ids.
+- **Checked at publish.** An unknown input, a bad `from`, or a missing capability fails validation.
+- **Testing:** pass `inputs` to the test context — `createFunctionTestContext({ def, inputs: { entity: { id: 'p1', name: 'Kettle' } } })`.
+
 ## Exposing a function to the AI agent
 
 An `http` function can be offered to the AI agent as a **callable tool**, alongside the built-in

package/dist/http.d.ts

@@ -71,6 +71,11 @@ export declare function initializeApi(options: {
     awaitAuth?: boolean;
     /** How long (ms) to wait for the async token before letting requests proceed anyway. Default 8000. */
     awaitAuthTimeoutMs?: number;
+    /**
+     * proxyMode only: how long (ms) a request waits for the parent host's reply before failing with a
+     * 504 SmartlinksApiError (errorCode PROXY_TIMEOUT). Default 90000. 0 = wait indefinitely.
+     */
+    proxyTimeoutMs?: number;
     iframeAutoResize?: boolean;
     logger?: Logger;
     /**

package/dist/http.js

@@ -31,6 +31,10 @@ let baseURL = null;
 let apiKey = undefined;
 let bearerToken = undefined;
 let proxyMode = false;
+// How long a request through the parent (proxyMode) waits for the host's reply. Without a limit, a host
+// that never answers (no responder, a dropped message) leaves the call pending forever: no network
+// request in the frame, no error. 90 s covers the longest platform call (a 60 s function deadline).
+let proxyTimeoutMs = 90000;
 let ngrokSkipBrowserWarning = false;
 let extraHeadersGlobal = {};
 /**
@@ -522,6 +526,8 @@ export function initializeApi(options) {
         });
     }
     proxyMode = !!options.proxyMode;
+    if (options.proxyTimeoutMs !== undefined)
+        proxyTimeoutMs = Math.max(0, Number(options.proxyTimeoutMs) || 0);
     // Auto-enable ngrok skip header if domain contains .ngrok.io and user did not explicitly set the flag.
     // Infer ngrok usage from common domains (.ngrok.io or .ngrok-free.dev)
     const inferredNgrok = /(\.ngrok\.io|\.ngrok-free\.dev)(\b|\/)/i.test(baseURL);
@@ -1082,11 +1088,30 @@ async function proxyRequest(method, path, body, headers, options) {
     };
     logDebug('[smartlinks] proxy:postMessage', { id, method, path, headers: headers ? redactHeaders(headers) : undefined, hasBody: !!body });
     return new Promise((resolve, reject) => {
-        proxyPending[id] = { resolve, reject };
+        proxyPending[id] = withProxyTimeout(id, `${method} ${path}`, resolve, reject);
         window.parent.postMessage(msg, "*");
-        // Optionally: add a timeout here to reject if no response
     });
 }
+/**
+ * Wrap a pending proxy request's resolve/reject with the proxy timeout (proxyTimeoutMs): if the host
+ * hasn't answered by then, the request fails with a 504 PROXY_TIMEOUT instead of hanging forever.
+ */
+function withProxyTimeout(id, what, resolve, reject) {
+    if (!(proxyTimeoutMs > 0))
+        return { resolve, reject };
+    const timer = setTimeout(() => {
+        if (!proxyPending[id])
+            return;
+        delete proxyPending[id];
+        const message = `The host page did not answer ${what} within ${proxyTimeoutMs >= 1000 ? `${Math.round(proxyTimeoutMs / 1000)}s` : `${proxyTimeoutMs}ms`} (proxyMode). The parent may not be handling SmartLinks proxy requests.`;
+        logDebug('[smartlinks] proxy:timeout', { id, what });
+        reject(new SmartlinksApiError(message, 504, { code: 504, errorCode: 'PROXY_TIMEOUT', message }));
+    }, proxyTimeoutMs);
+    return {
+        resolve: (data) => { clearTimeout(timer); resolve(data); },
+        reject: (err) => { clearTimeout(timer); reject(err); },
+    };
+}
 /**
  * Upload a FormData payload via proxy with progress events using chunked postMessage.
  * Parent is expected to implement the counterpart protocol.
@@ -1794,8 +1819,7 @@ export async function sendCustomProxyMessage(request, params) {
     };
     logDebug('[smartlinks] proxy:custom postMessage', { id, request, params: safeBodyPreview(params) });
     return new Promise((resolve, reject) => {
-        proxyPending[id] = { resolve, reject };
+        proxyPending[id] = withProxyTimeout(id, `custom request ${request}`, resolve, reject);
         window.parent.postMessage(msg, "*");
-        // Optionally: add a timeout here to reject if no response
     });
 }

package/dist/openapi.yaml

@@ -19124,6 +19124,8 @@ components:
           enum:
             - collection
             - global
+        inputs:
+          $ref: "#/components/schemas/AppFunctionInputs"
         apiVersion:
           type: string
         handler:
@@ -19233,6 +19235,8 @@ components:
         fetch:
           type: object
           additionalProperties: true
+        inputs:
+          $ref: "#/components/schemas/ServerFunctionInputs"
       required:
         - collectionId
         - appId
@@ -19240,6 +19244,34 @@ components:
         - secrets
         - caller
         - fetch
+        - inputs
+    AppFunctionInputs:
+      type: object
+      properties:
+        entity:
+          type: boolean
+        collection:
+          type: boolean
+        appConfig:
+          type: boolean
+        product:
+          type: object
+          additionalProperties: true
+    ServerFunctionInputs:
+      type: object
+      properties:
+        entity:
+          type: object
+          additionalProperties: true
+        collection:
+          type: object
+          additionalProperties: true
+        appConfig:
+          type: object
+          additionalProperties: true
+        product:
+          type: object
+          additionalProperties: true
     ServerFunctionHttpEvent:
       type: object
       properties:
@@ -26623,8 +26655,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/testing/index.d.ts

@@ -1,4 +1,4 @@
-import type { AppFunctionDef, ServerFunctionContext } from '../types/appManifest.js';
+import type { AppFunctionDef, ServerFunctionContext, ServerFunctionInputs } from '../types/appManifest.js';
 export declare class CapabilityError extends Error {
     capability: string;
     code: string;
@@ -62,6 +62,8 @@ export interface CreateFunctionTestContextOptions {
     sl?: TestSlImpl;
     /** Backing fetch (defaults to global fetch). Still gated by the `network` capability. */
     fetch?: typeof fetch;
+    /** What the platform would have prefetched as `ctx.inputs` (e.g. `{ entity: product }`). Default `{}`. */
+    inputs?: ServerFunctionInputs;
 }
 export interface FunctionTestContext extends ServerFunctionContext {
     /** Captured log lines (also written via ctx.log). */

package/dist/testing/index.js

@@ -176,6 +176,7 @@ export function createFunctionTestContext(opts) {
         log: (message, data) => {
             logs.push(Object.assign({ at: new Date().toISOString(), message: String(message) }, (data ? { data } : {})));
         },
+        inputs: Object.freeze(Object.assign({}, (opts.inputs || {}))),
         logs,
     };
 }

package/dist/types/appManifest.d.ts

@@ -268,6 +268,14 @@ export interface AppFunctionDef {
      * Per-call `{ scope }` and the `appData.global` / `appData.collection` handles override this.
      */
     dataScope?: 'collection' | 'global';
+    /**
+     * Data the platform fetches BEFORE the run and hands over as `ctx.inputs` — no round trip from your
+     * code (for isolated functions, no network hop). Same authority and capabilities as the equivalent
+     * `ctx.sl` read; a missing, denied or oversized (> 256 KB) input arrives as `null`, never an error.
+     * Event-trigger functions get `entity` (the record the event is about) by default; `entity: false`
+     * opts out. See server-functions.md → "Inputs".
+     */
+    inputs?: AppFunctionInputs;
     /** SDK/manifest API version this function targets (pinned for runtime compatibility). */
     apiVersion?: string;
     /** Exported handler name in the functions bundle. Defaults to `name`. */
@@ -403,6 +411,29 @@ export interface ServerFunctionContext {
     fetch: typeof fetch;
     /** Structured logging captured into run telemetry. */
     log: (message: string, data?: Record<string, any>) => void;
+    /** Data prefetched for this run, per the definition's `inputs` (read-only; `{}` when none). */
+    inputs: Readonly<ServerFunctionInputs>;
+}
+/** What a function asks to have prefetched (`AppFunctionDef.inputs`). */
+export interface AppFunctionInputs {
+    /** Event triggers: the record the event is about — product (needs `sl:products:read`), app record of
+     *  this app (`sl:records:read`), or the interaction event itself. On by default; `false` opts out. */
+    entity?: boolean;
+    /** The collection's public record. */
+    collection?: boolean;
+    /** This app's config for the collection — e.g. its `interactionIds`. Needs `sl:data:read`. */
+    appConfig?: boolean;
+    /** Http triggers: a product named by the request. Needs `sl:products:read`. */
+    product?: {
+        from: `body.${string}` | `query.${string}` | 'path';
+    };
+}
+/** `ctx.inputs` — what was prefetched for this run (keys you declared; `null` when unavailable). */
+export interface ServerFunctionInputs {
+    entity?: Record<string, any> | null;
+    collection?: Record<string, any> | null;
+    appConfig?: Record<string, any> | null;
+    product?: Record<string, any> | null;
 }
 /** The HTTP request handed to an `http`-trigger function as `event`. */
 export interface ServerFunctionHttpEvent<TBody = any> {

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 {