[SebTardif]

Problem and behavior

ClawSweeper comments and item edits shared one GitHub Actions concurrency group. An overlapping edit could cancel an explicit review command; ignored bot-label runs could also displace useful work before the job filter ran.

Group runs by event type and comment identity, and isolate ignored bot labels. Edits to the same comment and superseding item metadata still cancel older runs as before. Adds 11 regression tests and a minimal, read-only pull-request/push CI workflow. Updates the pinned GitHub App token action from v3.2.0 to v3.3.0, which includes patched HTTP dependencies.

Validation

• The original workflow fails five new regression cases; the fixed workflow passes all 11.
• node --test --test-concurrency=2 tests/*.test.mjs
• actionlint -shellcheck= .github/workflows/*.yml
• Independent Codex P0–P2 review before landing.
• Existing hosted scheduler proof at the contributor's original head: comment succeeded, first edit cancelled, second edit cancelled, last edit succeeded. This demonstrates scheduling, not credential-dependent downstream dispatch.

Original concurrency fix by @SebTardif; maintainer completion adds tests, documentation, the changelog, and the action update.

[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 separates comment runs and ignored bot-label events from item-update concurrency groups.

Example: A review comment on fork pull request 1 is followed by overlapping body edits.

• Before: An edit can cancel the comment workflow because both use the same item concurrency group.
• After: Comment run 37850978898 succeeds while earlier item-update runs are cancelled and the last edit succeeds.

Review scores

Measure	Result	What it means
Overall readiness	🦞 diamond lobster (5/6)	A focused, useful scheduler repair with verified hosted behavior and no actionable correctness or security findings.
Proof confidence	🦞 diamond lobster (5/6) ✨ media proof bonus	Sufficient (linked_artifact): The changed GitHub Actions concurrency owner was exercised on GitHub-hosted runners using the reviewed head: the comment workflow survived overlapping item updates while earlier update runs were cancelled. The contributor explicitly excludes credential-dependent downstream dispatch, which this patch does not change.
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 requested review or automerge comment can lose its dispatcher run when the item is edited or synchronized.
Reason: Independent comment commands should survive unrelated item updates, and the patch repairs that behavior with one focused change.

Merge readiness

✅ Ready for maintainer review

This PR fixes a concurrency collision still present on current main; the hosted evidence supports the scheduler change, and no introduced defect was found.

Priority: P2
Reviewed head: 46a12f4cea9890971012bed37a53dd5f3340880e

Before merge

None.

Findings

None.

Agent review details

How this fits together

The GitHub Actions dispatcher receives issue, pull request, and comment events, applies scheduling and filtering, and forwards eligible events to ClawSweeper.

flowchart LR
  A[GitHub item events] --> C[Workflow concurrency]
  B[GitHub comment events] --> C
  C --> D[Event filtering]
  D --> E[Dispatch credentials]
  E --> F[ClawSweeper event dispatch]

Loading

Technical review

Best possible solution:

Keep the focused scheduler fix so item updates cannot cancel independent comment commands.

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

Current-main source assigns comments and edits on the same item to one group and enables cancellation for edits, establishing the cancellation path without running target code.

Is this the best way to solve the issue?

Separating scheduling identities at the workflow owner addresses the collision directly while retaining item-update supersession and existing dispatch behavior.

AGENTS.md: not found in the target repository.

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

Provenance checked

• Workflow concurrency grouping changes intended behavior with a stated reason (adca467: The workflow was added to dispatch ClawSweeper events. Commit inspection and the commit-to-PR lookup found no separate rationale requiring comments and item updates to cancel each other.)

Testing

Proof path: shipped entry point.

Security

None.

Evidence

What I checked:

• Pinned change and current-main behavior: The introduced diff changes only the concurrency group. Main groups all event types by item number; the patch adds event name, comment identity, and a separate suffix for bot-label events while preserving cancellation conditions. (.github/workflows/clawsweeper-dispatch.yml:15, 46a12f4cea98)
• Feature history: Scoped history, commit inspection, and blame identify steipete as the author and committer of the workflow addition. The commit states its dispatch purpose; GitHub reports no associated PR explaining intentional cross-event cancellation. (.github/workflows/clawsweeper-dispatch.yml:15, adca46792e86)
• Hosted scheduler proof: GitHub verifies that https://github.com/SebTardif/clawsweeper.bot/actions/runs/37850978898 ran the reviewed workflow head and succeeded during overlapping pull_request_target events. Runs 37850980806 and 37850986692 were cancelled; run 37850991214 succeeded. The temporary proof PR concurrency overlap proof SebTardif/clawsweeper.bot#1 has the reviewed commit as its base. Credential-dependent dispatch was explicitly outside this scheduler demonstration. (.github/workflows/clawsweeper-dispatch.yml:15, 46a12f4cea98)
• Discussion and deployment status: The contributor's fix: keep comment commands out of the item concurrency group #2 (comment) points to hosted overlap proof. The Vercel failure is an external-contributor deployment authorization gate, corroborated by fix: keep comment commands out of the item concurrency group #2 (comment), rather than a workflow defect. (46a12f4cea98)
• Canonical search and policy: All-state GitHub searches for concurrency and dispatch return only this PR. The checkout contains no AGENTS.md, VISION.md, or maintainer-note entries; repository policy permits closing only certainly implemented changes, which this PR is not. (adca46792e86)

Labels

Label changes:

No label changes.

Label justifications:

• P2: The existing workflow can cancel a requested command during item updates; the focused fix has limited scope.
• rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🦞 diamond lobster 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 (64 earlier review cycles; latest 8 shown)

• reviewed 2026-10-13T19:59:25.554Z sha 46a12f4 :: needs maintainer review before merge. :: none
• reviewed 2026-10-13T21:43:42.631Z sha 46a12f4 :: needs maintainer review before merge. :: none
• reviewed 2026-10-14T02:01:00.676Z sha 46a12f4 :: needs maintainer review before merge. :: none
• reviewed 2026-10-14T05:26:46.881Z sha 46a12f4 :: needs maintainer review before merge. :: none
• reviewed 2026-10-14T07:34:28.557Z sha 46a12f4 :: needs maintainer review before merge. :: none
• reviewed 2026-10-14T08:52:12.252Z sha 46a12f4 :: needs maintainer review before merge. :: none
• reviewed 2026-10-14T10:28:09.600Z sha 46a12f4 :: needs maintainer review before merge. :: none
• reviewed 2026-10-14T11:58:23.385Z sha 46a12f4 :: needs maintainer review before merge. :: none

Reviewed October 14, 2026, 10:23 AM ET / 14:23 UTC (Revision 65).

[SebTardif]

@clawsweeper re-review

The body now has hosted runs. A comment dispatch succeeded while two overlapping edits cancelled each other.

[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/37851632895
• Updated: 2026-10-08T22:09:28.787Z

[steipete]

Reviewed the concurrency fix and maintainer completion. Five regression cases fail against the previous workflow, and all 11 pass with this change locally and on Linux. Independent Codex P0–P2 review is clean. The same reviewed head also has successful tests, security analysis, and a Vercel preview through #3.

[steipete]

Merged through this original PR, with contributor credit preserved. Thanks @SebTardif.

The original workflow failed five concurrency regression cases. All 11 cases now pass locally and on Linux, and independent Codex review found no actionable P0–P2 issues. The reviewed PR head passed CI, security analysis, and Vercel preview checks. The cancelled legacy dispatch check passed on one retry.

Temporary maintainer PR #3 supplied the preview for the identical head without changing deployment authorization or repository security settings, and is now closed. The final change also updates the GitHub App token action to v3.3.0.