opencode_cli version range 1.18.31-1.18.34, 1.19.0-1.19.3 #712

As an OpenCode user on any recent 1.18.x/1.19.x, I want SkillSpector to accept my CLI version so a patch release does not break my scans.

The gap

The provider exact-pins one version, so every upstream patch release locks out users until a new pin PR lands. The runtime debug config resolved-subset check is the load-bearing safety net and already re-verifies the deny-all policy per invocation; the version gate can widen without weakening fail-closed.

What I am asking for

Please accept the releases that are individually verified: 1.18.31 through 1.18.35 and 1.19.0 through 1.19.3. Keep rejecting prereleases and unparsable output, keep both gates (preflight + auth check) plus the debug config subset check. Done when users on any verified release get scans and anything outside still fails closed.

Note on the shape (updating the original ask)

The original ask was an inclusive MIN/MAX range. Review feedback (and the fact that a raised MAX can silently admit an unverified patch) settled on an explicit verified set instead: nine exact triples, each with its own evidence, never a range. The set is the implementation of this request; each future widening is one triple plus one evidence line.

This could be achieved by

• Keeping one shared predicate used by both gates over an explicit set of verified triples, with error messages listing the verified members
• Boundary tests (accept every member; reject 1.18.30, 1.18.36, 1.19.4, prerelease, garbage, empty) and a live matrix per version
• OpenCode 2.x (preview, no stable release yet) is tracked separately