Best possible solution:

Land one focused Windows Scheduled Task normalization fix, preferably with this PR's profile and copy-style coverage, after redacted native Windows proof confirms managed tasks are skipped and extra tasks still warn.

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

Yes for a source-level reproduction: current main preserves the leading backslash, so \OpenClaw Gateway can miss the managed-task skip and flow into the extra-service warning path. I did not establish a live Windows reproduction in this read-only review.

Is this the best way to solve the issue?

Yes for the code shape: normalizing at the Windows task-name classifier keeps the fix local and preserves default/profile task handling while restoring warnings for copy-style tasks. It is not merge-ready until native Windows proof and duplicate-PR coordination are resolved.

AGENTS.md: found and applied where relevant.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 5d350e785a91.

Label justifications:

• P2: This is a focused gateway status/doctor false-positive fix with limited blast radius, but it can affect Windows users following cleanup guidance.
• rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🦪 silver shellfish and patch quality is 🐚 platinum hermit.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The supplied proof is mocked Windows-path Vitest output from macOS, and the PR explicitly says native Windows Task Scheduler execution was not tested; add redacted native schtasks, openclaw gateway status --deep, or openclaw doctor --deep output after this patch, then update the PR body so ClawSweeper can re-review automatically or ask a maintainer to comment @clawsweeper re-review.

PR surface:

Source +14, Tests +14. Total +28 across 2 files.

What I checked:

• Repository policy read: Root AGENTS.md was read fully and applied; no scoped AGENTS.md owns src/daemon, and the only maintainer note present is Telegram-specific. (AGENTS.md:1, 5d350e785a91)
• Current main source reproduction: On current main, isOpenClawGatewayTaskName lowercases the raw task name but does not strip a leading \, so \OpenClaw Gateway misses the durable OpenClaw Gateway comparison. (src/daemon/inspect.ts:201, 5d350e785a91)
• Windows scan entry point: The Windows deep scan parses schtasks /Query /FO LIST /V, checks isOpenClawGatewayTaskName, then reports remaining OpenClaw or legacy-looking tasks as extra services. (src/daemon/inspect.ts:509, 5d350e785a91)
• User-visible warning path: Daemon status prints nonempty extraServices as Other gateway-like services detected and emits the Windows cleanup hint from renderGatewayServiceCleanupHints. (src/cli/daemon-cli/status.print.ts:447, 5d350e785a91)
• Scheduled task naming contract: The durable Windows gateway task name is OpenClaw Gateway for the default profile and OpenClaw Gateway (<profile>) for named profiles. (src/daemon/constants.ts:54, 5d350e785a91)
• PR implementation evidence: The PR strips leading slashes before comparing task names and narrows managed-task recognition to the default or parenthesized profile naming shape, leaving copy-style tasks reportable. (src/daemon/inspect.ts:201, b913bb377f73)

Likely related people:

• steipete: Recent GitHub path history shows multiple daemon duplicate-service and schtasks-adjacent commits touching src/daemon/inspect.ts, src/daemon/inspect.test.ts, and src/daemon/schtasks.ts, including companion service false-positive work near this classifier. (role: recent area contributor; confidence: high; commits: dd0f5937d2b5, 3536c927dade, f348284fa9eb; files: src/daemon/inspect.ts, src/daemon/inspect.test.ts, src/daemon/schtasks.ts)
• Linux2010: Authored a recent Windows schtasks fallback fix in the daemon service area, which is adjacent to this PR's Windows Task Scheduler behavior even though not the exact classifier line. (role: adjacent Windows schtasks contributor; confidence: medium; commits: 501e74ddf34f; files: src/daemon/schtasks.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.