hopper-dispatchlisted

# Hopper Dispatch Dispatch exactly one Hopper task unless the user explicitly provides multiple task IDs. ## Before dispatching: is this a dispatch at all **Hopper is accountable for a result; it is not a place to run a process you need to steer.** Two questions, both must pass: 1. **Could you compute the one correct answer yourself?** If yes, do it yourself — a determinate query (source summary, commit log, version lookup) costs minutes and dollars through a dispatch and comes back less reliable. 2. **Can you state the whole question now?** If no, it is exploratory; a single-spawn, no-retry dispatch gives you no way to steer, and a follow-up is a whole new dispatch. Then: **is independence the point** — is the value in an answer that does not share your context and priors? Judge by the DELIVERABLE, not the topic: a review reads source as its *method* and returns a judgment (dispatch); "summarize this module" reads source and returns *data* (do it yourself). A request with no matching task-type is answered by that absence — see `docs/WHEN-TO-USE.md`, or `hopper-dispatch --task-types` for the per-type for/not-for note. ## Steps 1. Locate the target project root: use the current directory when it contains `.hopper/`; otherwise walk upward. If no `.hopper/` exists, ask for the project root or `HOPPER_DIR`. 2. Locate the CLI: prefer `hopper-dispatch` on `PATH`; otherwise search upward from this `SKILL.md` for `cli/bin/hopper-dispatch` and run it with `node`. 3. Validate t