chore(sprint-status): reconcile epic-33 done + epic-37 9-story scope#49
Open
ALLiDoizCode wants to merge 1 commit intomainfrom
Open
chore(sprint-status): reconcile epic-33 done + epic-37 9-story scope#49ALLiDoizCode wants to merge 1 commit intomainfrom
ALLiDoizCode wants to merge 1 commit intomainfrom
Conversation
- Flip epic-33 from in-progress to done (retro was already done; status now consistent) - Add epic-37 to sprint-status.yaml with all 9 shipped stories and done retro - Update epic-37 planning doc to reflect 3 → 9 story growth (37.4 Town follow-up; 37.5–37.9 accounting/metric correctness fixes uncovered while wiring earnings JSON) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two pieces of post-hoc cleanup for closed epics. No code change; documentation/state-file only.
in-progress→done. All 9 stories were already markeddoneand the retrospective was alreadydone— the epic-level status was the only stale field.sprint-status.yaml. It shipped (retro 2026-04-21, see_bmad-output/implementation-artifacts/epic-37-retro-2026-04-21.md) but was never tracked in the sprint-status file — it jumps 36 → 38.epic-37-admin-api-dashboard-observability.md) updated to reflect 3 → 9 story growth during execution. 37.4 was a Town follow-up after 37.3 shipped (per-peer earnings JSON); 37.5–37.9 are accounting/metric correctness fixes uncovered while wiring the per-peer counters and earnings projection — they were too tightly coupled to ship separately because the dashboard JSON would have surfaced incorrect values without them.Out of scope
_bmad/custom/config.user.tomlgitignore entry (its file header marks it gitignored but it's not yet in.gitignore).Test plan
git diff mainis exactly the two files described above🤖 Generated with Claude Code