[samertall]

Why

The README documents publishing to GitHub Pages through .github/workflows/deploy.yml, but this workflow was missing. GitHub Pages is currently disabled, leaving the otherwise installable front-end MVP without a public demo URL.

What changes

• On every PR to main: run npm test and npm run build using Node.js 22.
• On pushes to main (or manual runs on main): build, upload dist/, then deploy the static artifact through the official GitHub Pages Actions.
• Restrict deployment to the default main branch and grant deployment credentials only to the deploy job.
• Keep existing local-only data semantics; no backend, analytics, API keys, or external service dependencies are introduced.

Validation

• GitHub Actions PR check passes (tests + build).
• Repository owner explicitly authorizes public GitHub Pages publishing.
• Owner selects Settings → Pages → Source: GitHub Actions.
• After merge, verify the published site is functional, its routes/assets work, and that it is clearly labeled a front-end MVP.

Publication is intentionally not enabled by creating this PR. This change is ready for review but should not be merged until the owner approves public deployment.

[coderabbitai]

Caution

Review failed

The pull request is closed.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[coldtea-pr-lens]

Note

The title starts with ci:, so PR Lens left this pull request undrawn. Comment @pr-lens draw to draw it

_{github.comment.notice: false in .github/pr-lens.yml turns this note off}