Is this intended behaviour that if we do InputAction.Disable() (which is under the hood call DisableControls), then call InputAction.Reset() which changes state to InputActionPhase.Waiting but not touching controls, and then call InputAction.Enable() controls stays disabled, because Reset changes phase and Enable as result wont call EnableControls because it will do early out here
As result controls will be disabled forever until we again call Disable for setting a phase to InputActionPhase.Disabled and then can call Enable which will do the job and will enable controls.
At least we should have some error\warning about that, at best this case should be covered IMO
Simple reproduce case:
Get any InputAction, call Disable() (under the hood will also do DisableControls), call Reset() (which will change state to Waiting), call Enable() - Which will do nothing (look initial message)