docs: correct stale self-hosted-only database architecture claims
Staging has actually been running on managed AWS RDS (musehub-staging-db) since 2026-04-05, not the self-hosted Postgres container every doc claimed. Add correction notes pointing to the new canonical docs/database-architecture.md across infrastructure.md, db-management.md, pre-launch-checklist.md, and the production-readiness docs for Sections 0, 5, 8, and 12.
Most importantly, fixes musehub-production-infrastructure-launch-todo.md's prior conclusion that the RDS instance was 'very likely orphaned/unused' and awaiting a decommission decision -- it is staging's real, live database and must not be decommissioned. Also corrects Section 8's/#180's premise that staging has zero backups: RDS already provides native automated backups and point-in-time recovery.
Semantic Changes
26 symbols
Files Changed
~9
1061 in snapshot
0 comments
muse hub commit comment sha256:e9bdf7fbf5451787b3c5b7c82b3c9991c1c1f4cc9cf06e28036a4e834a34acf8 --body "your comment"
No comments yet. Be the first to start the discussion.