test: add browser smoke coverage for dashboard

[Ciprian-LocalPulse]

Problem

The frontend workflow still treated type checking as build/test evidence. The dashboard now exposes provenance boundaries, but CI did not exercise the rendered UI in a browser or prove that a deployable artifact exists.

Change

• Add Vite as the frontend production build path.
• Replace the frontend test script with a Playwright-powered browser smoke script that serves dist, launches Chromium, mocks API responses, and exits cleanly.
• Cover rendered desktop and mobile provenance labels, fixture boundaries, publication origin labels, graph navigation, source navigation, and unavailable-API handling.
• Update the frontend workflow to install Chromium before browser smoke checks.
• Update README, changelog, and roadmap to describe the stronger frontend evidence without overstating deployment or scientific validation.

Verification

• npm --prefix apps/web run lint
• npm --prefix apps/web run build
• npm --prefix apps/web test
• python -m ruff check --no-cache .
• python -m pytest -p no:cacheprovider -q
• python scripts/audit_documentation.py --json
• git diff --check
• python -m compileall -q src

The browser smoke test uses mocked API responses and verifies product boundaries; it is not a full accessibility audit, visual regression suite, load test, or production deployment proof.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
openlongevity	Ready	Preview	Sep 23, 2026 2:29am UTC