hunt-runlisted

<objective> Execute a hunt phase. Documented flags are available behaviors, not implied active behaviors. Treat `--wave N`, `--gaps-only`, and `--interactive` as active only when the literal token appears in `$ARGUMENTS`. If none of these tokens appear, run the standard full-phase execution flow. The execution boundary is the shared THRUNT runtime contract: - each material hunt action is shaped as a `QuerySpec` - connectors return one normalized result envelope - query logs and receipts are emitted from runtime metadata, not connector-specific ad hoc blobs - connector-backed execution can be inspected locally with `thrunt-tools runtime list-connectors`, `thrunt-tools runtime doctor`, `thrunt-tools runtime smoke`, `thrunt-tools pack render-targets`, and `thrunt-tools runtime execute` `--wave N` executes only a single wave and must not mark the whole phase complete until no incomplete plans remain. **Creates or updates:** - `.planning/QUERIES/*.md` - `.planning/RECEIPTS/*.md` - Phase `SUMMARY.md` - `.planning/STATE.md` - `.planning/HYPOTHESES.md` when new pivots emerge - `.planning/HUNTMAP.md` when phase status changes **After this command:** Run `/hunt-validate-findings <phase>`. </objective> <context> Available optional flags (documentation only): - `--wave N` — run only Wave `N` - `--gaps-only` — run only gap-closure plans - `--interactive` — stop after each wave for operator review Active flags must be derived from `$ARGUMENTS`. Do not infer that a flag is active jus