S4.9 — Docs, migration guide, ADR-0003 accepted
Intent
Document the 0.9.0 model and give users one migration path for all its breaking changes.
Acceptance criteria
-
- fallible
is_valid/is_satisfied/distance_goal(Ok(..)) Send + Syncon checkers, spaces, goals (Rc/RefCell→Arc/Mutex)PlanningErrornon-exhaustive, noPartialEq, newUservariant- default fraction 0.05 → 0.01 and no ×0.1 (set 0.005 for the old single-space spacing)
SpaceInformation+ProblemDefinition+setup(pd); bindings dropsetup; JSStateValidityCheckerremoved- binding exceptions; JS setter rename
- spaces shared and frozen once used
- fallible
Source
Agreed in the senior-engineer grilling 2026-10-08 (decisions: repo docs/planning/adr/0003-motion-validation.md; glossary: CONTEXT.md). Regeneration spec: oxmpl - sprint-006. Line references are as of origin/main c558556 (2026-10-08), before E3. E3 renames things (rand Rng→RngExt, PyO3 with_gil→attach, edition 2024), so re-grep before trusting a line number.