Summary: The repo documents multiple deployed contract versions, but there is no concrete plan for migrating users or state when versions change.
Why it matters: Without a migration story, switching the active contract can strand balances, break governance history, or force users to relearn a new flow without guidance. Versioned deployments only help if the transition is explicit and documented.
Scope:
- Define what needs to move between versions and what should remain immutable.
- Explain how the frontend should guide users through the switch.
- Add rollback and validation steps for operators.
Acceptance notes:
- The migration path is documented in plain language.
- User-facing implications are listed clearly.
- State-preservation risks are called out before a version cutover.
Summary: The repo documents multiple deployed contract versions, but there is no concrete plan for migrating users or state when versions change.
Why it matters: Without a migration story, switching the active contract can strand balances, break governance history, or force users to relearn a new flow without guidance. Versioned deployments only help if the transition is explicit and documented.
Scope:
Acceptance notes: