chore(container-runner): tighten comments

[abcxff]

No description provided.

[abcxff]

Stack for rivet-dev/actors

• #5594 feat(container-runner): drain engine sleeps unless the idle …
• #5595 feat(container-runner): jitter idle timeout to avoid teardow …
• #5585 feat(container-runner): self-sleep on repeated actor start
• #5586 feat(container-runner): sleep on startup idle timeout
• #5589 chore(container-runner): tighten comments 👈
• #5587 feat(container-runner): exit process when the last child sto …
• #5588 feat(container-runner): drain child before SIGTERM on engine …
• #5584 feat(container-runner): drain children and engine concurrent …
• #5565 fix(envoy-client): ack terminating stop commands so pegboard …
• main

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

_{change zrxxyxls}

[claude]

Review

This is a pure comment/doc-comment tightening pass over container-runner, no functional code changes (verified every hunk in the diff touches only //, ///, or //! lines / markdown prose).

Findings

Nothing blocking. A few observations:

• Em dash removal is consistent and complete in all touched Rust files (actor.rs, child.rs, input.rs, main.rs, monitor.rs, proxy.rs) and matches the CLAUDE.md rule against em dashes in prose/comments. README.md still has a handful of leftover em dashes (lines ~187, 242, 280, 347-348) in sections this PR didn't touch — not a blocker since it's out of scope for this diff, but worth a follow-up if the goal is a fully em-dash-clean container-runner/.
• No information loss from the trims — I checked the two condensations that looked riskiest:
  • main.rs's EXIT doc originally said it's cancelled on "actor stopped, failed start, or signal"; the new version says "last child stopped or a signal." I traced request_exit/EXIT.cancel() call sites and a failed on_start never calls request_exit (the child is never registered, so there's no "last child" to trigger the empty-registry exit path). The new wording is actually more accurate than the old one, not just shorter — nice catch.
  • monitor.rs's module doc dropped the itemized "Memory sources, in preference order" / "CPU sources, in preference order" lists, but that detail is preserved next to the MemSource/CpuSource enum variants themselves (each variant has its own /// doc), so nothing was actually lost, just relocated closer to the code it describes.
  • The Args.port field doc dropped the RIVET_PORT vs PORT platform distinction, but that explanation is still present as an inline comment right above where port is resolved in async_main.
• "Cloud Run" → "serverless"/"Rivet Compute" renames are a nice cleanup for genericizing the docs/comments away from a specific vendor concept, consistent with keeping this code as a general RivetKit serverless example rather than GCP-specific.

Other categories

• Bugs/correctness: N/A, no logic changed.
• Performance: N/A.
• Security: N/A.
• Test coverage: N/A, no behavior changed, so no new tests needed.

Nice cleanup — comments read as complete sentences now and match the repo's comment-style conventions.