hopper-resultlisted

# Hopper Result Print the closed result for a background-dispatched Hopper task. The CLI reads `.hopper/handoffs/<task-id>-output.md` and may return parser-designated output from its guarded sidecar. ## Steps 1. Locate the target project root containing `.hopper/`, then locate `hopper-dispatch` from `PATH` or the plugin root near this `SKILL.md`. 2. Validate the task ID with `^[A-Za-z][A-Za-z0-9._-]{0,99}$`; reject slashes, `..`, whitespace, quotes, shell metacharacters, and newlines. 3. Run `hopper-dispatch --result <task-id>`. 4. Surface the CLI output, including closed status, vendor, diagnostic, recovered-output advisory, and parser-designated output when `--full` is used. 5. If the task is still `in-progress`, tell the user to use `hopper-dispatch --watch <task-id>` or `hopper-dispatch --progress <task-id>`. ## Failed task handling `failed` remains a failure even when Hopper safely retains parser-designated text. Do not report the task as successful or close it automatically. - `verified-complete`: the parser observed a terminal marker. Read the safe text with `hopper-dispatch --result <task-id> --full`, assess it manually, and make any follow-up dispatch a separate explicit task. - `unknown-completeness`: the safe text may be partial. Read it only as advisory and independently verify findings before acting or closing work. - `no-text`: no safe parser-designated text was recovered. Use the public adapter diagnostic to troubleshoot, then create and dispatch a separa