Restore canonical GuardScope production domain

[Bukassi600104]

What changed

• replaced the stale security@guardscope.io security.txt contact with security@guardscope.app
• added a repository-wide regression test that rejects guardscope-update variants and the retired .io domain

Root cause

The application build was healthy, but the guardscope.app custom-domain alias had disappeared from the existing Vercel project. Vercel therefore returned 404 for every production route. The domain alias has been restored by a fresh production deployment.

Impact

The public website, health endpoint, privacy policy, terms, and security.txt are live again on the canonical domain. CI now prevents the invalid update/legacy domains from returning in tracked source.

Verification

• npm test in backend (39 passed)
• npm run build in backend
• npm test in extension (8 passed)
• npm run build in extension
• live HTTP 200 checks for /, /api/health, /privacy, and /terms

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
guard-scope	Ready	Preview	Aug 11, 2026 2:58pm