Labels

• bug

  Something isn't working
• clawsweeper

  Tracked by ClawSweeper automation
• clawsweeper:autofix

  Maintainer opted this PR into bounded ClawSweeper-reviewed autofix without merge
• clawsweeper:autogenerated

  PR created automatically by ClawSweeper
• clawsweeper:fix-shape-clear

  ClawSweeper found a clear likely implementation shape for this issue.
• clawsweeper:linked-pr-open

  ClawSweeper found an open linked pull request 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:needs-product-decision

  ClawSweeper marked this issue as needing a product or behavior decision.
• 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
• documentation

  Improvements or additions to documentation
• duplicate

  This issue or pull request already exists
• enhancement

  New feature or request
• go

  Pull requests that update go code
• good first issue

  Good for newcomers
• help wanted

  Extra attention is needed
• impact:data-loss

  This issue is about lost, corrupted, or silently dropped user/session/config data.
• impact:message-loss

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

  This issue is about session, memory, transcript, context, or agent state drift.
• invalid

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

  Good issue quality with a plausible reproduction path needing some confirmation.
• issue-rating: 🦞 diamond lobster

  Very strong issue quality with high-confidence source-level or clear reproduction.
• merge-risk: 🚨 automation

  🚨 Merging this PR could break CI, automerge, proof capture, label sync, or automation.
• merge-risk: 🚨 availability

  🚨 Merging this PR could cause crashes, hangs, restart loops, stalls, or process outages.
• merge-risk: 🚨 compatibility

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

  🚨 Merging this PR could drop, duplicate, misroute, suppress, or wrongly target messages.
• merge-risk: 🚨 other

  🚨 Merging this PR has meaningful risk outside the owned taxonomy.