B01: P6: beta readiness

Go implementation tracking epic

Selected stack: Go + Wails v2 + React/TypeScript + SQLite. Implementation starts on the next machine. Each child below is a separate PR; do not implement this epic in one PR.

Child tasks

• B01a: Distributable package and notices
  • Merged prerequisites: F01c, I01d, R02c.
  • Acceptance: R1/R6: reproducible package, dependency/license inventory, clean-machine install and launch; experimental/extension features excluded unless independently complete.
• B01b: Upgrade and rollback validation
  • Merged prerequisites: B01a.
  • Acceptance: Back up before migration, interrupted-upgrade and restore tests; demonstrate package/data rollback on target Linux without blindly downgrading schema.
• B01c: Beta compatibility and release evidence
  • Merged prerequisites: B01b.
  • Acceptance: R1-R8: real claimed Linux matrix, accessibility/performance/privacy evidence and usage docs; all current-commit checks/review resolved. Publication remains a separate authorized action.

Workflow

See TASKS.md, ROADMAP.md, and CONTRIBUTING.md. Aim for 100-400 handwritten changed lines per PR; split above 600 unless inseparable. Merge prerequisites before dependents. Update task evidence and this checklist after each completed PR. Close this epic only when every child passes; optional work can remain deferred.

All tasks are not started. Live game access and publication/merge actions follow the user's explicit authorization. The planning handoff does not claim runtime validation.

Start by reading TASKS.md, ROADMAP.md, and CONTRIBUTING.md, then review the B01a, B01b, and B01c prerequisites and acceptance criteria. Treat each child as a separate PR rather than implementing this epic as one change. Done means the relevant child’s reproducible package, rollback validation, or beta evidence is complete and its task evidence is updated.