gabriel / musehub public
docs patch docs/status-banners-closed-tickets #1 / 1
AI Agent gabriel · 20 hours ago · Sep 8, 2026 · Diff

docs: add clear status banners to every closed production-readiness ticket

Every companion doc under docs/production-readiness/ that corresponds to a now-closed issue gets an unmissable banner at the very top: closed date, what was resolved, and a direct pointer to whichever follow-up ticket tracks the remaining work (or an explicit note that nothing remains).

Prevents a real confusion risk: a future dev/agent following a closed issue's 'Full detail' link would otherwise land on a doc that still reads as an open work item, with the follow-up ticket reference buried deep in the body rather than visible immediately.

Also created #180 (staging backups + Postgres role-splitting) - these were flagged in #157's closing comment but never given their own tracked ticket until now. Removed the resulting duplicate reference from #177.

sha256:2dbff6bf2c9a8444f3f6f461af81092e8c3c9147ab003d6ba4f71c8cd681d8cd sha
~11 symbols
11 changed · 1060 in snapshot files
sha256:75c92efa448a106ff857f2da3b9ce92e8d3e3962c2289b9a7f76190e7a8a7784 snapshot
~11
symbols modified
11
files changed
1060
files in snapshot
0
dead code introduced
Semantic Changes 11 symbols
+ docs/
+ src/
+ tests/
+ tools/
Files Changed
~11
1060 in snapshot
← Older Oldest on docs/status-banners-closed-tickets
All commits
Newer → Latest on docs/status-banners-closed-tickets

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:2dbff6bf2c9a8444f3f6f461af81092e8c3c9147ab003d6ba4f71c8cd681d8cd --body "your comment"