mkautobuildlisted

<!-- Lifecycle canonical source: .claude/workflow.yaml — autobuild steps are Step 0–6 (distinct from the 7 lifecycle phases) --> # mk:autobuild — Autonomous Multi-Hour Build Orchestration Step-file workflow that runs the complete generator/evaluator harness pipeline as an autonomous build. Handles green-field product builds (planner stage → contract stage → evaluator loop → ship decision) with adaptive scaffolding density based on detected model tier. <!-- Note: autobuild pipeline stages are numbered Step 0–6 (see Workflow section below). --> <!-- "Stage" is used to name pipeline roles to avoid clashing with the 7 lifecycle phases. --> ## When to Use Activate when: - User runs `/mk:autobuild "build a X"` (or any green-field product description) - Existing kit detection routes a green-field "build me an app" intent here instead of `mk:cook` - A multi-hour autonomous build is requested with no manual handholding Skip when: - The task is a single feature, bug fix, or refactor → use `/mk:cook` instead - The task is a doc update → use the existing doc skills - The request is "explain X" or "review Y" → use the appropriate single-shot skill ## Hard Constraints 1. **Adaptive density** — picks scaffolding density via `mk:scale-routing` (or `density-select.sh`); honors `MEOWKIT_AUTOBUILD_MODE` env override 2. **Budget caps** — warns at $30 spent, requires explicit approval at $100, hard-blocks at user-set `--budget` value 3. **6-hour wall-clock timeout** — hard limit per Anthro