work-testlisted

# Work / 4. Test Write meaningful tests for behavior the product genuinely promises or currently depends on. Read [../QUALITY.md](../QUALITY.md#meaningful-testing) before acting; its testing standard is binding. Work directly in the parent conversation. Do not spawn agents or register a goal unless the user explicitly asks. Testing is implementation work: inspect first, show the plan, make the smallest justified edits, run the tests, and report the evidence. ## Inspect before writing Read the applicable project instructions, repository status and diff, implementation, existing tests and helpers, public APIs, consumers, and actual user flows. Identify the behavior users or current callers rely on. Do not invent requirements, hypothetical threats, or unrealistic edge cases. If the user did not name a target, choose the smallest coherent feature or current change that can be understood and tested safely. State the scope. If no meaningful behavior is worth testing, stop and explain why; never add a test only to increase coverage. ## Publish the test plan Before editing, provide one entry per justified behavior in this exact format: 1. **Behavior being protected** 2. **Why it matters** 3. **Test level:** unit, integration, or end-to-end 4. **Exact observable assertion** Keep the plan short. Prefer a small number of high-value tests in this order: 1. Core happy paths. 2. Realistic failure paths. 3. Important boundaries. 4. Previously broken behavior. 5. Data persistence,