hunt

Prepare a work order for `$CLAUDE_PROJECT_DIR`. Propose, never impose: the punch list changes only on an explicit yes. If `.nightshift/` does not exist, stop and point to `/nightshift:setup` first. ## 1. Offer the jobs Present the three presets from `${CLAUDE_PLUGIN_ROOT}/skills/nightshift/references/walkthrough-item.md`, one line each, and ask which one — and how many hours it gets (every preset is open-ended; the hours are its only cost cap): - **Coverage hunt** — meaningful tests until the whistle. - **Defect hunt** — review → fix until a full pass finds nothing new, or the whistle. - **Standing loop** — improve and discover; only the clock ends it. ## 2. Write the work order Append the chosen preset and its hours to `.nightshift/work-orders.md` — hunt's own file; the drafting table stays the owner's room. Never clobber orders already sitting there — append below them: ```text ## Work order — <ISO date time> Hours: <N> - [ ] **<the preset item, verbatim>** ... ``` The hours are inert while the order sits here — the clock starts only at the cut. ## 3. Ask: start now? One question. On **yes**: - **clear every stale run-control marker first** — remove them all if present: `.nightshift/STOP`, `.nightshift/.stall`, `.nightshift/.notified`, `.nightshift/.ended`, `.nightshift/deadline`, `.nightshift/.session-end`, `.nightshift/.shift-session`, and `.nightshift/.watchman-tick`; if `.nightshift/.watchman` holds a live pid, kill it first. The two commonest endin...