simplify support priority levels

[ehfeng]

Summary

• Collapses P0/P1/P2/P3 into two levels: Priority (P0, P1) and Normal (P2, P3) on /info/support.
• Updates the priority levels table, response times table, and per-tier availability/response bullets to match.

Test plan

• Preview renders cleanly on Mintlify branch URL
• Tables align and copy reads naturally

---

Note

Low Risk
Documentation-only changes that rename and consolidate support severity levels; no runtime or data-handling impact.

Overview
Simplifies /info/support by collapsing the P0–P3 severity scheme into two levels: Priority (production blocked/impacted) and Normal (bugs/questions/requests).

Updates enterprise tier bullets (availability/response) and rewrites the priority/response-time tables to use the new two-level terminology across Standard, Premium, Platinum, and Platinum+.

^{Reviewed by Cursor Bugbot for commit c3ce62f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	May 14, 2026, 12:15 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[firetiger-agent]

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

Any PR that changes the kernel API. Monitor changes to API endpoints (packages/api/cmd/api/) and Temporal workflows (packages/api/lib/temporal) in the kernel repo

Reason: PR modifies documentation/support info content, not kernel API endpoints or Temporal workflows.

To monitor this PR anyway, reply with @firetiger monitor this.

[cursor]

Risk assessment: Low risk.

This PR only modifies info/support.mdx, simplifying public support-priority terminology and response-time tables. There are no application codepaths, shared systems, infrastructure, config, redirects, or prompt/instruction files changed. The main risk is that this is user-facing support/SLA copy, but the technical blast radius is limited to a single documentation page.

I found no existing approval on the PR and no CODEOWNERS file in the base or head revisions, so I’m approving.

  

_{Sent by Cursor Automation: Assign PR reviewers}