Reconcile Win-CodexBar 0.61.0 release notes

[Finesssee]

Summary

• Reconcile the Windows 0.61.0 changelog with the provider, account, usage-detail, and CLI changes represented by the open port PRs.
• Set the Windows release metadata to 0.61.0 / build 149, matching the upstream 0.61.0 release line.
• Keep this closure lane documentation and metadata only; runtime port work remains in the linked PRs.

Dependencies

This closure PR is logically dependent on #556, #557, #558, #559, #560, #562, #565, #566, #567, #568, #569, and #570.

Validation

• git diff --check
• Exact changed-file set: CHANGELOG.md, version.env
• No build or generated target directory created because the worktree is operating under the storage floor; provider/runtime validation is covered by the individual port PRs and hosted CI.

[coderabbitai]

Warning

Review limit reached

Next included review available in 36 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 414372da-ad43-4685-906f-a7d1d148282b

📥 Commits

Reviewing files that changed from the base of the PR and between e1b7b06 and 4c7ab31.

📒 Files selected for processing (13)

• CHANGELOG.md
• apps/desktop-tauri/src-tauri/src/commands/bridge.rs
• apps/desktop-tauri/src-tauri/src/commands/provider_detail.rs
• apps/desktop-tauri/src-tauri/src/commands/providers.rs
• apps/desktop-tauri/src-tauri/src/commands/tests.rs
• apps/desktop-tauri/src-tauri/src/powertoys.rs
• apps/desktop-tauri/src-tauri/src/tray_bridge.rs
• apps/desktop-tauri/src-tauri/src/usage_metric.rs
• apps/desktop-tauri/src/components/MenuCardDetails.tsx
• apps/desktop-tauri/src/surfaces/settings/providers/sections/UsageSection.tsx
• apps/desktop-tauri/src/types/bridge.ts
• rust/src/core/usage_snapshot.rs
• version.env

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Finesssee]

0.61.0 upstream coverage audit

This note records the closure classification for the upstream 0.61.0 review. PR #571 remains metadata-only; no implementation code is added to it.

Windows-applicable lanes

• Antigravity b6d885ca — implemented in #574: final selected strategy IDs and outcomes are exposed in usage/diagnose output without fabricating fallback traces.
• Claude /usage settings e91635fc — implemented in #572: the Windows CLI probe keeps --settings {"remoteControlAtStartup":false} through one shared helper.
• Claude account switching 9a2f5e42 — implemented in #573: account changes wait for refresh/reconciliation before settling.

Windows-inapplicable upstream-only lanes

• Devin eac3f261 — N/A. The upstream change is the macOS browser local-storage session importer; Win-CodexBar uses the Windows Devin API/bearer and workspace/org path.
• Codex 19cafac8 — N/A. The upstream change is AppKit NSMenu tracking/rebuild behavior; Windows uses the React/Tauri account menu and event-driven reload path.
• Sharing fc2020a2 — N/A. The upstream change sanitizes a macOS ShareStatsPayload gateway/model-family field with no Windows equivalent; Windows sharing/reporting parity is covered by the applicable [0.60.5] Port usage spend sharing semantics #549 lane.

The three implementation PRs are sibling branches from codex/port-0.61.0-provider-details and are intentionally separate from this release-notes PR.

[Finesssee]

Thermo-Nuclear Review: PR #571 — Reconcile Win-CodexBar 0.61.0 release notes

Verdict: REQUEST CHANGES

Docs-only reconciliation (CHANGELOG.md + version.env), so applied proportionally: structure, consistency, and truthfulness of the notes. Two substantive findings: a shipped 0.60.x feature silently dropped from the release line, and a version bump that jumps the build number past anything the 0.60.x history supports.

Structural regressions

• The "Unreleased → 0.61.0" migration deletes the Grok Add account entry that was the sole content of the previous Unreleased section. Base CHANGELOG.md Unreleased read: "Grok: Settings and tray Add account flow matching Codex/Claude — isolated grok login --oauth, save current CLI login, switch, and remove without logging out the active session." That feature is real and shipped in 0.60.3's history (commit 6e44867, "Harden Grok multi-account persistence and usage UI (Harden Grok multi-account persistence and usage UI #538)", which includes "Add Grok account save/switch/add-login in Settings and the tray"), yet the rewritten ## [Windows] 0.60.3 section below does not mention it, and the new 0.61.0 section doesn't either. The entry has simply vanished from the changelog. A reconciliation PR's entire job is to make the notes match what shipped; this loses a user-facing feature line. Add it to the 0.61.0 "Added" list (or to the 0.60.3 section if the team dates Harden Grok multi-account persistence and usage UI #538 there) with its PR link.
• version.env jump BUILD_NUMBER=91 → 149 with MARKETING_VERSION 0.60.3 → 0.61.0 has no stated basis. The changelog shows the 0.60.x line ending at build 91 (0.60.3). Picking 149 invents ~58 build numbers with no explanation in the PR body ("matching the upstream 0.61.0 release line" does not explain why the build number jumps). If this mirrors an upstream build number, say so in a comment/PR note; if it's arbitrary, it's future Winget/updater confusion (AGENTS.md: version bumps should change only version-specific fields with care). Either justify it or move incrementally.

Missed simplification opportunities (code-judo)

• Not applicable to code, but one docs-judo note: the new "Highlights" bullets restate almost verbatim the five most-marketed "Added" entries. For a two-page changelog this duplication is cheap; keep only if this format is the established convention for previous releases (0.60.3 has no Highlights section — so this introduces a new layout at the same time as the reconciliation, which makes 0.61.0 structurally unlike every prior section). Either backport the Highlights format to older sections in a later pass or drop it here for consistency.

Spaghetti / branching complexity

• none found (docs).

Boundary / abstraction / type problems

• Not applicable (docs). One consistency check that does belong to "boundary": the PR body says this is "logically dependent on Port DeepSeek per-model spend from upstream 0.61.0 #556 … Port Replicate billing provider #570", but the notes are written as if all are merged (present tense, PR links). If any of those PRs shrink or are abandoned, these notes rot silently. Acceptable for a release-line draft kept "Unreleased"; just keep the dependency list in the body accurate until merge.

File-size / decomposition concerns

• none found. CHANGELOG.md grows by ~40 lines; well within reason.

Lower-priority notes

• "Windows port aligned to upstream CodexBar 0.61.0" is a header claiming parity for the entire upstream 0.61.0 line while the section then lists only the ported subset; earlier sections phrase this as "Windows port of upstream 0.56.8 → 0.60.3". Prefer the older phrasing ("Windows port of upstream 0.60.3 → 0.61.0") which describes a range actually covered.
• The PR's own validation (git diff --check, exact changed-file set) is proportionate for a docs lane; no CI concern since main-bound docs still ride the hosted gate per AGENTS.md.
• Cross-check done: every PR link (Port DeepSeek per-model spend from upstream 0.61.0 #556–Port Replicate billing provider #570) in the Added list exists as an open port PR targeting the same base, and names match their PR titles — the mapping itself is accurate.