So far, in our codebase, we don't use `Unspecified` variant of protobuf enums. However It is required by protobuf format: https://cloud.google.com/apis/design/design_patterns#enum_default_value. It can be a source of bugs as seen in #8360. We will have occurrences of it, since we need to handle protobuf messages. However should ban its instantiation, e.g. ```rs let x = <MESSAGE>::Unspecified ``` We can do so via clippy.