feat: redesign public status page

[masterfung]

Summary

• replace the generic dark Upptime shell with the approved responsive Mighty cream/yellow design
• explain in one sentence that Mighty detects manipulated documents and media before lenders fund loans or insurers pay claims
• add accurate search, social, structured-data, sitemap, robots, and AI-readable discovery metadata
• emit direct HTTP-200 service-history routes with unique titles/canonicals so response-time charts work on direct links
• preserve keyboard access to time-range controls and use a high-contrast focus indicator
• brand the web manifest, icons, theme color, and social preview consistently
• align hosting/launch docs with the live GitHub Pages + Cloudflare DNS-only topology

Status-page risk

• This change does not make a new SLA, compliance, or availability claim.
• Public text contains no customer data, secrets, or exploitable details.
• Monitor/component changes were tested from outside the Mighty stack.
• Workflow actions remain pinned to full commit SHAs.
• ruby scripts/validate.rb passes.

Validation

• ruby scripts/validate.rb
• actionlint
• zizmor --min-severity high .github/workflows/
• git diff --check
• clean pinned Upptime v1.17.0 install, patch, and static export
• verified /history/website/, /history/api/, and /history/scan-gateway/ return 200 locally and render charts
• desktop and narrow responsive screenshot review
• generated metadata, branded manifest/icons, sitemap, and keyboard-focus CSS inspection

Deployment and rollback

After merge, manually run Static Site CI and verify the homepage, assets,
metadata, and all three direct history routes on https://status.trymighty.ai.
The workflow publishes only the generated static site; monitoring behavior and
production endpoints are unchanged. Roll back by reverting this PR and running
Static Site CI again.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is enabled.}