Add Hyper-V Control and isolate plugin release streams

.agents/plugins/marketplace.json

@@ -19,6 +19,12 @@
       "source": {"source": "local", "path": "./plugins/frida-use"},
       "policy": {"installation": "AVAILABLE", "authentication": "ON_INSTALL"},
       "category": "Security"
+    },
+    {
+      "name": "hyper-v-control",
+      "source": {"source": "local", "path": "./plugins/hyper-v-control"},
+      "policy": {"installation": "AVAILABLE", "authentication": "ON_INSTALL"},
+      "category": "Developer Tools"
     }
   ]
 }

.gitattributes

@@ -1,3 +1,6 @@
 *.zip filter=lfs diff=lfs merge=lfs -text
 *.patch text eol=lf -whitespace
 *.manifest text eol=lf
+src/HyperVControl/** text eol=lf
+tests/HyperVControl.Tests/** text eol=lf
+plugins/hyper-v-control/** text eol=lf

.github/workflows/hyper-v-control.yml

@@ -0,0 +1,35 @@
+name: Hyper-V Control
+on:
+  push:
+    paths: ['src/HyperVControl/**', 'tests/HyperVControl.Tests/**', 'plugins/hyper-v-control/**', 'plugins/rizin-re-toolkit/**', 'scripts/build-hyperv-control.ps1', 'scripts/test-installer.ps1', 'scripts/test-release-isolation.ps1', '.github/workflows/hyper-v-control.yml']
+  pull_request:
+    paths: ['src/HyperVControl/**', 'tests/HyperVControl.Tests/**', 'plugins/hyper-v-control/**', 'plugins/rizin-re-toolkit/**', 'scripts/build-hyperv-control.ps1', 'scripts/test-installer.ps1', 'scripts/test-release-isolation.ps1', '.github/workflows/hyper-v-control.yml']
+  workflow_dispatch:
+permissions:
+  contents: read
+jobs:
+  windows:
+    runs-on: windows-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-dotnet@v4
+        with:
+          dotnet-version: '10.0.401'
+      - name: Build self-contained EXE and plugin
+        shell: pwsh
+        run: ./scripts/build-hyperv-control.ps1
+      - name: Verify pinned runtime reproducibility
+        shell: pwsh
+        run: git diff --exit-code -- plugins/hyper-v-control/runtime.json
+      - name: Unit and stdio protocol validation
+        shell: pwsh
+        run: |
+          dotnet run --project tests/HyperVControl.Tests -c Release -- unit $PWD
+          if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }
+          dotnet run --project tests/HyperVControl.Tests -c Release -- smoke $PWD
+          if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }
+          ./scripts/test-release-isolation.ps1
+      - uses: actions/upload-artifact@v4
+        with:
+          name: hyper-v-control-win-x64
+          path: build/hyperv-control/release/

.gitignore

@@ -3,3 +3,6 @@ build/
 test/
 __pycache__/
 *.pyc
+**/bin/
+**/obj/
+plugins/hyper-v-control/bin/

HyperVControl.slnx

@@ -0,0 +1,4 @@
+<Solution>
+  <Project Path="src/HyperVControl/HyperVControl.csproj" />
+  <Project Path="tests/HyperVControl.Tests/HyperVControl.Tests.csproj" />
+</Solution>

README.md

@@ -1,20 +1,23 @@
 # Jerry's Plugin Marketplace
 
-A personal Codex plugin marketplace. Each plugin lives in its own folder, so this repository can grow beyond the original Rizin bundle.
+A personal Codex plugin monorepo. Each plugin has its own identity, version, installation directory and release stream.
 
 | Plugin | What it provides |
 | --- | --- |
 | [Rizin RE Toolkit](plugins/rizin-re-toolkit) | A portable Windows x64 Rizin CLI, RetDec/Ghidra/jsdec decompilers, YARA, FLIRT, and a skill for native binary and memory-dump analysis. |
 | [Capstone Binary Patching](plugins/capstone-binary-patching) | A uv-managed Capstone/LIEF CLI and skill for binary patches, instruction diffs, patch porting, verification and rollback, with native Windows experiments. |
 | [Frida Use](plugins/frida-use) | Windows-focused live instrumentation, Python/JavaScript debugging, API tracing, malware analysis, reverse engineering, and reversible runtime patching. |
+| [Hyper-V Control](plugins/hyper-v-control) | A compiled C# stdio MCP EXE and skill for VM lifecycle, checkpoints, Basic/Enhanced computer use, guest files/UI, and user/kernel debugging. |
 
 ## Add to Codex
 
 ```powershell
 codex plugin marketplace add JerryLinLinLin/jerry-plugin-marketplace --ref main
 ```
 
-Open the plugin directory, select **Jerry's Plugin Marketplace**, and install **Rizin RE Toolkit**, **Capstone Binary Patching**, or **Frida Use** as needed. A normal marketplace clone does not need the build-source submodules. The Rizin CLI is downloaded separately from GitHub Releases when its skill needs it. Frida Use bundles its own skill, scripts, and references; install the Frida runtime in your analysis environment as described in its README.
+Open the plugin directory, select **Jerry's Plugin Marketplace**, and install **Rizin RE Toolkit**, **Capstone Binary Patching**, **Frida Use**, or **Hyper-V Control** as needed. A normal marketplace clone does not need the build-source submodules. Rizin and Hyper-V Control download their own verified runtimes from separate release streams. Frida Use bundles its own skill, scripts, and references; install the Frida runtime in your analysis environment as described in its README.
+
+**Hyper-V Control:** plugin/skill ID `hyper-v-control`, invocation `$hyper-v-control`, version `0.1.0`. Its C# stdio MCP is distributed as a self-contained Windows x64 EXE. A complete plugin ZIP includes the EXE; for a marketplace source installation, run [its installer](plugins/hyper-v-control/scripts/install.ps1) before reconnecting the MCP. See [setup and validation](plugins/hyper-v-control/README.md).
 
 **Capstone Binary Patching** is a separate skill-and-CLI plugin for patching work; see its
 [setup and experiments](plugins/capstone-binary-patching). Its Python dependencies are managed by uv,
@@ -28,7 +31,15 @@ and it requires no MCP server or account connection.
 
 The catalog is [.agents/plugins/marketplace.json](.agents/plugins/marketplace.json), following the [official OpenAI plugin marketplace format](https://developers.openai.com/plugins/build/plugins). Plugin paths are relative to the repository root.
 
-The [plugin/skill release 0.4.0](https://github.com/JerryLinLinLin/jerry-plugin-marketplace/releases/tag/rizin-re-toolkit-v0.4.0) is versioned separately from the Rizin portable runtime below.
+## Releases and downloads
+
+| Component | Release | What to download |
+| --- | --- | --- |
+| Hyper-V Control | [0.1.0](https://github.com/JerryLinLinLin/jerry-plugin-marketplace/releases/tag/hyper-v-control-v0.1.0) | Namespaced Windows x64 EXE or complete plugin ZIP |
+| Rizin RE Toolkit plugin/skill | [0.4.1](https://github.com/JerryLinLinLin/jerry-plugin-marketplace/releases/tag/rizin-re-toolkit-v0.4.1) | Plugin ZIP or skill; includes the isolated, paginated runtime installer |
+| Rizin portable runtime | [0.3.1](https://github.com/JerryLinLinLin/jerry-plugin-marketplace/releases/tag/rizin-v0.3.1) | Existing runtime bundle and its unchanged `SHA256SUMS` |
+
+Use the [release organization guide](docs/releases.md) for tag/asset naming, per-plugin checksum pins, independent runtime versions and publication steps. Installers do not use the repository-wide Latest release to select a plugin. Existing Rizin URLs remain compatible.
 
 ## Portable Rizin download
 
@@ -50,13 +61,15 @@ and use English link labels even when the original source is in another language
 
 1. Create `plugins/<plugin-name>/plugin.json` and `skills/<skill-name>/SKILL.md` within that folder. Keep referenced assets and scripts inside the plugin.
 2. Add its entry to `.agents/plugins/marketplace.json`, using `source.path: ./plugins/<plugin-name>`, a category, and installation/authentication policies.
-3. Bump the plugin's semantic version when shipping changes. Keep large CLI binaries in versioned GitHub release assets.
+3. Bump the plugin's semantic version when shipping changes. Follow [the release conventions](docs/releases.md) for component tags, namespaced assets and isolated runtime installation. Keep large binaries in GitHub Releases.
 4. Validate the manifest and skill, then test discovery with Codex.
 
 Rizin includes a portable Agent Plugins manifest and a `.codex-plugin/plugin.json` compatibility manifest. It is a CLI-and-skill plugin and needs no MCP server or account connection.
 
 ## Build and verification
 
+This is a plugin monorepo. Hyper-V Control's C# source is under `src/HyperVControl`, its protocol/live validation harness under `tests/HyperVControl.Tests`, and its distributable plugin under `plugins/hyper-v-control`. Build its self-contained EXE and plugin ZIP with `scripts/build-hyperv-control.ps1`; see [Hyper-V Control](plugins/hyper-v-control/README.md) for runtime setup and [feature extraction](plugins/hyper-v-control/docs/extraction.md).
+
 See [the build guide](docs/build.md), [component lock file](bundle.lock.json), and [release validation](docs/validation-v0.3.1.md). Build sources are pinned under `sources/`; Windows compatibility patches live under `patches/`. Generated files stay in the ignored `build/` directory.
 
 ## License

docs/releases.md

@@ -0,0 +1,66 @@
+# Releases and binary distribution
+
+This repository is a marketplace of independently versioned plugins. A GitHub Release belongs to one plugin or one explicitly separate runtime stream; it is not a version of the whole marketplace. GitHub assets are a flat list, so filenames carry their own identity.
+
+## Release index
+
+| Stream | Version and tag | Downloads | Installation |
+| --- | --- | --- | --- |
+| Hyper-V Control | [0.1.0](https://github.com/JerryLinLinLin/jerry-plugin-marketplace/releases/tag/hyper-v-control-v0.1.0) | C# EXE and complete Windows x64 plugin ZIP | `%LOCALAPPDATA%\Programs\HyperVControl\0.1.0` or the ZIP's `bin` directory |
+| Rizin RE Toolkit plugin/skill | [0.4.1](https://github.com/JerryLinLinLin/jerry-plugin-marketplace/releases/tag/rizin-re-toolkit-v0.4.1) | Plugin ZIP and `.skill` | Codex plugin/skill directory |
+| Rizin portable runtime | [0.3.1](https://github.com/JerryLinLinLin/jerry-plugin-marketplace/releases/tag/rizin-v0.3.1) | Rizin 0.9.1 Windows x64 runtime bundle | `%LOCALAPPDATA%\Programs\Rizin\rizin-v0.3.1` |
+| Capstone Binary Patching | Plugin `0.1.0`, marketplace source | Skill/scripts; dependencies installed by uv | Its uv-managed environment; no repository binary release required |
+| Frida Use | Plugin `1.0.0`, marketplace source | Skill/scripts/references; Frida installed separately | The selected analysis environment; no repository binary release required |
+
+The marketplace's source of truth for plugin identity/version remains `plugins/<id>/plugin.json`. A compiled plugin additionally owns its runtime pin, installer, launcher and release builder. Do not couple unrelated plugin versions.
+
+## Naming rules for new releases
+
+| Item | Pattern | Hyper-V example |
+| --- | --- | --- |
+| Git tag | `<plugin-id>-v<semver>` | `hyper-v-control-v0.1.0` |
+| Release title | `<Display name> <version> — <platform or package role>` | `Hyper-V Control 0.1.0 — Windows x64 MCP and Plugin` |
+| Standalone executable | `<plugin-id>-<rid>-v<version>.exe` | `hyper-v-control-win-x64-v0.1.0.exe` |
+| Complete plugin ZIP | `<plugin-id>-plugin-v<version>[-<rid>].zip` | `hyper-v-control-plugin-v0.1.0-win-x64.zip` |
+| Multi-file runtime ZIP, when needed | `<plugin-id>-runtime-<rid>-v<version>.zip` | Use when an EXE requires adjacent runtime files |
+| Optional skill archive | `<plugin-id>-v<version>.skill` | `rizin-re-toolkit-v0.4.1.skill` |
+| Checksums | `<plugin-id>-v<version>-SHA256SUMS.txt` | `hyper-v-control-v0.1.0-SHA256SUMS.txt` |
+| Asset inventory | `<plugin-id>-v<version>-release.json` | `hyper-v-control-v0.1.0-release.json` |
+
+Use .NET-style runtime identifiers such as `win-x64`, `win-arm64`, `linux-x64`, and `osx-arm64`. A filename should stay unambiguous when copied into a shared Downloads directory. An installed executable may have a stable local name such as `HyperVControl.exe`; the installer maps the namespaced download to that name inside the plugin's own versioned directory.
+
+For a genuinely independent runtime version, use a separate `<runtime-id>-runtime-v<version>` stream and pin the relationship from the consuming plugin. A plugin may update documentation without rebuilding a large, unchanged runtime. Existing Rizin runtime tags (`rizin-v0.3.1`) and asset names are legacy compatibility contracts and are not renamed.
+
+## Download and upgrade isolation
+
+- Never use repository-wide `/releases/latest` or `/releases/latest/download/...` from an installer. The newest release may belong to a different plugin.
+- Prefer an exact release tag, platform, asset filename and SHA-256 pin in the consuming plugin. Hyper-V's `runtime.json` contains all four; its installer rejects a mismatched plugin, tag, platform or asset URL before downloading.
+- When latest-in-stream discovery is necessary, filter both tag family and asset name, skip drafts/prereleases, paginate until the stream is found, and verify the selected asset checksum. Rizin's installer follows this path and retains its legacy `SHA256SUMS` lookup.
+- Keep install directories separate and versioned. Reuse a matching verified installation; do not overwrite a different checksum in place or alter a global PATH implicitly. Rizin's user PATH change remains opt-in; Hyper-V uses an absolute executable path.
+- Keep old tags/assets immutable. Fix a published build with a new patch version. Draft assets may be replaced before publication; published assets are never replaced by this workflow.
+- Publish independent plugin releases with `--latest=false`. The global GitHub Latest badge is not a plugin index. This preserves existing legacy behavior; the table above is the entrypoint for choosing a component.
+
+## Packaging and publication
+
+1. Build/test the component and its installer in an isolated directory. For Hyper-V, use .NET SDK `10.0.401` and `scripts/build-hyperv-control.ps1`. The runtime patch is pinned to `10.0.12`; no compiler or .NET installation is needed by end users.
+2. Commit the runtime pin together with the implementation and packaging. CI verifies that rebuilding the EXE does not change the committed pin. Source paths and Git revision metadata are excluded from the binary identity; GitHub's release tag records the source commit. This avoids a circular dependency between a commit ID and the binary checksum committed within it.
+3. Open and validate the PR, merge it, and tag the exact merged commit. Include only the component's assets in its release. Do not upload all files in a shared `build` directory.
+4. Prepare a draft release with explicit tag/title/target, upload the named EXE/ZIP, asset inventory and checksum file, then publish it without moving the repository-wide Latest badge.
+5. Download the published assets, verify their hashes against the committed pin and inventory, and exercise the real installer in a temporary directory before reporting completion.
+
+For Hyper-V, upload these four files from `build/hyperv-control/release`:
+
+```text
+hyper-v-control-win-x64-v0.1.0.exe
+hyper-v-control-plugin-v0.1.0-win-x64.zip
+hyper-v-control-v0.1.0-release.json
+hyper-v-control-v0.1.0-SHA256SUMS.txt
+```
+
+The ZIP contains the EXE, manifests, English skill/documentation, launcher, installer, and licenses. The EXE-only download is for direct stdio MCP configuration. Local convenience aliases (`HyperVControl.exe`, `SHA256SUMS`) are not additional public Hyper-V assets. The inventory records primary asset names, roles, platforms, sizes and hashes; the checksum file also covers the inventory and does not hash itself.
+
+Rizin RE Toolkit 0.4.1 is an installer-only maintenance release; its runtime remains 0.3.1. Its release retains a `SHA256SUMS` compatibility asset and additionally publishes the namespaced checksum filename. The existing `rizin-v0.3.1` release is left untouched. Future Rizin runtime releases retain the existing runtime asset family and `SHA256SUMS` while older installers are supported.
+
+## Validation
+
+`scripts/test-release-isolation.ps1` substitutes only HTTP responses while performing real hash checks, extraction, version execution and installation. It tests a full page of unrelated releases before Rizin, a misleading tag with a Rizin-looking asset, drafts, prereleases, corrupt downloads, idempotent Hyper-V installation and coexistence of installation directories. The small synthetic Rizin version probe validates installer behavior; the actual published Rizin runtime is separately downloaded and executed for release verification.

plugins/hyper-v-control/.codex-plugin/plugin.json

@@ -0,0 +1,15 @@
+{
+  "name": "hyper-v-control",
+  "version": "0.1.0",
+  "description": "Hyper-V lifecycle, graphical guest control, and Windows debugging with a compiled C# stdio MCP.",
+  "skills": "./skills/",
+  "mcpServers": "./.mcp.json",
+  "interface": {
+    "displayName": "Hyper-V Control",
+    "shortDescription": "VM lifecycle, computer use, and Windows debugging.",
+    "developerName": "JerryLinLinLin",
+    "category": "Developer Tools",
+    "capabilities": ["Read", "Write", "Execute"],
+    "logo": "./assets/icon.svg"
+  }
+}

plugins/hyper-v-control/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "hyper-v-control": {
+      "command": "powershell.exe",
+      "args": ["-NoLogo", "-NoProfile", "-NonInteractive", "-ExecutionPolicy", "Bypass", "-File", "${PLUGIN_ROOT}/scripts/start.ps1"]
+    }
+  }
+}

plugins/hyper-v-control/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 JerryLinLinLin
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.