dispatch-task-completelisted

# dispatch-task-complete Close a VantagePeers task safely. Wraps `mcp__vantage-peers__complete_task` and `mcp__vantage-peers__update_task` with auto-assembly of a `completionNote` containing at least one proof token (commit SHA, PR#, VP id, test ratio, artifact path, URL). The Day 76 Evidence-Bound Done hook (`enforce-evidence-bound-completion.py`) rejects claim-only notes — this skill ensures every close ships with a verifiable jeton de preuve. ## When to use - User says: "complete task <id>", "mark done", "close <id>", "finish task", "task done", "wrap up task". - You finished work tracked by a VP task and need to move it to `done` or `review`. - You want to chain a `[DONE]` notification to the creator with the same proof tokens. ## When NOT to use - Task is blocked — use `block_task` instead. - Task hasn't been started — use `start_task` first. - You have zero evidence and refuse to fabricate any — stop and surface the gap to the user. ## Inputs - `taskId` (required) — Convex id, format `k[a-z0-9]{32}`. - `intent` (optional, default `done`) — one of `done` | `review`. - `summary` (optional) �� one-sentence description of what was accomplished. If omitted, the skill drafts one from recent context. - `extraProof` (optional) — proof tokens the user wants to force-include (URL, SHA, PR#, ratio, path). ## Workflow ### 1. Resolve taskId + intent If the user said "close k7abc..." extract the id verbatim. If they said "close the auth task" and only one in-flight task mat