Prevent non-erased gauge version to have empty validity range This is a follow-up to revision ba0339118d9c, that did not introduce such constraint by virtue of missing that we have the information which gauge is 'current' readily at hand in the erased flag.

# documentation
**/README*
**/docs
**/*.md

# backend binary
cmd/gemma/gemma

# Dependency directories
**/node_modules

# local dotenv environment variables file
client/.env.local

# Tags tables
**/TAGS