Practical Application

For each implementation issue:

1. Identify one concrete behavior from the issue.
2. Write a test that fails because that behavior is absent.
3. Run the test and confirm the failure is meaningful.
4. Implement only enough code to make the test pass.
5. Repeat for the next behavior.
6. Run the relevant service or module tests.
7. Run the full test suite and type checker required by the repository.
8. Fix every failure before committing.
9. Include the checks and their results in the completion summary.

Review the tests before reviewing the implementation. The tests reveal what the agent believed the task meant. If the tests assert the wrong behavior, green output does not establish correctness.

Use TDD most aggressively where the behavior can be expressed through stable module interfaces. Service logic and data transformations are well suited to this. Front-end appearance is harder to capture with the same confidence and requires additional human inspection.