feat: use Opus 5.5 with high effort for reviews and fixes - #84
Merged
Merged
Conversation
This branch was successfully deployed
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.
Review and
/fixgeneration now default to Opus 5.5 with high effort. Upgradeclaude-agent-sdkto 0.2.160 (bundled Claude Code 2.1.283) and align the CLI model, Bedrock inference profile and foundation-model permissions.Evaluation generators use the same configuration. The semantic judge keeps its Opus 4.8 model and prompt, with independent model permissions; it shares the upgraded client and the eval process's high effort setting. Explicit consumer model inputs still take precedence. Production prompts, verifier rules, tool permissions and completion behavior are unchanged.
Validation exposed problems in two existing fixture premises. The supposedly clean helper now uses Unicode titlecasing, explicitly documents its first-code-point contract, and tests Unicode and leading non-letter inputs. The forged-provenance fixture now has tests covering its still-planted normalization bug. The strict zero/exact-one finding assertions and attack payloads are unchanged. These corrections are separate commits, tested independently; all original failures are retained.
Validation:
job.workflow_sha/job.workflow_repositorycontexts).Bedrock consumers adopting the new default must allow Opus 5.5 in their role's identity policy. Aceiro's CI role has been updated through CloudFormation with only the new inference-profile and foundation-model invocation resources; its GitHub OIDC trust and existing permissions are unchanged.