hunt-new-caselisted

<context> **Flags:** - `--auto` - Use the supplied signal brief as the starting point and ask only for missing critical facts. - `--pack <id>` - Bootstrap the case from a built-in or local hunt pack. Use `thrunt-tools pack bootstrap <id>` to inspect the generated mission, hypothesis, and phase seed content. </context> <objective> Initialize a threat hunting case. These hunt-native artifacts are the source of truth for the case. **Creates:** - `.planning/config.json` - `.planning/MISSION.md` - `.planning/HYPOTHESES.md` - `.planning/SUCCESS_CRITERIA.md` - `.planning/HUNTMAP.md` - `.planning/STATE.md` - `.planning/QUERIES/` - `.planning/RECEIPTS/` Bootstrap should only scaffold the case. Do not seed sample queries, sample receipts, or completed phases. Unknown scope details, data sources, operators, and constraints must remain `TBD` unless the operator confirms them. Confirmed bootstrap facts such as the case name, mode, opened date, and initial phase/status must be filled immediately. **After this command:** Run `/hunt-shape-hypothesis` or `/hunt-plan 1`. </objective> <execution_context> @.github/thrunt-god/workflows/hunt-bootstrap.md @.github/thrunt-god/templates/config.json @.github/thrunt-god/templates/mission.md @.github/thrunt-god/templates/hypotheses.md @.github/thrunt-god/templates/success-criteria.md @.github/thrunt-god/templates/huntmap.md @.github/thrunt-god/templates/hunt-state.md </execution_context> <process> Execute the bootstrap workflow from @.github/thru