Best possible solution:

Refresh or replace the branch so the chosen Overview redesign preserves current-main token, loading, cron, and i18n behavior, includes redacted Control UI proof, and is reconciled with #86460.

Do we have a high-confidence way to reproduce the issue?

Yes. Source inspection of the PR head against current main shows the resolver removal, nullish-to-zero rail counts, disabled-cron warning path, and missing i18n key without needing a browser run.

Is this the best way to solve the issue?

No. The dashboard direction is plausible, but the best merge path must preserve current-main auth-token and rail semantics, add real visual proof, and settle the overlapping Overview direction first.

Full review comments:

• [P1] Restore scoped gateway token resolution — ui/src/ui/views/overview.ts:302-304
  The URL input now clears the token unless the raw trimmed URL is unchanged. Current main calls resolveGatewayTokenForUrlEdit, which keeps the token for same-normalized endpoint edits and reloads a scoped token for a known gateway switch.
  Confidence: 0.93
• [P2] Preserve unknown rail counts — ui/src/ui/views/overview.ts:92-94
compactCount turns null or undefined into 0, and the new rail uses it for nullable sessions and optional usage totals while Overview data can still be unloaded. That can falsely report zero sessions or messages before data exists.
  Confidence: 0.89
• [P2] Use the active cron failure predicate — ui/src/ui/views/overview.ts:277
  The rail checks job.state?.lastStatus === "error" directly, so disabled jobs with historical errors can still mark automation as warning. Current main centralizes this through isCronJobActiveFailure to count only enabled jobs as active failures.
  Confidence: 0.9
• [P2] Use a defined messages translation key — ui/src/ui/views/overview.ts:546-547
usage.metrics.messages is not present in the English locale bundle; the existing user-facing label is usage.overview.messages. As written, the rail can render the raw missing key.
  Confidence: 0.91

Overall correctness: patch is incorrect
Overall confidence: 0.93

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 010b61746379.

Label justifications:

• P2: This is a normal-priority Control UI feature with limited blast radius but concrete merge-blocking auth and rail defects.
• merge-risk: 🚨 compatibility: The PR changes existing Overview URL-edit and loading-state behavior in ways that can break current user expectations after upgrade.
• merge-risk: 🚨 auth-provider: The diff can clear or fail to reload gateway authentication tokens during URL edits and known gateway switches.
• merge-risk: 🚨 other: The rail can misreport operator state and the PR overlaps another active Overview redesign without a canonical direction.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🧂 unranked krab.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The PR body lists tests only and needs redacted after-fix Control UI proof such as a screenshot, recording, terminal/live output, linked artifact, or logs; private details should be redacted before posting proof. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

PR surface:

Source +385. Total +385 across 2 files.

What I checked:

• Root policy read: Read the full root AGENTS.md; its protected-label, read-beyond-diff, real-proof, auth/session compatibility, and UI review guidance affected this review. (AGENTS.md:20, 010b61746379)
• Scoped UI policy read: Read ui/AGENTS.md; its i18n source-of-truth guidance applies because the PR adds user-facing Overview rail labels. (ui/AGENTS.md:1, 010b61746379)
• Live PR state: Live GitHub state shows the PR is open, non-draft, conflicting/dirty, has the protected maintainer label, and has no maintainerCanModify flag enabled. (99cb556dd681)
• PR head removes scoped token resolver: The PR head clears the token unless the raw trimmed URL is unchanged, bypassing current-main scoped gateway-token behavior. (ui/src/ui/views/overview.ts:302, 99cb556dd681)
• Current-main token resolver contract: Current main calls resolveGatewayTokenForUrlEdit from the Overview URL input, and the helper preserves same-normalized endpoint tokens or reloads the scoped session token for a changed endpoint. (ui/src/ui/views/overview.ts:272, 010b61746379)
• Token resolver provenance: Merged PR fix(ui): preserve gateway token during safe websocket url edits #73923 introduced the current scoped-token resolver behavior on main. (ui/src/ui/storage.ts:203, 59950f7b5266)

Likely related people:

• BunsDev: Authored and merged the dashboard-v2 Overview refactor and usage overview styling that shaped the current Overview/card/CSS surface. (role: overview surface introducer and recent UI contributor; confidence: high; commits: f76a3c5225bb, a5309b6f93db, 3bbbe33a1b91; files: ui/src/ui/views/overview.ts, ui/src/ui/views/overview-cards.ts, ui/src/styles/components.css)
• omarshahine: Merged the Model Auth status card work that shares the Overview dashboard's provider/auth status surface. (role: recent adjacent Overview auth/status contributor; confidence: medium; commits: 507b7189177a; files: ui/src/ui/views/overview.ts, ui/src/ui/views/overview-cards.ts, src/gateway/server-methods/models-auth-status.ts)
• vincentkoc: Merged the PR that added resolveGatewayTokenForUrlEdit and the current Overview URL-edit token preservation behavior. (role: merger for current gateway-token resolver contract; confidence: high; commits: 59950f7b5266; files: ui/src/ui/storage.ts, ui/src/ui/views/overview.ts, ui/src/ui/views/overview.node.test.ts)
• ZengWen-DT: Authored the merged active-cron-failure fix whose current-main predicate the new rail bypasses. (role: recent adjacent Overview cron behavior contributor; confidence: high; commits: 9fa14ff61a85, ee7fbdfc3cbc; files: ui/src/ui/cron-status.ts, ui/src/ui/views/overview-cards.ts, ui/src/ui/app-settings.ts)
• steipete: History shows prior merged Control UI/Overview/CSS maintenance in this area, separate from authoring this proposed branch. (role: recent area contributor; confidence: medium; commits: f665da8dbcf3, 4505987b9c8b, 2380c1b5fd64; files: ui/src/ui/views/overview.ts, ui/src/styles/components.css)

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.