ci: web Playwright E2E tests are not executed in CI pipeline

[jongio]

Summary

The Playwright E2E test suite in web/tests/ contains 8 spec files covering homepage, getting-started, examples, security, CLI reference, changelog, navigation, and accessibility. However, the website.yml CI workflow only builds and deploys the site — it never runs these tests.

Impact

• Regressions in page content, navigation, or accessibility can reach production undetected
• The existing test investment provides no automated safety net
• Contributors may unknowingly break pages without feedback

Current State

Tests that exist but are never run in CI:

Test File	Coverage
homepage.spec.ts	Main landing page
getting-started.spec.ts	Getting started guide
examples.spec.ts	Code examples page
security.spec.ts	Security guidelines
cli-reference.spec.ts	CLI reference docs
changelog.spec.ts	Changelog page
navigation.spec.ts	Cross-page navigation
accessibility.spec.ts	WCAG AA compliance

Playwright config is already set up with multi-browser support (Chromium, Firefox, WebKit) and mobile viewports (Pixel 5, iPhone 12).

Recommendation

Add a test step to the website.yml workflow (or a dedicated web-test workflow) that:

1. Installs dependencies with pnpm install
2. Installs Playwright browsers with pnpm exec playwright install --with-deps
3. Runs pnpm test:web after the build step
4. Gates PR merges on test success
5. Uploads Playwright HTML report as a workflow artifact on failure

This can run on ubuntu-latest and should execute on pull requests that modify files under web/.