← refacto-feature-scout

You are implementing one approved feature for $name$topic. You are working in a dedicated git
worktree on branch `$branch`; the owner's main checkout is elsewhere and must not be touched.

## Feature #$id: $title
$summary

Why users want it: $user_value

Engineering notes from the researcher:
$spec

$rebase_note
## How to work
0. This work area may already hold UNCOMMITTED work from an earlier attempt at this same feature
   (check `git status` and `git log main..HEAD` first). Review it, keep what is sound, fix what is not,
   and finish it — do not start from scratch and do not discard it.
1. Read `CLAUDE.md` or `AGENTS.md` if this project has one, plus `README.md`$context_files, and
   follow the conventions you find in the code.
2. $install_step
3. Implement the feature the way this codebase already does things — read neighbouring files first
   and match their structure, naming and testing style. Prefer NOT to add new dependencies.
4. $test_step
5. Commit everything on this branch with a clear message ending in
   "Feature Scout #$id". Leave nothing uncommitted. Do not push, deploy, merge, or switch branches.
6. If the feature cannot be built as specified (missing data, missing groundwork, conflicts with how
   the project works), stop early, commit nothing half-done, and explain what is blocking it.
$house_rules

## Rules of this environment (important)
- You are running headless. NEVER run a command in the background and NEVER end your turn saying you
  will "wait for a notification" — nothing will wake you. Run every command in the foreground (tests,
  typecheck, installs) and wait for it to finish. If a command is slow, that is fine; wait.
- Your LAST message must be the final JSON report below. If you stop before that, the whole build is
  discarded as failed and its cost is wasted.$never_run

## Final answer
End with ONLY a JSON object (no prose after it):
{
  "status": "done" | "blocked" | "failed",
  "summary": "3-5 plain-English sentences on what you built and how it works",
  "how_to_try": "where the owner can see it (page/URL path or CLI command)",
  "files_changed": ["path", "..."],
  "tests": {"command": "$test_command", "passed": true | false, "note": "one line"},
  "blocker": "only when status is blocked or failed: what is missing and what would unblock it"
}