Labels

• bug

  bug

  Something isn't working

• codex:blocked

  codex:blocked

  Codex could not complete because quota, permissions, or another external blocker must be resolved.

• codex:needs-rerun

  codex:needs-rerun

  A new push or stale result means @codex review should be requested again.

• codex:needs-review

  codex:needs-review

  A Codex review is needed for the current PR head.

• codex:review-requested

  codex:review-requested

  A Codex review was requested or should be running automatically.

• codex:reviewed

  codex:reviewed

  Codex posted a review result or thumbs-up after the latest request.

• codex:setup-issue

  codex:setup-issue

  Codex could not run because account, connector, environment, or repo setup is missing.

• 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

• good first issue

  good first issue

  Good for newcomers

• help wanted

  help wanted

  Extra attention is needed

• invalid

  invalid

  This doesn't seem right

• javascript

  javascript

  Pull requests that update javascript code

• merge-risk: 🚨 automation

  merge-risk: 🚨 automation

  May affect CI, review automation, proof capture, or label sync.

• merge-risk: 🚨 compatibility

  merge-risk: 🚨 compatibility

  May break existing users, config, migrations, defaults, or upgrade paths.

• merge-risk: 🚨 data-loss

  merge-risk: 🚨 data-loss

  Can lose, corrupt, or silently drop user, session, or config data.

• merge-risk: 🚨 other

  merge-risk: 🚨 other

  Merging this PR has meaningful risk outside the owned taxonomy.

• merge-risk: 🚨 security-boundary

  merge-risk: 🚨 security-boundary

  May affect sandboxing, authorization, credentials, or sensitive data.

• P0

  P0

  Emergency: data loss, security bypass, crash loop, or unusable core runtime.

• P1

  P1

  High-priority user-facing bug, regression, or broken workflow.

• P2

  P2

  Normal priority with limited blast radius.

• P3

  P3

  Low-priority cleanup, docs, polish, ergonomics, or speculative work.

• proof: missing

  proof: missing

  No verifiable behavior proof has been supplied yet.

• proof: sufficient

  proof: sufficient

  The supplied proof is convincing enough for review routing.

• proof: supplied

  proof: supplied

  The PR includes structured after-fix behavior proof.

• proof: 🎥 video

  proof: 🎥 video

  The PR includes video or recording evidence.

• proof: 📸 screenshot

  proof: 📸 screenshot

  The PR includes screenshot evidence.

• python

  python

  Pull requests that update python code