cv4vs-ci-installlisted

# Install the CI artifact Testing what CI actually produced is four manual steps: find the run, download the artifact, open the zip to see whether it is intact, then hand it to `tools\extension.ps1`. This does the sequence and refuses to install a package that is missing pieces. Why the check matters: on 2026-07-21 the CI artifact was missing the entire `WebView2/` folder. It installed without a word of complaint, and the failure only surfaced as a `DirectoryNotFoundException` when the chat pane was opened. A VSIX that installs is not a VSIX that works. ## Procedure ### 1. Find the run ```powershell gh run list --branch <branch> --limit 1 --json databaseId,headSha,status,conclusion ``` Same rules as [cv4vs-ci-log](../cv4vs-ci-log/SKILL.md): the run must be `completed`, and `headSha` has to be compared with `git rev-parse HEAD`. Two extra conditions here, because this one changes the machine: - **`conclusion` must be `success`.** A failed run may still have uploaded an artifact. - **If `headSha` differs from HEAD, stop and say so.** With a report a stale run is merely confusing; installing one puts the wrong commit on disk under the right name, which is exactly the kind of mismatch that costs an afternoon. ### 2. Download ```powershell $dir = "C:\temp\cv4vs-ci-vsix" Remove-Item -LiteralPath $dir -Recurse -Force -ErrorAction SilentlyContinue gh run download <id> --repo Corsinvest/cv4vs-agents --dir $dir ``` Clear the folder first: `gh run download` does not overwr