Add package resolution to the VS Code plugin

[omerzi]

Overview

Adds JFrog package-resolution policy injection to the VS Code Copilot plugin. The plugin is self-contained: it wires the SessionStart hook, vendors the reviewed agent-hook modules, records their immutable source revision, and validates the assembled runtime path.

Details

• Registers the dedicated VS Code package-resolution SessionStart adapter alongside the existing Agent Guard injector.
• Vendors the complete modules bundle from jfrog-agent-hooks commit b680ef382997c57e806e59182bab0ebbfdec87dd.
• Records module provenance in sync-modules-vendor.json.
• Strengthens CI validation to require and parse the adapter, execute it with a Copilot payload, and verify valid SessionStart context.
• Bumps both plugin versions to 1.0.10.
• Documents Node.js and VS Code hook/plugin settings required for installation.

Flow

flowchart LR
    A[VS Code loads JFrog plugin] --> B[hooks/hooks.json]
    B --> C[Agent Guard SessionStart]
    B --> D[Package resolution SessionStart]
    D --> E[Vendored VS Code adapter]
    E --> F[Vendored shared capability]
    F --> G[Artifactory routing context]

Loading

Test plan

• Run the complete hook validation script.
• Verify the vendored adapter exists and passes node --check.
• Execute the package-resolution hook with a Copilot SessionStart payload.
• Assert non-empty, valid hookSpecificOutput.additionalContext.
• Verify Agent Guard force-enable and force-disable behavior remains intact.
• Verify vendored modules exactly match the pinned upstream revision.
• Complete a manual VS Code smoke test proving public npm is refused when governed.

Dependency

Depends on upstream agent-hooks PR: https://github.jfrog.info/JFROG/jfrog-agent-hooks/pull/48