gabriel / musehub public
docs task/fix-stale-prod-instance-runbook #1 / 1
AI Agent gabriel · 1 hour ago · Sep 17, 2026 · Diff

docs: fix stale production instance ID/account in incident runbook

The runbook and instance-ID table still pointed at i-0855d6efe7fa1a49d, the legacy Nonproduction-account instance retired during the 2026-08-25 production rebuild. Real production is i-043aaed71bef11903 in a separate, dedicated AWS account, reachable only via the musehub-production SSO profile. This caused ~15 minutes of wasted effort during the 2026-09-17 production outage before the correct instance was found.

sha256:95c1e74446fa16e9155eac4d5ded6fcfc9df130916d4dc84b53a98097fb96575 sha
sha256:4c406127fd42cddb7bd2282519704e86a5ed7129fe2682617e23821e2bddb259 parent
+1 ~3 −1 symbols
1 changed · 1075 in snapshot files
sha256:8ca708b3ade909d85655dcc656d0e380ff5629f8b33658c3f03e8f832d15a2d2 snapshot
+1
symbol added
~3
symbols modified
−1
symbol removed
1
file changed
1075
files in snapshot
0
dead code introduced
Semantic Changes 5 symbols
~ .museagent.md .md 1 symbol added, 1 symbol removed, 3 symbols modified
− Recovering a Down Staging Instance section Recovering a Down Staging Instance L168–201
+ Recovering a Down Staging or Production Instance section Recovering a Down Staging or Production Instance L168–220
~ musehub — Agent Configuration
~ Repo-Specific Notes
~ Instance IDs
Files Changed
~1
1075 in snapshot
~ .museagent.md .md
← Older Oldest on task/fix-stale-prod-instance-runbook
All commits
Newer → Latest on task/fix-stale-prod-instance-runbook

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:95c1e74446fa16e9155eac4d5ded6fcfc9df130916d4dc84b53a98097fb96575 --body "your comment"