feat(catalog): add linear extension to community catalog

[ashbrener]

Summary

Adds the linear community extension (spec-kit-linear) to extensions/catalog.community.json for discovery.

Extension repo: https://github.com/ashbrener/spec-kit-linear · Release: v0.2.0

What it does

Mirrors spec-kit feature directories into Linear: one Linear Issue per spec, sub-issues per task phase (checklists + inter-phase blocking relations), auto-synced via six after_* lifecycle hooks. Direction is filesystem → Linear, reconcile-based, unidirectional — never mutates the local filesystem.

Category	integration
Effect	Read+Write (creates per-repo config under .specify/extensions/linear/)
Commands	5 — speckit.linear.push / .pull / .status / .seed / .install
Hooks	6 — after_specify/clarify/plan/tasks/implement/analyze
License	MIT · Requires spec-kit ≥ 0.1.0
Tags	issue-tracking, linear, tasks-sync, lifecycle-mirror, memory, cross-repo

Entry fields copied verbatim from the extension's extension.yml manifest. download_url pins to the immutable v0.2.0 release tag.

Install model

catalog.community.json is discovery-only (install_allowed: false in the default stack). Install:

specify extension add linear --from https://github.com/ashbrener/spec-kit-linear/archive/refs/tags/v0.2.0.zip

Test plan

• Catalog JSON parses; linear inserted between learn and m365
• download_url resolves (HTTP 200 — /archive/refs/tags/v0.2.0.zip)
• version (0.2.0) matches extension.yml at the v0.2.0 tag
• tags use issue-tracking (matching jira / azure-devops)
• Entry surfaced by specify extension search linear once live

Companion docs-table PR: #2750. Submission issue: #2778.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a new community extension entry to the catalog for a Linear integration (“Linear Bridge”).

Changes:

• Added a linear extension record with metadata (links, version, tags, capability counts).
• Registered compatibility requirements (speckit_version) and provided feature counts (commands, hooks).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mnriem]

Going forward for a new/update extension submission please use the extension submissions issue template as that will speed things up

[Copilot]

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1

[mnriem]

Please address Copilot feedback

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

[ashbrener]

Thanks for the review — Copilot feedback addressed:

• download_url is pinned to the immutable release-tag archive (/archive/refs/tags/v0.2.0.zip), matching the advertised version. The earlier note flagged refs/heads/main.zip; that was on a prior revision — the branch had already been switched to the tag.
• tags: aligned the one-off issue-tracker → issue-tracking, consistent with the existing jira and azure-devops entries.

I've also bumped the entry to the latest release (v0.2.0), and filed the submission via the Extension Submission template per your guidance: #2778.

Ready for re-review — happy to adjust anything further.

[ashbrener]

Addressed + refreshed:

• Rebased onto latest main (both this PR and the docs-table PR docs(community): list spec-kit-linear in community extensions table #2750), so they're current with upstream.
• The two new comma findings are false positives. The file parses as valid JSON — python -c "import json; json.load(open('extensions/catalog.community.json'))" succeeds (106 entries), and both boundaries already carry the separator: the learn object closes with }, immediately before "linear", and the linear object closes with }, immediately before "m365". The flagged lines are inside the diff hunk; the commas are on the lines just above each "<key>": { and weren't visible in the hunk context.
• Earlier items remain resolved: download_url pins to the immutable /archive/refs/tags/v0.2.0.zip, and the tag is issue-tracking (matching jira/azure-devops).

Happy to adjust anything further — ready for re-review.