mpckit/pull-requests/beta-0-5-0/plan-for-0-5-0-beta.md

Plan for 0.5.0 (beta) instead of 1.0

Branch: beta-0-5-0 → main

What changed

The current milestones (M1–M9) produce a beta release for testing, 0.5.0, not 1.0. The milestones needed for 1.0, including beta testers using pre-1.0 versions, will be added later.

• docs/build-plan.md:
  • Every "1.0" is now "0.5.0": title, "What 0.5.0 is", "Not in 0.5.0", the design notes, and M9's done-when ("a tagged v0.5.0 build").
  • A line under the title says 0.5.0 is a beta release for testing and the 1.0 milestones come later.
• docs/xpj-format-and-scope.md: the same scope was labelled "1.0" there and the plan refers to it, so those labels are now "0.5.0" too. The scope heading notes it was agreed on 2026-11-10 as the 1.0 scope and renamed on 2026-11-11.
• internal/project/project.go: two comments ("every edit 1.0 makes", "tuning ranges for 1.0") now say 0.5.0.

Not changed: the format doc's "2.0" labels (features after this release), and the test comment calling start/end trim "a 2.0 feature". They can be revisited when the 1.0 milestones are planned.

Merges cleanly with m8-load-guard-rails, which also edits the build plan (checked with a trial merge).

Testing

Docs and comments only. go vet ./internal/project passes.