fix(cli): explain older Harness schema as a version mismatch - #1079
Merged
berenddeboer merged 1 commit intoAug 14, 2026
Merged
Conversation
A newer CLI talking to a still-running older Harness failed `candidates` and `status` with `GRAPHQL_VALIDATION_FAILED` and an internal field name (`intakeCandidates`, `kanbanStatus`). Those commands exist in `--help`, so the output read as a broken CLI rather than "restart the Harness." Missing GraphQL fields this CLI requires are now remapped to `HARNESS_VERSION_MISMATCH`. The message names this CLI version, the Harness origin, the operator command, and how to upgrade (`ready-for-agent start`). When the Harness can answer `Query.version`, the message also names the server version; pre-`version` servers omit that clause. Also added `Query.version` on the Harness and ran the Bun/Nx TypeScript shim from pre-commit so `typescript-sync` keeps `readConfigFile`. Verified with CLI error-mapping tests, process contracts for old `candidates`/`status` (with and without `Query.version`), GraphQL `version` tests, and the Effect CLI suite. A review note about duplicated process-test servers was left as-is to match the existing contract style. Closes #1072
berenddeboer
marked this pull request as ready for review
August 14, 2026 08:32
berenddeboer
deleted the
rfa/berenddeboer-ready-for-agent/1072/wi-01KZZMAWQCVKQZT53RS9NZ5E1Z
branch
August 14, 2026 08:32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A newer CLI talking to a still-running older Harness failed
candidatesand
statuswithGRAPHQL_VALIDATION_FAILEDand an internal field name(
intakeCandidates,kanbanStatus). Those commands exist in--help,so the output read as a broken CLI rather than "restart the Harness."
Missing GraphQL fields this CLI requires are now remapped to
HARNESS_VERSION_MISMATCH. The message names this CLI version, theHarness origin, the operator command, and how to upgrade
(
ready-for-agent start). When the Harness can answerQuery.version,the message also names the server version; pre-
versionservers omitthat clause.
Also added
Query.versionon the Harness and ran the Bun/Nx TypeScriptshim from pre-commit so
typescript-synckeepsreadConfigFile.Verified with CLI error-mapping tests, process contracts for old
candidates/status(with and withoutQuery.version), GraphQLversiontests, and the Effect CLI suite. A review note aboutduplicated process-test servers was left as-is to match the existing
contract style.
Closes #1072