feat: add DM screen and battle organizer#151
Merged
Merged
Conversation
Daren9m
marked this pull request as ready for review
July 20, 2026 03:11
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.
What changed
Why
DMs need one configurable command surface for session references and a dedicated live-combat workflow. The shared battle state lets the standalone organizer and DM-screen initiative element stay synchronized, while the encounter handoff removes duplicate setup at the table.
User impact
Users can prepare a reusable DM screen, launch generated encounters directly into initiative, and continue managing the same battle from either
/battleor the embedded initiative tracker.Validation
npm run typechecknpm run lintnpm test— 649 tests passednpm run build— static export completed successfully