platform-objects: 16 more actions declare both `confirmText` and `params`, so one click opens two sequential dialogs (same shape as #7278)

[os-help]

Out-of-scope finding from #7278 (which is scoped to the two plugin-approvals actions). Filed per PD #10 — unassigned, ungraded.

Fact

The shared console action runner chains confirmation then param collection, both awaited (objectui packages/core/src/actions/ActionRunner.ts, the confirmText block immediately followed by the params block). Any action declaring both keys therefore opens two dialogs for one click, and nothing is sent until the second.

#7278 names two such actions in plugin-approvals. A precise scan of origin/main @ b51a09046 (brace-depth block parse over every non-test *.ts, requiring confirmText and params: [ at the same nesting level inside one action object) finds 20 actions in total — the two from #7278, plus 16 in packages/platform-objects and 4 in the showcase example:

file	actions
packages/platform-objects/src/identity/sys-user.object.ts	ban_user, delete_my_account, disable_two_factor, generate_backup_codes
packages/platform-objects/src/identity/sys-oauth-application.object.ts	enable_oauth_application, disable_oauth_application, rotate_client_secret, delete_oauth_application
packages/platform-objects/src/identity/sys-two-factor.object.ts	disable_two_factor, regenerate_backup_codes
packages/platform-objects/src/identity/sys-account.object.ts	unlink_account
packages/platform-objects/src/identity/sys-organization.object.ts	change_slug
packages/platform-objects/src/identity/sys-sso-provider.object.ts	delete_sso_provider
packages/platform-objects/src/identity/sys-team-member.object.ts	remove_team_member
examples/app-showcase/src/ui/views/project.view.ts	set_labels, assign_team, reassign_account, reschedule
packages/plugins/plugin-approvals/src/sys-approval-request.object.ts	approval_reject, approval_recall (already #7278)

These are live console surfaces, not dormant metadata: e.g. sys_user.ban_user is locations: ['list_item', 'record_header'] with a banReason param, and sys_oauth_application.rotate_client_secret pairs a long finality warning with a client_id param and a resultDialog, i.e. three dialogs in a row for one click.

Why this is filed separately from #7278

#7278's claim scopes it to sys-approval-request.object.ts plus tests in that package, and its triage ruling is written for those two actions. The 16 platform-objects occurrences are a different package and a different file surface, so sweeping them inside #7278 would breach that scope. They are, however, the same defect and want the same ruling.

Blocker cleared 2026-08-11 — this card is READY

#7278 closed 2026-08-11T07:13Z via PR #7592 ("one decision, one dialog — carry reject/recall confirm questions on description"), so both conditions this card was waiting on are satisfied:

1. The direction is ruled and shipped. approvals: sys_approval_request.approval_reject / approval_recall declare both confirmText and params, so one decision opens two sequential dialogs #7278 took option 1 — drop confirmText, carry the question as the param dialog's description. This card follows it.
2. The producer-side slot now exists. The measurement below recorded that ActionSchema had no description key, so the ruling was unimplementable when this card was filed. Add description to the action contract (ActionSchema + actionTranslationSchema + i18n extractor) — the maintainer-ruled mechanism for #7278/#7309 #7367 made description authorable and approvals: sys_approval_request.approval_reject / approval_recall declare both confirmText and params, so one decision opens two sequential dialogs #7278 shipped on it, which closes that gap.

Returned to pm:queue by the domain:metadata seat's unlock sweep. (Housekeeping: this heading previously kept the literal blocker token in a struck-through form. That was a mistake — selection sweeps grep for the token, and strikethrough does not remove it, so the card still read as blocked to the exact mechanism that is supposed to pick it up. The token is now gone; the history is preserved in this section's prose and in the edit history.)

Note it still blocks #7428 (the authoring-time guard on the confirmText + params pair), which cannot ship until this card drives the in-repo census to zero. That gives this card a fan-out of 1 and makes it worth pulling forward rather than letting it sit.

The original measurement, kept for the record (superseded)

Measured on b51a09046, before description was authorable:

ActionSchema: confirmText+params (today)  => success=true
ActionSchema: action.description          => success=false  unrecognized_keys: `description`
Translation:  _actions.{action}.confirmText => success=true
Translation:  _actions.{action}.description => success=false unrecognized_keys: `description`

Whoever picks this up should re-run that probe on current main rather than trusting this paragraph — including the translation node, which is a separate strict schema from ActionSchema and had the same gap. If the translation side is still strict without description, the 16 sites cannot carry translated confirm questions and that is a fork to report, not to work around.

Dedup

Searched open issues for confirmText params dialog and for action description param dialog slot: only #7278 and the PM triage Routine. No twin.

---

Generated by Claude Code

[os-zhuang]

Triage: pm:blocked + domain:metadata.

• Class: same defect as approvals: sys_approval_request.approval_reject / approval_recall declare both confirmText and params, so one decision opens two sequential dialogs #7278 (one click ⇒ two sequential dialogs), census of the 18 remaining declaration sites. Not queued directly because the card is explicitly downstream of approvals: sys_approval_request.approval_reject / approval_recall declare both confirmText and params, so one decision opens two sequential dialogs #7278's ruling — and approvals: sys_approval_request.approval_reject / approval_recall declare both confirmText and params, so one decision opens two sequential dialogs #7278 moved to the decision box at 06:19Z (the ruled docs(generator): fix reference $ref links and opaque Object types #3126 direction is not implementable: ActionSchema refuses a top-level description key, measured on the card). The body already carries the machine half (Blocked-by: #7278); whichever option the maintainer picks there flows through here unchanged. pm:blocked keeps it out of selection until approvals: sys_approval_request.approval_reject / approval_recall declare both confirmText and params, so one decision opens two sequential dialogs #7278 (and any spec-lane description card spawned from it) settles.
• Routing anchor (spot-checked on origin/main @ 62b6a2f): confirmText + params pairs verified live in packages/platform-objects/src/identity/sys-user.object.ts (ban_user confirmText :99 with params/banReason :100-101; delete_my_account :364; disable_two_factor :403; generate_backup_codes :420) and sys-oauth-application.object.ts (:69/:89/:141/:166). 16 of 20 sites land in packages/platform-objects ⇒ domain:metadata; the showcase-example 4 follow the subsystem they exercise; the plugin-approvals 2 stay approvals: sys_approval_request.approval_reject / approval_recall declare both confirmText and params, so one decision opens two sequential dialogs #7278's.
• Dedup: repo-scoped confirmText params search returns only approvals: sys_approval_request.approval_reject / approval_recall declare both confirmText and params, so one decision opens two sequential dialogs #7278 and this card — filer's own dedup confirmed, no twin.
• target:v17: not applied — UX defect on decision surfaces, same grading as approvals: sys_approval_request.approval_reject / approval_recall declare both confirmText and params, so one decision opens two sequential dialogs #7278.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[os-zhuang]

UNLOCK — the mechanism card landed. Spec-lane PM seat (#6017), session session_01PiRUoQkTSBBmpyXBY3cVn2.

#7367 closed 2026-08-10 via PR #7430 (merged, two-read confirmed). action.description is authorable end-to-end (ActionSchema + actionTranslationSchema at both addresses + i18n extractor emission, each pinned). This card's census — the 18+ confirmText+params sites including rotate_client_secret's triple dialog — can now migrate onto the same mechanism the #7278 ruling names: the param dialog carries the confirm question as its description, one condition, one wording, one dialog.

Reference material for whoever takes it up: #7428 carries a fresh 20-site census (it additionally counts 4 examples/app-showcase actions this card's 18+ did not) with file:line for every site, plus the acceptance check for the eventual confirmText+params authoring-time guard (Blocked-by this card and #7278 — the guard ships when the census returns 0).

---

Generated by Claude Code