f782c51c18
A human stage parks its run on a person, and the terminal client could answer it while the app had no decide request at all. This adds the missing piece so a waiting run is answerable from the phone. Protocol/repo: - PipelinesRepository.decideRun sends the same `decide_run` request the CLI and TUI build: stage (optional; the server infers it), option, optional feedback, with the exact wire names internal/protocol/message.go declares. Message gains the stage/option/feedback fields; no second mechanism is invented. - A waiting run/step now forces the existing push-driven full get_run (runDetailNeedsFullSync), so the waiting step's recorded options/prompt surface live with no refresh and no server field added. - RunState.Waiting (label "waiting", FrontHand glyph, violet palette entry) makes the waiting state honest in the list and summary. UI: - DecisionPrompt is the one shared surface: a "Waiting for your decision" card with a deliberate Decide action, plus the sheet showing the run and waiting stage, the author's instructions, every option as written with the label it routes to, an optional feedback field, and a Confirm decision button that is disabled until an option is chosen. It sits above the run detail's tabs and at the top of the waiting stage's pane, reachable from where the operator already is. - Answering applies the returned run detail immediately, so the new stage shows without a manual refresh. A refusal keeps the sheet open with the server's own message verbatim and silently re-reads the run rather than faking success. - Pure helpers pendingDecision, DecisionOption, DecisionDraft (the confirm gate) and decisionRefusalMessage; Tests: HumanDecisionTest and DecisionTest (13 new) plus waiting cases in RunEventsTest and RunStatusTest. Scope: android/ only. No server/Go/installer/Docker change, no new dependency (the glyph is from the already-declared material-icons-extended), no run started from the app, no adb or device use. Reflected where it belongs: android/README.md gained the dated feature section for this change. Checked and needing no update: the packaged pipeline templates (the change touches no pipeline definition), the repository's top-level README and docs/ topic docs (none enumerates the app's operations or the decide protocol; the TUI/CLI wording they carry is unchanged), and the packaged authoring skill references (the decide protocol is unchanged and already documented; no reference describes this app surface).