hyperflow-dispatch

# hyperflow-dispatch — execution phase (Antigravity single-agent) Execute the task file from `hyperflow-plan`. **No sub-agent dispatch and no model tiers in Antigravity** — you do each batch yourself, then self-review before committing. Follow the `hyperflow` doctrine. ## Per batch 1. **Implement** every sub-task in the batch (sequentially; they were planned as small, independent units). 2. **Self-review** the batch diff against the level checklist: - **L1** syntax/format/obvious bugs · **L2** spec compliance, naming, edge cases · **L3** cross-file integration + security (secrets, injection, validation). - Elevate to L3 when the change touches auth, data, or external input. Fix anything found before committing. 3. **Quality gates** on affected files: run the project's lint, typecheck, and tests. Fix failures (never `--no-verify`). 4. **Commit per sub-task** — one sub-task = one conventional commit (respect commitlint: lowercase subject, allowed scope). Stage only that sub-task's files; never commit files you didn't change. 5. **Update the task file's status block** (tick the sub-task, bump progress) and append any durable learning to `.hyperflow/memory/`. ## After all batches 6. **Final integration self-review** over the cumulative diff — catch cross-batch contradictions, scope leaks, and `any`/type regressions. 7. **End gate** via AskUserQuestion: offer to run `hyperflow-audit` (independent review) and/or `hyperflow-deploy`. Both are binary (no recommended marker)...