12 lines
1.2 KiB
Markdown
12 lines
1.2 KiB
Markdown
## Planned Migration
|
|
|
|
- Treat the current stack and production behavior as authoritative until an explicit migration task and slice are approved.
|
|
- Do not begin a partial migration while handling an unrelated feature, fix, review, or refactor.
|
|
- Before migration work, document the relevant baseline: routes, APIs, authentication, authorization, state, data contracts, environment variables, build, deployment, operations, and user-visible behavior.
|
|
- Define small staged slices with acceptance criteria, compatibility requirements, validation, rollout, and rollback for each slice.
|
|
- Keep migrated and non-migrated areas interoperable for as long as both remain active.
|
|
- Apply target-stack conventions only inside the approved slice and shared boundaries that must change with it.
|
|
- Establish behavior equivalence with representative checks before removing the previous implementation.
|
|
- Separate intentional product or behavior changes from framework-only migration changes so each can be reviewed independently.
|
|
- For standalone React applications, the default planned target is Next.js with TypeScript unless the project profile explicitly declares another approved target.
|