realign

Migrating persisted data during an enum realignment requires an explicit old→new mapping to drive both code changes and database migration logic. You must map, collapse, drop, or introduce values, then verify the migration safely transforms old rows without corrupting behavior.

A state vocabulary realignment changes the semantic meaning of domain model enums due to business requirement updates, requiring persisted data migration. A refactor preserves behavior, while cleanup involves no requirement change, so realignment prevents under-scoping migration work.

After renaming an enum at the type root, use the type checker to fix type leaks, then run a grep-based audit to find non-typed string usages, payloads, fixtures, docs, and UI-related named constants that reference the old state values.

Handling collapsed or dropped enum values during schema migration requires an explicit old→new mapping that defines how old values transform into the new meaning. Use the project's existing migration pattern to version and verify the persisted data transformation safely.

You can use the project's existing migration pattern if available, or add a minimal tracked migration runner if one is missing. The realignment process requires safe versioned migration verification to ensure persisted rows transform correctly.

Renaming state machine values without an explicit old→new mapping corrupts behavior because persisted rows still hold old values that no longer match the new semantic meaning. A realignment distinguishes semantic changes from refactors to ensure data migration logic matches code changes.