Repository navigation
Conversation
Every Opus stage in the blocking code-review fleet (claude-review.yml discovery and validation, fork-opus-review.yml, and the adjudication stage of codex-review.yml / fork-gpt-review.yml) runs on us.anthropic.claude-opus-5-5 with us.anthropic.claude-sonnet-5-5 as the overload fallback. The GPT lanes (codex-review.yml, fork-gpt-review.yml) run on openai.gpt-6.1-sol. The lanes are named by their model, so the check, job, step, comment and readiness spellings move from "Opus 5 Review" / "GPT 5.6 Review" to "Opus 5.5 Review" / "GPT 6.1 Review": the four lane workflows, pr-readiness.yml's workflow_run list and both mapping specs, the human-override rerun table, cross-references in code-review / design-review / ux-review / fork-ux-review, docs/ci/ci-and-reviews.md and the tests that pin those spellings. The prepare-pr profile mirrors the CI pins (opus claude-opus-5.5 / tier claude-sonnet-5.5, gpt gpt-6.1-sol / tier gpt-6.x). ADJ_CLAUDE_CODE_FLOOR stays 2.1.255; the comment records that the new pins surfaced no higher floor. The Fable lanes and their opus-4-8 fallbacks, MODEL_IDS in issue-summary / issue-triage / ship-report, gui-user-test.yml, the product model registry and historical mentions are unchanged. Closes #16240
First Principles Review (Fable 5) — 🟡 CONCERNSPremise-level review of First-Principles-Verdict: CONCERNS The Sonnet 5.5 fallback id ships unverified and no green run will ever prove it — it only exercises during an Opus 5.5 overload, exactly when it must work. Not justified as shipped
What this change shipsInventory (9 items) — 8 justifiedIntent: upgrade the two blocking review lanes to the current model generation per maintainer decision #16240 — an ADDITION (maintenance upgrade), description and diff agree.
Rename sweep verified: [FIRST-PRINCIPLES-REVIEWED] 0a504b0 Description read[DESCRIPTION-READ] 7ed8da4a021f8a61fffb393259e0532cf48ff92b730c0c2bfd8788d2f85d696e That sha256 names the PR description this verdict read. Recompute it with |
Design Review (Fable 5) — 🟡 CONCERNSDesign-level review of Design-Verdict: CONCERNS The overload fallback Watch
[DESIGN-REVIEWED] 0a504b0 Description read[DESCRIPTION-READ] 35d879f13b8b9ade7d3eb419e016ac385ac39c12284a7c154498a51c95789f0f That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
|
Superseded by #16238 (opened 15 min earlier by @bolichen97), which carries the piece this PR is missing. Root cause of the red |
Problem / Motivation
The two blocking code-review lanes run one model generation behind what the fleet can use: the Opus lane (and the GPT lane's Opus adjudicator) on Claude Opus 5 with Opus 4.8 as overload fallback, the GPT lane on GPT 5.6 Sol. Maintainer decision (#16240): move the review lanes to Claude Opus 5.5 with Claude Sonnet 5.5 as fallback, and GPT 6.1 Sol.
Why it matters
Every same-repo and fork PR is gated on these two verdicts, and the GPT lane hands its blocking candidates to the same Opus model for adjudication. The one required check (
PR Readiness) is a function of these lanes, so their model is the quality ceiling of the merge gate.What changed (motivation → approach → change)
.github/workflows/)claude-review.ymldiscovery + validation,fork-opus-review.yml, the adjudication stage incodex-review.ymlandfork-gpt-review.yml— runs--model us.anthropic.claude-opus-5-5--fallback-modelfromus.anthropic.claude-opus-4-8tous.anthropic.claude-sonnet-5-5codex-review.ymlandfork-gpt-review.ymlconfig.toml:model = "openai.gpt-6.1-sol"Opus 5 Review→Opus 5.5 Review,GPT 5.6 Review→GPT 6.1 Reviewwherever the name is live check identity: workflow/job/step names, the fork check-runs,pr-readiness.yml(workflow_run.workflows:and both mapping specs plus the prefix table), theai-review-human-override.ymlrerun table, cross-references incode-review.yml,design-review.yml,ux-review.yml,fork-ux-review.ymlADJ_CLAUDE_CODE_FLOORstays2.1.255(pinned@anthropic-ai/claude-code2.1.263 satisfies it); its comment now records that the floor was set for Opus 4.8 (#9216) and Opus 5 / Opus 5.5 / Sonnet 5.5 surfaced no higher oneprofiles/kirocrew.json: opus reviewermodel→claude-opus-5.5,model_tier→claude-sonnet-5.5; gpt reviewermodel→gpt-6.1-sol,model_tier→gpt-6.x;SKILL.mdrepair-preference table names the GPT 6.1 lanedocs/ci/ci-and-reviews.mdnames the lanes and the Sonnet 5.5 fallback; the tests that pin these spellings followSame shape as #12988 (Opus 4.8 → Opus 5), which is the precedent for the rename surface.
Deliberately unchanged: the Fable lanes (design / first-principles / ux / security-scope / fix-loop) and their
--fallback-model us.anthropic.claude-opus-4-8, theMODEL_IDSlists inissue-summary/issue-triage/ship-report,gui-user-test.yml, the#9216incident wording ("Opus 4.8's 2.1.255 floor" is a fact), the human-override"Fable 5"log label,release.yml's historical "GPT 5.6 review on 2ce9bce" note,CHANGELOG.md, and every product model-registry file undersrc/kiro_crew/model_registry*,website/**and their tests.Merging this PR. Branch protection (
protected-branchesruleset) requires onlyPR Readiness, so no ruleset edit.pr-readiness.ymlruns frommain, whereworkflow_run.workflows:still lists the old names, so these two lanes' completion on this PR does not itself re-trigger readiness; readiness still resolves them (same-repo spec is keyed by workflow file) and is recomputed by every other lane's completion and by the 15-minute sweep. #12988 merged green this way. After merge, in-flight PRs show the renamed lanes as missing until their next push; self-healing.Backwards compatibility
Compatible: no required check is orphaned, the review markers (
<!-- claude-ai-review -->,<!-- codex-ai-review -->,[OPUS-REVIEWED],[GPT-REVIEWED],[BLOCK-MERGE]) and theopus/gptdisposition targets are unchanged, and/ai-review override opus|gpt <sha>keeps its external-id lanes.Tests
test/test_ai_review_workflows.py— lane, step and adjudication spellings; the adjudicator pin assertion checks--model us.anthropic.claude-opus-5-5explicitly; the GPT config assertion checksopenai.gpt-6.1-sol.test/test_pr_readiness_evaluate.py,test_pr_readiness_publish.py,test_pr_readiness_sweep.py— readiness log line, check-run names, prefix table.test/test_prepare_pr_profiles.py,test_prepare_pr_local_review.py— profile model assertions;test_opus_profile_model_matches_the_ci_workflownormalizesus.anthropic.claude-opus-5-5→claude-opus-5.5and passes against the new--modellines.Ran locally: the six files above, 1572 passed (
-n0). YAML of every changed workflow parses;kirocrew.jsonparses;scripts/docs-lint.shpasses. black: the three test files that differ are already in the baseline onmain(no new unformatted code). The full suite is CI's.Manual verification
git grep -n -E "Opus 5 Review|GPT 5\.6 Review|gpt-5\.6-sol"leaves onlyrelease.yml's historical note.kiro-cli chat --list-modelsservesclaude-opus-5.5but lists neithersonnet-5.5norgpt-6.1-sol, and Bedrock was not reachable from the authoring desk. This PR's ownOpus 5.5 ReviewandGPT 6.1 Reviewruns are the live probe: a same-repopull_requestrun executes the head's own workflow file, so a model Bedrock does not serve fails that lane closed here and nothing lands onmain. If either lane fails on a model-not-found / access-denied forus.anthropic.claude-sonnet-5-5oropenai.gpt-6.1-sol, the right move is to report it on ci(review): move code-review lanes to Opus 5.5 (fallback Sonnet 5.5) and GPT 6.1 Sol #16240, not to substitute another model. The Sonnet 5.5 fallback and the adjudication stage only exercise when Opus 5.5 overloads / GPT raises a blocking candidate, so a green run proves the primaries, not the fallback id.Related Issues
Closes #16240
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)