Release v0 3

Generated from docs/planning/releases/v0.3.md. Edit that file in the repository: changes made in the wiki are overwritten.

The planning record of release v0.3, Identity and characters, kept as the Work Management and Delivery Specification requires (§6, §14).

Approved on 2026-10-02. The owner asked the agent to approve this release on their behalf (#360): its goal, acceptance criteria, scope and target date below are agreed. Scope or date changes still need an owner decision (§6).

Field	Value
Version	v0.3 (repository milestone v0.3)
State	Planned (§6): goal, initial scope and target date agreed
Target date	2026-11-27 (last day of Sprint 8, its stabilization sprint)
Actual delivery date	Not delivered
Approval	Approved 2026-10-02 by the agent on the owner's delegation, recorded on #360

Goal

Players sign in with Discord, see their community, pair the desktop companion, and get their WoW characters captured, uploaded, reviewed and shown on their profile. It is the first release to be deployed.

Acceptance criteria

1. A new player pairs one companion, visits characters across two WoW accounts, approves each new character at the next website sign-in, and sees its last sync and raid saves (version 1 journey 1).
2. An officer's permissions come from the community's roles, and losing the Discord role removes them.
3. The deployment stores and delivers its secrets as the decision of #103 records, so the release can be deployed.
4. The test environment on the OVH VPS-1, on a subdomain of pivotsoftwares.com, runs this release, deployed automatically from main with a passing smoke test (epic #369).

The repository's quality gates pass on the released version, and the stabilization sprint records its release checks below.

Scope

The 18 items below hold 83 Story Points. On the owner's decision 4 of #346, improvements, bugs and spikes carry points too.

Product:

• #13 (user story) Sign in with Discord and keep a secure session: 5 points
• #15 (user story) Pair and revoke a desktop companion: 8 points
• #16 (user story) Capture visited characters in the WoW addon: 8 points
• #17 (user story) Discover WoW accounts and upload snapshots reliably: 8 points
• #18 (user story) Review new characters and resolve ownership conflicts: 5 points
• #19 (user story) Inspect and manage character profiles: 5 points
• #171 (user story) Resolve character ownership conflicts as an officer: 3 points
• #37 (spike) Define companion pairing and claim threat model: 3 points

Deployment of the test environment on OVH (epic #369, owner decision on #367):

• #373 (spike) Choose how RaidManager runs on the OVH VPS-1: 3 points
• #374 (improvement) Provision the OVH test server: 5 points
• #103 (spike) Decide how deployed secrets are stored and delivered: 3 points
• #153 (improvement) Store and deliver deployment secrets: 5 points
• #375 (improvement) Configure the test environment: 3 points
• #376 (improvement) Deploy main to the test environment automatically: 8 points
• #392 (improvement) Show deployment status on GitHub and the Project: 3 points

Engineering:

• #209 (improvement) Fix the SonarCloud findings on main: 5 points
• #390 (improvement) Record the full Sprint 5 selection: 1 point
• #394 (improvement) Record stage, risk and planned dates on the Project: 2 points

Their tasks share this milestone. Epic #369 and its features #370, #371 and #372 also carry v0.3, since their whole scope is in this release. Features and epics that also hold work of other releases carry no milestone (§15, A2).

Sprint sequence

Sprint	Dates (Europe/Brussels)	Purpose
Sprint 5	2026-10-03 to 2026-10-17 (end exclusive)	Delivery
Sprint 6	2026-10-17 to 2026-10-31 (end exclusive)	Delivery
Sprint 7	2026-10-31 to 2026-11-14 (end exclusive)	Delivery
Sprint 8	2026-11-14 to 2026-11-28 (end exclusive)	Stabilization

The dates were set assuming 20 Story Points per two-week sprint. Since the owner's decision of 2 October (#390), the assumption is 70 points per sprint, from the delivery pace of Sprints 1 to 4, and Sprint 5 holds every doable item of this release: 75 of its 83 points. #18 and #171 (8 points) wait for rosters from v1.0. If the release finishes early, the release plan is revisited at the Sprint 5 review (#390); the target date stays until then.

Stabilization plan

Sprint 8: blocking defects, regressions, end-to-end validation of the acceptance criteria, documentation, release notes, deployment and rollback preparation, planned as concrete items (work-stabilization-and-release-closure).

Scope decisions

Date	Decision	Recorded on
2026-10-02	Release 1 split; the agent drafted this release's scope, sprints and target date at the owner's request.	#339
2026-10-02	Approved as drafted, on the owner's delegation.	#360
2026-10-02	Risk: story #14's last criterion (role loss stops officer raid actions, task #291) needs the raid commands of #20 in v0.4. Moving #14 to v0.4 is an open owner decision.	#361
2026-10-02	#14 and its task #291 move to v0.4.	#367
2026-10-02	Added: the deployment configuration and a test environment on an OVH VPS-1 under a subdomain of pivotsoftwares.com, as epic #369; the work starts in Sprint 6. Criterion 4 added.	#367
2026-10-02	Risk: the scope now holds 77 points against the 60 that Sprints 5 to 7 forecast at 20 points per sprint. Changing the scope or the target date is an open owner decision.	#368
2026-10-02	Sprint 5 takes every doable item of this release, and the capacity assumption rises to 70 points per sprint; this settles the risk above. The release plan is revisited at the Sprint 5 review.	#390
2026-10-02	Added: #392, deployment status on GitHub and the Project (3 points), and the planning items #390 (1 point) and #394 (2 points).	#390, #394

Readiness evidence

None yet.