feat(site): support policy page

[mhartington]

Summary by CodeRabbit

• New Features

  • Added a Support Policy page with hero/CTAs, support channels table, response times, business hours, severity level definitions, and public holidays.
  • Added structured support-policy data used by the page.

• Chores

  • Configured permanent URL redirects to improve navigation for legacy paths.

• Style

  • Adjusted vertical spacing on the Terms page layout.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Apr 2, 2026 1:58pm
docs	Ready	Preview, Comment	Apr 2, 2026 1:58pm
eclipse	Ready	Preview, Comment	Apr 2, 2026 1:58pm
site	Ready	Preview, Comment	Apr 2, 2026 1:58pm

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

Adds a new Support Policy page and accompanying typed data module, updates vertical spacing on the Terms page, and adds a Vercel redirects configuration for the site application.

Changes

Cohort / File(s)	Summary
Support Policy Page apps/site/src/app/support-policy/page.tsx	New Next.js route exporting metadata and default SupportPolicyPage component. Renders hero with CTAs and multiple content sections; table-driven rendering for support channels, response times, and severity levels. Includes local helper SupportPolicyTableCheck for accessible "Yes"/"-" cells.
Support Policy Data apps/site/src/data/support-policy.ts	New TypeScript module exporting typed data: SupportChannel, ResponseTime, SeverityLevel types and corresponding arrays supportChannels, responseTimes, severityLevels, plus publicHolidays.
Existing Page Styling apps/site/src/app/terms/page.tsx	Minor layout change: added Tailwind class my-24 to the Terms page hero container (vertical spacing adjustment).
Vercel Redirect Configuration apps/site/vercel.json	New Vercel config file adding permanent redirects (multiple legacy paths to /, one to /postgres, and one external redirect to docs).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat(site): support policy page' directly and clearly describes the main change: adding a new support policy page feature to the site.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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 and usage tips.}

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	Apr 2, 2026, 2:05 PM

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

apps/site/src/app/support-policy/page.tsx (1)

4-96: Consider extracting data arrays to a dedicated data file.

The terms page follows a pattern of separating content data into @/data/terms. For consistency and easier content management, you could move these arrays to @/data/support-policy.ts. That said, co-locating them here works fine for a single-page use case.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@apps/site/src/app/support-policy/page.tsx` around lines 4 - 96, Move the
inline data arrays (supportChannels, responseTimes, severityLevels,
publicHolidays) out of page.tsx into a new module (e.g., export them from a new
"@/data/support-policy.ts") and replace the local declarations with imports in
page.tsx; ensure you export each array by name from the new file and update any
references in page.tsx to use the imported symbols so the page continues to
render unchanged.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/site/src/app/support-policy/page.tsx`:
- Line 183: The Discord link uses an insecure http URL; update the anchor for
"Discord" (the <a href="http://pris.ly/discord">Discord</a> instance) to use
https by changing the href to "https://pris.ly/discord" so the external link is
requested over TLS.

---

Nitpick comments:
In `@apps/site/src/app/support-policy/page.tsx`:
- Around line 4-96: Move the inline data arrays (supportChannels, responseTimes,
severityLevels, publicHolidays) out of page.tsx into a new module (e.g., export
them from a new "@/data/support-policy.ts") and replace the local declarations
with imports in page.tsx; ensure you export each array by name from the new file
and update any references in page.tsx to use the imported symbols so the page
continues to render unchanged.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b65c39d3-cab6-489d-b635-1043c9de815b

📥 Commits

Reviewing files that changed from the base of the PR and between 07457e0 and 79f71cd.

📒 Files selected for processing (3)

• apps/site/src/app/support-policy/page.tsx
• apps/site/src/app/terms/page.tsx
• apps/site/vercel.json