@linzumi/cli 1.0.6 → 1.0.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@linzumi/cli",
-  "version": "1.0.6",
+  "version": "1.0.8",
   "description": "Linzumi CLI \u2014 point a Codex agent at the real code on your laptop, with your team watching and steering from shared threads.",
   "type": "module",
   "bin": {
@@ -48,6 +48,7 @@
     "@types/blessed": "^0.1.27",
     "@types/node": "^22.18.6",
     "esbuild": "^0.27.2",
+    "fast-check": "^3.23.2",
     "tsx": "^4.21.0",
     "vitest": "^1.6.1"
   }

package/scripts/build.mjs

@@ -9,6 +9,10 @@ const packageRoot = dirname(dirname(fileURLToPath(import.meta.url)));
 
 await rm(join(packageRoot, 'dist'), { recursive: true, force: true });
 
+const banner = {
+  js: "import { createRequire } from 'node:module';\nconst require = createRequire(import.meta.url);",
+};
+
 await build({
   entryPoints: [join(packageRoot, 'src/index.ts')],
   bundle: true,
@@ -25,9 +29,36 @@ await build({
   sourcemap: false,
   legalComments: 'none',
   external: ['ws', 'undici', 'blessed', '@anthropic-ai/claude-agent-sdk'],
-  banner: {
-    js: "import { createRequire } from 'node:module';\nconst require = createRequire(import.meta.url);",
-  },
+  banner,
+});
+
+// The in-guest Linzumi MCP bridge: a self-contained MCP server bundle that the
+// VM Codex supervisor injects into a coding job's microVM and runs with a plain
+// `node`. Unlike dist/index.js it bundles EVERYTHING (no `external`), so the
+// guest needs no extra npm packages - only Node, which provisioning already
+// installs. The MCP server path uses only the bundled @modelcontextprotocol/sdk
+// and global fetch; it never touches ws/undici/blessed/claude-agent-sdk, so
+// bundling with no externals stays lean (Spec:
+// plans/2026-06-12-local-vm-codex-execution-phase1.md in-guest MCP bridge).
+// Output extension is .mjs (not .js): the bundle is ESM (banner createRequire +
+// a node:url built-in import are top-level `import` statements). In the guest it
+// lives at /opt/linzumi/ next to the CJS relay.js with no package.json in scope,
+// so a `.js` would be treated as CommonJS on Node versions without ESM-syntax
+// detection and throw "Cannot use import statement outside a module". A
+// `package.json {"type":"module"}` marker would fix mcp-server but BREAK the CJS
+// relay.js at the same path, so the unambiguous `.mjs` extension is the correct
+// fix.
+await build({
+  entryPoints: [join(packageRoot, 'src/mcpServerEntry.ts')],
+  bundle: true,
+  platform: 'node',
+  target: 'node20',
+  format: 'esm',
+  outfile: join(packageRoot, 'dist/mcp-server.mjs'),
+  minify: true,
+  sourcemap: false,
+  legalComments: 'none',
+  banner,
 });
 
 await mkdir(join(packageRoot, 'dist/assets'), { recursive: true });