What issue are you seeing?

Two repository issue forms currently reference labels that do not exist in openai/codex, so new issues filed through those forms can miss the intended auto-labeling:

• .github/ISSUE_TEMPLATE/3-cli.yml declares labels: [bug, needs triage], but the repo does not have a needs triage label.
• .github/ISSUE_TEMPLATE/6-docs-issue.yml declares labels: [docs], but the repo does not have a docs label; the existing repo label is documentation.

This is a repo-owned workflow bug rather than a product behavior bug, but it directly affects issue triage quality and labeling consistency.

What steps can reproduce the bug?

1. Inspect the issue form definitions in the repo:
   • .github/ISSUE_TEMPLATE/3-cli.yml
   • .github/ISSUE_TEMPLATE/6-docs-issue.yml
2. Compare their declared labels with the current repo labels:

existing labels include:
- documentation
- needs-response

missing labels referenced by templates:
- needs triage
- docs

Repo-side evidence:

• 3-cli.yml currently contains:

labels:
  - bug
  - needs triage

• 6-docs-issue.yml currently contains:

labels: [docs]

• gh label list -R openai/codex shows documentation and needs-response, but not docs or needs triage.

Additional impact surface:

• the TUI feedback flow for external users builds GitHub issue links against template=3-cli.yml in codex-rs/tui/src/bottom_pane/feedback_view.rs, so that in-app path also routes through the affected CLI template metadata.

What is the expected behavior?

Issue forms should reference labels that actually exist in the repository, so issues opened from those forms receive the intended automatic labels.

Additional information

This looks like a narrow fix entirely within repo metadata:

• align the issue template labels with the current repo labels, or
• restore/create the missing labels if the template names are still the intended taxonomy.

I searched existing issues before filing and did not find one specifically tracking this issue-template label drift.