@@ -10,7 +10,7 @@ Clause-②: no (narrowing) — `ActionIconPropsSchema` and the `action:group` /
 
 Metadata-protocol: narrowed (a page `action:icon`, and an `action:group` or `action:menu` member, may no longer declare `confirmText` beside a non-empty array `params`)
 
-<!-- adr-0087: not-required (no-migration-prescription) No key of any schema is added, removed or renamed: the icon row and the container member already declared both keys and keep them, and this adds the pair refusal the other three action doors carry. There is no rewrite that keeps what the author meant without reading it (the confirm sentence may or may not suit the param dialog's description line), so the author decides, and the refusal names the remedy. The in-repo census at the base found no shipped action:icon or container member carrying the pair; the one carrier was this package's own test fixture, repaired here. -->
+<!-- adr-0087: registered ui-page-action-row-confirm-text-beside-params-refused -->
 
 **BREAKING** accept-set narrowing at `ActionIconPropsSchema` and the `action:group` / `action:menu` member rows (`@objectstack/spec`), served where a page's component `properties` are judged: the component-props gate (`component-props-invalid`, `@objectstack/lint`) at every CLI command (`os validate`, `os compile`, the publish gate) and at the runtime `page` save door. `defineStack` does not parse a component's `properties` bag, so it does not refuse the pair.
 
@@ -19,4 +19,4 @@ Metadata-protocol: narrowed (a page `action:icon`, and an `action:group` or `act
 - **Unchanged.** `confirmText` with no `params`, beside `params: []`, or beside an object `params` (an icon's static parameter values; a `type: 'api'` member's request payload — neither opens a dialog) parses as before; so does an array `params` with `description`.
 - **Who sees it.** An author whose page declares an `action:icon`, or an `action:group` / `action:menu` member, with both keys. A stored page keeps loading and serving; its next save is refused, with the remedy in the finding.
 
-**The remedy.** Move the confirm sentence to the action's `description`, which the param dialog draws under its title, and drop `confirmText`. On an `action:icon` with no `label`, `description` is also the tooltip text.
+**The one-line fix: move the confirm sentence to the action's `description`, which the param dialog draws under its title, and drop `confirmText`.** `os migrate meta --from 17` lists the D3 entry `ui-page-action-row-confirm-text-beside-params-refused`, which names all four page action rows (`action:button`, `action:icon`, and each `action:group` / `action:menu` member) — the `action:button` refusal shipped earlier in 18.x is covered by the same entry. The rewrite is by hand, because whether the sentence reads as the dialog's description line is the author's call. On an `action:icon` with no `label`, `description` is also the tooltip text; give the icon a `label` to keep them apart.
@@ -0,0 +1,34 @@
+// Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.
+
+import type { SemanticMigration } from '../../types.js';
+
+export const entry: SemanticMigration = {
+  id: 'ui-page-action-row-confirm-text-beside-params-refused',
+  surface: 'the `confirmText` of a page action row beside a non-empty array `params`: `properties.confirmText` '
+    + 'beside a non-empty array `properties.params` on an `action:button` or `action:icon`, and `confirmText` '
+    + 'beside a non-empty array `params` on each `action:group` / `action:menu` member of `properties.actions`. '
+    + 'Not `params: []`, not an object `params` (an `action:button` / `action:icon` row\'s static parameter '
+    + 'values, a `type: \'api\'` member\'s request payload), and not a row with no `params`',
+  replacement: 'the confirm question on the row\'s `description`, which the param dialog draws under its title, '
+    + 'and no `confirmText`: one dialog that asks the question and collects the inputs. A row that collects '
+    + 'nothing keeps its `confirmText` and drops the `params`. ⛔ NOT mechanically convertible: whether the '
+    + 'confirm sentence reads as the param dialog\'s description line, or should be reworded, is the '
+    + 'author\'s call.',
+  reason:
+    'The console\'s action runner awaits the confirm dialog and only then opens the param dialog for an array '
+    + '`params`, and all four rows forward both keys to it (an array `params` as `actionParams`), so a row '
+    + 'carrying both showed the user TWO dialogs for one decision: a confirm that already read as "the action '
+    + 'ran" while nothing had been sent, then the param prompt. `ActionSchema` and `InlineActionSchema` already '
+    + 'refuse the pair; the four page rows now carry that rule with the same predicate and the same refusal '
+    + 'text. On an `action:icon` with no `label`, `description` is also the tooltip text, so moving the '
+    + 'question there changes the hover text too; give the icon a `label` to keep them apart. A page\'s '
+    + '`properties` is not parsed on the metadata load path, so a stored page keeps loading; `os validate`\'s '
+    + 'props gate, which the metadata save door also runs on the next save of the page, parses it against '
+    + 'these same rows and reports the refusal at the row\'s `confirmText`. Measured producers: none shipped '
+    + 'in this repository; the one carrier was a spec test fixture, respelled.',
+  acceptanceCriteria:
+    'No `action:button` / `action:icon` `properties` and no `action:group` / `action:menu` member declares '
+    + '`confirmText` beside a non-empty array `params`; `os validate` reports no `component-props-invalid` '
+    + 'finding at `properties.confirmText` or `properties.actions.N.confirmText` for the pair, and every row '
+    + 'with no `params`, `params: []` or an object `params` parses as before.',
+};
@@ -2,23 +2,28 @@
 
 /**
  * `confirmText` beside a non-empty `params`: TWO sequential dialogs for ONE
- * decision. ONE predicate and ONE refusal, read by the three doors that refuse
+ * decision. ONE predicate and ONE refusal, read by the five doors that refuse
  * the pair: `ActionSchema` and `InlineActionSchema` (`action.zod.ts`), and the
- * page `action:button` row, `ActionButtonPropsSchema` (`component.zod.ts`).
- * Pinned in `action-confirm-params-guard.test.ts`, which asserts the three
+ * page action rows in `component.zod.ts` — `action:button`
+ * (`ActionButtonPropsSchema`), `action:icon` (`ActionIconPropsSchema`) and each
+ * `action:group` / `action:menu` member. Pinned in
+ * `action-confirm-params-guard.test.ts`, which asserts the five doors'
  * messages equal.
  *
  * The console action runner awaits the confirm, THEN the param prompt (objectui
  * `packages/core/src/actions/ActionRunner.ts`), so the first dialog already
  * reads as "the action ran" while nothing has been sent. The `element:button`
  * renderer hands an inline action to that same runner, and the `action:button`
- * block forwards its row's `confirmText` and an array `params` (as
- * `actionParams`) to it too, so the pair opens the same two dialogs on all
- * three doors.
+ * and `action:icon` blocks forward their row's `confirmText` and an array
+ * `params` (as `actionParams`) to it too, as the `action:group` /
+ * `action:menu` containers do for each member, so the pair opens the same two
+ * dialogs on all five doors.
  *
  * An empty `params` collects nothing and opens no second dialog, so it is not
- * the pair. Nor is an object-form `params`: on an `action:button` row an object
- * is the static parameter values, which open no dialog, and the
+ * the pair. Nor is an object-form `params`: on an `action:button` /
+ * `action:icon` row an object is the static parameter values, and on a
+ * `type: 'api'` container member the request payload; neither opens a
+ * dialog, and the
  * `Array.isArray` read below leaves it alone.
  *
  * Lives in its own module, not in `action.zod.ts`, so `component.zod.ts` can