Release v0 1 - AnnabiGihed/RaidManager GitHub Wiki
Generated from
docs/planning/releases/v0.1.md. Edit that file in the repository: changes made in the wiki are overwritten.
The planning record of release v0.1, Delivery foundation, 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.1 (repository milestone v0.1) |
| State | Delivered to main, not deployed: no deployment exists yet, so it is neither Ready nor Released (§6) |
| Target date | 2026-09-30 (the day its last sprint ended) |
| Actual delivery date | 2026-09-30 to main; not deployed |
| Approval | Each change was approved and merged through its pull request; no release approval was given |
Goal
A repository that can be developed safely: domain foundations, automated review and merge, quality gates, published documentation, a local run, and mockups for the first screens. (reconstructed)
Acceptance criteria
None were agreed before the work. Each item met its own criteria, with evidence on its issue and pull request.
Scope
36 completed outcome items, with their tasks, by close date:
- #40 (spike) Validate Warmane reset and difficulty rule matrix
- #144 (improvement) Merge approved pull requests automatically
- #145 (improvement) Require an operator review, then a peer review
- #146 (bug) A ready pull request stayed open after GitHub refused the merge
- #148 (improvement) Enforce documentation quality gates
- #149 (improvement) Publish the documentation to the GitHub Wiki
- #151 (improvement) Run the product locally with the Aspire AppHost
- #152 (improvement) Browse the API in an interactive reference
- #155 (improvement) Gate pull requests on test coverage
- #157 (improvement) Codify the Project workflow and completion rules
- #181 (user story) Design the mockup for character review after sign-in
- #207 (improvement) Fail pull requests on SonarCloud findings
- #177 (user story) Design the mockup for Discord sign-in and session
- #178 (user story) Design the mockup for community linking and officer permissions
- #179 (user story) Design the mockup for companion pairing and revocation
- #180 (user story) Design the mockup for companion account discovery and upload
- #182 (user story) Design the mockup for character profiles
- #183 (user story) Design the mockup for the raid list and raid editor
- #184 (user story) Design the mockup for raid templates and recurrence
- #185 (user story) Design the mockup for the website signup form
- #186 (user story) Design the mockup for the Discord signup flow
- #187 (user story) Design the mockup for raid changes and reminders
- #188 (user story) Design the mockup for readiness re-evaluation and exceptions
- #189 (user story) Design the mockup for the candidate workspace
- #190 (user story) Design the mockup for draft compositions and the bench
- #164 (improvement) Require a Penpot mockup for every UI work item
- #168 (improvement) Generate Penpot mockups and render their SVGs in the repository
- #172 (bug) documentation spelling errors pass CI but show in the editor
- #198 (bug) a mockup path counts as a mockup before the file exists
- #349 (user story) Sign in with Discord and keep a secure session (part delivered in v0.1)
- #351 (user story) Review new characters and resolve ownership conflicts (part delivered in v0.1)
- #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)
- #357 (improvement) Enforce the Epic, Feature, Story and Task hierarchy (part delivered in v0.1)
- #358 (improvement) Adopt the Command Center design system for mockups (part delivered in v0.1)
Sprint sequence
| Sprint | Date |
|---|---|
| Sprint 1 | 2026-09-29 |
| Sprint 2 | 2026-09-30 |
Stabilization plan
Owner exception (#339): Sprint 2 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.
Scope decisions
| 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 |
Readiness evidence
Not applicable until a deployment exists. These items ship with the first deployed release.