Skip to content

fix: order thinking variants and prepare v1.0.62 - #709

Merged
LeXwDeX merged 1 commit into
mainfrom
fix/variant-effort-order
Oct 3, 2026
Merged

LeXwDeX merged 1 commit into
mainfrom
fix/variant-effort-order

Conversation

@LeXwDeX

@LeXwDeX LeXwDeX commented Oct 3, 2026 •

Copy link
Copy Markdown
Owner

Why

Ctrl-T followed variant object insertion order. Merging configured low and medium variants into generated high and max variants could make the cycle run high, max, low, medium.

What changed

Order available reasoning variants after the final provider configuration merge and disabled-variant filter. The TUI, app, and direct-run interface now receive known effort names in increasing order. Existing parameters, saved selections, and the default-mode cycle remain intact. Include the v1.0.62 release notes.

Closes #708

Evidence

The regression reproduced the old order before the fix. The release checkout passed 486 focused provider, transform, variant, boot, and release-helper tests. All 31 workspace typecheck tasks passed. Lint passed its unchanged 4850-warning limit with 4834 warnings and no errors. Formatting and release-note rendering passed.

An isolated source TUI completed 11 Ctrl-T steps from default through the available variants and back to default. Screen labels and persisted selections matched at every step. The app cycle tests passed (7 tests). Direct footer rendering, layout, and menu tests passed (27 tests, 5 existing skips). The test created no sessions or messages and left no running process. Astra reviewed the final five-file patch.

Native CI passed on PR head 6cf7909: Typecheck and Linux unit tests plus Linux/Windows E2E. The unit job also passed the Go tests, both client generation checks, and HTTP API gates.

Typecheck attempt 1 hit the existing 3-second schema-validation subprocess watchdog. The 14 schema-budget tests passed once locally with coverage, and the complete Typecheck job passed unchanged on attempt 2. No tests or timeout limits were changed.

Checklist

  • Validate with the pinned Bun, Node, and Go versions.
  • Keep the change limited to the ordering fix, regression tests, and release notes.
  • Preserve disabled variants, request parameters, and persisted selection identity.
  • Validate the derived v1.0.62 notes before release.
  • Require all four native CI checks to pass on the PR head before merge.

@LeXwDeX
LeXwDeX marked this pull request as ready for review October 3, 2026 20:25
@chatgpt-codex-connector

Copy link
Copy Markdown

The account paying for this security review has reached its Codex usage limits. The payer can check the Codex usage dashboard. For personal accounts, using credits requires enabling “Use credits for security reviews” in Code review settings. If you do not manage the paying account, contact this repository's admins.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 3, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-03T20:28:04.584802Z 6cf7909 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@LeXwDeX
LeXwDeX merged commit 23b9c4f into main Oct 3, 2026
9 of 14 checks passed
@LeXwDeX
LeXwDeX deleted the fix/variant-effort-order branch October 3, 2026 20:56
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.

fix: order reasoning variants by increasing effort

1 participant