fix: Return to the previous prompt when one is dismissed

[razor-x]

Summary

Dismissing a prompt ended the whole command. Escaping out of a single mistyped or misread answer — picking the wrong connected account for connected_account_id, say — threw away every parameter gathered so far and exited.

Now a dismissal abandons that one answer and returns to the step before it, and the prompt says so:

◆  [/devices/get] Parameters · Esc: go back
│  Search:
│  ● device_id [device1]
│    name
│    [Back]
│  ↑/↓ to select • Enter: confirm • Type: to search
└

Implementation

No new machinery. The prompts already reported a dismissal as PromptCancelledError; the only place it was handled was the top-level catch in src/bin/cli.ts, which ends the command. Each step of a flow now catches it and returns to the step before.

Escape and ctrl-c are treated identically — neither is special-cased, and nothing inspects which key was pressed.

The hint comes from one small helper, withBackHint in src/lib/util/prompt.ts, applied to the message of each prompt whose caller catches the dismissal — and only those, so it never promises a way back that does not exist. It goes on the message because clack builds its keyboard hint line from a hardcoded list: autocomplete has no option for it at all (@clack/prompts/dist/index.mjs:191-195), and showInstructions on select/multiselect only toggles the stock text on or off. Making that line itself customizable needs an upstream change to clack, worth a separate PR.

Behavior

Where you dismiss	What happens	Hinted
A parameter's value prompt (text, number, enum, list, resource picker, timestamp)	Back to the parameter menu, parameter left as it was	Yes
The parameter menu	Leaves the command, same as its [Back] entry	Yes
A sub-object's menu	Back to the parent menu, same as its [Back] entry	Yes
The list or metadata editor's action menu	Finishes editing, keeping changes so far	Yes
A prompt inside those editors	Back to the editor's action menu	Yes
A sub-command menu	Up one level	Yes
The top-level command menu	Stops the CLI, as before	No
Login, workspace and server selection, action attempt polling	Stops the CLI, as before	No

A dismissal with no step to go back to still stops the CLI with Cancelled and exit code 1, exactly as before.

Note on exiting

With ctrl-c now going back a level, leaving a deep flow in one keystroke is worth a follow-up. ctrl-d looks like it exits, but only by accident: it closes clack's readline, the prompt promise never settles, and Node bails with exit code 13 and an unsettled-promise warning, so no error handling or message runs. Verified in a pty. Happy to make that a clean exit separately — it needs care not to leave the terminal in raw mode.

Testing

• src/lib/interact-for-blueprint-object.test.ts — dismissing the parameter menu leaves the command; dismissing a value prompt returns to the menu with the parameter unset; a previously supplied value survives a dismissal; the menu and value prompts carry the hint.
• src/lib/interact-for-command-selection.test.ts — a sub-command menu is hinted, the top-level menu is not.
• The prompt mocks in those tests and in interact-for-custom-metadata.test.ts now replace only the prompts, so the real PromptCancelledError and withBackHint are exercised.
• Rendered frame checked against real clack output, and the flows checked in a pty.

Full suite green: 181 tests across 18 files, plus typecheck, lint, and formatting.