Best possible solution:

Keep the narrow prefilter, preserve generic github_activity forwarding for ordinary comments, and merge only after maintainers verify both non-command and supported-command issue_comment behavior on the exact head.

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

Yes from source inspection: current main creates the target comment token for every issue_comment before the later grep exits on non-command comments. I did not run a live GitHub Actions reproduction in this read-only review.

Is this the best way to solve the issue?

Yes, this is the narrow target-repo fix for the OpenClaw ingress side: move command detection before target write-token minting while leaving generic activity forwarding intact. The remaining best-fix requirement is live dispatch proof against the receiver contract.

AGENTS.md: found and applied where relevant.

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

Label changes:

• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🦞 diamond lobster.
• remove rating: 🦐 gold shrimp: Current PR rating is rating: 🐚 platinum hermit, so this older rating label is no longer current.

Label justifications:

• P2: This is a normal-priority maintainer automation fix with limited product blast radius but concrete ClawSweeper workflow impact.
• merge-risk: 🚨 automation: The diff changes the GitHub Actions gate that decides whether ClawSweeper comment commands are acknowledged and dispatched.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🦞 diamond lobster.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: The external-contributor real behavior proof gate is not applicable because this is a maintainer-labeled MEMBER PR, though live Actions log proof would still reduce automation risk.

PR surface:

Tests +25, Config +18, Other +10. Total +53 across 6 files.

What I checked:

• Current main mints the target token before filtering: Current main creates the target comment token for every issue_comment with app credentials, then filters command-looking comments later inside the acknowledgement/dispatch script. (.github/workflows/clawsweeper-dispatch.yml:84, b796890b9777)
• PR head moves the filter earlier: The PR head adds comment_filter and gates both Create target comment token and Acknowledge and dispatch ClawSweeper comment on is_command == true. (.github/workflows/clawsweeper-dispatch.yml:84, b5389b59e46b)
• Receiver command contract checked: The ClawSweeper receiver accepts /auto merge, /autoclose, /review, /clawsweeper, and mention commands, matching the target-side prefilter's intended command family. (openclaw/clawsweeper/src/repair/comment-command-text.ts:17, 855cffa7c7ae)
• Current documentation describes the ClawSweeper lanes: docs/ci.md documents the target-side workflow as the OpenClaw bridge into ClawSweeper, with a distinct clawsweeper_comment lane for explicit commands and github_activity for general activity. Public docs: docs/ci.md. (docs/ci.md:83, b796890b9777)
• Companion ClawSweeper work exists: The PR body's companion work is reflected by merged openclaw/clawsweeper PRs fix(ci): reduce ClawSweeper GitHub API pressure clawsweeper#343 and docs: align ClawSweeper comment prefilter clawsweeper#345, which reduce GitHub API pressure and align target-dispatcher docs.
• Workflow validation is partly green: Live checks show actionlint, no-tabs, check, dependency guard, and security-sensitive guard succeeded for the current head; several broader CI/CodeQL jobs were still pending during review. (b5389b59e46b)

Likely related people:

• vincentkoc: Recent OpenClaw workflow and script-routing history shows Vincent Koc carrying the affected ClawSweeper dispatch and Windows taskkill routing surfaces. (role: recent area contributor; confidence: high; commits: fe1d981a47af, 4f8fd48ea76e, e486a1d1cf7e; files: .github/workflows/clawsweeper-dispatch.yml, scripts/test-projects.test-support.mjs, scripts/lib/windows-taskkill.mjs)
• steipete: Commit history on the dispatch workflow shows Peter Steinberger introducing and hardening the ClawSweeper command and activity dispatch paths. (role: workflow feature contributor; confidence: medium; commits: 3e67ee63b4e0, 5d2ee19e5abb, 1327f6742fd5; files: .github/workflows/clawsweeper-dispatch.yml)
• brokemac79: Blame on the ClawSweeper receiver command parser points to brokemac79 for the current exact command-line parsing contract that this target prefilter must preserve. (role: adjacent receiver parser contributor; confidence: medium; commits: a07fc1f94; files: openclaw/clawsweeper/src/repair/comment-command-text.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.