Labels

• bug

  Something isn't working
• clawsweeper:current-main-repro

  ClawSweeper found a high-confidence current-main issue reproduction.
• clawsweeper:fix-shape-clear

  ClawSweeper found a clear likely implementation shape for this issue.
• clawsweeper:needs-live-repro

  ClawSweeper needs live local, crabbox, or manual validation to confirm this issue.
• clawsweeper:needs-maintainer-review

  ClawSweeper marked this issue as needing maintainer review before automation.
• clawsweeper:no-new-fix-pr

  ClawSweeper does not recommend queueing a new automated fix PR for this issue.
• clawsweeper:queueable-fix

  ClawSweeper marked this issue as an existing queue_fix_pr work candidate.
• clawsweeper:source-repro

  ClawSweeper found a high-confidence source-level issue reproduction.
• dependencies

  Pull requests that update a dependency file
• docker

  Pull requests that update docker code
• documentation

  Improvements or additions to documentation
• duplicate

  This issue or pull request already exists
• enhancement

  New feature or request
• feature: ✨ showcase

  ClawSweeper spotlight: unusually compelling feature idea for maintainer attention.
• github_actions

  Pull requests that update GitHub Actions code
• good first issue

  Good for newcomers
• help wanted

  Extra attention is needed
• impact:message-loss

  This issue is about lost, duplicated, misrouted, or suppressed channel messages.
• impact:other

  This issue has meaningful maintainer-visible impact outside the owned taxonomy.
• invalid

  This doesn't seem right
• issue-rating: 🐚 platinum hermit

  Good issue quality with a plausible reproduction path needing some confirmation.
• issue-rating: 🦀 challenger crab

  Exceptional issue quality: high-confidence current-main reproduction and actionable evidence.
• issue-rating: 🦞 diamond lobster

  Very strong issue quality with high-confidence source-level or clear reproduction.
• javascript

  Pull requests that update javascript code
• merge-risk: 🚨 compatibility

  🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades.
• merge-risk: 🚨 other

  🚨 Merging this PR has meaningful risk outside the owned taxonomy.
• merge-risk: 🚨 security-boundary

  🚨 Merging this PR could weaken sandboxing, authorization, credentials, or sensitive data.
• P1

  Urgent regression or broken agent/channel workflow affecting real users now.
• P2

  Normal priority bug or improvement with limited blast radius.
• P3

  Low-risk cleanup, docs, polish, ergonomics, or speculative feature.