docs(compute): remove beta label from rivet compute

[abcxff]

No description provided.

[abcxff]

Stack for rivet-dev/rivet

• #5413 feat(cli): pipe deploy runner config flags to managed pool r …
• #5412 feat(dashboard): show connection token inline with get-or-cr …
• #5410 chore(dashboard): bump rivet-gg/cloud and adopt sdk connecti …
• #5411 feat(dashboard): add connection token issuing ui
• #5409 feat(dashboard): allow typing cpu value in compute tab
• #5408 feat(dashboard): add compute tab to namespace settings drawe …
• #5414 docs(compute): remove beta label from rivet compute 👈
• #5407 fix(container-runner): report crashed child exits as errored …
• #5406 feat(rivetkit): report actor run() errors to the engine as e …
• main

Get stack: forklift get 5414
Push local edits: forklift submit
Merge when ready: forklift merge 5414

_{change qqkuorrw}

[claude]

Review: docs(compute): remove beta label from rivet compute

Overview

Removes the "Beta" designation from Rivet Compute across the dashboard deploy-option list, the pricing component, and the docs page, and refactors Provider/deployOptions in frontend/packages/shared-data/src/deploy.ts to use an explicit union type instead of one derived via satisfies + as const.

Correctness

• Verified badge is optional on DeployOption, so dropping badge: "Beta" from the rivet entry is safe and the {option.badge ? <Badge>...} : null rendering in getting-started.tsx degrades cleanly (no leftover badge).
• Checked for other lingering "beta" references tied to Rivet Compute (sitemap, docs landings) — the remaining badge: "Beta" hits in website/src/sitemap/mod.ts and docsLandings.ts are for the Rust/Effect.ts SDK quickstarts and agentOS, unrelated to this change, so nothing was missed.
• compute-pricing.ts comment/doc updates ("pending-pricing notice" instead of "beta notice") accurately describe the still-existing finalized gating behavior in ComputePricing.tsx — no functional change there, just wording.

Code quality / style

• The Provider type change (deriving it from an explicit union instead of (typeof deployOptions)[number]["name"]) is a minor design regression: previously the type was mechanically derived from the data (single source of truth), so adding/removing/renaming a deployOptions entry automatically kept Provider in sync. Now Provider and the array must be kept in sync by hand. This isn't required to remove the beta badge — worth double-checking this refactor was intentional/desired rather than an incidental side effect, since it's unrelated to the PR's stated purpose (removing the beta label).
• That said, the new form is easy to read and each deployOptions entry is still checked against Provider via the name: Provider field, so a typo'd provider name will still fail to typecheck.

Test coverage

• Pure content/label changes with a low-risk type refactor; no tests included, which is consistent with the scope of this PR (no behavioral logic beyond a string literal type).

Risk

Low risk — text/label removal plus a type-representation refactor that TypeScript will catch if deployOptions and Provider drift apart.