fix: accept canonical ClawSweeper comment commands

[SebTardif]

What changes

Ignore marked maintainer opt-in reminders before matching command text, so quoted commands do not create another dispatch. Keep the existing shared-router command set unchanged. Add regression tests that execute the workflow's actual prefilter shell, document the behavior, and thank @SebTardif in the changelog.

Validation

The reminder regression failed on the previous main branch and passed with the guard. All 31 tests passed locally and on Linux Crabbox; actionlint passed; independent Codex review found no actionable P0–P2 defects.

Exact-head Actions: https://github.com/openclaw/clawsweeper.bot/actions/runs/38954619857

Merged as 36005e7. Original contributor-hosted proof remains available at https://github.com/SebTardif/clawsweeper.bot/actions/runs/38833517729.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[vercel]

@SebTardif is attempting to deploy a commit to the OpenClaw Foundation Team on Vercel.

A member of the Team first needs to authorize it.

[clawsweeper]

Codex review: needs maintainer review before merge.

What this changes

This PR prevents marked maintainer opt-in reminders from triggering comment-command dispatch.

Example: A comment contains <!-- clawsweeper-maintainer-opt-in:opened item=42 --> followed by /review.

• Before: The prefilter admits the reminder and starts the acknowledgement and dispatch step.
• After: The prefilter rejects the reminder and skips that step.

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, correct fix supported by hosted workflow evidence and regression coverage.
Proof confidence	🐚 platinum hermit (4/6) ✨ media proof bonus	Sufficient (linked_artifact): Current-head GitHub-hosted issue-comment runs exercise the actual workflow prefilter and show reminder suppression, ordinary-candidate admission, and unsupported-form rejection. The supplied output identifies the unchanged missing-credential exit; credentialed downstream dispatch is outside this guard's behavior.
Patch quality	🦞 diamond lobster (5/6)	No actionable review findings were identified.

Product

Kind: Bug fix · Worth it: Yes · Fix scope: Complete
User problem: A bot reminder containing command text starts another command-dispatch attempt.
Reason: Suppressing explicitly marked reminders restores the established dispatcher behavior without changing user commands or defaults.

Merge readiness

✅ Ready for maintainer review

This PR fixes a current prefilter defect with a focused guard; the earlier unsupported-alias finding is resolved, and no blocking code findings remain.

Priority: P2
Reviewed head: 688c5bf95d528ce3012ccb96448786d12516d2ed

Before merge

None.

Findings

None.

Agent review details

How this fits together

The GitHub Actions dispatcher receives issue comments, filters command candidates, and forwards admitted comments to the shared ClawSweeper router.

flowchart TD
  A[GitHub issue comment] --> B[Comment prefilter]
  B --> C[Marked reminder ignored]
  B --> D[Command candidate]
  D --> E[Acknowledgement and dispatch]
  E --> F[Shared ClawSweeper router]

Loading

Technical review

Best possible solution:

Land the narrow reminder guard while preserving the existing command set.

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

Main's expression admits a reminder containing a separate /review line, and no marker guard prevents the resulting dispatch path.

Is this the best way to solve the issue?

The guard matches the shared dispatcher's established behavior and addresses the cause without expanding command support.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 13419ce4ddee.

Provenance checked

• Comment prefilter keeps the original intent (adca467: The original workflow filters command candidates before acknowledgement and forwarding; the new guard preserves that purpose while excluding generated reminders.)

Testing

Proof path: shipped entry point.

Security

None.

Evidence

What I checked:

• Focused introduced change: The pinned diff adds only the reminder-marker guard to production behavior; the existing command expression is unchanged. (.github/workflows/clawsweeper-dispatch.yml:49, 688c5bf95d52)
• Current-main behavior and provenance: Main still admits command text without checking the reminder marker. The original workflow addition contains that behavior; subsequent merged work in fix: keep comment commands out of the item concurrency group #2 addresses concurrency instead. (.github/workflows/clawsweeper-dispatch.yml:49, 13419ce4ddee)
• Earlier finding resolved: Comparison with the previously reviewed head confirms that the expanded slash aliases were removed and rejected-form coverage was added. (tests/comment-prefilter.test.mjs:45, 688c5bf95d52)
• Hosted behavior evidence: The issue-comment runs https://github.com/SebTardif/clawsweeper.bot/actions/runs/38833517729, https://github.com/SebTardif/clawsweeper.bot/actions/runs/38833553117, and https://github.com/SebTardif/clawsweeper.bot/actions/runs/38833554944 all use the reviewed head: reminder and unsupported-form runs skip acknowledgement, while the ordinary command candidate enters it. The workflow blob matches the reviewed file. Log downloads were blocked by the network allowlist, and the fork's issue-comment endpoint returned HTTP 410; accessible job records corroborate the supplied scenarios. (.github/workflows/clawsweeper-dispatch.yml:49, 688c5bf95d52)
• Authoritative dependency contract and scoped policy: The target workflow dispatches directly to this repository, and the PR relies on its parser contract, establishing the dependency-policy signal. Its full root AGENTS.md was read; its own release-file rules were not transferred to the target. The shared dispatcher has the same marker guard, and extractClawSweeperCommandLine confirms the rejected standalone forms are unsupported. (.github/workflows/clawsweeper-dispatch.yml:79, 983558446396)
• Checks and inspection limits: Current-head test and dispatch checks succeeded. Vercel reports an authorization gate before deployment, rather than a diff-caused failure. No target AGENTS.md or maintainer-notes directory exists. Local follow-history and merge-stat inspection encountered a missing historical object; available creation-commit content, path history, and blame establish the relevant behavior. The checkout remains clean. (688c5bf95d52)

Likely related people:

• Peter Steinberger: Raw commit adca467 adds .github/workflows/clawsweeper-dispatch.yml:42 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: adca46792e86; files: .github/workflows/clawsweeper-dispatch.yml)
• Sebastien Tardif: Raw commit 13419ce adds .github/workflows/clawsweeper-dispatch.yml:15 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 13419ce4ddee; files: .github/workflows/clawsweeper-dispatch.yml)

Labels

Label changes:

• add proof: sufficient: Contributor real behavior proof is sufficient.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🦞 diamond lobster.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.
• remove rating: 🦪 silver shellfish: Current PR rating is rating: 🐚 platinum hermit, 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: The defect queues unnecessary work for marked reminder comments, with limited blast radius.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🦞 diamond lobster.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.
• proof: sufficient: Contributor real behavior proof is sufficient.

Rating scale

6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

History

Review history (1 earlier review cycle)

• reviewed 2026-10-16T01:04:12.192Z sha 4ee6f77 :: needs real behavior proof before merge. :: [P2] Ensure newly admitted aliases are parsed before queuing them

Reviewed October 15, 2026, 9:13 PM ET / October 16, 2026, 01:13 UTC (Revision 2).

[SebTardif]

@clawsweeper re-review

[clawsweeper]

🦞👀
Exact review queued.

Re-review progress:

• State: Complete
• Detail: The durable review result and its route handoff completed.
• Run: https://github.com/openclaw/clawsweeper/actions/runs/38834020771
• Updated: 2026-10-16T01:14:33.753Z

[steipete]

Verified the regression on main and the fix at 58e1b58. The 31-test suite, actionlint, independent review, and exact-head Actions checks pass.