Possible signal types. The value must match the kvadblib value.
NOTE (known proto3 deviation): The zero value is SIGNAL_TYPE_INVALID rather than
SIGNAL_TYPE_UNSPECIFIED because the values are mapped directly to kvadblib constants
(0 = invalid/unrecognised type). Changing the zero value would require cascading
changes across the service implementation.
Possible signal types. The value must match the kvadblib value.
NOTE (known proto3 deviation): The zero value is SIGNAL_TYPE_INVALID rather than SIGNAL_TYPE_UNSPECIFIED because the values are mapped directly to kvadblib constants (0 = invalid/unrecognised type). Changing the zero value would require cascading changes across the service implementation.