docs: point status and trust links at paradev.com

Merged
KI
7h ago
+90-86

Summary

The status page (incident.io) and trust center (Oneleet) moved to status.paradev.com and trust.paradev.com on Nov 1. The old superset.sh hosts 301 to the new ones (Cloudflare rules), so links still work, but:

  • https://status.superset.sh/proxy/status.superset.sh now returns {}, so the runbook's check command reads nothing. The incident-triage skill's summary.json URL goes through an extra redirect.
  • Two marketing pages (legal/security, the SOC 2 changelog post) link the old trust host.

COMPANY.STATUS_URL and COMPANY.TRUST_URL already build from ROOT_DOMAIN, so the footer, header, contact, pricing and enterprise links were already on paradev.com. This PR only fixes hard-coded links:

  • .agents/skills/incident-triage/SKILL.md: status host and summary.json URL.

  • docs/runbooks/incidents.md: heading, DNS row (new setup), JSON check command.

  • apps/marketing/content/legal/security.mdx, apps/marketing/content/changelog/2026-08-27-soc-2-type-ii.mdx: trust link.

  • plans/20261026-app-domain-move.md: status/trust rows now say 200.

  • Pricing and enterprise SOC 2 FAQ answers: no longer hard-code the host. Both use trustHost = new URL(COMPANY.TRUST_URL).host, like the contact page. The pricing FAQ gets it from faqValues next to its other placeholders (faqAnswer replaces a descriptor's own values, so a template literal would have rendered {trustHost}). The enterprise FAQ interpolates it in the message. All 17 catalogs keep their translations with {trustHost} in place of the host; check:i18n passes with nothing missing.

Hard-coded on purpose: Markdown/MDX (the skill, runbook, plan, and two marketing content pages), which can't read COMPANY.

Not changed: app-identity.test.ts (tests the superset.sh defaults when NEXT_PUBLIC_ROOT_DOMAIN is unset) and the old Boid plan.

Test plan

  • Preview: /pricing, /enterprise, /ja/pricing, /ja/enterprise show trust.paradev.com in the open FAQ answer and the FAQ JSON-LD; no {trustHost} anywhere in the HTML.
  • check:i18n, marketing tsc, biome, pricing and FAQ tests pass locally; all CI checks pass.
  • curl https://status.paradev.com/proxy/status.paradev.com and /api/v2/summary.json return the page JSON (200).
  • https://trust.paradev.com and https://status.paradev.com return 200; the old hosts 301 to them with path and query kept.
  • git grep finds no other hard-coded status/trust superset.sh links outside the test and old plans.

Summary by cubic

Points the status page and trust center links in the runbook, incident-triage skill, marketing pages, and the pricing and enterprise FAQ answers at their new paradev.com hosts.

The status page (incident.io) and trust center (Oneleet) now live on status.paradev.com and trust.paradev.com. The old superset.sh hosts 301 to them, but https://status.superset.sh/proxy/status.superset.sh now returns {}, so the runbook's check command and the incident-triage skill read nothing. Template-based links already build from ROOT_DOMAIN, so only hard-coded links were changed; app-identity.test.ts is untouched because it exercises the superset.sh defaults when ROOT_DOMAIN is unset.

  • The SOC 2 FAQ answers in pricing/constants.ts and EnterpriseFAQ/constants.ts now interpolate trustHost, built from COMPANY.TRUST_URL; all 17 locale catalogs use the {trustHost} placeholder with their translations kept, and check:i18n passes.

Summary by CodeRabbit

  • Documentation
    • Updated incident guidance and status-page checks to use status.paradev.com.
    • Updated security documentation and the SOC 2 report link to use trust.paradev.com.
  • Improvements
    • Security and SOC 2 links in enterprise and pricing FAQs now use the current trust-site domain across supported languages.