Lighthouse perf budget CI FIXED

[stpatrickghost]

Add Lighthouse CI with Budget Enforcement

What it does:
Adds automated performance, accessibility, best-practices, and SEO auditing to every pull request via Lighthouse CI, with enforced score budgets and PR comments.

Files Changed
.github/workflows/lighthouse.yml
lighthouserc.json

Closes #72

[vercel]

@stpatrickghost is attempting to deploy a commit to the truthixify's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@stpatrickghost Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[truthixify]

Merge is clean. One blocker: drop package-lock.json (25,919 lines npm lockfile). This repo uses pnpm.

rm package-lock.json
git add -u
git commit --amend
git push --force-with-lease

Lighthouse config + workflow are good as-is. After the lockfile is gone I will merge.

[truthixify]

Almost there. The Lighthouse workflow + budget config look right and test-merge cleanly. But the 25919-line package-lock.json is still in the PR. This repo uses pnpm.

rm package-lock.json
git add -u
git commit --amend --no-edit
git push --force-with-lease

Then I will merge.

[truthixify]

The 25919-line package-lock.json is still in the PR. The Lighthouse work itself test-merges cleanly, so this is the only blocker. From the repo root:

rm package-lock.json
git add package-lock.json
git commit -m "drop npm lockfile"
git push

(or amend the existing commit if you prefer). Then I will merge.