HVE Installation and Cohort Baseline

Up: HVE Core · Delivery: Environment, Instructor Readiness

Microsoft Guidance

The installation guide offers a VS Code extension, Copilot CLI plugin, and selective clone adoption. Extension ID: ise-hve-essentials.hve-core.

The extension has Stable and PreRelease channels. The CLI registration tracks main; it does not provide equivalent release channels. Selective clone adoption supports controlled versions and component selection. MCP integrations are optional.

CLI installation:

copilot plugin marketplace add microsoft/hve-core
copilot plugin install hve-core@hve-core

Confirm declared components are discoverable, including RPI Agent and its phase entry points. Microsoft directs users to gitignore .copilot-tracking/, which stores workflow evidence locally. Local persistence therefore does not automatically provide a team handoff or an assessment submission.

Proposed Cohort Release Checklist

These checks are Frontier delivery requirements; none has been completed yet.

• Choose one supported host and installation method for the pilot.
• Record the exact HVE extension version or source commit, editor and Copilot versions, selected model, and starter repository commit.
• Test learner access, organization policies, model access, and component discovery.
• Run the complete exercise on a clean learner environment; record time, failures, and recovery steps.
• Export required assessment artifacts through an explicit submission process; exclude secrets and client data.
• Retest before the cohort and control updates during delivery.

A CLI marketplace registration alone is insufficient evidence of a fixed cohort version. Choose a reproducible baseline and verify the actual installed components before publishing lab instructions. Track cost and tenancy decisions in ^q-009.