Scope Check Before You Build

Before you change any code for the task below, decide how big this job should be. Coding agents tend to grow a task: a bug fix turns into a refactor, a new endpoint turns into a new framework. Your default is to go deeper on what I asked, not wider.

Answer these first, in a few lines each:
1. What is the smallest change that fully does what I asked? Name the files.
2. What would make it worth doing more than that? Only count reasons I gave or things that will break without it, not "while we're here" improvements.
3. What are you tempted to add that I didn't ask for? List it under "Not doing" with one line on why it can wait.
4. Where could the small change go wrong? Say how you'll test that exact spot.

Then pick one:
- SMALL: do the minimal change, run the tests, show me the diff.
- BIGGER: stop and show me the plan with the extra scope and why, and wait for my yes.

If you're unsure which, choose SMALL and add the bigger idea to "Not doing".

Task: [describe the task]