@henols/vice-mcp 0.2.1 → 0.2.2

package/README.md

@@ -50,6 +50,7 @@ VICE MCP server.
 | `VICE_MCP_HOST` | Host to reach the VICE MCP server on. |
 | `VICE_SKIP_RESOURCE_INSTALL=1` | Disable deploying host launcher scripts into `<project>/tools/`. |
 | `MASTRA_TELEMETRY_DISABLED=1` | Disable Mastra telemetry. |
+| `VICE_LIVE_STOCK_BIN` | Absolute path to a genuinely unpatched stock VICE binary; opts `stock-live.test.ts` in (default-skipped). |
 
 ## Development
 
@@ -64,7 +65,7 @@ export CONTAINER_WORKSPACE_PATH="$(git rev-parse --show-toplevel)"
 export HOST_WORKSPACE_PATH="/host$(git rev-parse --show-toplevel)"
 ```
 
-`npm run test:automated` is the subset of `npm test` that excludes the three
+`npm run test:automated` is the subset of `npm test` that excludes the nine
 manual-only files (see `test-gate.mjs`'s own header).
 
 ```sh

package/THIRD-PARTY-NOTICES.md

@@ -72,32 +72,9 @@ availability gate; CI installs it via `apt-get install -y acme` in
 `.github/workflows/ci.yml`'s `build` job). **No ACME source, header, data
 table or output is included in this repository or in the published
 package**, so ACME's licence does not attach to anything shipped. ACME never
-appears in `.claude/mcp/vice/package.json`'s `files[]`, `dependencies`, or
+appears in `src/mcp/vice/package.json`'s `files[]`, `dependencies`, or
 `devDependencies` — it is an apt/CI-installed tool, never an npm package.
 
-## Build/CI tools — not incorporated: regenerator2000
-
-regenerator2000 is invoked as an **external CLI subprocess** (Phase 10's
-`R2000-09` bootstrap and `R2000-06` reassembly proof) against a real,
-locally-installed `regenerator2000` binary. **No regenerator2000 source,
-data table, or output is included in this repository or in either
-published package**, so its licence does not attach to anything shipped.
-
-Its licence is **`MIT OR Apache-2.0`** — dual, at the user's option —
-confirmed from the crate's own crates.io licence field, with both
-`LICENSE-MIT` and `LICENSE-APACHE` shipping in the crate. (Do not read this
-as Apache-2.0 alone: that stale, single-licence claim is what `R2000-03`'s
-own requirement text and `.planning/notes/regenerator2000-integration.md`
-still carried before Phase 10 corrected it here.)
-
-Verified version `0.9.20`, published 2026-07-11 by `ricardoquesada`
-(matching the linked GitHub repository owner), checked 2026-08-20 — so this
-provenance claim is re-checkable against a specific release.
-
-regenerator2000 never appears in `.claude/mcp/vice/package.json`'s
-`files[]`, `dependencies`, or `devDependencies` — it is a `cargo
-install`-provided tool, never an npm package.
-
 ## Explicitly NOT a source: VICE
 
 VICE is GPL-2 and this repository is MIT. **No opcode fact, protocol

package/{r2000-acme-ident.ts → anno-acme-ident.ts}

@@ -1,29 +1,29 @@
 #!/usr/bin/env node
-// r2000-acme-ident.ts -- the ONE authoritative place in this repo for the
+// anno-acme-ident.ts -- the ONE authoritative place in this repo for the
 // ACME identifier policy (T-11-ENUM-NAME / T-11-NAME-INJECT): what makes a
 // string a legal ACME symbol/label name, and the single check function that
 // decides it.
 //
-// WHY THIS MODULE EXISTS: this policy started life inside r2000-enum-gen.ts,
+// WHY THIS MODULE EXISTS: this policy started life inside anno-enum-gen.ts,
 // consumed only by its own `createOrUpdateEnum()`/`sanitizeVariantMap()`.
 // T-11-NAME-INJECT widened the finding to a SECOND entry route --
-// `r2000_set_label_name` (both outer and batch-inner) in r2000-tools.ts, and
-// `importLabels()` in r2000-symbols.ts -- and `r2000-enum-gen.ts` statically
-// imports `runR2000Tool` FROM `r2000-tools.ts`, so `r2000-tools.ts` cannot
-// import the policy back from `r2000-enum-gen.ts` without forming a module
+// `anno_set_label_name` (both outer and batch-inner) in anno-tools.ts, and
+// `importLabels()` in anno-symbols.ts -- and `anno-enum-gen.ts` statically
+// imports `runAnnoTool` FROM `anno-tools.ts`, so `anno-tools.ts` cannot
+// import the policy back from `anno-enum-gen.ts` without forming a module
 // cycle. This module has no import from anywhere else in this repo, so
 // every one of those consumers (and any future one) can import it directly.
 //
 // WHAT THIS IS THE ONE AUTHORITATIVE PLACE FOR: `MAX_ACME_IDENTIFIER_LENGTH`,
 // `ACME_IDENT_RE`, `ACME_RESERVED_MNEMONICS` and `assertLegalAcmeIdentifier()`
 // -- the complete, only definition of "legal ACME identifier" in this repo.
-// `r2000-enum-gen.ts` re-exports `assertLegalAcmeIdentifier` /
+// `anno-enum-gen.ts` re-exports `assertLegalAcmeIdentifier` /
 // `MAX_ACME_IDENTIFIER_LENGTH` from here so its own existing consumers and
 // tests keep their current import path; it does not hold a second copy.
 //
 // WHAT NOT TO DO, named concretely:
 //   - Never add a second identifier regex anywhere in this repo. The
-//     `r2000-regbits-gen.ts` / `r2000-regbits.test.ts` copies of
+//     `anno-regbits-gen.ts` / `anno-regbits.test.ts` copies of
 //     `ACME_IDENT_RE` predate this module and are out of this plan's scope
 //     (260821-a86) to consolidate -- but no NEW copy should be added; import
 //     this module's `assertLegalAcmeIdentifier()` instead.
@@ -34,8 +34,8 @@
 //     caller-visible name must never diverge from what actually gets
 //     exported into ACME source.
 //   - Never import anything from this repo into this module. It must stay
-//     importable by both `r2000-tools.ts` and `r2000-enum-gen.ts` (which
-//     imports `runR2000Tool` FROM `r2000-tools.ts`) without a cycle.
+//     importable by both `anno-tools.ts` and `anno-enum-gen.ts` (which
+//     imports `runAnnoTool` FROM `anno-tools.ts`) without a cycle.
 export const MAX_ACME_IDENTIFIER_LENGTH = 200;
 
 const ACME_IDENT_RE = /^[A-Za-z_][A-Za-z0-9_]*$/;
@@ -65,15 +65,15 @@ const ACME_RESERVED_MNEMONICS: ReadonlySet<string> = new Set([
  * `ACME_RESERVED_MNEMONICS`'s own header comment for how that specific list
  * was measured, not assumed).
  *
- * T-11-ENUM-NAME (the highest-value threat in this phase): regenerator2000
+ * T-11-ENUM-NAME (the highest-value threat in this phase): The external analyser
  * validates only the ENUM name server-side
  * (`app_state.rs:443`, `validate_new_enum_name`) and performs ZERO
  * validation on variant names -- they flow straight into
  * `format!("{}_{}", enum_name, variant)` at export time
  * (`formatter_acme.rs:367-369`). This function is called on BOTH the enum
  * name and every variant name, and is called BEFORE any
- * `r2000_create_project_enum`/`r2000_update_project_enum` call reaches
- * `runR2000Tool()` -- proven zero-spawn in `r2000-enum-gen.test.ts`.
+ * `anno_create_project_enum`/`anno_update_project_enum` call reaches
+ * `runAnnoTool()` -- proven zero-spawn in `anno-enum-gen.test.ts`.
  */
 export function assertLegalAcmeIdentifier(id: string, what: string): void {
   if (id.length === 0) {