@colixsystems/widget-sdk 0.92.0 → 0.93.0

package/README.md

@@ -65,6 +65,16 @@ See the design reference for the full architecture: [`docs/architecture/widget-m
 
 `v0.91.0` — pre-publish. The package surface (types, function names, export paths) is the v1 contract; runtime behaviour for some hooks is stubbed (each hook documents what's wired and what isn't). It is **not yet published to npm**.
 
+### What's new in 0.93.0 (contract 1.66.0)
+
+**BREAKING: a widget no longer declares server-side actions.** `manifest.actions` is removed from the contract and **refused** by `validateManifest` — an author who declares it now fails the publish with a message naming the replacement, rather than shipping a widget that quietly carries no automation.
+
+- **Why.** `actions` made a widget two products in one package: a React component that renders, and a script that never renders at all — different runtime, different lifecycle, different review concerns, one manifest. Automation is now its own marketplace deliverable, an **Action** (`@colixsystems/action-sdk`), with its own manifest, starter kit, developer guide, submit button and platform-admin review. A workspace installs and configures it separately from any widget.
+- **What to do instead.** Move the script into an Action manifest (`appstudio-action lint` / `pack`), publish it, and let the workspace install it. Its `propertySchema` is filled in by the **installing operator** rather than a page author, and the values reach the script as the `properties` global.
+- **Removed from the contract**: the `actions` manifest field. `CONTRACT.actionTriggerTypes` / `actionScriptGlobals` / `actionScriptMaxBytes` remain exported for now but describe a surface no widget field uses — the action-sdk owns that vocabulary.
+- **Existing installs are unaffected.** A tenant Action row materialised from a widget manifest keeps running, keeps its bindings and keeps its run history; the platform migrated those rows onto the Action that ships the automation. What is gone is the ability to declare a NEW one on a widget.
+- **No parity impact.** Actions never ran in the rendered app, so nothing about the Player or the export changes.
+
 ### What's new in 0.92.0 (contract 1.65.0)
 
 **New `useInterpretDraft(tableId)` hook — turn one sentence into DRAFT record values.** A new DATASTORE hook reading a new `interpret` method on the existing `ctx.datastore` slice (`@colixsystems/datastore-client` 0.13.0). Returns `{ interpret, interpreting, error, result, available }`. Call `interpret(text, { fields, timeZone })` **imperatively** from an event handler — never on mount or in a render loop — and it resolves to `{ values, unresolved }`, where `values` is keyed by column NAME (the same shape `useDatastoreMutation().create` takes) and `unresolved` names the fields the sentence did not state.

package/dist/contract.cjs

@@ -1590,17 +1590,6 @@ const MANIFEST_SCHEMA = {
     description:
       "Optional. Tables the widget needs, seeded into the workspace at install time. Authors wire them into the widget's `tableRef` properties via the Properties Panel — the SDK does not auto-bind. Limits: 8 tables, 24 columns per table. RELATION columns address siblings by `targetSuffix` (must be declared earlier in the array). Tables persist across uninstalls.",
   },
-  actions: {
-    type: "object[]",
-    required: false,
-    description:
-      "Optional. Server-side actions the widget declares. Each runs in the shared isolated-vm action runner (cron- or record-triggered) — NEVER in the rendered app. Operators enable them per tenant from the Properties Panel; the action materialises DISABLED until they bind an integration API key (and, for record_* triggers, a target table) in the Actions admin page. Each entry: { key (stable, unique within the manifest), name, description?, triggerTypes (a non-empty array of unique values from " +
-      ACTION_TRIGGER_TYPES.join(", ") +
-      "; combine them so one script serves several events — the script's `triggerType` global names the event that actually fired), scheduleCron? (required iff triggerTypes contains 'schedule'; node-cron syntax), timeoutMs? (100–300000), scriptSource (≤200 KiB; runs against " +
-      ACTION_SCRIPT_GLOBALS.join(", ") +
-      " — NOT the React surface, so SDK imports/hooks are unavailable) }. Do NOT include triggerTableId or apiKeyId — those are tenant-local and bound after install.",
-    default: [],
-  },
   translations: {
     type: "object",
     required: false,
@@ -2891,7 +2880,11 @@ const CONTRACT = deepFreeze({
   //    published widget keeps validating. The script's `triggerType` global
   //    now names the trigger that actually FIRED the run ('manual' and 'app'
   //    included), which is what makes a multi-trigger script able to branch.
-  version: "1.65.0",
+  // 1.66.0: BREAKING — `actions` is removed from the manifest contract and
+  // REFUSED by the validator (sc-4879). Server-side automation ships as its own
+  // marketplace deliverable (`@colixsystems/action-sdk`), which a workspace
+  // installs and configures separately. A widget renders; it does not automate.
+  version: "1.66.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,

package/dist/contract.js

@@ -1590,17 +1590,6 @@ const MANIFEST_SCHEMA = {
     description:
       "Optional. Tables the widget needs, seeded into the workspace at install time. Authors wire them into the widget's `tableRef` properties via the Properties Panel — the SDK does not auto-bind. Limits: 8 tables, 24 columns per table. RELATION columns address siblings by `targetSuffix` (must be declared earlier in the array). Tables persist across uninstalls.",
   },
-  actions: {
-    type: "object[]",
-    required: false,
-    description:
-      "Optional. Server-side actions the widget declares. Each runs in the shared isolated-vm action runner (cron- or record-triggered) — NEVER in the rendered app. Operators enable them per tenant from the Properties Panel; the action materialises DISABLED until they bind an integration API key (and, for record_* triggers, a target table) in the Actions admin page. Each entry: { key (stable, unique within the manifest), name, description?, triggerTypes (a non-empty array of unique values from " +
-      ACTION_TRIGGER_TYPES.join(", ") +
-      "; combine them so one script serves several events — the script's `triggerType` global names the event that actually fired), scheduleCron? (required iff triggerTypes contains 'schedule'; node-cron syntax), timeoutMs? (100–300000), scriptSource (≤200 KiB; runs against " +
-      ACTION_SCRIPT_GLOBALS.join(", ") +
-      " — NOT the React surface, so SDK imports/hooks are unavailable) }. Do NOT include triggerTableId or apiKeyId — those are tenant-local and bound after install.",
-    default: [],
-  },
   translations: {
     type: "object",
     required: false,
@@ -2891,7 +2880,11 @@ const CONTRACT = deepFreeze({
   //    published widget keeps validating. The script's `triggerType` global
   //    now names the trigger that actually FIRED the run ('manual' and 'app'
   //    included), which is what makes a multi-trigger script able to branch.
-  version: "1.65.0",
+  // 1.66.0: BREAKING — `actions` is removed from the manifest contract and
+  // REFUSED by the validator (sc-4879). Server-side automation ships as its own
+  // marketplace deliverable (`@colixsystems/action-sdk`), which a workspace
+  // installs and configures separately. A widget renders; it does not automate.
+  version: "1.66.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,

package/dist/manifest.cjs

@@ -4,7 +4,7 @@
 // re-exports the same functions defined here so there is exactly one
 // implementation.
 
-const { CONTRACT, normaliseActionTriggerTypes } = require("./contract.cjs");
+const { CONTRACT } = require("./contract.cjs");
 
 const PAYLOAD_VALUE_TYPES = CONTRACT.payloadValueTypes;
 
@@ -39,20 +39,6 @@ const VALID_CATEGORIES = new Set([
 ]);
 const VALID_PLATFORMS = new Set(["web", "native"]);
 
-// REQ-WIDGET-ACTION — structural validation for manifest-declared server
-// actions. Mirrors the backend action.service caps; the runner re-validates
-// the cron expression (node-cron) and binds the tenant-local API key + table
-// at enable time, so we only check shape + size here (cross-env: no Buffer).
-const VALID_ACTION_TRIGGERS = new Set([
-  "schedule",
-  "record_created",
-  "record_updated",
-  "record_deleted",
-]);
-const ACTION_SCRIPT_MAX_BYTES = 200 * 1024;
-const ACTION_TIMEOUT_MIN_MS = 100;
-const ACTION_TIMEOUT_MAX_MS = 5 * 60 * 1000;
-
 // REQ-L10N-WIDGET — caps + patterns for manifest-declared translations.
 // The relative key pattern is deliberately tighter than the dictionary's
 // own KEY_RE: once the host namespaces it (`widget.<id>.<key>`) the result
@@ -133,54 +119,22 @@ function validateManifestTranslations(translations, manifestId, errors) {
   }
 }
 
-function validateManifestActions(actions, errors) {
-  if (!Array.isArray(actions)) {
-    errors.push("manifest.actions must be an array (omit it or use [] for none)");
-    return;
-  }
-  const seenKeys = new Set();
-  for (const a of actions) {
-    if (a === null || typeof a !== "object") {
-      errors.push("manifest.actions entries must be objects");
-      break;
-    }
-    if (!isNonEmptyString(a.key)) {
-      errors.push("manifest.actions[].key must be a non-empty string");
-    } else if (seenKeys.has(a.key)) {
-      errors.push(`manifest.actions[].key "${a.key}" is duplicated`);
-    } else {
-      seenKeys.add(a.key);
-    }
-    pushIf(errors, isNonEmptyString(a.name), "manifest.actions[].name must be a non-empty string");
-    const triggerTypes = normaliseActionTriggerTypes(a);
-    if (triggerTypes === null) {
-      errors.push(
-        `manifest.actions[].triggerTypes must be a non-empty array of unique values from ${[...VALID_ACTION_TRIGGERS].join(", ")}`,
-      );
-    } else if (triggerTypes.includes("schedule")) {
-      pushIf(
-        errors,
-        isNonEmptyString(a.scheduleCron),
-        "manifest.actions[].scheduleCron is required when triggerTypes contains 'schedule'",
-      );
-    }
-    if (!isNonEmptyString(a.scriptSource)) {
-      errors.push("manifest.actions[].scriptSource must be a non-empty string");
-    } else if (utf8ByteLength(a.scriptSource) > ACTION_SCRIPT_MAX_BYTES) {
-      errors.push("manifest.actions[].scriptSource exceeds 200 KiB");
-    }
-    if (a.timeoutMs !== undefined) {
-      const t = Number(a.timeoutMs);
-      if (!Number.isFinite(t) || t < ACTION_TIMEOUT_MIN_MS || t > ACTION_TIMEOUT_MAX_MS) {
-        errors.push("manifest.actions[].timeoutMs must be between 100 and 300000");
-      }
-    }
-    if (a.triggerTableId !== undefined || a.apiKeyId !== undefined) {
-      errors.push(
-        "manifest.actions[] must not include triggerTableId or apiKeyId — those are tenant-local and bound after install",
-      );
-    }
-  }
+// REQ-MKT-ACTION (sc-4879): a widget no longer declares server-side actions.
+//
+// `manifest.actions` was how an automation shipped before Actions existed as
+// their own marketplace deliverable — a widget was two products in one package,
+// a component that renders and a script that never renders at all. It is now
+// REFUSED rather than ignored: an author who declares it believes the
+// automation will ship, and silence would publish that misunderstanding.
+//
+// The replacement is a marketplace Action (`@colixsystems/action-sdk`), which
+// the workspace installs and configures on its own.
+function validateManifestActions(_actions, errors) {
+  errors.push(
+    "manifest.actions is no longer supported — ship the automation as a " +
+      "marketplace Action (@colixsystems/action-sdk) instead of declaring it " +
+      "on a widget",
+  );
 }
 
 function canonicalCategory(c) {
@@ -355,7 +309,7 @@ function validateManifest(m) {
     }
   }
 
-  // `actions` is optional (additive in SDK 1.8.0) — only validate when present.
+  // Present at all is now an error (sc-4879) — see validateManifestActions.
   if (manifest.actions !== undefined) {
     validateManifestActions(manifest.actions, errors);
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@colixsystems/widget-sdk",
-  "version": "0.92.0",
+  "version": "0.93.0",
   "description": "Common widget interface for AppStudio. Implements WidgetManifest, WidgetContext, property schema, and helper hooks.",
   "type": "module",
   "main": "./dist/index.js",