fix(release): restore Kova matrix contracts#23
Merged
Conversation
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
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.
What Problem This Solves
Kova
mainlost three release-validation contracts during history reconciliation: truncatedpayloads[].textrecovery, calibrated process resource caps, and auth/model configuration before the first real OpenClaw service start. That made OpenClaw beta release performance fail despite successful agent turns and expected resource use.Fixes #22.
Why This Change Was Made
--modelselection before the first service startThe explicit model option replaces OpenClaw workflow-time source rewriting and lets callers request GPT 5.6 through Kova public CLI.
User Impact
OpenClaw release performance can distinguish product regressions from harness regressions again. Live runs select the intended model before startup, and successful truncated agent responses no longer become false failures.
Evidence
npm run check(208/208)npm run test:snapshots(21/21)npm run check:web-payload(1/1)node --checkon changed modulesgit diff --check2f48202248a37aad357bd70a6953475cd4816f81