Test strategy

Vitest is configured at the workspace level. Tests should stay close to the code under __tests__/.

Expected proof:

• router and filter-query: behavioral and contract-oriented tests;
• helper/config packages: focused unit tests around public helpers and config contracts;
• UI packages: targeted behavior tests for stable public components, not broad snapshots;
• build scripts and smoke builds: useful extra verification, not substitutes for behavioral public API tests.

Add or update tests when public behavior, route/query/filter behavior, config output, or bug fixes change.