gabriel / musehub public
fix BREAKING task/production-readiness #3 / 22
AI Agent gabriel · 24 days ago · Aug 8, 2026 · Diff

fix: guard /_debug/memory behind settings.debug to prevent info disclosure in production

sha256:75bfa7f70856f7e02992044c996fc30bf066d3e2a8d90e4d4e6afde803cf2a76 sha
sha256:20b27796ed512236119feef48b4577a8fd9ded05a15267dd4e6da23604ad1f1a parent
+1 ~5 −2 symbols
3 changed · 1047 in snapshot files
sha256:1f2647fb279b1edc55f4f1d1d3b6a6d2e040ca0dadae13bb5c77263f0b0d0cae snapshot
+1
symbol added
~5
symbols modified
−2
symbols removed
3
files changed
1047
files in snapshot
0
dead code introduced
Semantic Changes 8 symbols
~ docs/musehub-production-readiness-checklist.md .md 4 symbols modified
~ Accepted Risks and Deferred Work
~ table
~ MuseHub Production-Readiness Checklist
~ Application Security
~ docs/production-readiness/14-application-security.md .md 1 symbol added, 1 symbol removed, 1 symbol modified
− ⚠️ Finding — /_debug/memory is exposed unconditionally in production section ⚠️ Finding — /_debug/memory is exposed unconditionally in production L5–16
+ ✅ Fixed — /_debug/memory was exposed unconditionally in production section ✅ Fixed — /_debug/memory was exposed unconditionally in production L5–13
~ Section 14 — Application Security
~ musehub/main.py .py 1 symbol removed
− debug_memory function async_function debug_memory L412–420
Files Changed
~3
1047 in snapshot
~ docs/musehub-production-readiness-checklist.md .md
~ docs/production-readiness/14-application-security.md .md
~ musehub/main.py .py
Older docs: update Suggested Ownership Split table to reflect full 20-… sha256:20b27796ed512236119feef48b4577a8fd9ded05a15267dd4e6da23604ad1f1a All commits Newer docs: add deploy onboarding runbook for expanded 5-person team, … sha256:d47368ca2aca9e5eb1af87830daba9201111f8d38fa86b0f4cfa8b0d069f0f3b

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:75bfa7f70856f7e02992044c996fc30bf066d3e2a8d90e4d4e6afde803cf2a76 --body "your comment"