Found during 0.4.0 RC local-command testing (2026-07-30).
Observed
$ chctl local use not.a.version
Error: No matching version found for: invalid version 'not.a.version': all parts must be numeric
(exit 1)
Two error layers are concatenated: the outer "No matching version found for:" (which expects a version string after the colon) wraps the inner parse error "invalid version '...': all parts must be numeric". The result reads as garbled — "no matching version found for: invalid version" is not a sentence.
Expected
A parse failure should short-circuit before the lookup path adds its wrapper:
Error: invalid version 'not.a.version': all parts must be numeric
Purely an error-plumbing fix in the version-resolution path (the inner error is already the right message).
Found during 0.4.0 RC local-command testing (2026-07-30).
Observed
Two error layers are concatenated: the outer "No matching version found for:" (which expects a version string after the colon) wraps the inner parse error "invalid version '...': all parts must be numeric". The result reads as garbled — "no matching version found for: invalid version" is not a sentence.
Expected
A parse failure should short-circuit before the lookup path adds its wrapper:
Purely an error-plumbing fix in the version-resolution path (the inner error is already the right message).