[mnriem]

Description

Automatically apply the triage-must-have verdict to issues opened through the Extension Submission form. The form now applies only that label; the separate maintainer-applied extension-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 publishing guide documents the intake behavior, and regression coverage verifies both the extension form and negative cases for every other 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,689 passed, 19 skipped
• .venv/bin/python -m pytest tests/test_github_workflows.py -q — 121 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 existing issue forms and workflows, changed the issue-form configuration and publishing documentation, added regression tests, ran validation, and prepared this pull request on behalf of @mnriem.

[Copilot]

Copilot review overview

🟡 Changes recommended

The publishing guide incorrectly says automation updates a README table instead of docs/community/extensions.md.

Review effort: Balanced
Findings: 1

Open (1)

• Document the correct extensions approval file · New

What changed in this PR

Automatically prioritizes extension submissions using issue-form metadata while preserving maintainer-gated catalog validation.

Changes:

• Applies only triage-must-have to extension submissions.
• Documents the intake flow.
• Tests extension and non-extension forms.

File	Description
.github/​ISSUE_TEMPLATE/​extension_submission.yml	Configures automatic intake labeling.
extensions/​EXTENSION-PUBLISHING-GUIDE.md	Documents the updated submission flow.
tests/​test_github_workflows.py	Adds positive and negative label coverage.

---

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

[Copilot]

Copilot review overview

🔵 Needs a closer look

The publishing guide still incorrectly attributes automated catalog edits to maintainers.

Review effort: Balanced
Findings: None

Resolved since last review (1)

• Document the correct extensions approval file

Previously missed (1)

In code that hasn't changed since last review

Clarify automated catalog updates and maintainer PR review flow

extensions/​EXTENSION-PUBLISHING-GUIDE.md:157

This step still attributes the catalog edits to the maintainer, but the add-community-extension workflow itself edits both allowed files and opens a draft PR (.github/workflows/add-community-extension.md:342-377); the maintainer reviews that PR rather than manually adding the entry. Please describe the automated update so submitters have the correct approval flow.

[mnriem]

Addressed the latest review in 168a96a0. The publishing guide now describes the actual flow: the add-community-extension workflow validates the submission, updates extensions/catalog.community.json and docs/community/extensions.md in a draft pull request, and a maintainer reviews and merges that generated PR.

Validation: .venv/bin/python -m pytest tests/test_github_workflows.py -q passed (121 tests), and git diff --check passed.

AI disclosure: Posted on behalf of @mnriem by GitHub Copilot using GPT-5.6 Sol in autonomous mode; the documentation correction, validation, commit, and this review-round summary were AI-assisted.

[Copilot]

Copilot review overview

🟢 Approval recommended

The configuration, documentation, and regression coverage consistently implement the stated intake behavior.

Review effort: Balanced
Findings: None