Discord go-live: execute Orca→Outpost cutover (Phase 9) #59

Context

Flip from Orca to Outpost as the live Discord support bot.

Source: the Outpost go-live runbook (internal), Phases 9 + 10.

Depends on: Shadow-mode validation issue returning READY.

Checklist

• Final validation: npx tsx scripts/cutover/validate-quality.ts returns READY
• Dry run: npx tsx scripts/cutover/execute-cutover.ts
• Review dry-run output (health checks, ticket counts, quality metrics)
• Execute: npx tsx scripts/cutover/execute-cutover.ts --confirm
  • Disables shadow mode (SHADOW_MODE=false)
  • Posts announcement to Discord
• Manually disable the Orca bot in Discord server settings
• Monitor Outpost responses for the first 2 hours
• Confirm response latency < 5 minutes on new threads
• Check ticket dashboard for incoming Discord tickets

Rollback plan

If quality degrades within the first 2h:

• npx tsx scripts/cutover/rollback.ts --confirm --reason "..." (re-enables shadow mode, logs event)
• Manually re-enable Orca bot

Acceptance

• Outpost is the only bot responding in monitored channels
• 24h post-cutover: response quality and error rates within targets
• Orca bot offline / removed from the guild
• Decommission Orca scheduled (after 1-week rollback window)