docs(deploy): add container runner page

[abcxff]

No description provided.

[abcxff]

Stack for rivet-dev/rivet

• #5394 refactor(container-runner): rewrite on rivetkit actor runtim …
• #5395 feat(rivetkit): re-export serverless_http and default absent …
• #5392 docs(deploy): add container runner page 👈
• #5393 ci(publish): build and publish container runner release arti …
• #5391 feat(container-runner): add container runner crate and e2e h …
• main

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

_{change mqospzuu}

[claude]

Review

Docs-only change (new deploy/container-runner.mdx page + sitemap entry). I cross-checked the page's technical claims against the actual container-runner/ implementation and CI config, and everything lines up:

• CLI flags/env vars/defaults table matches container-runner/src/main.rs exactly (--port resolution order, CHILD_PORT/7770, RIVET_ACTOR_NAME/game, RIVET_RUNNER_VERSION/1, RIVET_SERVERLESS_BASE_PATH//api/rivet, RIVET_STOP_GRACE_SECS/25, RIVET_READINESS_TIMEOUT_SECS/30).
• Per-actor input JSON schema (command/args/env/port) matches container-runner/src/input.rs::ActorInput.
• Release artifact URL pattern (releases.rivet.dev/rivet/{version}/container-runner/rivet-container-runner-<target>) matches the upload_prefix: container-runner artifacts in .github/workflows/publish.yaml.
• --instance-request-concurrency 1 deploy flag exists in engine/packages/cli/src/commands/deploy.rs and its semantics ("concurrent requests per instance") correctly support the "one actor per container" recommendation.
• rivet WebSocket subprotocol claim matches WS_PROTOCOL_STANDARD = "rivet" in rivetkit-typescript.
• Frontmatter (title/description/skill) matches the required docs schema, the /docs/deploy/rivet-compute link target exists, and the dockerfile @nocheck annotation follows the same convention used elsewhere for non-typecheckable snippets.
• Sitemap addition is correctly nested under Deploy alongside the existing Reference section.

No bugs, security concerns, or test-coverage gaps to flag. Nothing here is executable, so there's nothing to unit test, and the content is accurate as written. Nice, tight page.

Nitpick (non-blocking): the new "Advanced" sidebar section under Deploy has a single entry. Fine as-is, but worth folding into "Reference" if it doesn't grow.