Repository navigation
Release v0 2
Generated from
docs/planning/releases/v0.2.md. Edit that file in the repository: changes made in the wiki are overwritten.
The planning record of release v0.2, Design system and process, kept as the Work Management and Delivery
Specification requires (§6, §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. Its one-day sprints adapt past work to the specification; they
don't change its rules.
| Field | Value |
|---|---|
| Version |
v0.2 (repository milestone v0.2) |
| State | Delivered to main, not deployed: no deployment exists yet, so it is neither Ready nor Released (§6) |
| Target date | 2026-10-02 (the day its last sprint ended) |
| Actual delivery date | 2026-10-02 to main; not deployed |
| Approval | Each change was approved and merged through its pull request; no release approval was given |
One design system and code standards for the website, mockups for every version 1 screen, and the work management specification applied to the board. (reconstructed)
None were agreed before the work. Each item met its own criteria, with evidence on its issue and pull request.
27 completed outcome items, with their tasks, by close date:
- #191 (user story) Design the mockup for coverage and composition warnings
- #192 (user story) Design the mockup for roster review and publication
- #193 (user story) Design the mockup for raid-night attendance and swaps
- #194 (user story) Design the mockup for boss assignments
- #195 (user story) Design the mockup for the roster export to the WoW addon
- #196 (user story) Design the mockup for gear warnings and attendance history
- #197 (user story) Design the mockup for character ownership conflicts
- #201 (improvement) Adopt the Command Center design system for mockups
- #267 (improvement) Reusable Blazor components and one project-wide theme
- #260 (improvement) Organize the website by feature
- #270 (improvement) Clean up branches after every merge
- #273 (bug) the AppHost logs a timeout exception every minute on Aspire 13.6.0
- #278 (improvement) Keep the agent's working practices in the repository
- #283 (improvement) Give every Blazor component its own folder
- #203 (improvement) Re-theme the website to the design system
- #308 (user story) create RaidManager roles with chosen permissions
- #158 (improvement) Enforce the Epic, Feature, Story and Task hierarchy
- #323 (improvement) Adopt the Work Management and Delivery Specification
- #339 (improvement) Split release 1 into releases and sprints
- #343 (improvement) Show releases and sprints clearly on the Project
- #350 (user story) Link a community and enforce officer permissions (part delivered in v0.2)
- #352 (user story) Review new characters and resolve ownership conflicts (part delivered in v0.2)
- #353 (user story) Browse, create, and edit scheduled raids (part delivered in v0.2)
- #346 (improvement) Keep each sprint on one release and complete estimates and stages
- #360 (improvement) Plan Sprint 5 and approve release v0.3
- #367 (improvement) Apply the release decisions of 2 October and add the OVH test deployment to v0.3
- #378 (improvement) Bring the OVH deployment spike into Sprint 5
| Sprint | Date |
|---|---|
| Sprint 3 | 2026-10-01 |
| Sprint 4 | 2026-10-02 |
Owner exception (#339): Sprint 4 counts as the final sprint of this release, but it wasn't a stabilization sprint; it also delivered new work. The quality gates of each pull request (build, tests, coverage, documentation, review and SonarCloud) applied throughout.
| Date | Decision | Recorded on |
|---|---|---|
| 2026-10-02 | Release 1 split; this release groups the work finished in its sprints. | #339 |
| 2026-10-03 | Scope list corrected to the Project: it follows each item's milestone, with the parts split from mixed-release items (#347) and the items finished later on 2 October. #164, #168, #172, #198 and #190 belong to v0.1, since their tasks finished in Sprint 2. | #401 |
Not applicable until a deployment exists. These items ship with the first deployed release.
- 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