Issue Description
Follow-on work for #2063
#2008 updates the hve-core-installer skill to auto-wire Copilot hooks (chat.hookFilesLocations for .github/hooks/) for all clone-based install methods (1–6), but the Extension quick-install path does not. After a Marketplace install, the Extension Success Report only emits a manual instruction telling users to edit chat.hookFilesLocations themselves. The extension physically bundles hooks, but VS Code has no contributes.chatHooks point, so a declarative extension cannot activate them.
Proposal: extend the installer skill with a consented, Extension-path-scoped hook-enable step that activates the bundled hooks at runtime, in one of two modes:
- Workspace-copy (default): copy .github/hooks/ into the workspace hooks (auto-discovered by VS Code; upgrade-stable).
- User-global: register a ~-rooted entry in chat.hookFilesLocations (note: must be refreshed after extension upgrades since the install path is versioned).
Scope guardrails:
- Must require explicit user consent (hooks execute commands).
- Must not double-wire hooks for clone-based methods, which already configure them.
- Keep the extensions declarative — do not convert them into code-bearing extensions.
Additional Context
No response
Issue Description
Follow-on work for #2063
#2008 updates the hve-core-installer skill to auto-wire Copilot hooks (chat.hookFilesLocations for .github/hooks/) for all clone-based install methods (1–6), but the Extension quick-install path does not. After a Marketplace install, the Extension Success Report only emits a manual instruction telling users to edit chat.hookFilesLocations themselves. The extension physically bundles hooks, but VS Code has no contributes.chatHooks point, so a declarative extension cannot activate them.
Proposal: extend the installer skill with a consented, Extension-path-scoped hook-enable step that activates the bundled hooks at runtime, in one of two modes:
Scope guardrails:
Additional Context
No response