fix: update railway docs to include graceful shutdown

[MasterPtato]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[MasterPtato]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• fix(pb-envoy): hard abort ws to tunnel on ping error #4776
• fix(outbound): implement drain grace period #4775
• fix(pb): fix pool config defaults #4774
• fix(pb): remove actor sleep ts when allocated #4772
• refactor(gateway): clean up and fix lost tunnel msgs #4771
• refactor(pb): fix actor overdue alarm handling #4770
• fix: update railway docs to include graceful shutdown #4715 👈 (View in Graphite)
• fix: add wf registry command #4714
• chore: move code #4713
• fix(gas): add large txn retries for pulling signals, tighten commit interval for actors #4712
• fix: improve epoxy propose errors, add gcp logging fmt #4698
• fix: autogenerate bare protocol versions #4696
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

PR Review: fix: update railway docs to include graceful shutdown

This PR adds a "Graceful Shutdown" section to the Railway self-hosting docs. The intent is correct and valuable, but there are a few issues to address before merging.

---

Critical: Wrong recommended grace period

The new section recommends 60 seconds as a grace period. Every other doc in the repo specifies 130 seconds:

• actors/versions.mdx: "Ensure your platform's shutdown grace period is at least 130 seconds"
• general/production-checklist.mdx: "Set a graceful shutdown period of at least 130 seconds."
• self-hosting/kubernetes.mdx: terminationGracePeriodSeconds: 130

The 130-second floor exists because the runner waits up to 120 seconds for actors to drain (plus a ~10-second buffer). A 60-second drain window will silently truncate actor draining on every deploy, defeating the purpose of this feature.

Fix: Update all three drainingSeconds examples (dashboard UI, config-as-code, env var) to use 130 instead of 60.

---

CLAUDE.md violation: Em dashes

CLAUDE.md explicitly states: "Do not use em dashes (—). Use periods to separate sentences instead."

Two em dashes appear in the new content:

• **Draining seconds** — the grace window...
• ...the wrapper becomes PID 1 and swallows the signal — your app never drains...

These need to be rewritten using periods or restructured sentences.

---

Clarity: PID 1 guidance should specify which service it targets

A Railway project from this guide has two services: the Rivet Engine (Step 2, rivetdev/engine:latest) and the user's application (Step 3). The PID 1 / signal-forwarding warning applies specifically to the user's application container, not to the Rivet Engine image. The section doesn't make this distinction, so readers may either modify the Rivet Engine image unnecessarily or skip the fix for their own app.

---

Minor: Section placement

The forward-reference at Step 2 points to a "Graceful Shutdown" section that appears after Step 3. Readers following numbered steps will be directed to a section they haven't reached yet. Consider moving the shutdown section before Step 3 or embedding it as a sub-step under Step 2.

---

What looks correct

• Frontmatter fields (title, description, skill) are all present and valid.
• No rivet.gg usage; Railway links correctly use railway.com.
• Documenting all three configuration methods (dashboard, config-as-code, env var) is a nice touch.
• Conventional commit format is followed.