We need an executable migration path, not only a design doc. Python gr2 should coexist with gr1 during transition, and the later Rust port should be a backend swap rather than a second UX migration.
Scope:
- add Python-first migration/import commands
- make coexistence explicit when a workspace is still partially gr1-driven
- preserve current repo state while generating Python gr2 workspace structures/specs
- align with HOOK-CONFIG-MODEL.md migration rules
Why:
- transition is currently documented but not executable
- adoption depends on a safe path from gr1 -> Python gr2
- this should be validated before any Rust rewrite/port plan
Acceptance:
- an existing gr/gripspace user can bootstrap into Python gr2 without a second conceptual migration
- the CLI makes the coexistence/transition state explicit
- migration does not require Rust gr2 binary support
We need an executable migration path, not only a design doc. Python gr2 should coexist with gr1 during transition, and the later Rust port should be a backend swap rather than a second UX migration.
Scope:
Why:
Acceptance: