Best possible solution:

Keep the cleanup, reconcile the public-surface budget for the intended export reduction, refresh onto current main, and merge only after exact-head CI is green or explicitly maintainer-classified.

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

Not applicable: this is a cleanup PR, not a bug report with a failing user path. The merge blocker is reproducible from exact-head CI via the plugin SDK surface budget check.

Is this the best way to solve the issue?

Not yet: localizing implementation-only UI exports is the right cleanup shape, but the submitted branch is not merge-ready until the public-surface budget and current-main CI drift are reconciled.

Full review comments:

• [P2] Update the public-surface budget for removed exports — ui/src/components/config-form.ts:2
  This branch removes exports, and exact-head CI now reports the pinned/configured public-surface budget is stale: plugin-sdk-surface-report.test.ts expected exports: 10460 while the branch reports 10458. Please update the intended surface budget for the merged result, or keep the exports if they are still meant to remain public.
  Confidence: 0.91

Overall correctness: patch is incorrect
Overall confidence: 0.88

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 6273e82ca55a.

Label changes:

• add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
• add status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: The author is a repository member and this is an internal cleanup PR, so the external contributor real-behavior proof gate does not apply.
• remove rating: 🐚 platinum hermit: Current PR rating is rating: 🦐 gold shrimp, so this older rating label is no longer current.
• remove status: 👀 ready for maintainer look: Current PR status label is status: ⏳ waiting on author.

Label justifications:

• P3: This is a low-risk internal Control UI cleanup with a small validation/baseline blocker and no claimed user-visible behavior change.
• rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
• status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: The author is a repository member and this is an internal cleanup PR, so the external contributor real-behavior proof gate does not apply.

PR surface:

Source -9, Tests -13. Total -22 across 11 files.

Acceptance criteria:

• [P1] Run or request the exact-head CI equivalent for checks-node-compact-small-whole-2, or node scripts/run-vitest.mjs run --config test/vitest/vitest.tooling.config.ts --reporter=verbose.
• [P1] Confirm test/scripts/plugin-sdk-surface-report.test.ts passes with the intended merged public-surface count.
• [P1] Confirm exact-head lint is green after rebasing onto current main.

What I checked:

• Repository policy read: Root AGENTS.md was read fully and its PR-review, protected-label, UI cleanup, and CI-proof guidance was applied. (AGENTS.md:1, 6273e82ca55a)
• Scoped UI policy checked: ui/AGENTS.md was read; it only adds i18n/generated-locale constraints, which this PR does not touch. (ui/AGENTS.md:1, 6273e82ca55a)
• Live PR state: Live metadata shows an open member PR at head 7399c88 with the protected maintainer label. (7399c888e808)
• Removed export consumer check: At the PR head, the targeted symbols only appear at local definitions, same-module call sites, or updated tests; no remaining cross-module consumer of the removed exports appeared in the UI tree. (7399c888e808)
• Pairing behavior remains covered: The PR-head tests assert resolvePairingHint directly for the same pairing-required, connected, null, unrelated, and auth-error cases formerly covered through the wrapper. (ui/src/lib/overview-hints.node.test.ts:76, 7399c888e808)
• Exact-head CI budget failure: The current CI run for head 7399c88 failed test/scripts/plugin-sdk-surface-report.test.ts because the branch reports exports: 10458 while the pinned/configured budget expected 10460. (test/scripts/plugin-sdk-surface-report.test.ts:129, 7399c888e808)

Likely related people:

• steipete: Merged the recent Control UI PR that owns several touched modules and authored adjacent session-group work used by the affected UI paths. (role: merger and adjacent UI contributor; confidence: high; commits: e5e721fdc5de, 52d929288fb1, 5157446a2c35; files: ui/src/lib/overview-hints.ts, ui/src/lib/sessions/custom-groups.ts, ui/src/lib/sessions/session-options.ts)
• SnoutFirst: Authored the merged Control UI PR whose squashed merge commit currently owns the overview-hints and config-form modules touched by this cleanup. (role: recent area contributor; confidence: medium; commits: e5e721fdc5de, d4e9d21b3368; files: ui/src/lib/overview-hints.ts, ui/src/lib/overview-hints.node.test.ts, ui/src/components/config-form.ts)
• vincentkoc: Recent merged export-localization PRs by this author touched the same Control UI cleanup theme, and this PR continues that bounded surface-reduction work. (role: adjacent cleanup owner; confidence: medium; commits: 9d86728795e0, 7399c888e808; files: ui/src/app/config.ts, ui/src/app/context.ts, ui/src/components/config-form.node.ts)

• 🦀 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.

• reviewed 2026-07-07T02:10:20.429Z sha 003c0e0 :: needs maintainer review before merge. :: none