Launch Ops Runbook (v2.0.0 Post-Launch Polish)
This runbook defines launch-day monitoring and distribution for the trust-and-infra fanout path (no X/Reddit dependency).
Same-Day Fanout Order (9 Channels)
- GitHub release page refresh (
v2.0.0 copy + install-proof block)
- npm parity confirm (
@jtalk22/slack-mcp@2.0.0)
- MCP registry parity confirm (
2.0.0)
- Smithery listing metadata/parity update (or timestamped propagation note)
awesome-mcp-servers listing PR refresh- Glama metadata sync and canonical link verification
- HN thread update comment (high-signal install proof + support path)
- GitHub Discussions announcement/support threads update
- GitHub Pages/docs surface publish + link verification
Monitoring Cadence
- First 4 hours: every 30 minutes
- Up to 24 hours: every 60 minutes
Track:
- install reports and blocker count
- npm/MCP parity state
- listing propagation status (Smithery/Glama)
- inbound issue and discussion severity
Triage Rules
P1 install blocker:
- acknowledge within 30-60 minutes
- provide immediate workaround
- add fix to patch queue
Non-blocking request:
- acknowledge and route to issue/discussion template
- provide timeline as best effort
Escalation Triggers
- If install failures exceed 3 unique reports in 24h:
- pause outbound promotion
- prioritize hotfix
- If support load exceeds 2 hours/day for 2 days:
- switch to stability-only mode
- defer non-critical requests
24h / 48h / 72h Follow-Up
24h:
- publish release-health delta and short technical summary
48h:
- patch docs for top recurring setup questions
72h:
- ship
v2.0.1 only if launch defects are confirmed
Evidence Log
Use:
docs/release-health/launch-log-template.md
Capture:
- channel
- UTC timestamp
- URL or command evidence
- action taken
- observed result (
success|partial|blocked)