Update agent-parity-governance preset to v0.2.0

[hindermath]

Summary

• update the community catalog entry for agent-parity-governance from v0.1.0 to v0.2.0
• point the download URL at the published v0.2.0 tag ZIP
• update the community presets table to reflect the added model-routing guidance and template count

Validation

• ruby -rjson parsed presets/catalog.community.json and verified version, download URL, and template count
• git diff --check
• previously smoke-tested the published v0.2.0 ZIP with specify preset add --from https://github.com/hindermath/spec-kit-preset-agent-parity-governance/archive/refs/tags/v0.2.0.zip --priority 60

[Copilot]

Pull request overview

Note

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

Updates the Agent Parity Governance community preset to version 0.2.0, which adds agent-neutral Spec Kit model-routing guidance and additional templates.

Changes:

• Bumps preset version from 0.1.0 to 0.2.0 with updated description and download URL
• Increases template count from 6 to 9 and adds agent-md and model-routing tags
• Updates the corresponding row in the community presets documentation table

Reviewed changes

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

File	Description
presets/catalog.community.json	Bumps agent-parity-governance preset to v0.2.0, updates description, templates count, tags, and timestamps
docs/community/presets.md	Updates the docs table entry to reflect the new description and template count

---

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

[hindermath]

Thank you for reviewing the community preset catalog updates.

I have submitted the updated Agent Parity Governance preset as v0.2.0 in this PR. The standalone preset repository has already been updated and tagged at v0.2.0, and the catalog entry now points to the new GitHub ZIP download URL.

This update keeps the existing agent-guidance parity behavior and adds agent-neutral Spec Kit model-routing guidance. The routing guidance intentionally avoids pinning vendor-specific model names in feature artifacts, so specs, plans, and tasks remain reproducible when available models or agents change.

I validated the catalog JSON locally and smoke-tested the published v0.2.0 ZIP with specify preset add --from https://github.com/hindermath/spec-kit-preset-agent-parity-governance/archive/refs/tags/v0.2.0.zip --priority 60. Please let me know if you would like any wording, metadata, or catalog formatting adjusted.

[hindermath]

Hi @mnriem,

friendly follow-up on this PR: this is the Agent Parity Governance preset catalog update to v0.2.0.

The standalone preset repository has already been published and tagged as v0.2.0, and this PR updates the Spec Kit community catalog entry to point to the corresponding GitHub ZIP download. Functionally, the update keeps the existing agent-guidance parity behavior and adds agent-neutral Spec Kit model-routing guidance, without pinning vendor-specific model names in generated feature artifacts.

I also validated the catalog JSON locally and smoke-tested the published v0.2.0 ZIP with specify preset add.

From my side, the PR is ready for maintainer review and further processing. Please let me know if any wording, metadata, or catalog formatting should still be adjusted.

Thank you very much for your time and review support.

[mnriem]

Please resolve conflicts

[hindermath]

Hi @mnriem,

thank you for the heads-up. The merge conflicts in this PR have now been resolved.

What I did:

• rebased codex/update-agent-parity-v0.2.0 onto the current github/spec-kit:main
• resolved the conflict in presets/catalog.community.json
• kept the current upstream catalog structure and preserved the Agent Parity Governance v0.2.0 update
• retained the catalog-level updated_at value for this v0.2.0 catalog update
• verified that the final PR diff is still limited to:
  • presets/catalog.community.json
  • docs/community/presets.md

Local validation completed:

• JSON syntax check for presets/catalog.community.json
• conflict-marker scan
• git diff --check

The branch has been pushed back to the PR and GitHub now reports it as mergeable again. From my side, it is ready for maintainer review and further processing.

Thank you very much for your time and support.