@clawsweeper re-review

Current head 22689ec has all visible GitHub checks passing (lint-build-test, Linux x64 CLI, Linux ARM64 CLI, GitGuardian). This is ready for review on the green head.

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

• State: Failed
• Detail: The targeted re-review timed out or was rate-limited while waiting for exact-review Codex capacity, and the bounded capacity retry limit is exhausted.
• Run: https://github.com/openclaw/clawsweeper/actions/runs/27722847758
• Updated: 2026-06-17T22:28:15.844Z

Maintainer repair pushed at fb8936e25c95cc9c9ea17d1fa6e22648b2f440d0.

Changes:

• Keep Codex and Claude plan-history recording always on.
• Require the existing historical-tracking opt-in before generic providers record new history.
• Keep already-saved generic history visible after opt-out.
• Detect generic weekly charts by actual 10,080-minute windows, including primary-only and extra-window snapshots.
• Use extra weekly windows only as fallback, preserving a provider's standard weekly quota.
• Ignore reset-only usageKnown=false extras for persistence and chart filtering.
• Add changelog credit for @kiranmagic7.

Proof:

• swift test --filter 'UsageStorePlanUtilizationTests|PlanUtilizationHistoryChartMenuViewTests' - 44 tests passed.
• make check - format, locale, and strict lint gates passed with zero violations.
• Full branch Codex autoreview - no accepted/actionable findings (0.86 confidence), after fixing two P2 findings.
• Ad-hoc exact-head package passed deep strict code-sign verification.
• Packaged app E2E with isolated config and a live local z.ai HTTP fixture: app stayed alive, made 3 provider requests, and persisted schema v1 weekly history with windowMinutes: 10080 and usedPercent: 42.
• Existing historicalTrackingEnabled state and z.ai history were restored byte-for-byte/absence-for-absence; normal app relaunched; worktree clean.

A real-account z.ai run was attempted first. 1Password was visibly locked after inactivity and op could not proceed without the master unlock, so no secret was read or exposed. The packaged fixture still exercises the exact app startup, provider HTTP fetch, refresh, opt-in gate, persistence coordinator, and on-disk provider-history document path.

Post-#1572 rebase: exact candidate is now eda0636.

Only the adjacent changelog insertion conflicted; both contributor credits were preserved. The 44 focused history/chart tests passed again and the branch diff check is clean. CI restarted on this head.