Choose what happens next at a workflow decision

Output contract: Show governed artifacts, hashes, identity warnings, and the exact confirmation before recording any decision. For suggested actions, pair Shell with the returned Copilot command; honor commandGuidance. If absent, say "Copilot: no verified equivalent"; never invent a slash command.

Boundary: singularity-flow session current --json → ready/workId, cwd=repositoryPath; use CLI/workItemRoot paths; never $HOME.

Turn boundary — decision-only: singularity-flow decision choose, singularity-flow decision applicability, singularity-flow decision scope, singularity-flow decision completeness and singularity-flow decision plan are the only permitted mutations. Never edit files, run tests, builds, raw git, submit, approve, reject or next, or choose for the person. Any refusal ends this turn.

1. Run singularity-flow decision show <WORK-ID> --json. If pending is null and every applicability entry is satisfied, say the Story is not waiting for a decision, show ahead when present, and stop. If only applicability is open, go to step 6.
2. Show pending.label, why it waits (reason, round, maxRounds), who decides (by), values, and every option: id, label, toLabel, reach, skipLabels. With anyStep, a step ID or end may be named instead.
3. Ask the person to type the option ID, or a step, and a reason. Never supply, infer or default either.
4. Run singularity-flow decision choose <WORK-ID> --fetch --option <ID> --reason "<REASON>" --expected <pending.key>, or --to <STEP> in place of --option. The CLI checks the person's approval group and that the question has not changed.
5. Report the commit, route, skipped steps, authority group and next phase. Show Next in Copilot: /sf-next and stop.
6. For each applicability entry not satisfied, show responsibility, declaredReason and who decides (authority). Ask the person why it does not apply to this Story; never supply one. Run singularity-flow decision applicability <WORK-ID> --fetch --responsibility <RESPONSIBILITY> --reason "<REASON>", report the commit, and stop.
7. Scope statements: run singularity-flow evidence scope <WORK-ID> --json. For each unresolved item show id, text and sourceId; ask the person for a disposition (clauses for included or existing) and a reason, never supplying either. Run singularity-flow decision scope <WORK-ID> --fetch --item <ID> --as <DISPOSITION> [--clause <IDS>] --reason "<REASON>".
8. Completeness review, only when structurallyComplete is true: show inventorySha256 and ask the person to answer each article (completeness, ambiguity, consistency, verifiability, boundary-conditions, non-functional) as satisfied, exception or not-applicable, with what they assessed. Run singularity-flow decision completeness <WORK-ID> --fetch --confirm <inventorySha256> --article <ID>=<DECISION>... --reason "<REASON>". Say it records a review, never that the scope is correct.
9. Unplanned path: ask which row it belongs to, or its supporting class and why. Run singularity-flow decision plan <WORK-ID> --fetch --add-location <CLAUSE>=<PATH> --reason "<REASON>".