bts-implementlisted

# Implementation: final.md → Working Code Implement the spec for recipe: $ARGUMENTS ## Settings Read `.bts/config/settings.yaml` for project-specific limits. Use settings values if present, otherwise use defaults noted in each step. ## Prerequisites 0. **Resolve recipe ID**: If `$ARGUMENTS` is empty or not a recipe ID, run `bts recipe status` to find the active recipe. Use its ID for all `{id}` references below. If no active recipe → "No active recipe. Run /recipe blueprint first." 1. Verify final.md exists: ```bash ls .bts/specs/recipes/{id}/final.md ``` If not found → "Run /recipe blueprint first." 2. Verify spec quality gate: - Check `verify-log.jsonl` exists and last entry has critical=0, major=0, minor_resolvable=0 (status "converged" — same bar the stop hook applied at `<bts>DONE</bts>`; minor_deferred may be > 0) - If verify-log is missing or the bar is not met → "Spec not verified. Run /recipe blueprint to complete verification before implementing." - This prevents implementing from unverified or manually-created specs. 3. Check recipe phase: ```bash bts recipe status ``` - If phase is "finalize" → fresh start, go to Step 1 - If phase is "implement" → resume from tasks.json (Step 3) - If phase is "test" → smart resume based on artifacts. Code simulation is detected by a `simulations/*-code.md` file (the code-mode output), NOT by the simulations/ directory existing — document-mode simula