implement-tasklisted

# Implement task The "smallest change that satisfies the criteria" is the whole discipline. Every extra line is review surface, a merge risk, and a place for a defect. The project already has a way to do this; find it and extend it rather than inventing a parallel shape. ## When to use - An accepted assignment requires changes to code, config, tests, or docs. ## When not to use - Investigation-only work with no change: that is `investigate-issue`. - The criteria are not yet confirmed: run `accept-assignment` first. ## Inputs - The confirmed criteria and constraints from `accept-assignment`. - The project's conventions and check commands from `load-project-context`. - The relevant source, tests, and documentation. ## Procedure 1. **Orient before editing.** Find the code that already does the closest thing; read it and its tests. Match its structure, naming, and error handling instead of introducing a new style, and locate the project's build / test / lint / typecheck commands. 2. **Plan the smallest change.** Note the files you expect to touch. If the list grows past the accepted area, stop and re-check with `accept-assignment` or `raise-blocker`. 3. **Change one thing at a time.** Make the minimal edit that satisfies a criterion, and add a test alongside behavior when the project's pattern expects one. Do not fold in unrelated cleanups, renames, or formatting. 4. **Run the project's checks as you go.** Run the narrowest relevant check after ea