Automatically prioritize bundle submissions

[mnriem]

Description

Automatically apply the triage-must-have verdict to issues opened through the Bundle Submission form. The form now applies only that label; the separate maintainer-applied bundle-submission label continues to gate catalog validation.

This uses deterministic native issue-form metadata instead of issue-content heuristics or a workflow with write permissions. Other issue forms and the manual triage rubric remain unchanged. The bundle reference documents the intake behavior and the automated draft-PR lifecycle, and regression coverage verifies the bundle form, preserves exact extension/preset coverage, and checks every other canonical issue form.

Testing

• Tested locally with uv run specify --help — not applicable; no CLI behavior changed
• Ran existing tests with uv sync && uv run pytest
• Tested with a sample project (if applicable) — not applicable; this is GitHub issue-form configuration

Validation results:

• uv sync --extra test — passed
• LC_ALL=en_US.UTF-8 .venv/bin/python -m pytest — 9,735 passed, 19 skipped
• .venv/bin/python -m pytest tests/test_github_workflows.py -q — 124 passed
• uvx ruff@0.15.0 check tests/test_github_workflows.py — passed
• git diff --check — passed

AI Disclosure

• I did not use AI assistance for this contribution
• I did use AI assistance (fill in the disclosure below)

AI disclosure: Implemented with GitHub Copilot using GPT-5.6 Sol in autonomous mode. Copilot investigated the finalized extension and preset intake patterns, changed the bundle issue-form configuration and reference documentation, added regression tests, ran validation, and prepared this pull request on behalf of @mnriem.

[Copilot]

Copilot review overview

🟢 Approval recommended

The change follows established intake patterns with focused regression coverage; only a non-blocking documentation clarification remains.

Review effort: Balanced
Findings: 1

Open (1)

• Clarify triage automation also applies to extension and preset submissions · New

What changed in this PR

Automatically prioritizes Spec Kit bundle submissions using native issue-form labels while preserving maintainer-controlled catalog validation.

Changes:

• Applies only triage-must-have on bundle submission.
• Documents intake and the automated draft-PR lifecycle.
• Adds bundle regression coverage while preserving checks for other forms.

File	Description
tests/​test_github_workflows.py	Tests bundle labeling and other-form exclusions.
docs/​reference/​bundles.md	Explains submission handling and catalog publication.
.github/​ISSUE_TEMPLATE/​bundle_submission.yml	Updates automatic labeling and intake guidance.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[mnriem]

Addressed the review clarification in commit c7180d96 by stating that bundle submissions join extension and preset submissions in the native triage-must-have intake behavior, while the manual rubric for other issues remains unchanged.

Validation:

• npx --yes markdownlint-cli2 docs/reference/bundles.md — passed
• git diff --check — passed

Posted on behalf of @mnriem by GitHub Copilot using GPT-5.6 Sol in autonomous mode. Copilot made the documentation-only review fix, validated it, committed it, and prepared this review-round summary.

[Copilot]

Copilot review overview

🟢 Approval recommended

The focused configuration change preserves the validation gate and includes positive and negative regression coverage.

Review effort: Balanced
Findings: None

Resolved since last review (1)

• Clarify triage automation also applies to extension and preset submissions