Repository navigation
Sprint 1
Generated from
docs/planning/sprints/sprint-01.md. Edit that file in the repository: changes made in the wiki are overwritten.
The planning record of Sprint 1, kept as the Work Management and Delivery Specification requires (§7, §14). Reconstructed on 2026-10-02 from the items' close dates (#339), when the owner split release 1. No sprint was planned in advance: the goal summarizes what was done, and no capacity was recorded at the time. These one-day sprints adapt past work to the specification; they don't change its rules.
| Field | Value |
|---|---|
| Sprint | Sprint 1 (Project iteration Sprint 1) |
| State | Ended |
| Start | 2026-09-29 00:00 Europe/Brussels, inclusive |
| End | 2026-09-30 00:00 Europe/Brussels, exclusive |
| Duration | One day (history, owner decision on #339) |
| Release | v0.1 |
Lay the delivery foundation: the domain model, the first tasks and the Warmane lockout research.
None recorded at the time. The sprint is reconstructed from completed work.
Completed outcome items, by close date (their tasks closed with them):
- #40 (spike) Validate Warmane reset and difficulty rule matrix
- #148 (improvement) Enforce documentation quality gates
- #354 (user story) Respond on the website with multiple characters and presets (part delivered in v0.1)
- #355 (user story) Capture complete and fresh raid-save evidence (part delivered in v0.1)
- #356 (user story) Evaluate combined raids and block confirmed locks (part delivered in v0.1)
Corrected on 2026-10-03 to match the Project (#401): the list now follows each item's Sprint field, including the parts split from mixed-release items (#347).
Unfinished work: items worked on during this day but not finished stay open on their planned release, with their finished tasks recorded in this sprint. No Story Points were recorded for these days.
- Product scope
- Architecture
- Visual guide
- Diagram maintenance
- Review a pull request
- Design a screen
- Test the addon
- Set up Discord
- Provision the server
- Glossary
- API contracts
- Addon snapshot contract
- Project automation
- Work management specification
- Warmane lockout evidence
- Planning
-
Decisions
- Index
- Foundation and authentication
- Character synchronization
- Documentation publication
- Protected automatic squash merges
- Viewed files before approval
- Operator review before a peer
- Auto-merge when ready
- Merge with the workflow token
- Meaningful review comments
- Read queries from the write database
- Website session and API trust
- Interactive Server rendering with Radzen
- Scalar API reference
- GitHub Wiki mirror
- Coverage gate
- Work item hierarchy
- Penpot mockups
- Generated Penpot mockups
- Dark design system
- SonarCloud findings
- Addon roster import
- Discord role checks
- Discord servers at sign-in
- Community roles
- Work item classification
- Work management specification adoption
- OVH test environment
- Environment secrets
- PostgreSQL
- Companion pairing
- WoW addon in Lua
- Windows companion in Avalonia
- Companion in the Microsoft Store
- Workflows on a self-hosted runner