verify-enum-values

You prevent enum string drift by validating literals against the backend source of truth in Enums.kt before writing them. This cross-file parity checking ensures Kotlin enums, dispatchers, handlers, and frontend types stay aligned.

Renaming an enum value safely requires verifying the exact literal against backend Enums.kt first, then updating every dependent layer consistently. This prevents runtime rejection and hard-to-trace failures across dispatchers, handlers, and CLI wrappers.

Runtime rejection occurs when frontend types experience enum string drift from the backend Enums.kt source of truth. Validating action types, phases, and roles literals before editing code prevents these silent bugs caused by mismatched string values.

You validate action types and role literals by checking them against backend/src/main/kotlin/com/werewolf/model/Enums.kt before editing any related code or documentation. This confirms the exact literal and maintains cross-file parity across all layers.

You can use this enum validation for shell scripts and CLI wrappers, not just Kotlin code. It verifies that any string literal referencing action types, phases, roles, statuses, vote contexts, or win conditions matches the backend source of truth.

You need to check enum parity across database constraints and documentation before changing any werewolf action, phase, or role value. Validating literals against backend Enums.kt ensures every dependent layer stays aligned and prevents silent bugs.