Skip to content

fix(transport): prohibit flash model fallback in review/debate#394

Merged
RyderFreeman4Logos merged 1 commit intomainfrom
fix/no-flash-in-review-debate
Mar 10, 2026
Merged

fix(transport): prohibit flash model fallback in review/debate#394
RyderFreeman4Logos merged 1 commit intomainfrom
fix/no-flash-in-review-debate

Conversation

@RyderFreeman4Logos
Copy link
Owner

Summary

Retry behavior

Scenario Retry sequence
csa run (default) original -> pro -> flash -> API key fallback
csa review / csa debate original -> pro -> API key fallback (no flash)

Test plan

  • Unit test: test_no_flash_fallback_stops_retry_after_attempt_2
  • All 2466 unit + 16 e2e tests pass
  • just pre-commit clean

Review and debate require high-quality reasoning models. The transport
retry loop previously could degrade from pro to flash on quota errors,
which is unacceptable for these quality-critical paths.

- Add _CSA_NO_FLASH_FALLBACK env signal, respected by retry logic
- When set, max retry attempts reduced from 3 to 2 (skips flash)
- Inject signal in review_cmd.rs and debate_cmd.rs extra_env
- Also inject _CSA_API_KEY_FALLBACK in review/debate (was missing)
- Add test verifying no-flash stops retry at attempt 2
@chatgpt-codex-connector
Copy link

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@RyderFreeman4Logos
Copy link
Owner Author

Merge Rationale

Cloud bot: disabled (pr_review.cloud_bot = false)

Local review coverage:

  1. Cumulative review: csa review --branch main via claude-code — PASS (session 01KKBB6EX7D)

Test results: 2466 unit + 16 e2e tests pass. just pre-commit clean.

@RyderFreeman4Logos RyderFreeman4Logos merged commit 8338a43 into main Mar 10, 2026
4 of 6 checks passed
@RyderFreeman4Logos RyderFreeman4Logos deleted the fix/no-flash-in-review-debate branch March 10, 2026 07:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant