@youdie006/prodex 0.40.21 → 0.40.23

package/dist/chatgpt-browser.js

@@ -805,6 +805,23 @@ async function navigateIdleChatGptPage(page, url) {
  * navigation cannot leave the old thread's state in place. A false result
  * must not be used as permission to send into stale content.
  */
+// Measured 5.2-8.5 s for the new-chat page to settle (2026-09-30).
+const FRESH_CHAT_TIMEOUT_MS = 15_000;
+/** Poll until the document marked before a navigation has been replaced and the new one has a composer. */
+async function waitForReloadedDocument(page, deadline) {
+    while (Date.now() < deadline) {
+        try {
+            if (await evaluateOnPage(page, reloadedDocumentReadyExpression()) === true)
+                return true;
+        }
+        catch (error) {
+            if (!/execution context|cannot find context|Runtime\.evaluate failed/i.test(String(error)))
+                throw error;
+        }
+        await sleep(300);
+    }
+    return false;
+}
 async function waitForFreshChatGptPage(page, timeoutMs) {
     const deadline = Date.now() + timeoutMs;
     while (Date.now() < deadline) {
@@ -3682,8 +3699,16 @@ export async function sendChatGptPrompt(options) {
         // caller timed out and released the process lock. Project homes supply
         // their own fresh composer and must not pass through the root first.
         const freshUrl = options.temporary ? "https://chatgpt.com/?temporary-chat=true" : "https://chatgpt.com/";
+        // A tab already on the root is an empty chat before the navigation
+        // commits, so the fresh-chat check passed on the page being left and the
+        // send then typed or attached into a document that was replaced under it
+        // (measured: "composer has no file input" on every attach from the root).
+        // The mark proves the page in hand is the one the navigation produced.
+        await evaluateOnPage(page, markDocumentForReloadExpression());
         await navigateIdleChatGptPage(page, freshUrl);
-        if (!await waitForFreshChatGptPage(page, 8_000)) {
+        const freshDeadline = Date.now() + FRESH_CHAT_TIMEOUT_MS;
+        if (!await waitForReloadedDocument(page, freshDeadline) ||
+            !await waitForFreshChatGptPage(page, Math.max(0, freshDeadline - Date.now()))) {
             throw new ChatGptBrowserBlockerError({
                 code: "fresh_chat_not_ready",
                 message: "The new-chat page did not become an empty conversation. Nothing was sent.",
@@ -5098,7 +5123,23 @@ export function attachmentStateExpression(fileNames) {
       .map((el) => (el.getAttribute("aria-label") || el.getAttribute("title") || el.getAttribute("alt") || ""))
       .join(String.fromCharCode(10));
     const haystack = text + String.fromCharCode(10) + labels;
-    const present = names.filter((name) => haystack.includes(name));
+    // Uploading a name that was used before makes ChatGPT show it as
+    // "stem(3).ext", so that spelling counts as the same file.
+    const shownAsRenamed = (name) => {
+      const dot = name.lastIndexOf(".");
+      const stem = dot > 0 ? name.slice(0, dot) : name;
+      const ext = dot > 0 ? name.slice(dot) : "";
+      let from = 0;
+      while ((from = haystack.indexOf(stem + "(", from)) !== -1) {
+        let i = from + stem.length + 1;
+        const digitsStart = i;
+        while (i < haystack.length && haystack[i] >= "0" && haystack[i] <= "9") i += 1;
+        if (i > digitsStart && haystack.startsWith(")" + ext, i)) return true;
+        from += 1;
+      }
+      return false;
+    };
+    const present = names.filter((name) => haystack.includes(name) || shownAsRenamed(name));
     const attachedFiles = [...document.querySelectorAll('input[type="file"]')]
       .reduce((total, el) => total + (el.files ? el.files.length : 0), 0);
     // A visible progressbar means a file is still going up; sending now would

package/docs/releasing.md

@@ -16,6 +16,81 @@ 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.22 Release Record
+
+Release commit `a5f9596` on `main` (cut after PR #12, merge `563f381`); tag `v0.40.22`.
+
+**Publishing**
+- `publish.yml` run 36817391329 failed on its first attempt on macOS 15 Intel and Windows Server 2025. The failures were 30 s test timeouts in `tests/store.test.ts` (both runners) and `tests/followup-budget.test.ts` (Windows). Neither test touches the change, and PR #12 had passed all six platforms.
+- Nothing was published by that attempt.
+- Re-running the failed jobs passed all six platforms. npm publish with SLSA v1 provenance and the GitHub Release followed (2026-10-01 05:31 UTC).
+- Before tagging, `npm run release:verify` passed on the release commit after a build.
+
+**What it fixes**
+- Repeat attachments: ChatGPT shows a re-uploaded name as `name(3).txt`.
+
+**Installation on 2026-10-01**
+- Global npm, each verified with `prodex --version` = 0.40.22.
+- WSL, M3, Mac mini: installed. Running services were not restarted: 6 stdio MCP servers on WSL and 7 on M3 keep older code until their clients reconnect. The Mac mini had none running.
+- M4: not reachable (hostname does not resolve); not updated.
+- The browser container builds from its own branch. It received the same fix in its 2026-10-01 rebuild; an npm install does not update it.
+
+**Live check after install**
+- A `--new-chat --attach` send from WSL through the installed 0.40.22 failed three times with "composer has no file input". This is a separate defect in the new-chat wait, fixed in the next change.
+- With that fix built from source, the same file attached twice answered both times. That also exercises the 0.40.22 renamed-upload fix on the host browser.
+
+## Browser Container Rebuild 2026-10-01
+
+The container image was rebuilt again from `feat/headless-browser-compatibility` `b5eac7d` with uncommitted patches. None of them is pushed to that branch; they still have to be reconciled when that branch merges with `main`.
+
+**Patches**
+- The streaming selector from 2026-09-30.
+- The new-chat wait raised from 8 s to 15 s.
+- The non-text (image) answer detection from 0.40.21, adapted to the branch's message reader.
+- The renamed-upload attachment fix from this change.
+
+**Image and checks**
+- Image `sha256:d2880fda5ab9`.
+- Full suite 1989 passed on the patched tree.
+- Each container swap was gated on the send lock being free (lock file absent, or its holder pid dead). The 2026-09-30 check only looked at process names.
+
+**Verified live in the container after the swap**
+- Three fresh-chat sends in a row answered, 35-36 s each; this flow failed about one send in three before the patch.
+- A create-image send returned the non-text note in 49 s, where it had timed out after 6 min 40 s.
+- The same file attached twice in a row answered `plum-7` both times. Before the fix, the second upload, shown by ChatGPT as `attach-probe(3).txt`, waited out the upload budget.
+- An MCP `initialize` through `scripts/container-client.mjs` answered (server reports 0.40.18, the branch's version).
+
+**Impact on clients**
+- Clients connected to the container's MCP have to reconnect after each swap.
+
+## Browser Container Rebuild 2026-09-30
+
+Not an npm release; the container `prodex-browser-browser-1` builds from `feat/headless-browser-compatibility`, so this section records its state.
+
+A live check of the container build of `b5eac7d` (2026-09-30) found: web search and temporary chats answered; fresh-chat sends failed intermittently with `fresh_chat_not_ready`; `--attach` failed on the upload budget; a create-image send timed out after 6 min 40 s; and streaming was never detected (15 of 15 samples reported idle while ChatGPT showed its Stop button), because the branch's `CHATGPT_STREAMING_SELECTOR` does not match the redesigned composer's plain `aria-label="Stop"` button.
+
+**Rebuild.** Image `sha256:45951848a88b`, built from `b5eac7d` plus one uncommitted line: `CHATGPT_STREAMING_SELECTOR` gained `form button[aria-label="Stop"]` and `form button[aria-label="중지"]`, the same selectors `main` shipped in 0.40.21. Nothing was pushed to that branch; the change lives only in the image. Verified: the selector is present in `/app/dist/chatgpt-browser.js`; container healthy with the profile volume kept; `pro browser login --wait` found the session READY; a fresh-chat send answered in 20 s while a 1 s sampler read the page as generating on all 9 samples during which the Stop button was visible (task `task_20260930_014256`).
+
+**Interrupted consult.** The swap at about 01:37 UTC interrupted a consult that another session had started over MCP at 01:34:31 (`task_20260930_013431`, left `claimed` with no thread), and dropped every client's MCP connection to the container; clients have to reconnect with `/mcp`. The pre-swap check only looked for `pro browser ask` processes and missed MCP consults. Before swapping the container again, check whether the send lock's holder process is alive, not the process names. Whether ChatGPT accepted that prompt was never recorded, so it must not be resent blindly.
+
+**Still open on the branch, not fixed in this image.**
+
+- Fresh-chat flake: the new-chat page took 5.2, 5.2, 5.6 and 8.5 s to become ready in four timed runs inside the container, while `waitForFreshChatGptPage` allows 8 s. The fix is a longer budget.
+- `--attach` and create-image failures: `main` 0.40.21 has fixes for both.
+- These belong to the branch owner and have to be reconciled when the branch merges with `main`.
+
+## 0.40.21 Release Record
+
+Release commit `936b009` on `main` (cut after PR #10, merge `5e74ba2`); tag `v0.40.21`. `publish.yml` run 36538816944 passed all six platforms on the first attempt, then npm publish with SLSA v1 provenance and the GitHub Release (2026-09-29 08:08 UTC).
+
+What it fixes: what 0.40.20 left broken after the ChatGPT redesign - sends starting on a fresh chat, composer tools, `--project-new`, image answers that timed out, and response streaming that was never detected. Found by a live feature matrix against the published 0.40.20; each fix re-run live before release. `--project-new` created a probe project in the user's account, which was deleted afterwards through the project's own actions menu after checking the menu belonged to that project; the other nine projects were compared by id and left intact.
+
+Installation on 2026-09-29, global npm, each verified with `prodex --version` = 0.40.21:
+
+- WSL, M3, Mac mini: installed. On WSL a fresh-chat consult through the installed binary answered (`v21-ok`). Running services were not restarted: 3 stdio MCP servers on WSL and 4 on M3 keep older code until their clients reconnect; the Mac mini had none.
+- M4: not reachable (hostname does not resolve); not updated.
+- The browser container still runs its own build of `feat/headless-browser-compatibility` `b5eac7d` (see 0.40.20); it was not rebuilt for this release.
+
 ## 0.40.20 Release Record
 
 Release commit `b8f8004` on `main` (cut after PR #9, merge `b134eae`); tag `v0.40.20`. `publish.yml` run 36522237267: the first attempt failed on macOS 15 Intel, where `tests/cli.test.ts` "uses an explicit --cwd target for doctor checks" exceeded its 30 s timeout on the slowest runner (full suite 9.5 min there; the same code had passed that runner in PR #9's CI, and no earlier failed CI run showed this test). Nothing was published by that attempt. Re-running the failed job passed all six platforms, then npm publish with SLSA v1 provenance and the GitHub Release (2026-09-29 05:18 UTC).

package/package.json

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