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

Update the top-level status overview or service-summary path so a reachable Gateway suppresses or reclassifies user-systemd not installed rows for externally managed system services, while preserving gateway-status failure hints when RPC is not reachable.

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

Yes, source-reproducible: the linked report gives concrete Linux system-unit steps, and current main formats top-level service rows without considering gatewayReachable. I did not run a live Linux host in this read-only review.

Is this the best way to solve the issue?

No. Suppressing the daemon-printer hint is useful but not sufficient; the fix should cover the top-level openclaw status --deep overview/service-row path with focused regression coverage.

Label justifications:

• P2: This is a focused CLI diagnostics bug fix with limited blast radius but real operator confusion.
• merge-risk: 🚨 automation: The PR body can automatically close the linked report even though the reported top-level status surface is not fixed by the current diff.
• rating: 🧂 unranked krab: Current PR rating is 🧂 unranked krab because proof is 🧂 unranked krab, patch quality is 🧂 unranked krab, and Not merge-ready: the patch misses the reported status surface and the after-fix proof is mock-only.
• 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 reports only a mocked Linux unit test from a macOS source checkout, with no live Linux systemd-system Gateway 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.

Full review comments:

• [P2] Fix the top-level status rows too — src/cli/daemon-cli/status.print.ts:323
  This guard only affects printDaemonStatus, which is used by openclaw gateway status; openclaw status --deep still builds the Gateway service and Node service rows through readServiceStatusSummary and formatStatusServiceValue, so a reachable system-scoped Gateway can still show systemd user not installed. Because the PR body closes openclaw status --deep reports 'systemd user not installed' false positive when gateway runs under systemctl system #85094, please move or extend the fix to the top-level status overview path before merge.
  Confidence: 0.9

Overall correctness: patch is incorrect
Overall confidence: 0.9

What I checked:

• PR diff targets daemon status output: The changed condition is in printDaemonStatus, the openclaw gateway status printer, not the top-level openclaw status --deep overview path named in the linked report. (src/cli/daemon-cli/status.print.ts:323, 84329182a7c4)
• Top-level status uses separate service rows: openclaw status --deep builds its overview surface from gatewayService and nodeService summaries, then formats Gateway service and Node service rows through the shared overview row formatter. (src/commands/status.command.ts:268, 84329182a7c4)
• False-positive row path remains on main: When the user-scope service is not installed and runtime is not detected as running, formatStatusServiceValue returns <label> not installed; this path does not receive or check gatewayReachable. (src/commands/status-all/format.ts:151, 84329182a7c4)
• Service summary only treats runtime-running as external management: readServiceStatusSummary marks a service externally managed only when the service command is absent and state.running is true; a healthy system-scoped Gateway reachable over RPC is not used here. (src/commands/status.service-summary.ts:26, 84329182a7c4)
• Mock-only proof in PR body: The PR body says the real environment tested was a local macOS checkout with Linux mocked in the focused unit test, and explicitly says live Linux systemd system-service Gateway install was not tested. (7bccc6678fca)
• Current source attribution: Local blame attributes the central service-summary, overview formatter, and daemon-printer lines to commit 2b1c01f769a898964c6937564864c947f1541746; this is useful for routing current-main context, not for assigning fault. (src/commands/status.service-summary.ts:19, 2b1c01f769a8)

Likely related people:

• vincentkoc: Current-main blame for the top-level status formatter, service summary, and daemon status printer points to Vincent Koc's commit in the available local history. (role: recent area contributor; confidence: medium; commits: 2b1c01f769a8; files: src/commands/status-all/format.ts, src/commands/status.service-summary.ts, src/cli/daemon-cli/status.print.ts)

Codex review notes: model gpt-5.5, reasoning high; reviewed against 84329182a7c4.

• The egg game starts only after the PR passes the real-behavior proof check.
• Before that, no creature or rarity is rolled. The treat waits for real proof.
• This is still just collectible flavor: proof affects review readiness, not creature quality.