Features/GitHub fixes

[NickTheDevOpsGuy]

Description

Brief description of what this PR does and why.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement

Testing

• I have tested these changes locally
• I have tested these changes in multiple browsers/environments if applicable
• npm run test (unit tests) passes
• npm run build succeeds
• If UI/routing changed: tested PWA install/update (or noted N/A)
• If Stats/mobile/layout changed: quick manual check on real device

Checklist

• My code follows the project's coding standards
• I have performed a self-review of my code
• I have commented my code where necessary
• My changes generate no new warnings or errors
• I have updated documentation (e.g. README) if needed

How to Test

1. Check out this branch
2. Run npm install
3. Run npm run test (unit tests)
4. Run npm run build
5. Run npm run dev or npm run dev:host
6. Test on both mobile and desktop
7. (Optional) Run npm run test:e2e after npx playwright install
8. (Optional) For PWA: run npm run preview and use Install / Add to Home Screen

Screenshots (if applicable)

Release Notes

For user-facing changes, copy relevant sections from CHANGELOG_UPDATE.md into the PR description or release notes.

Additional Notes

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
phuzzle	Ready	Preview, Comment	May 27, 2026 11:27am

[hannahro15]

Lgtm

[hannahro15]

Lgtm