🔒 security(web): load headers from Vercel project root

[scttbnsn]

Summary

The browser-security policy merged in #138 was stored at the repository root, but the live Vercel project is configured with website as its Root Directory. The completed production deployment therefore ignored vercel.json, even though the static policy test passed.

This follow-up moves the policy into the deployed project root and changes the regression test to fail if it ever drifts outside that root again. It must land before the v1.4.3 tag is cut.

Changes

• require website/vercel.json in the security-header regression test
• relocate the existing catch-all CSP and hardening policy into the configured Vercel project root
• correct the path recorded in the security report

Verification

• Reproduced missing CSP and hardening headers on the completed production deployment
• Confirmed website is the Vercel project Root Directory
• Watched the new regression fail before the relocation
• Targeted security-header test passes after the relocation
• npm test: 89 tests passed
• npm run build: both workspaces passed
• Full pre-push gate passed: GoReleaser snapshot, Go lint, race tests, govulncheck, fuzz smoke, dependency dedupe, Knip, Biome, JavaScript tests, workspace build, and clean-tree

Release Gate

After merge, wait for the production Vercel deployment and verify the exact CSP and hardening headers on both / and /docs before cutting v1.4.3.

TDD Audit

Test commit	Impl commit	gate_status
da5f453 test(web): require headers in Vercel project root	5022419 security(web): load headers from deployment root	skill

Aggregate: 2 skill, 0 fallback, 0 exempt — 0 missing.

gate_status: skill=2, fallback=0, exempt=0, missing=0

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
sockguard-website	Ready	Preview, Comment	Jul 20, 2026 5:51pm

[coderabbitai]

Warning

Review limit reached

@scttbnsn, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7fcddb5b-c064-49d4-a061-ecc053f74c9f

📥 Commits

Reviewing files that changed from the base of the PR and between 41b7fe8 and 5022419.

📒 Files selected for processing (3)

• scripts/security-headers.test.mjs
• security_best_practices_report.md
• website/vercel.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/security-headers-vercel-root

---

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

_{Comment @coderabbitai help to get the list of available commands.}