chore(issues): apply the feature-request label from the feature request form

[Quick104]

Problem

Related issue: N/A
Validation tasks: none

Feature requests filed through the issue form only get the enhancement label, which maintainers also put on their own work items. The community bot now gives each triaged feature request a post in a Discord forum where members can discuss it, and it finds those issues by a dedicated feature-request label. This form now applies that label, so requests filed through it qualify once triage adds triaged.

Approach

Adds feature-request to the form's labels; enhancement stays, so existing searches and filters keep working. Requests filed another way get the label during triage. The label already exists here, and silo-server gets the same change in Silo-Server/silo-server#2103.

Validation

• The form parses, and its labels are enhancement and feature-request; the label exists in this repository.
• Not run: app builds and tests, since only the issue form changed.

Evidence

Evidence: https://evidence.siloserver.org/r/silo-android/feature-request-label/

Risks

None identified.

Checklist

• I read and can explain the complete diff.
• This pull request addresses one concern.
• The Evidence section shows every change a user can see, or says there is none.

AI Disclosure

• Harness: Claude Code, run inside T3 Code
• Tool(s): Claude Code
• Model(s): claude-opus-5-5[1m]
• Involvement: Fully AI-generated, human verified
• Adversarial review: n/a

🤖 Generated with Claude Code

Note

Add feature-request label to feature request issue template

Updates the labels field in feature-request.yml so issues from this template also get the feature-request label. The existing enhancement label remains.

^{Macroscope summarized 5d25ea0.}

[silo-kody]

Silo Kody — review complete

Review finished. Check the inline comments for findings and verify each suggestion against the code and tests.

Reviewing changes in Silo

• Include the related issue, expected behavior, and validation steps in the PR description.
• For API changes, describe the effect on Apple and Android clients and Jellyfin compatibility.
• For plugin changes, identify the affected SDK contract, plugin, and catalog entry.
• Follow this repository's AGENTS.md and CONTRIBUTING.md.
• Request another review with @kody start-review in a PR comment.
• React with 👍 or 👎 to give feedback on individual suggestions.

Review settings

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	❌

⚠️ 1 Kody Rule(s) were not evaluated

These rules declare that they need repository context beyond this diff, and the review could not retrieve it, so they were not judged on this pull request:

• Validate download ownership before publishing subtitle bytes

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-08T16:02:01.801602Z	5d25ea0	PR opened
🔒 Security Review	✅ Completed 2026-10-08T16:02:45.264936Z	5d25ea0	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 1986828a-a367-4b4d-8ad4-812a7bcc1b1c

📥 Commits

Reviewing files that changed from the base of the PR and between cad4d0b and 5d25ea0.

📒 Files selected for processing (1)

• .github/ISSUE_TEMPLATE/feature-request.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The feature request issue template now applies both the enhancement and feature-request labels.

Changes

Feature request template

Layer / File(s)	Summary
Update feature request labels .github/ISSUE_TEMPLATE/feature-request.yml	The template adds the feature-request label and retains enhancement.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 5d25e

The form now applies both labels. The separate community bot’s behavior remains unverified, but no failure in this change is demonstrated and no code-backed merge blocker remains.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: applying the feature-request label from the feature request form.
Description check	✅ Passed	The description is directly related to the changeset. It explains the label update, its purpose, validation, and scope.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}