cv4vs-verifylisted

# Verify a build in the Exp instance The gate for this project is a green MSBuild plus a manual pass in the experimental instance. There is no test project, and `.vsct` ids, XAML `x:Class` and the manifest all fail at *runtime*, not at compile time. **This skill cannot run the test.** The panes live inside Visual Studio and nothing outside the process can see them — same limitation `cv4vs-run` states. What it does is the part around the test: confirm the right build is installed before, and read the log after. ## Before: is the right thing installed? ```powershell .\tools\extension.ps1 ``` Prints, per hive: instance name, version, and path. What to look for: - **One copy per hive.** More than one and VS loads both — duplicate menu entries and two MCP servers racing for the same lock file, which reads as a bug in the code. The script flags this in red; `-Reinstall` collapses them. - **The expected hive.** Experimental unless there is a reason otherwise. `-Normal` shows the other side. - **The build under test.** The status output has no date, because VSIXInstaller restamps extracted files with the install time. The packaging date is printed when installing, not afterwards — so if there is doubt about which build is on disk, reinstall rather than guess. Then start it: ```powershell devenv /rootsuffix Exp ``` First launch after an install is slow: VS rebuilds the MEF cache. ## The check, by risk Not in menu order — in the order things actually break: 1. **C