Cover the requested behavior with unit tests. Follow vitest-v5 (or the stack's test skill) and existing file conventions. Do not chase coverage percentage.
- Read neighboring tests and the test skill. Colocate
*.test.tsbeside the implementation. - Test the behavior that can fail: public API, error paths, and the regression this change needs.
- Mock only at documented boundaries. Prefer real types and factories the repo already uses.
- Run the focused file, then the package test script.
- Docs:
/w-docsif behavior or commands changed.
