realign

What problem does it solve?

Realignments rename a domain model’s meaning (e.g., enum/state vocabulary) and may require migrating persisted data so old values are transformed into the new meaning without corrupting behavior.

Core Features & Use Cases

• Confirm realignment scope: Distinguishes realignment from refactor (behavior-preserving) and cleanup (no requirement change) to prevent under-scoping migration work.
• Explicit old→new mapping: Forces an agreed mapping (mapped, collapsed, dropped, and newly introduced values) that drives both code changes and migration logic.
• Type-first then grep sweep: Renames at the type/enum root, uses the type checker to fix leaks, then audits non-typed string usages, payloads, and fixtures (including docs and UI-related named constants).
• Production-grade migration guidance: Ensures persisted data migration is done via the project’s existing migration pattern (or adds a minimal tracked migration runner if missing), with verification and an optional data-integrity review pass.

Quick Start

Ask your agent to realign a renamed enum/state vocabulary and migrate any persisted rows from the old values to the new values while updating all non-typed string leaks.