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

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

Best possible solution:

Land this only after the Doctor repair stack is rebased or merged cleanly, maintainers accept the initial preview and SDK contract, and broad Doctor proof confirms preview mode stays non-mutating.

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

Not applicable as a bug reproduction. For review risk, the stack/mergeability issue is reproducible with git apply --check, and the PR body provides terminal proof for the new preview behavior.

Is this the best way to solve the issue?

Unclear until maintainer contract review: the implementation direction is coherent, but the public CLI/SDK schema and stacked branch state need explicit acceptance before merge.

Label changes:

• add proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-patch terminal proof for the Doctor dry-run/diff JSON command in an isolated WSL setup, including parsed output and a non-mutation check.
• add rating: 🦐 gold shrimp: Current PR rating is 🦐 gold shrimp because proof is 🐚 platinum hermit, patch quality is 🦐 gold shrimp, and The proof is now useful, but the patch remains a broad draft stack with mergeability and public-contract risk.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): The PR body includes after-patch terminal proof for the Doctor dry-run/diff JSON command in an isolated WSL setup, including parsed output and a non-mutation check.
• remove rating: 🧂 unranked krab: Current PR rating is rating: 🦐 gold shrimp, so this older rating label is no longer current.
• remove status: 📣 needs proof: Current PR status label is status: 👀 ready for maintainer look.

Label justifications:

• P2: This is a normal-priority Doctor CLI feature with meaningful but bounded blast radius.
• merge-risk: 🚨 compatibility: The PR exposes new Doctor preview JSON/diff fields and public health-check SDK exports that users or plugins can depend on.
• merge-risk: 🚨 security-boundary: The preview path covers security, policy, sandbox, auth, config-audit, and service repair surfaces where non-mutating behavior must hold.
• merge-risk: 🚨 availability: The patch routes core Doctor repair/preflight behavior, so a bad merge could break openclaw doctor repair or preview runs.
• rating: 🦐 gold shrimp: Current PR rating is 🦐 gold shrimp because proof is 🐚 platinum hermit, patch quality is 🦐 gold shrimp, and The proof is now useful, but the patch remains a broad draft stack with mergeability and public-contract risk.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): The PR body includes after-patch terminal proof for the Doctor dry-run/diff JSON command in an isolated WSL setup, including parsed output and a non-mutation check.
• proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes after-patch terminal proof for the Doctor dry-run/diff JSON command in an isolated WSL setup, including parsed output and a non-mutation check.

What I checked:

• Current main CLI behavior: Current main registers doctor --lint and --json as lint-only options and has no Doctor dry-run or diff preview flags. (src/cli/program/register.maintenance.ts:24, 299ed808347c)
• PR CLI surface: The PR adds --dry-run, --diff, and broader --json option text, then routes dry-run/diff into doctorCommand as repair preview options. (src/cli/program/register.maintenance.ts:24, a2cf3c5bb714)
• Preview non-mutation path: The PR makes preview mode set repair intent for Doctor flow while passing non-repair config options, suppressing presentation notes for JSON, and disabling legacy config/state preflight migrations. (src/flows/doctor-health.ts:11, a2cf3c5bb714)
• Preview report aggregation: The PR routes selected structured health checks through the repair runner and appends findings, changes, warnings, effects, diffs, and counts into the preview report. (src/flows/doctor-health-contributions.ts:440, a2cf3c5bb714)
• Public SDK contract change: The PR exports defineSplitHealthCheck and new runnable health-check types from the public openclaw/plugin-sdk/health surface, making compatibility review necessary. (src/plugin-sdk/health.ts:8, a2cf3c5bb714)
• Real behavior proof in PR body: The PR body reports a WSL source-checkout run of node --import tsx src/entry.ts doctor --fix --dry-run --diff --json against an isolated fake home, with parsed preview JSON and no legacy config copy created. (a2cf3c5bb714)

Likely related people:

• steipete: Peter Steinberger authored the Doctor flow-contribution refactor and appears repeatedly in recent Doctor/CLI/docs history for the affected files. (role: feature-history owner; confidence: high; commits: 7d6d642cb825, 755263499672; files: src/flows/doctor-health-contributions.ts, src/flows/doctor-repair-flow.ts, docs/cli/doctor.md)
• vincentkoc: Vincent Koc has recent history on Doctor health checks and nearby core refactors that affect the structured health-check surface. (role: adjacent area contributor; confidence: medium; commits: 8143b9a23ead, 74e7b8d47b18; files: src/flows/doctor-core-checks.ts, src/commands/doctor-claude-cli.ts)
• joshavant: Josh Avant worked on SecretRef and doctor/status hardening, which is relevant because this PR previews security-sensitive Doctor auth and config paths. (role: adjacent security/SecretRef contributor; confidence: medium; commits: da34f81ce237, a2cb81199e22; files: src/commands/doctor-auth.ts, src/commands/doctor-gateway-health.ts)
• gumadeiras: Gustavo Madeira Santana has history on session and cron maintenance hardening, which overlaps the PR's structured repair preview coverage. (role: adjacent session/cron contributor; confidence: medium; commits: eff3c5c70778; files: src/commands/doctor-session-locks.ts, src/commands/doctor-cron.ts)

Codex review notes: model gpt-5.5, reasoning high; reviewed against 299ed808347c.

• Eggs appear after the PR passes real-behavior proof. It is here for vibes, not verdicts: it does not change labels, ratings, merge decisions, or automation.
• The shell reacts to review momentum: open follow-up work warms it up, re-review makes it wobble, and a clean final review lets it hatch.
• Hatchability usually comes from sufficient real-behavior proof, no blocking P0/P1/P2 findings, no security attention needed, and clean correctness. A merged PR is already final, so merge makes the egg hatchable independently.
• The hatch is seeded from this repository and PR number, so the same PR keeps the same creature; the reviewed head SHA can only change safe visual details.
• Rarity is just collectible sparkle: 🥚 common, 🌱 uncommon, 💎 rare, ✨ glimmer, and 🌈 legendary.