@clawsweeper review current head 8bfdd86f37c1708aef619344d7f16279f0e9c426. Adds structured dry-run repair effects for channel plugin blocker findings while leaving real plugin enablement as an explicit operator action. Focused proof is listed in the PR body.

🦞🧹
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.

Codex review: stale review; fresh review needed.

Summary
The latest durable ClawSweeper review was for head 8bfdd86f37017ea417945eb80e2c68656ecd0efe, but the PR head is now 9c44766ab51a5ba7fefa58960d1767020c6f3c6f. Its old verdict and PR readiness labels are no longer current.

Next step
Run or wait for a fresh ClawSweeper review on the current PR head.

Codex review finding:

The dry-run effect added for core/doctor/channel-plugin-blockers is not reachable from a supported Doctor command. The check adds a repair() implementation (src/flows/doctor-health-contributions.ts:1640-1667), but the contribution still supplies run: runStartupChannelMaintenanceHealth (src/flows/doctor-health-contributions.ts:1669). createDoctorHealthContribution only invokes runStructuredDoctorHealthContribution when run is omitted (src/flows/doctor-health-contributions.ts:144-151), so the new effect is skipped by openclaw doctor --fix. The shared structured repair pass only selects extension checks (src/flows/doctor-health-contributions.ts:440-453, src/flows/health-check-registry.ts:29-40), and the CLI makes --only a lint-only option (src/cli/program/register.maintenance.ts:42-83); there is no doctor fix --dry-run --only core/doctor/channel-plugin-blockers command path.

Best fix: wire this core check into an actual structured repair/dry-run entry point, or keep the blocker check detect-only and remove the unreachable repair effect/tests/body claim.

Accepted Omar's reachability finding and parked this PR.

This PR was only the structured dry-run backfill for core/doctor/channel-plugin-blockers. Since that repair hook is not reachable from a supported Doctor CLI path today, I reverted the PR content in 9c44766ab5 rather than leaving a misleading dry-run effect claim.

Current branch state:

• Diff against origin/main is empty.
• git diff --check passes.

Recommended next step: keep this PR parked/close it, and reintroduce channel plugin blocker dry-run effects only after we add a real supported core structured repair/dry-run entry point.