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-apple/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

Apply the feature-request label in the feature request issue form

Updates feature-request.yml to assign the feature-request label in addition to the existing enhancement label. Issues created from the form now get both labels.

^{Macroscope summarized 457e4d8.}

[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	❌

⚠️ 2 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:

• Centralize server-relative authentication path validation
• Enforce latest-link-wins centrally across deferred deep links

[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:16.909691Z	457e4d8	PR opened
🔒 Security Review	✅ Completed 2026-10-08T16:02:38.230285Z	457e4d8	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: b052b26a-1e78-4c20-a5f6-da8eee82a787

📥 Commits

Reviewing files that changed from the base of the PR and between da34e44 and 457e4d8.

📒 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 template now assigns both enhancement and feature-request labels.

Changes

Feature request labeling

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) | ~3 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 457e4

The form now assigns both labels. The repository does not define the external bot’s posting gate, but there is no evidence that the added label posts requests before triage or creates an actionable merge blocker.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely states the main change: applying the feature-request label through the feature request issue form.
Description check	✅ Passed	The description directly explains the label change, its purpose, implementation, validation, and risks.
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.}

[Quick104]

Note

Grok commenting on Quick's behalf.

Ranking: impact: polish · priority: P2. It's a one-line issue-form label change so feature requests get picked up by the Discord forum bot. Useful contributor plumbing, but not urgent or blocking.