apm packaging

[aymenfurter]

Problem

Extension is hard to install

Proposed Solution

follow similar pattern like Daniel in his project:
https://github.com/danielmeppiel/finops-workshop#install-the-cost-dashboard-as-a-copilot-canvas-apm

Alternatives Considered

No response

[github-actions]

🎯 Triage report

This reads as a feature request to reduce installation friction by packaging AI Engineer Coach more like the linked Copilot canvas APM example. The repo already documents a self-built VSIX path and a local canvas path, so the gap appears to be distribution/packaging UX rather than a defect in existing functionality.

I did not find a clear duplicate in the current issue set. The closest hits were other install/runtime topics, but not the same packaging request.

📊 Assessment

Dimension	Value	Reasoning
Type	Feature	The issue asks for a new packaging/install path rather than reporting broken behavior.
Labels	enhancement, dx	enhancement already fit; dx also fits because the request is specifically about setup/install experience.
Severity	Low	The report describes friction in adopting the project, but does not show a broken core workflow, regression, or data-loss/security impact.
Coding agent	Needs more info	Direction is clear, but success criteria are still underspecified for implementation: target artifact, release channel, and install flow are not yet explicit.

💡 Notes and suggestions

Relevant existing repo context:

• README.md already says the extension is not published to a marketplace or Releases page and is currently installed by building a .vsix locally.
• README.md also has a Run as a canvas in the GitHub Copilot app section, so the likely gap is a smoother packaged install path, not the absence of canvas support itself.

Useful next clarifications before assigning implementation:

1. Confirm the desired outcome: prebuilt APM artifact, published VSIX/release asset, or another install surface.
2. Define the supported install path(s): GitHub Copilot app only, VS Code only, or both.
3. Decide whether this is primarily a packaging automation task, a release/distribution task, or a documentation/discoverability task.

A likely implementation breakdown once the target is chosen:

• add the packaging/build automation for the chosen artifact
• document the install flow in README.md and docs/content/getting-started/installation.md
• if distribution changes, wire it into the repository’s release/publishing workflow

Reference from the issue for comparison:

• https://github.com/danielmeppiel/finops-workshop#install-the-cost-dashboard-as-a-copilot-canvas-apm

Generated by Agentic Triage for issue #163 · 58 AIC · ⌖ 14.9 AIC · ⊞ 22.4K · ◷

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@df35cf29fb856d1c3b8f023ed46d19126e7813bf