chore(container-runner): default stop grace to 10s

[abcxff]

No description provided.

[abcxff]

Stack for rivet-dev/rivet

• #5557 docs(container-runner): sync deploy docs with runner source
• #5556 fix(container-runner): read cgroup v1 memory usage under gvi …
• #5548 feat(container-runner): log version and git sha at actor sta …
• #5549 feat(container-runner): setup instance memory and cpu usage …
• #5546 fix(rivetkit): keep actor event loop alive through shutdown …
• #5539 feat(container-runner): report actors as crashed on unexpect …
• #5536 feat(container-runner): log unexpected platform SIGTERM as a …
• #5530 fix(rivetkit-core): cancel driver alarm before sqlite teardo …
• #5531 feat(container-runner): keep instance warm instead of self-e …
• #5533 chore(container-runner): default stop grace to 10s 👈
• #5528 fix(rivetkit): log and surface actor startup failures
• #5529 fix(rivetkit): treat empty actor input bytes as absent
• #5558 fix(sdks): drop rivet-util metrics dep from protocol crates …
• main

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

_{change xnpvnuup}

[claude]

@-

[claude]

Review

Small, well-scoped change: lowers the default stop_grace_secs from 25s to 10s and generalizes doc comments away from Cloud-Run-specific wording to platform-agnostic language. No logic changes beyond the default value.

Verified consistency:

• effective_stop_grace() (main.rs:161) takes min(stop_grace, signal_child_stop_grace()) on signal-initiated shutdown, where signal_child_stop_grace() is 40% of the 10s SIGTERM_BUDGET default (4s) — so the signal-shutdown path is unaffected by this change since 4 < 10 was already the binding constraint, and remains so at 4 < 10.
• The engine-initiated stop path (actor.rs:151, child.stop(cfg.stop_grace)) now waits up to 10s instead of 25s before SIGKILL — this is the actual behavioral change from this PR.
• sleep_grace_period (main.rs:314) is derived as stop_grace + 10s, so it drops from 35s to 20s as a side effect. Worth double-checking this is still comfortably above the real-world child shutdown time for the actors this runner hosts, since core aborts on_destroy mid-stop if this deadline is too short (per the comment above it).
• No stale 25 references remain in README or comments.
• The Cloud-Run-specific wording removed here still appears in container-runner/README.md and a few files under container-runner/examples/, which is fine since those weren't part of this PR's scope, but worth a follow-up sweep if the intent is to fully genericize the platform language.

No bugs, security, or test coverage concerns — this is a config-default/comment change with no new logic paths. No new tests are needed for a default-value tweak like this.