Gate standards selection with the author range only
An author’s requires.repo-standards range says which CLI versions the author
tested when an adopter selects that standards version. Repository Standards
also re-validated the range from the retained manifest during a CLI update, so
an exact or upper-bounded range stranded every established adopter: the pinned
CLI could not select the next standards version, and the next CLI could not
update the retained one. The range now gates selection of a standards version
only. A CLI update validates the retained standards against the candidate CLI’s
supported source formats, which the product owns. Authors are told to declare an
open-ended minimum. The trade-off is that an adopter can run a CLI the author
never tested against their standards; the format version carries that
compatibility promise instead of the author.