@youdie006/prodex 0.40.32 → 0.40.33

package/dist/cli-pro.js

@@ -1,5 +1,6 @@
 import { existsSync, realpathSync, statSync } from "node:fs";
 import { mkdir, readFile, writeFile } from "node:fs/promises";
+import { createServer as createNetServer } from "node:net";
 import path from "node:path";
 import { BrowserProcessInspectionError } from "./browser-process.js";
 import { buildDryRunBundle } from "./bundle.js";
@@ -2464,7 +2465,54 @@ export async function assertBrowserLaunchStayedAlive(opened, timeoutMs) {
         const detail = formatBrowserEarlyExit(outcome.earlyExit);
         throw new Error(`Chrome/Chromium exited before DevTools became reachable (${detail}). Check the visible browser environment, profile lock, display access, or PRODEX_CHROME, then retry.`);
     }
-    throw new Error(`Chrome/Chromium did not expose a reachable DevTools endpoint after launch. Check the visible browser environment, profile lock, display access, or PRODEX_CHROME, then retry.`);
+    // A browser prodex cannot reach is of no use to it, and left running it
+    // made every later attempt refuse it as wedged (measured 2026-10-19).
+    await endLaunchedBrowser(opened.processId);
+    if (!(await canBindLoopbackPort(opened.port))) {
+        throw new Error(`Chrome started, but its DevTools control port ${opened.port} on 127.0.0.1 is already taken, so prodex cannot reach it. ` +
+            `On WSL with networkingMode=mirrored, Windows reserves port ranges at boot and they apply inside WSL too ` +
+            `(measured 2026-10-19: 9240-9339 reserved, covering 9333); list them with \`netsh interface ipv4 show excludedportrange protocol=tcp\`. ` +
+            `Free the port (as administrator: \`net stop winnat\` then \`net start winnat\`; a Windows dynamic port range starting at 49152 keeps it from coming back), ` +
+            `or use another port with --port or PRODEX_CDP_PORT. The browser prodex started was closed.`);
+    }
+    throw new Error(`Chrome/Chromium did not expose a reachable DevTools endpoint after launch. Check the visible browser environment, profile lock, display access, or PRODEX_CHROME, then retry. The browser prodex started was closed.`);
+}
+async function endLaunchedBrowser(processId) {
+    if (!processId)
+        return;
+    const alive = () => {
+        try {
+            process.kill(processId, 0);
+            return true;
+        }
+        catch {
+            return false;
+        }
+    };
+    try {
+        process.kill(processId, "SIGTERM");
+    }
+    catch {
+        return;
+    }
+    for (let waited = 0; waited < 5_000 && alive(); waited += 100)
+        await sleep(100);
+    if (alive()) {
+        try {
+            process.kill(processId, "SIGKILL");
+        }
+        catch {
+            // Already gone.
+        }
+    }
+}
+/** Whether anything already holds this loopback port, a Windows reservation included. */
+function canBindLoopbackPort(port) {
+    return new Promise((resolve) => {
+        const server = createNetServer();
+        server.once("error", () => resolve(false));
+        server.listen(port, "127.0.0.1", () => server.close(() => resolve(true)));
+    });
 }
 /** Whether a send asked for ChatGPT's Pro step, on either axis that can name it. */
 export function isProSelection(selection) {

package/docs/releasing.md

@@ -16,6 +16,30 @@ Release target: `v0.40.13` on `main`. The GitHub Release records the resolved co
 
 The release adds a guarded, opt-in transition and more accurate blocker reporting. It does not claim that headless Pro consultation is verified on either deployment target or that authentication can be retained indefinitely.
 
+## 0.40.32 Release Record
+
+Release commit `e0e260e` on `main` (cut after PR #26, merge `f57f413`); tag `v0.40.32`.
+
+**Publishing**
+- `publish.yml` run 38339570276 passed all six platforms on the first attempt, then npm publish with SLSA v1 provenance and the GitHub Release (2026-10-13 02:59 UTC).
+- `npm run release:verify` passed on the release commit after a build.
+
+**Installed**
+- WSL, M3, Mac mini: `prodex --version` reports 0.40.32. Running services were not restarted: 4 stdio MCP servers on WSL and 4 on M3 keep older code until their clients reconnect. The Mac mini had none running.
+- The maintainer watchdog checkout was pulled to `e0e260e` and rebuilt.
+
+**Verified live**
+- Before the fix, installed 0.40.31 refused a 500-line (12 KB) `--file` send as `request_mismatch`; installed 0.40.32 answered it (`amber-19`).
+- With the PR build: a 2,400-line `--file` is refused with the `--attach` pointer, and a 57 KB inline prompt answered in 84 s.
+
+**Browser container**
+- `container/redesign-patches` `f408fda` ports PR #26 onto the container's own transcript reader. Image `05c65e5dd1f4`; branch suite 2034 passed, 3 skipped. The swap was gated on the send lock; the ChatGPT tab opened on its own afterwards (the restart change from 2026-10-10, `42a027e`).
+- Live in the container: the 2,400-line `--file` refusal, the 500-line `--file` answer (`amber-19`), and the smoke (`PRODEX_PRO_SMOKE_OK`).
+
+**Also on 2026-10-11 to 10-13**
+- `container/redesign-patches` `42a027e`: the container restarts unless stopped and opens the ChatGPT root itself. Verified by sending SIGTERM to its Chromium: Docker restarted it and the smoke answered without a login step.
+- The canary stayed `ok` on build `314720d0` hourly from 2026-10-11 to 10-13.
+
 ## Browser Incident 2026-10-10: earlyoom
 
 **What happened**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@youdie006/prodex",
-  "version": "0.40.32",
+  "version": "0.40.33",
   "description": "Local receipt bus for coordinating Codex execution with ChatGPT Pro/Projects consultation.",
   "author": "youdie006",
   "license": "MIT",