@object-ui/core 17.5.0 → 17.7.0

package/dist/actions/TransactionManager.d.ts

@@ -24,8 +24,13 @@ export interface TransactionOperation {
     type: 'create' | 'update' | 'delete';
     /** Target resource name */
     resource: string;
-    /** Record ID (for update/delete) */
-    id?: string | number;
+    /**
+     * Record ID (for update/delete). A `string`, as `@objectstack/spec` declares
+     * every record door and as this type's own sibling `BatchTransactionOperation.id`
+     * already did; the rollback path hands it straight to `DataSource.update`
+     * (objectui#9333).
+     */
+    id?: string;
     /** Data payload */
     data?: Record<string, any>;
     /** Previous state (for rollback) */

package/dist/actions/actionKeys.d.ts

@@ -18,7 +18,7 @@
  *
  * That asymmetry was the issue. An open key set on a DECLARED METADATA CONTRACT
  * is what lets a typo (`targt`, `exectue`) and a tombstoned key (`execute`) both
- * sail through to a runner that then silently does nothing — the #2169 "Mark
+ * sail through to a runner that then silently does nothing — the objectstack-ai/objectstack#2169 "Mark
  * Done does nothing" shape.
  *
  * This module was step 1 of the staged narrowing: make the key set VISIBLE and
@@ -74,10 +74,12 @@
  * rejection" into a compile error at no cost. Hand-copying would have quietly
  * re-legitimized two dead keys — which is why the types are derived.
  *
- * 17 keys `ActionDef` declares that the spec does not own — `actionType`, `api`,
+ * 16 keys `ActionDef` declares that the spec does not own — `actionType`, `api`,
  * `chain`, `chainMode`, `close`, `condition`, `confirm`, `endpoint`, `modal`,
- * `navigate`, `onClick`, `onFailure`, `onSuccess`, `redirect`, `reload`, `toast`,
- * `actionParams`. Step 2 marked `@deprecated`, with the spec spelling to use
+ * `navigate`, `onClick`, `onFailure`, `redirect`, `reload`, `toast`,
+ * `actionParams`. (`onSuccess` was the 17th until objectui#5934 retired the
+ * runner's chained-callback meaning; the key is now spec-owned and derived,
+ * like the 18 below.) Step 2 marked `@deprecated`, with the spec spelling to use
  * instead, ONLY the four the runner itself proves are aliases: `actionType` (→
  * `type`), `api` and `endpoint` (→ `target`; `executeAPI` resolves
  * `api || endpoint || target`), and `navigate` (→ flat `target`/`openIn`;
@@ -106,11 +108,12 @@
 /**
  * Every property `ActionDef` declares, in declaration order.
  *
- * Kept as data because TypeScript types do not survive to runtime — and
- * `keyof ActionDef` cannot substitute for this list: the index signature widens
- * it to `string | number`, which is precisely the problem being worked around.
+ * Kept as data because TypeScript types do not survive to runtime — `keyof
+ * ActionDef` is erased along with the interface, so it cannot hand a runtime
+ * classifier a list of anything. `actionKeys.pin.test.ts` re-derives this one
+ * from the interface's AST, which is what keeps the data true.
  */
-export declare const ACTION_DEF_KEYS: readonly ["type", "actionType", "name", "label", "description", "confirmText", "confirm", "condition", "disabled", "api", "endpoint", "method", "navigate", "to", "external", "newTab", "replace", "onClick", "reload", "close", "redirect", "toast", "successMessage", "errorMessage", "refreshAfter", "undoable", "params", "actionParams", "resultDialog", "target", "body", "openIn", "modal", "chain", "chainMode", "onSuccess", "onFailure", "opensInNewTab", "newTabUrl", "locations", "visible", "requiredPermissions", "icon", "variant", "order", "component", "objectName", "ai", "aria", "bodyExtra", "bodyShape", "mode", "recordIdField", "recordIdParam", "requiresFeature", "shortcut", "bulkEnabled"];
+export declare const ACTION_DEF_KEYS: readonly ["type", "actionType", "name", "label", "description", "confirmText", "confirm", "condition", "disabled", "api", "endpoint", "method", "navigate", "to", "external", "newTab", "replace", "onClick", "reload", "close", "redirect", "toast", "successMessage", "errorMessage", "refreshAfter", "undoable", "params", "actionParams", "resultDialog", "target", "body", "openIn", "modal", "chain", "chainMode", "onFailure", "opensInNewTab", "newTabUrl", "locations", "visible", "requiredPermissions", "icon", "variant", "order", "component", "objectName", "ai", "bodyExtra", "bodyShape", "operation", "patch", "mode", "recordIdField", "recordIdParam", "requiresFeature", "onSuccess", "outcomeMessages", "shortcut", "bulkEnabled"];
 /**
  * Every property `@objectstack/spec`'s `ActionSchema` declares.
  *
@@ -125,7 +128,7 @@ export declare const ACTION_DEF_KEYS: readonly ["type", "actionType", "name", "l
  * test and wrong in shipped code — `@object-ui/types` made the same call for
  * `ActionComponent`. The pin test does the walk and fails the day this drifts.
  */
-export declare const SPEC_ACTION_KEYS: readonly ["_lock", "_lockDocsUrl", "_lockReason", "_lockSource", "_packageId", "_packageVersion", "_provenance", "ai", "aria", "body", "bodyExtra", "bodyShape", "bulkEnabled", "component", "confirmText", "description", "disabled", "errorMessage", "execute", "icon", "label", "locations", "method", "mode", "name", "newTabUrl", "objectName", "openIn", "opensInNewTab", "order", "params", "recordIdField", "recordIdParam", "refreshAfter", "requiredPermissions", "requiresFeature", "resultDialog", "shortcut", "successMessage", "target", "type", "undoable", "variant", "visible"];
+export declare const SPEC_ACTION_KEYS: readonly ["_lock", "_lockDocsUrl", "_lockReason", "_lockSource", "_packageId", "_packageVersion", "_provenance", "ai", "aria", "body", "bodyExtra", "bodyShape", "bulkEnabled", "component", "confirmText", "description", "disabled", "errorMessage", "execute", "execution", "icon", "label", "locations", "method", "mode", "name", "newTabUrl", "objectName", "onSuccess", "openIn", "opensInNewTab", "operation", "order", "outcomeMessages", "params", "patch", "recordIdField", "recordIdParam", "refreshAfter", "requiredPermissions", "requiresFeature", "resultDialog", "shortcut", "successMessage", "target", "type", "undoable", "variant", "visible"];
 /**
  * The `navigation` alias's own spelling of a target, read off the action itself
  * when no nested `navigate` object is present (`ActionRunner.executeNavigation`).
@@ -137,6 +140,54 @@ export declare const SPEC_ACTION_KEYS: readonly ["_lock", "_lockDocsUrl", "_lock
  * runner itself supports.
  */
 export declare const NAVIGATION_ALIAS_KEYS: readonly ["to", "external", "newTab", "replace"];
+/**
+ * Keys a HOST composes on the DISPATCH OBJECT at dispatch time — chrome the
+ * runtime reads once on its way to the dialog, that no author ever writes and
+ * no store ever holds.
+ *
+ * Distinct from every other list in this module, and the distinction is the
+ * whole point: each of the three lists above restates one AUTHORED surface —
+ * what `ActionDef` itself declares, what the spec's `ActionSchema` declares,
+ * and the `navigation` alias's objectui dialect — so a key joining one of them
+ * is a key an author may legally write. This list claims no such derivation and
+ * must not acquire one: a key here is the opposite, and writing it in metadata
+ * is still a compile error that must stay one. Maintainer ruling
+ * 2026-08-22 fixes both halves of that: ⛔ the key is NOT declared on
+ * `ActionDef` and ⛔ NOT added to {@link ACTION_DEF_KEYS}; it is declared at the
+ * seam, on `packages/app-shell/src/consoleActionDispatch.ts`'s
+ * `ConsoleActionDispatch`, and appears HERE only so the dev-mode warning below
+ * stops calling it unknown.
+ *
+ * Why the warning has to know: `classifyActionKeys` sees the object the runner
+ * was handed, which is the DISPATCH, not the stored metadata row. With the key
+ * absent from the inventory, `warnOnUnknownActionKeys` told the author that a
+ * key TWO files read is one "no reader recognizes", and prescribed promoting it
+ * to `ActionDef` — the one shape the ruling forbids for it. A diagnostic that
+ * fires on the product's own privileged path is how a console gets muted.
+ *
+ * {@link HOST_STASHED_PARAM_KEYS} below is the same category one level down —
+ * host-composed keys inside `params` rather than on the action itself — and
+ * cites `DeclaredActionsBar` by name for the same reason this does. Two lists
+ * because the two warnings ask different questions of different objects, not
+ * because the categories differ.
+ *
+ * `overrideNotice` — the privileged-override safety copy (objectui#5178),
+ * naming the approvers about to be bypassed.
+ * - producer: `packages/app-shell/src/views/DeclaredActionsBar.tsx`, on the
+ *   `can_act:false && can_override:true` branch.
+ * - readers: `packages/app-shell/src/hooks/useConsoleActionRuntime.tsx` and
+ *   `packages/app-shell/src/views/RecordDetailView.tsx`, the console's two
+ *   param-collection handlers, which render it ahead of the declared
+ *   description in the dialog's subtitle.
+ *
+ * Anything added here must satisfy all three of: composed by a host in code,
+ * never read back out of stored metadata, and read by the runtime. A key an
+ * AUTHOR is meant to write belongs on `ActionDef` — or, when the spec owns it,
+ * in `@objectstack/spec` first — and not in this list. `actionKeys.pin.test.ts`
+ * pins the contents exactly, so growing the set is a deliberate, reviewed edit
+ * rather than a quiet one.
+ */
+export declare const HOST_DISPATCH_ACTION_KEYS: readonly ["overrideNotice"];
 /**
  * Keys the spec has TOMBSTONED: still present in `ActionSchema` so the parser can
  * reject them BY NAME with a rename prescription, rather than fail with a bare
@@ -156,7 +207,16 @@ export declare const NAVIGATION_ALIAS_KEYS: readonly ["to", "external", "newTab"
  * a tombstone the spec keeps only in order to reject it by name.
  */
 export declare const RETIRED_ACTION_KEYS: Readonly<Record<string, string>>;
-/** Every key an action may legitimately carry today. */
+/**
+ * Every key an action may legitimately carry today — authored or host-composed.
+ *
+ * Four inputs, three of them mirrors of an authored surface and the fourth
+ * ({@link HOST_DISPATCH_ACTION_KEYS}) the host-composed dispatch chrome. The
+ * union is what `classifyActionKeys` consults, and it is deliberately wider
+ * than the authored surface: the runner classifies the object it was HANDED,
+ * and a host hands it a dispatch. Membership here grants nothing to an author —
+ * `ActionDef` is what decides that, and it is closed.
+ */
 export declare const KNOWN_ACTION_KEYS: ReadonlySet<string>;
 /** Split an action's own keys into the two things worth saying out loud. */
 export declare function classifyActionKeys(action: object | null | undefined): {
@@ -169,9 +229,11 @@ export declare function resetActionKeyWarnings(): void;
  * Dev-mode only: name the keys an action carries that no reader will ever look
  * at. Non-breaking by construction — it changes no types and rejects nothing.
  *
- * Silently binding no handler is the #2169 "Mark Done does nothing" shape, and
- * the compiler cannot help while the index signature stands. Until it comes
- * down, this is the audible half.
+ * Silently binding no handler is the objectstack-ai/objectstack#2169 "Mark Done does nothing" shape. The
+ * compiler now catches it in action literals AUTHORED IN CODE — objectstack#4075
+ * step 3 closed `ActionDef` — but not in the actions that arrive as DATA, which
+ * reach the runner unparsed and which no compiler ever looked at. This is the
+ * audible half for that population; see this module's header.
  */
 export declare function warnOnUnknownActionKeys(action: object | null | undefined, where?: string): void;
 /**

package/dist/actions/actionKeys.js

@@ -18,7 +18,7 @@
  *
  * That asymmetry was the issue. An open key set on a DECLARED METADATA CONTRACT
  * is what lets a typo (`targt`, `exectue`) and a tombstoned key (`execute`) both
- * sail through to a runner that then silently does nothing — the #2169 "Mark
+ * sail through to a runner that then silently does nothing — the objectstack-ai/objectstack#2169 "Mark
  * Done does nothing" shape.
  *
  * This module was step 1 of the staged narrowing: make the key set VISIBLE and
@@ -74,10 +74,12 @@
  * rejection" into a compile error at no cost. Hand-copying would have quietly
  * re-legitimized two dead keys — which is why the types are derived.
  *
- * 17 keys `ActionDef` declares that the spec does not own — `actionType`, `api`,
+ * 16 keys `ActionDef` declares that the spec does not own — `actionType`, `api`,
  * `chain`, `chainMode`, `close`, `condition`, `confirm`, `endpoint`, `modal`,
- * `navigate`, `onClick`, `onFailure`, `onSuccess`, `redirect`, `reload`, `toast`,
- * `actionParams`. Step 2 marked `@deprecated`, with the spec spelling to use
+ * `navigate`, `onClick`, `onFailure`, `redirect`, `reload`, `toast`,
+ * `actionParams`. (`onSuccess` was the 17th until objectui#5934 retired the
+ * runner's chained-callback meaning; the key is now spec-owned and derived,
+ * like the 18 below.) Step 2 marked `@deprecated`, with the spec spelling to use
  * instead, ONLY the four the runner itself proves are aliases: `actionType` (→
  * `type`), `api` and `endpoint` (→ `target`; `executeAPI` resolves
  * `api || endpoint || target`), and `navigate` (→ flat `target`/`openIn`;
@@ -106,9 +108,10 @@
 /**
  * Every property `ActionDef` declares, in declaration order.
  *
- * Kept as data because TypeScript types do not survive to runtime — and
- * `keyof ActionDef` cannot substitute for this list: the index signature widens
- * it to `string | number`, which is precisely the problem being worked around.
+ * Kept as data because TypeScript types do not survive to runtime — `keyof
+ * ActionDef` is erased along with the interface, so it cannot hand a runtime
+ * classifier a list of anything. `actionKeys.pin.test.ts` re-derives this one
+ * from the interface's AST, which is what keeps the data true.
  */
 export const ACTION_DEF_KEYS = [
     'type',
@@ -153,7 +156,6 @@ export const ACTION_DEF_KEYS = [
     'modal',
     'chain',
     'chainMode',
-    'onSuccess',
     'onFailure',
     'opensInNewTab',
     'newTabUrl',
@@ -171,13 +173,30 @@ export const ACTION_DEF_KEYS = [
     'component',
     'objectName',
     'ai',
-    'aria',
+    // `aria` left this list, with its `ActionDef` field, when `@objectstack/spec`
+    // 17.5.0 retired `action.aria` as a `retiredKey()` tombstone (objectui#10929):
+    // the derived type had become `undefined`, so the field mirrored nothing. It
+    // stays in `SPEC_ACTION_KEYS` below, because `ActionSchema` still declares the
+    // tombstone.
     'bodyExtra',
     'bodyShape',
+    // The declarative single-record field write (spec 17.3.0). Promoted from
+    // inventory-only to declared `ActionDef` fields when the runner learned to
+    // read them — the branch that dispatches `operation: 'update'` on the
+    // platform action route, ahead of `type`.
+    'operation',
+    'patch',
     'mode',
     'recordIdField',
     'recordIdParam',
     'requiresFeature',
+    // Moved from the runner-native cluster above by objectui#5934: the legacy
+    // chained-callback meaning is retired and the key's type now derives the
+    // spec's `{ navigate, openIn }` block.
+    'onSuccess',
+    // Spec 17.6.0's success copy per handler outcome (objectui#11344), declared
+    // when the runner learned to read it: the success toast's first rung.
+    'outcomeMessages',
     'shortcut',
     'bulkEnabled',
 ];
@@ -227,6 +246,14 @@ export const SPEC_ACTION_KEYS = [
     'disabled',
     'errorMessage',
     'execute',
+    // Added to `ActionSchema` in @objectstack/spec 17.5.0 (objectui#11073): the
+    // bulk dispatch contract the action's body is written for, in
+    // `bulkActionDefs`' own `'perRecord' | 'aggregate'` vocabulary. Listed for the
+    // reason `description` is — this array restates the spec's declared keys, so
+    // an action carrying it is not reported as having an unknown key. `ActionDef`
+    // does NOT declare it and the runner does not read it: the spec's own
+    // enforcement is `@objectstack/lint`'s authoring-time check.
+    'execution',
     'icon',
     'label',
     'locations',
@@ -235,10 +262,35 @@ export const SPEC_ACTION_KEYS = [
     'name',
     'newTabUrl',
     'objectName',
+    // Declared by `ActionSchema` as of @objectstack/spec 17.1.0 (objectui#5328).
+    // All four declared action surfaces forward it since objectui#5493/#6304, and
+    // `ActionDef` derives its type from the spec since objectui#5934 retired the
+    // runner's legacy chained-callback meaning for the same key.
+    'onSuccess',
     'openIn',
     'opensInNewTab',
+    // Added to `ActionSchema` in @objectstack/spec 17.3.0 (objectui#7122), the
+    // declarative single-record field write that mirrors a list view's
+    // `bulkActionDefs`: `operation: 'update'` applies `patch` (merged UNDER the
+    // collected `params`) to the current record on the data plane AS THE CALLER.
+    //
+    // Both keys were inventory-ONLY when that bump landed, under the maintainer's
+    // 2026-09-05 ruling on it ("record both as justified omissions now; forward
+    // only the key a runtime actually reads, once its semantics are read from
+    // upstream — no speculative forwarding"). That condition is now met: the
+    // runner reads both (`executeUpdateOperation`, dispatched ahead of `type`),
+    // `ActionDef` declares both, and every action surface forwards them — which
+    // is what `check:action-forward-parity` now requires rather than excuses.
+    'operation',
     'order',
+    // Added to `ActionSchema` in @objectstack/spec 17.6.0 (objectstack#21095,
+    // objectui#11344): success copy per handler outcome, keyed by the snake_case
+    // `outcome` the handler returns. `ActionDef` declares it (derived) and the
+    // runner reads it as the success toast's first rung, ahead of
+    // `successMessage`.
+    'outcomeMessages',
     'params',
+    'patch',
     'recordIdField',
     'recordIdParam',
     'refreshAfter',
@@ -264,6 +316,54 @@ export const SPEC_ACTION_KEYS = [
  * runner itself supports.
  */
 export const NAVIGATION_ALIAS_KEYS = ['to', 'external', 'newTab', 'replace'];
+/**
+ * Keys a HOST composes on the DISPATCH OBJECT at dispatch time — chrome the
+ * runtime reads once on its way to the dialog, that no author ever writes and
+ * no store ever holds.
+ *
+ * Distinct from every other list in this module, and the distinction is the
+ * whole point: each of the three lists above restates one AUTHORED surface —
+ * what `ActionDef` itself declares, what the spec's `ActionSchema` declares,
+ * and the `navigation` alias's objectui dialect — so a key joining one of them
+ * is a key an author may legally write. This list claims no such derivation and
+ * must not acquire one: a key here is the opposite, and writing it in metadata
+ * is still a compile error that must stay one. Maintainer ruling
+ * 2026-08-22 fixes both halves of that: ⛔ the key is NOT declared on
+ * `ActionDef` and ⛔ NOT added to {@link ACTION_DEF_KEYS}; it is declared at the
+ * seam, on `packages/app-shell/src/consoleActionDispatch.ts`'s
+ * `ConsoleActionDispatch`, and appears HERE only so the dev-mode warning below
+ * stops calling it unknown.
+ *
+ * Why the warning has to know: `classifyActionKeys` sees the object the runner
+ * was handed, which is the DISPATCH, not the stored metadata row. With the key
+ * absent from the inventory, `warnOnUnknownActionKeys` told the author that a
+ * key TWO files read is one "no reader recognizes", and prescribed promoting it
+ * to `ActionDef` — the one shape the ruling forbids for it. A diagnostic that
+ * fires on the product's own privileged path is how a console gets muted.
+ *
+ * {@link HOST_STASHED_PARAM_KEYS} below is the same category one level down —
+ * host-composed keys inside `params` rather than on the action itself — and
+ * cites `DeclaredActionsBar` by name for the same reason this does. Two lists
+ * because the two warnings ask different questions of different objects, not
+ * because the categories differ.
+ *
+ * `overrideNotice` — the privileged-override safety copy (objectui#5178),
+ * naming the approvers about to be bypassed.
+ * - producer: `packages/app-shell/src/views/DeclaredActionsBar.tsx`, on the
+ *   `can_act:false && can_override:true` branch.
+ * - readers: `packages/app-shell/src/hooks/useConsoleActionRuntime.tsx` and
+ *   `packages/app-shell/src/views/RecordDetailView.tsx`, the console's two
+ *   param-collection handlers, which render it ahead of the declared
+ *   description in the dialog's subtitle.
+ *
+ * Anything added here must satisfy all three of: composed by a host in code,
+ * never read back out of stored metadata, and read by the runtime. A key an
+ * AUTHOR is meant to write belongs on `ActionDef` — or, when the spec owns it,
+ * in `@objectstack/spec` first — and not in this list. `actionKeys.pin.test.ts`
+ * pins the contents exactly, so growing the set is a deliberate, reviewed edit
+ * rather than a quiet one.
+ */
+export const HOST_DISPATCH_ACTION_KEYS = ['overrideNotice'];
 /**
  * Keys the spec has TOMBSTONED: still present in `ActionSchema` so the parser can
  * reject them BY NAME with a rename prescription, rather than fail with a bare
@@ -283,15 +383,25 @@ export const NAVIGATION_ALIAS_KEYS = ['to', 'external', 'newTab', 'replace'];
  * a tombstone the spec keeps only in order to reject it by name.
  */
 export const RETIRED_ACTION_KEYS = {
-    execute: '`execute` was removed in @objectstack/spec 17 (#3855) — rename the key to `target`. ' +
+    execute: '`execute` was removed in @objectstack/spec 17 (objectstack-ai/objectstack#3855) — rename the key to `target`. ' +
         'The value (a script name or expression) is unchanged. ' +
         'Run `os migrate meta --from 16` to rewrite it automatically.',
 };
-/** Every key an action may legitimately carry today. */
+/**
+ * Every key an action may legitimately carry today — authored or host-composed.
+ *
+ * Four inputs, three of them mirrors of an authored surface and the fourth
+ * ({@link HOST_DISPATCH_ACTION_KEYS}) the host-composed dispatch chrome. The
+ * union is what `classifyActionKeys` consults, and it is deliberately wider
+ * than the authored surface: the runner classifies the object it was HANDED,
+ * and a host hands it a dispatch. Membership here grants nothing to an author —
+ * `ActionDef` is what decides that, and it is closed.
+ */
 export const KNOWN_ACTION_KEYS = new Set([
     ...ACTION_DEF_KEYS,
     ...SPEC_ACTION_KEYS,
     ...NAVIGATION_ALIAS_KEYS,
+    ...HOST_DISPATCH_ACTION_KEYS,
 ].filter((key) => !(key in RETIRED_ACTION_KEYS)));
 /** Split an action's own keys into the two things worth saying out loud. */
 export function classifyActionKeys(action) {
@@ -326,9 +436,11 @@ const isDev = () => globalThis.process?.env?.NODE_ENV !==
  * Dev-mode only: name the keys an action carries that no reader will ever look
  * at. Non-breaking by construction — it changes no types and rejects nothing.
  *
- * Silently binding no handler is the #2169 "Mark Done does nothing" shape, and
- * the compiler cannot help while the index signature stands. Until it comes
- * down, this is the audible half.
+ * Silently binding no handler is the objectstack-ai/objectstack#2169 "Mark Done does nothing" shape. The
+ * compiler now catches it in action literals AUTHORED IN CODE — objectstack#4075
+ * step 3 closed `ActionDef` — but not in the actions that arrive as DATA, which
+ * reach the runner unparsed and which no compiler ever looked at. This is the
+ * audible half for that population; see this module's header.
  */
 export function warnOnUnknownActionKeys(action, where = 'ActionRunner') {
     if (!isDev())
@@ -351,8 +463,11 @@ export function warnOnUnknownActionKeys(action, where = 'ActionRunner') {
     console.warn(`[${where}] action "${String(name)}" carries ${unknown.length === 1 ? 'a key' : 'keys'} no reader ` +
         `recognizes: \`${unknown.join('`, `')}\`. Nothing will read ${unknown.length === 1 ? 'it' : 'them'} — ` +
         'check for a typo, or promote the key to an explicit field on `ActionDef` ' +
-        '(packages/core/src/actions/actionKeys.ts). Warned rather than rejected because `ActionDef` ' +
-        'still carries `[key: string]: any`, so the compiler cannot see this (objectstack#4075).');
+        '(packages/core/src/actions/ActionRunner.ts), adding it to `ACTION_DEF_KEYS` ' +
+        '(packages/core/src/actions/actionKeys.ts) in the SAME commit — the pin test derives one ' +
+        'from the other, so either edit alone goes red. Warned rather than rejected because `tsc` ' +
+        'only sees actions authored in code: this one may have arrived as DATA, and stored ' +
+        '`sys_metadata` rows reach the runner unparsed (objectstack#3903).');
 }
 /**
  * Keys a HOST stashes into an action's `params` for the runner's own plumbing,

package/dist/actions/actionResponse.js

@@ -47,7 +47,7 @@
  * - **transport-level `success: false`** — the outer envelope reporting a
  *   failure directly.
  */
-import { actionErrorDetail } from './actionErrorDetail';
+import { actionErrorDetail } from './actionErrorDetail.js';
 /**
  * The handler's own return value — one level deeper than the action envelope.
  *
@@ -59,7 +59,7 @@ import { actionErrorDetail } from './actionErrorDetail';
 export function readActionPayload(envelope) {
     // objectstack#3962 servers single-wrap: `body.data` IS the handler value,
     // so most of the time this is the identity function. Only the exact LEGACY
-    // action envelope (pre-#3962: a boolean `success` and no keys beyond the
+    // action envelope (pre-objectstack-ai/objectstack#3962: a boolean `success` and no keys beyond the
     // envelope's own) is unwrapped one more level — a handler value that
     // merely contains a `success` key passes through untouched.
     if (isLegacyActionEnvelope(envelope)) {
@@ -82,7 +82,7 @@ export function isLegacyActionEnvelope(v) {
  */
 export function interpretActionResponse(res, json, label) {
     const envelope = json?.data;
-    // Pre-#3962 servers reported a rejection as HTTP 200 with the inner
+    // Pre-objectstack-ai/objectstack#3962 servers reported a rejection as HTTP 200 with the inner
     // `{success:false, error}`; current servers answer a real status, which
     // `res.ok` catches first. Detected narrowly so a handler value that merely
     // contains `success: false` is not misread as a failure.

package/dist/actions/index.d.ts

@@ -14,3 +14,5 @@ export * from './bulkFastPath.js';
 export * from './actionErrorDetail.js';
 export * from './actionResponse.js';
 export * from './serverActionHandler.js';
+export * from './recordIdParam.js';
+export * from './recordDelete.js';

package/dist/actions/index.js

@@ -14,3 +14,5 @@ export * from './bulkFastPath.js';
 export * from './actionErrorDetail.js';
 export * from './actionResponse.js';
 export * from './serverActionHandler.js';
+export * from './recordIdParam.js';
+export * from './recordDelete.js';

package/dist/actions/recordDelete.d.ts

@@ -0,0 +1,118 @@
+/**
+ * ObjectUI
+ * Copyright (c) 2024-present ObjectStack Inc.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+/**
+ * The ONE record-delete core — the confirm question and the delete itself —
+ * that every host's list Delete binds to (objectui#10383).
+ *
+ * ## Why this lives here, and why there is only one
+ *
+ * The console's object list deleted through `useObjectActions` (`app-shell`):
+ * the confirm question, the single delete with its ADR-0094 detection, the bulk
+ * delete and their toasts were written inline in that hook. The registered
+ * `object-view` renderer (`plugin-view`) had no delete at all — its grid
+ * handlers only refreshed — and the first repair COPIED those steps into a
+ * second flow. The copy already diverged on consent: it asked every row the
+ * plain "delete this record?" question, while the console asks a package-owned
+ * permission set the honest reset question. One operation with two
+ * implementations drifts on exactly the part that matters, so the rule is: the
+ * side with the governance keeps it, the other side re-binds to it, and there
+ * is one copy. This module is that copy, and both hosts call it.
+ *
+ * `@object-ui/core` is the lowest package both hosts already depend on. The
+ * host-specific pieces are INJECTED — the translator, the toast sink, the data
+ * source and the refresh — so this package gains no i18n or toast dependency.
+ * The host keeps its own confirm UI (`app-shell` runs the question through the
+ * action runner's confirm handler; `plugin-view` renders it in its own
+ * AlertDialog); the QUESTION comes from {@link recordDelete}.confirmText.
+ *
+ * ## ADR-0094 — a package-owned permission set is RESET, not deleted
+ *
+ * "Deleting" a `sys_permission_set` row whose `managed_by` is `'package'` does
+ * not remove it: the backend drops the environment overlay and resets the set
+ * to its shipped baseline. So the confirm asks the reset question and the
+ * success toast says "reset" — a promise of an irreversible delete the user can
+ * then see did not happen would be the dishonest copy. The row passed in is
+ * read first; when the caller has only an id (an SDUI header delete), the row
+ * is looked up with `findOne`, best-effort — a failed lookup falls back to the
+ * generic copy rather than blocking the delete.
+ *
+ * ## The result shape is the action runner's, on purpose
+ *
+ * `run` returns what a registered `delete` handler returns, because the console
+ * registers it as exactly that. The toasts here are the AUTHORITATIVE feedback,
+ * so every path returns WITHOUT an `error` key (and success returns `silent`) —
+ * otherwise the runner's post-execution hook, which has its own toast handler,
+ * would toast the same outcome a second time. The single exception is a
+ * request with no record id at all, which toasts nothing here and returns the
+ * `error` for the runner to report.
+ *
+ * Record ids are forwarded exactly as the caller supplied them; nothing here
+ * converts them.
+ */
+import type { ActionResult } from './ActionRunner.js';
+type Row = Record<string, unknown>;
+/** Translate a key — the host's `t`, injected so core takes no i18n dependency. */
+type Translate = (key: string, options?: Record<string, unknown>) => string;
+/** Everything `run` needs from its host. `confirmText` needs only the first two. */
+interface RecordDeleteDeps {
+    objectName: string;
+    t: Translate;
+    /** The object's display label, used by the toasts. */
+    label: string;
+    dataSource: {
+        delete(resource: string, id: string): Promise<unknown>;
+        findOne(resource: string, id: string): Promise<unknown>;
+    };
+    /** The host's toast sink (sonner's `toast` in both hosts today). */
+    toast: {
+        success(message: string): unknown;
+        error(message: string, data?: {
+            description?: string;
+        }): unknown;
+    };
+    /** Re-read the list after a delete. */
+    onRefresh?: () => void;
+}
+/**
+ * The request, in the action runner's `delete` shape — the console registers
+ * `run` as its `delete` handler, so the runner's action arrives here verbatim:
+ * `params.records` (several), `params.recordId` + optional `params.record`
+ * (one), and the legacy top-level `recordId`.
+ */
+interface RecordDeleteRequest {
+    params?: {
+        records?: unknown;
+        recordId?: unknown;
+        record?: Row | null;
+    };
+    recordId?: unknown;
+}
+/**
+ * The record-delete core: `confirmText` is the question to ask before deleting
+ * one record, `run` performs the delete (one record, or several settled
+ * together) and reports it. See the module docblock for objectui#10383 and
+ * ADR-0094.
+ */
+export declare const recordDelete: Readonly<{
+    /**
+     * The question to ask before deleting ONE record: the reset question for a
+     * package-owned permission set (ADR-0094), the plain delete question
+     * otherwise. Reads only the row it is handed — no lookup.
+     */
+    confirmText(deps: Pick<RecordDeleteDeps, "objectName" | "t">, record?: Row | null): string;
+    /**
+     * Delete, refresh and report. Several records (`params.records`, more than
+     * one with an `id`) are deleted one call each and settled together, then the
+     * list refreshes and ONE summary toast reports the batch. Otherwise one
+     * record is deleted; on success the list refreshes and a success toast shows
+     * (the reset copy for a package-owned permission set), on failure an error
+     * toast carries the error message and the list is left as it is.
+     */
+    run(deps: RecordDeleteDeps, request: RecordDeleteRequest): Promise<ActionResult>;
+}>;
+export {};