feat: upstream cli adaptation and settlement rework (0.0.35) - #34
Merged
Conversation
…cy codex plugin state
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.
summary
--output-schemaflows end to end (rescue raw args, exec argv, structured output capture, astructured:render footer), adversarial review gains a json schema verdict contract, and the 0.144.4 models cache schema drift workaround is deleted with the tested interval moving to 0.145.0 to 0.146.0grok doctorcapability and reports it as an advisory, ordinary managed runs require--no-wait-for-backgroundunconditionally, and best-of-n is retired so grok's protected roles shrink to four (burst, independence, live-web, large-context)engine-acceptance.mjs,/fusion:statsrecords every verdict through the one--record <id>=<verdict>form, a verdict recorded before the worker record turns terminal queues and settles automatically on the terminal transition, and the worker lifecycle backfills peer identity from rescue wrapper stops (the SubagentStop matcher now also coverscodex:codex-rescue,grok:grok-rescue, andgrok:grok-review-runner)breaking changes
/fusion:stats --record-acceptanceand--record-worker-acceptanceare removed; use--record <id>=<verdict>[:accept-failed-transport]/grok:best-of-nskill, thebest-of-nprotected role, and--transport-default-best-of-nare removedFUSION_CODEX_INCLUDE_LEGACYand thecodex-openai-codexcompatibility state root are no longer read, and legacycompleted/failedterminal statuses are no longer recognized--background-wait-timeoutfallback, requiring a grok cli that supports--no-wait-for-backgroundtest plan
already verified
npm test-> 896 pass, 0 fail, 1 skip (897 tests)node bench/manifest.mjs --check-> manifest up to datereviewer should verify