flow run: a declined confirmation stops the flow; --apply --yes confirms write steps

confirm() prints 'declined: <reason>' and exits 3 whenever the answer is no or nobody can answer (not a
terminal without --yes, serve without the owner's dialog), so no command reports success after declining.
flow run stops at such a step with 'step N declined: <reason>' (status declined), never ok. flow run
--apply --yes passes --yes to write steps only; --yes without --apply is refused. Pitfall 24.

skills/release-flows/SKILL.md

@@ -46,7 +46,11 @@ once (the second build step prints "prebuild skipped (already ran in this flow r
   changes. Show this output to the owner.
 - `--dry`: the plan only, nothing runs.
 - `--apply`: writes and shell steps run for real, **only after the owner agreed in chat**; each write command still
-  asks its own confirmation in the terminal. Never add `--yes` (flow validate refuses it).
+  asks its own confirmation in the terminal. Never add `--yes` to a step (flow validate refuses it).
+- `--apply --yes`: the owner's approval of every write step of this run (they get `--yes`; reads, waits and owner
+  steps do not). Only when the owner said so in chat for this run, e.g. a background run with a log where no terminal
+  can answer. Without `--yes` and without a terminal, a confirming command declines: the flow stops there with
+  "step N declined: not a terminal and no --yes ...", never "ok" (status `declined` in `--json` and the state file).
 - Owner steps never run in any mode: submit, release, phased release, rollout, sending review replies, price
   imports, inviting testers, Beta App Review, starting experiments, offer codes (AGENTS.md rule 1). They print as
   "YOUR CLICK" with the exact text, also when written as `run:`.