Add featured canvas plugins to catalog

[dhruvchand]

Summary

• Add catalog entries for two of the GitHub Copilot app's featured Canvas plugins, mirroring Add canvas-only plugins to catalog #24.
• sentry-triage (github/awesome-copilot) — Canvas-only; tagged canvas, canvas-only, github-copilot.
• microsoft-foundry (microsoft/foundry-dev-tools) — ships a Canvas and a skill, so it is not Canvas-only; tagged canvas + github-copilot only.
• Regenerate ai-catalog.json via scripts/generate_ai_catalog.py (also folds in routine live MCP-catalog drift, same as Add canvas-only plugins to catalog #24).

Why

The Copilot app's Customize → Featured tab (FEATURED_CANVAS_ENTRIES in extensionsFeatured.ts) references four Canvas plugins that were not in this catalog, so they could not be resolved by URN. #24 added 23 other Canvas plugins but none of the featured four. This PR adds the featured ones whose manifests are publicly resolvable.

Classification is explicit and decided per manifest — not inferred from names, descriptions, or keywords:

• sentry-triage declares only a Canvas extension (no agents/skills/hooks/MCP) → Canvas-only.
• microsoft-foundry also ships a skill (skills/validate-microsoft-foundry-hosted-agent) and an open-foundry-canvas command alongside its Canvas, so per CONTRIBUTING.md it keeps canvas + github-copilot without canvas-only.

Blocked: public source, but not ingestable today

The other two featured plugins are public but ship only a .claude-plugin/plugin.json manifest (no bare plugin.json, .plugin/plugin.json, or .github/plugin/plugin.json). Agent Finder's Copilot-plugin resolver rejects .claude-plugin/ manifests as non-Copilot, and scripts/fix_plugin_media_types.py reclassifies such paths to the Claude plugin media type — so adding them today would produce a broken, mis-typed entry. Not added:

• azure-devops-copilot-plugin — microsoft/azure-devops-copilot-plugin; Canvas code under extensions/azure-devops/, only manifest is .claude-plugin/plugin.json.
• jira-sprint-dashboard-canvas — atlassian-labs/copilot-marketplace; Canvas under extensions/jira-sprint-dashboard-canvas/, only manifest is the top-level .claude-plugin/plugin.json.

Upstream ask: publish a Copilot-style manifest (a bare plugin.json, or .github/plugin/plugin.json) in each repo so these can be catalogued.

Notes

• microsoft-foundry is filed as catalog/microsoft/microsoft-foundry-canvas.json to avoid colliding with the existing catalog/microsoft/microsoft-foundry.json, which is a different resource (an Azure skill from microsoft/azure-skills). The URNs differ by sourceSet, so there is no identifier collision.
• No new catalog/atlassian-labs/ publisher directory is added here: its only featured plugin (jira-sprint-dashboard-canvas) is blocked above.

Validation

• python3 -m unittest discover -s tests — all Canvas contract tests pass (two failures seen locally are pre-existing Windows-only path-separator assertions unrelated to these entries; they pass on the Ubuntu CI runner).
• python3 scripts/generate_ai_catalog.py and --check — regenerates cleanly and reports no staleness.

For context, this mirrors #24 (Add canvas-only plugins to catalog).

[Copilot]

Copilot review overview

🟢 Approval recommended

Both source entries satisfy catalog contracts and are represented exactly once in the generated artifact.

Review effort: Balanced
Findings: None

What changed in this PR

Adds two featured GitHub Copilot Canvas plugins to the catalog and refreshes the generated ARD artifact.

Changes:

• Adds Sentry Triage as Canvas-only.
• Adds Microsoft Foundry Canvas as a mixed-capability plugin.
• Regenerates the catalog with current MCP data.

File	Description
catalog/​github/​sentry-triage.json	Defines the Sentry Triage plugin.
catalog/​microsoft/​microsoft-foundry-canvas.json	Defines the Microsoft Foundry Canvas plugin.
ai-catalog.json	Includes both entries and refreshed MCP data.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.