remove-feature-flag

Removing a stabilized feature flag requires deleting its Cargo feature entry, stripping the FeatureFlag enum variant, and eliminating all conditional runtime checks to ensure no remaining flag-based behavior persists in the codebase.

Cleaning up dead branches from stabilized feature flags involves removing the flag from Cargo.toml, deleting the FeatureFlag enum variant, and eliminating obsolete keybindings, then validating the removal with a build and test suite to prevent regressions.

When deleting a feature flag, update Cargo features by removing the declaration from Cargo.toml, and update runtime checks by deleting all conditional logic branches associated with that flag to ensure the feature is permanently enabled.

Yes, removing a feature flag requires updating governance tracking such as DOGFOOD_FLAGS and release notes to reflect permanent removal, ensuring full traceability and preventing future confusion about the flag's status.

Manually removing feature flags without automated validation risks introducing regressions because leftover conditional checks or obsolete keybindings may persist, making it essential to validate the refactor with a build, tests, and a PR review.