steve b3dce188e1 Fix version check failing on non-200 status responses ...

When the engine returns 401 (auth required) or other non-200 responses,
the version check was parsing the error body, getting an empty version
string, and fatally exiting. Now skips the check on non-200 responses
and lets the actual API call surface the real error.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-02 21:52:24 +01:00

..

client.go

Fix version check failing on non-200 status responses

2026-04-02 21:52:24 +01:00

version_test.go

Independent client/engine versioning with compatibility check

2026-03-28 15:59:16 +00:00