chore(dx): tighten feedback loop — root lint/test, husky gates, check.sh signal-to-noise

[nokternol]

Summary

• Root npm test composes both workspaces sequentially (apps/api then apps/web), each running their own vitest config — avoids the Vite 5/6 hoisting conflict introduced by the root-level @sveltejs/vite-plugin-svelte@^4 (Storybook constraint)
• Root npm run lint runs biome check . across all files from one place
• lint-staged runs biome check --write on staged files and auto-restages any safe fixes before the commit lands
• .husky/pre-commit now covers three gates: lint-staged → tsc (both workspaces) → vitest (both workspaces); each step captures output and only prints on failure — the failure message is the next action, no scrolling required
• check.sh rewritten: silent on pass, deferred failure detail printed at the bottom; summary line shows N passed, N failed at a glance
• apps/web/vitest.config.ts: import.meta.dirname for the $env/dynamic/public alias so the config is CWD-agnostic
• vitest added to root devDependencies explicitly rather than relying on workspace hoisting

Why not a vitest workspace config?

Attempted but blocked: sveltekit() plugin captures process.cwd() at module load time and overrides Vite's root. Running it from repo root causes Vite 5 (root) vs Vite 6 (apps/web) type conflicts that break tsc. Composing via npm scripts is simpler and avoids touching the Storybook-sensitive Vite version split.

Test plan

• npm test passes from repo root
• npm run lint passes from repo root
• Make a deliberate type error, attempt commit — pre-commit blocks with the tsc error printed directly
• Make a deliberate test failure, attempt commit — pre-commit blocks with vitest output
• Fix both, commit succeeds — only ✅ lines printed
• CI quality-gate passes on this PR

🤖 Generated with Claude Code