[douglasjarquin]

Summary

Grok launch qualification now accepts any stable build at 1.0.67 or newer.
The check was an exact match for 1.0.67, so coordinator start --harness grok refused grok 1.0.70 (f50904eaee6c) [stable].
Nightly builds, malformed version lines, and anything older than 1.0.67 still fail.
Codex, Claude, and Devin stay pinned to one version.

Validation

• I followed the contributor checklist. The change is limited to the Grok version floor, but the full verifier was not run.
• I recorded the canonical verification command, result, and evidence path. Not run. mise run verify was not executed, and there is no .artifacts/verification/ record. MISE_ENABLE_TOOLS=go mise exec -- go test ./internal/launch -count=1 -timeout 120s -run 'TestGrokAcceptsMinimumStableVersion|TestPrepare' passed in the dev checkout.
• I recorded applicable manual or live checks, including anything not run. coordinator start --harness grok was not rerun after the helper rebuild.
• I stated deployment or release impact when relevant. No release is staged. The checkout runtime uses the compiled .local/bin/sumctl, so the new floor is what ./bin/sumctl runs only after that helper is rebuilt from the merged tree. The local installation helper was rebuilt from this branch before the pull request.

Human review and the branch-protection owner decide merge readiness.