Labels

• bug

  bug

  Something isn't working

• clawsweeper:fix-shape-clear

  clawsweeper:fix-shape-clear

  ClawSweeper found a clear likely implementation shape for this issue.

• clawsweeper:linked-pr-open

  clawsweeper:linked-pr-open

  ClawSweeper found an open linked pull request for this issue.

• clawsweeper:needs-maintainer-review

  clawsweeper:needs-maintainer-review

  ClawSweeper marked this issue as needing maintainer review before automation.

• clawsweeper:needs-product-decision

  clawsweeper:needs-product-decision

  ClawSweeper marked this issue as needing a product or behavior decision.

• clawsweeper:no-new-fix-pr

  clawsweeper:no-new-fix-pr

  ClawSweeper does not recommend queueing a new automated fix PR for this issue.

• clawsweeper:queueable-fix

  clawsweeper:queueable-fix

  ClawSweeper marked this issue as an existing queue_fix_pr work candidate.

• clawsweeper:source-repro

  clawsweeper:source-repro

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

• dependencies

  dependencies

  Pull requests that update a dependency file

• documentation

  documentation

  Improvements or additions to documentation

• duplicate

  duplicate

  This issue or pull request already exists

• enhancement

  enhancement

  New feature or request

• github_actions

  github_actions

  Pull requests that update GitHub Actions code

• go

  go

  Pull requests that update go code

• good first issue

  good first issue

  Good for newcomers

• help wanted

  help wanted

  Extra attention is needed

• impact:other

  impact:other

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

• invalid

  invalid

  This doesn't seem right

• issue-rating: 🌊 off-meta tidepool

  issue-rating: 🌊 off-meta tidepool

  Issue quality rating does not apply to this item.

• issue-rating: 🦞 diamond lobster

  issue-rating: 🦞 diamond lobster

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

• merge-risk: 🚨 auth-provider

  merge-risk: 🚨 auth-provider

  🚨 Merging this PR could break OAuth, tokens, provider routing, model choice, or credentials.

• merge-risk: 🚨 automation

  merge-risk: 🚨 automation

  🚨 Merging this PR could break CI, automerge, proof capture, label sync, or automation.

• merge-risk: 🚨 compatibility

  merge-risk: 🚨 compatibility

  🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades.

• merge-risk: 🚨 other

  merge-risk: 🚨 other

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

• merge-risk: 🚨 security-boundary

  merge-risk: 🚨 security-boundary

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

• merge-risk: 🚨 session-state

  merge-risk: 🚨 session-state

  🚨 Merging this PR could lose, corrupt, stale, or mis-associate session or agent state.

• no-stale

  no-stale

  Exempts this issue from stale automation.

• P1

  P1

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

• P2

  P2

  Normal priority bug or improvement with limited blast radius.

• P3

  P3

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