Start

Work Lane

GitHub Edit page

Work Lane

ClawSweeper reviews remain proposal-only. A review may now mark an open item as a queue_fix_pr work candidate when the report looks valid, narrow, and safe for a single ClawSweeper repair PR.

Reports store the lane fields in frontmatter:

  • item_category
  • reproduction_status and reproduction_confidence
  • requires_new_feature, requires_new_config_option, and

    • requires_product_decision

  • work_candidate: none, manual_review, or queue_fix_pr
  • work_status: none, manual_review, or candidate
  • work_priority and work_confidence
  • work_cluster_refs, work_validation, and work_likely_files

The dashboard shows fresh queue_fix_pr reports whose work_status is candidate. This is a manual promotion queue for the repair lane.

#Reproducible Bug Auto-Implementation

The automatic issue implementation lane is stricter than the manual work queue. It can create a PR only for reviewed issues that are exactly:

  • item_category: bug
  • reproduction_status: reproduced
  • reproduction_confidence: high
  • work_candidate: queue_fix_pr
  • work_confidence: high
  • requires_new_feature: false
  • requires_new_config_option: false
  • requires_product_decision: false

This intentionally excludes mixed feature/config/product work. If a fix would add a flag, setting, new mode, provider support, broad UX behavior, dependency, or maintainer policy choice, the review must not classify it as an automatic bug implementation candidate.

After review publish, sweep.yml scans the just-produced artifacts and dispatches repair-issue-implementation-intake.yml for eligible reports when CLAWSWEEPER_AUTO_IMPLEMENT_REPRO_BUGS=1. The intake workflow re-fetches the live issue, rejects protected/security/locked items, skips issues that already have an open PR reference or existing ClawSweeper implementation PR, writes the normal source: issue_implementation job, commits the ledger, then dispatches repair-cluster-worker.yml in autonomous mode.

Comment-triggered issue implementation uses the same durable job format. If a worker starts before the new state commit is visible in its checkout, the worker reconstructs the minimal source: issue_implementation job from the job path and continues instead of treating the dispatch as stale.

PRs created from this path are labeled clawsweeper and clawsweeper:autogenerated. The lane is PR-only: it does not merge or close the source issue. When a worker opens the PR from a maintainer command, it edits the existing ClawSweeper command status comment with the generated PR link so the same comment moves from queued to opened.

Promote a candidate from this checkout:

cd ~/Projects/clawsweeper
pnpm run repair:create-job -- \
  --from-report records/openclaw-openclaw/items/123.md
pnpm run repair:validate-job -- jobs/openclaw/inbox/clawsweeper-openclaw-openclaw-123.md

Commit and push the generated job, then dispatch mode: autonomous when the execution window is intentionally open. The repair lane checks for an existing open PR/body match and the clawsweeper/<cluster-id> branch before creating a duplicate job.