Separate Vitest and Playwright discovery so unit test runs never collect e2e specs #285
Description
Summary
frontend/src/App.jsx currently returns the maintenance page frontend/src/App.jlifrontend/src/App.jsx currently returns the maintenance page frontend/src/App.jlifrontend/src/App.jsx currently returns the maintenance page frontend/src/App.jlifrontend/src/A Why this matters
A good production app should degrade gracefully. If the contract API is degraded, users should still be able to understand the product, read status information, and access any functionality that does not require live contract interaction.
Proposed work
- Limit the maintenance gate to contract-dependent- Limit the maintenance gate to contract-dependent- Limit the maintenance gaks, status indicators, and any read-only cached surfaces available.
- Introduce route-level degraded states for feed, stats, and account-specific pages.
- Add clearer distinction between API outage, contract mismatch, and user connectivity problems.
Acceptance criteria
- Contract outages do not replace the entire application shell.
- Users still see branding, navigation, and context-specific fallback messaging.
- Different failure classes produce different user-facing messages.
- Tests cover route behavior when health checks fail.