[WRONG BRANCH] chore(release): promote verified candidate to 2.43.0 preview - #3677
Conversation
* fix(subagents): migrate featured roster to Astra first and 5.5 last * test(subagents): exercise malformed arrays and failed migration persistence * fix(subagents): retain rebased config through later startup migrations --------- Co-authored-by: t <a@b.com>
…dence (#3614) Owner-authorized corrective admin merge. Revalidates post-wait combo presence and matches fatal UTF-8 quota evidence handling. Typecheck/static verification passed; no local tests. Final dev Linux CI is the batch gate.
Owner-authorized admin squash of child-only #3551 carry onto corrected #3608. Scheme-matched proxy snapshot, explicit proxy transport binding, exact IPv6 prefix and NO_PROXY denial retained. Existing source security assessment and current static/typecheck evidence recorded. No local tests; final dev Linux CI is the batch gate.
Owner-authorized corrective admin merge. Verifies copied runtime bytes and rejects unexpected sources and symlinks without including Git metadata. Typecheck/static checks passed; no local tests or Docker execution. Final dev HEAD CI is the gate.
Owner-authorized final-CI repair: concrete Linux quota route and fixture failures corrected; typecheck/static checks passed, no local tests. Final dev HEAD CI is the gate.
Owner-authorized diagnostic follow-up for the actual Linux restart failure. Only the fixture launcher is instrumented; production behavior, assertions and time budgets unchanged. Raw output redacted. No local tests; next dev HEAD CI is the execution gate.
…ccount-quota-api # Conflicts: # devlog/_plan/260905_provider_usage_quota_parity/040_stack_landing.md
fix(quota): repair Windows reset fixtures and route inventory
fix(responses): preserve caller cancellation in eager SSE relay
…ttribution # Conflicts: # skills/ocx/references/01_management_surface.md # src/cli/capabilities.ts # src/server/management/route-registry.ts # tests/usage/quota-reset-notify.test.ts
…ttribution # Conflicts: # tests/usage/quota-reset-notify.test.ts
* feat(gui): unify quota activation under advanced settings * docs: attach privacy-safe unified quota settings screenshot * docs(gui): explain ordered quota activation writes * fix(gui): preserve unavailable opt-ins when enabling quota activation * docs: refresh quota control verification screenshot * fix(i18n): clarify per-account quota activation scope --------- Co-authored-by: t <a@b.com>
…cycle feat(responses): bounded canonical upstream WS reuse
…oseout-split-train
refactor: consolidate verified modularization train and closeout records
* feat: enable Fast selectors by default across external clients * fix: count Fast variants in OpenCode launch summary * fix: align suffix-shaped Fast discovery with ingress --------- Co-authored-by: t <a@b.com>
…#3670) * feat(xai): default Grok Responses and migrate legacy Chat choices * fix(responses): carry code-mode output guidance on the first turn * fix(xai): retain post-upgrade Chat choice through reauthentication * docs(xai): record first-output and isolated control verification * test(responses): build signature scrub fixture through the real parser * fix(xai): preserve OAuth account rotation on native Responses * test(xai): use a short synthetic refresh credential in the fixture * test(xai): explicitly select Chat in the Chat streaming regression --------- Co-authored-by: t <a@b.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Important Review skippedToo many files! This PR contains 1959 files, which is 1659 over the limit of 300. To get a review, reduce the PR to 300 files or fewer by splitting it into smaller PRs or changing its base branch. Usage-priced reviews support at most 300 files. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: ⛔ Files ignored due to path filters (40)
📒 Files selected for processing (1959)
You can disable this status message by setting the |
|
✅ Deterministic PR hygiene checks passed. |
리뷰 · 우선순위 77 / 80이 PR은 제품 기능을 새로 넣는 패치가 아닙니다. 오너가 고른 개발 후보 지금 헤드라인으로 실리는 최근 줄기는 tip의 Grok Responses 기본( 라인 메인테이너의 판단이 필요한 지점
너의 추천 이 댓글은 grok-bot이 작성했습니다 |
⏳ DRAFT
What to do
Its title has been prefixed with |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5c2d63465d
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| // rare (one per real reset), so the write cost is irrelevant. | ||
| // A failed write is reported rather than swallowed: the caller reads true as "safe to | ||
| // dispatch", and an unpersisted claim re-notifies on the next start. | ||
| return persistNow(); |
There was a problem hiding this comment.
Roll back the claim when persistence fails
When atomicWriteFile fails transiently—for example because the disk is full—persistNow() returns false, so the observer correctly skips dispatch, but the newly added key remains in claims. Later observations then treat the reset as already claimed, and their debounced baseline writes can persist that unsent claim once storage recovers, permanently suppressing the notification. Remove the new claim when persistence fails, or represent it as retryable until a durable write succeeds.
Useful? React with 👍 / 👎.
Summary
Promote the owner-approved development candidate af50c6d to preview as 2.43.0-preview.20260906. The owner explicitly directed shipping this candidate now and leaving pending fixes for later.
The promotion preserves preview history and the pinned candidate ancestry. The resolved tree differs from the candidate only in package.json version. No new production behavior is introduced by this promotion.
This is a maintainer-controlled release promotion. The dev-only target check is an expected promotion exception. The owner-requested administrative PR merge will be recorded here; no self-approval is claimed. Functional release gates remain required on the final preview commit.
Verification
Promotion carries the already-reviewed interface change from #3670; original implementation screenshot:
Checklist