@youdie006/prodex 0.40.26 → 0.40.27

package/dist/chatgpt-browser.js

@@ -191,7 +191,40 @@ export const CHATGPT_BLOCKER_SCAN_EXCLUDED_ANCESTORS = `${'[data-message-author-
  * sat in the thread for ten minutes while prodex waited for it. The model slug
  * attribute went with it; where it is absent the model is simply not known.
  */
-const CHATGPT_MESSAGE_NODES_JS = `
+/**
+ * A message's text with its source pills spelled out.
+ *
+ * Measured 2026-10-06: ChatGPT renders each source as an inline pill
+ * ([data-chatgpt-copy-reference]) and innerText puts its label on a line of
+ * its own, so a page-read answer came back as "walnut-9" plus a line
+ * "cont-att", or ended in a bare "blog.rust-lang.org" that read as part of
+ * the answer. A web source becomes " [label](url)", as the transcript reader
+ * writes it; a file source has no link and becomes " [label]". The label is
+ * looked for on its own line first, so the same words earlier in the prose
+ * are left alone.
+ */
+export const CHATGPT_RENDERED_MESSAGE_TEXT_JS = `
+    const renderedMessageText = (root) => {
+      let text = root.innerText || "";
+      const newline = String.fromCharCode(10);
+      const isSpace = (ch) => ch === " " || ch === newline || ch === String.fromCharCode(9) || ch === String.fromCharCode(13);
+      let cursor = 0;
+      for (const pill of [...root.querySelectorAll('[data-chatgpt-copy-reference]')]) {
+        const label = (pill.innerText || "").trim();
+        if (!label) continue;
+        const onOwnLine = text.indexOf(newline + label, cursor);
+        const at = onOwnLine >= 0 ? onOwnLine + 1 : text.indexOf(label, cursor);
+        if (at < 0) continue;
+        let start = at;
+        while (start > cursor && isSpace(text[start - 1])) start -= 1;
+        const link = pill.querySelector('a[href^="http"]');
+        const rendered = link ? " [" + label + "](" + link.getAttribute("href") + ")" : " [" + label + "]";
+        text = text.slice(0, start) + rendered + text.slice(at + label.length);
+        cursor = start + rendered.length;
+      }
+      return text;
+    };`;
+const CHATGPT_MESSAGE_NODES_JS = `${CHATGPT_RENDERED_MESSAGE_TEXT_JS}
     // ChatGPT keeps a previously opened conversation mounted but hidden
     // (measured 2026-10-06: two turns without a box on a project home), and
     // counting them made a fresh chat look like an existing conversation.
@@ -3437,6 +3470,14 @@ export async function recoverChatGptAnswerFromThread(options) {
                 lastAnswer = "";
                 continue;
             }
+            // A thread that is still loading already has the target URL but no
+            // turns (measured 2026-10-06), and judging the request on it refused a
+            // recovery of the very request it was asked for.
+            if (state.userMessageCount === 0) {
+                stableRuns = 0;
+                lastAnswer = "";
+                continue;
+            }
             if (options.requestId && !chatGptRequestMarkerMatches(state.lastUserText ?? "", options.requestId)) {
                 throw new ChatGptBrowserBlockerError({
                     code: "request_mismatch",
@@ -6019,7 +6060,7 @@ export function answerExpression() {
         const tagged = node.closest('[data-message-model-slug]');
         if (tagged) modelSlug = tagged.getAttribute('data-message-model-slug') || undefined;
       }
-      return { role, node, text: textNode.innerText || "", modelSlug };
+      return { role, node, text: renderedMessageText(textNode), modelSlug };
     });
     const assistantMessages = messages.filter((message) => message.role === "assistant");
     const userMessages = messages.filter((message) => message.role === "user");

package/docs/releasing.md

@@ -16,6 +16,52 @@ 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.26 Release Record
+
+Release commit `b413c24` on `main` (cut after PR #16, merge `af5cf20`); tag `v0.40.26`.
+
+**Publishing**
+- `publish.yml` run 37405732176 passed all six platforms on the first attempt, then npm publish with SLSA v1 provenance and the GitHub Release (2026-10-06 03:07 UTC).
+- PR #16's own CI needed one rerun on macOS Intel for an unrelated 30 s timeout in `tests/mcp-consult.test.ts`.
+- `npm run release:verify` passed on the release commit after a build.
+
+**What it fixes**
+- The ChatGPT page measured on 2026-10-06 broke several flows:
+  - Every project send was refused because a hidden, still-mounted conversation was counted.
+  - Attachments did not recognize timestamp-renamed uploads, picked a hidden composer form, and ran before the file input existed.
+  - Leftover chips were no longer detected.
+  - Composer tools were looked up or clicked before they worked.
+- Found by a live matrix against the installed 0.40.25, where `--project` sends, project attachments, new-chat attachments after a repeat upload and `--tool create-image` failed.
+
+**Installation on 2026-10-06**
+- Global npm, each verified with `prodex --version` = 0.40.26.
+- WSL, M3, Mac mini: installed. Running services were not restarted: 11 stdio MCP servers on WSL and 6 on M3 keep older code until their clients reconnect. The Mac mini had none running.
+- M4: not reachable (hostname does not resolve); not updated.
+
+**Live check after install (installed 0.40.26, shared WSL browser)**
+All eight answered:
+- `--project` plain and with `--attach`
+- `--tool create-image`
+- `--new-chat --attach`
+- `--continue --attach`
+- `--tool web-search --attach`
+- `--temporary --attach`
+- plain `--continue`
+
+**Browser container, same day**
+- Before the rebuild, the container build failed the same way: a project send was refused and a new-chat attachment timed out. Its tab then stopped answering CDP.
+- The same fixes were adapted to the branch code, where the transcript reader and the hover-verified tools click differ. The image `sha256:8e5734ee733c` was rebuilt from `b5eac7d` with all patches so far. These are still uncommitted, and nothing was pushed to `feat/headless-browser-compatibility`.
+- Branch suite: 1998 passed. The swap was gated on the send lock being free.
+- Verified in the container, all seven answered:
+  - a project send
+  - a new-chat attachment
+  - an attachment on a continued thread
+  - a project attachment
+  - create-image
+  - web search with an attachment
+  - a temporary chat with an attachment
+- An MCP client reconnect was needed after the swap.
+
 ## 0.40.25 Release Record
 
 Release commit `3c66da3` on `main` (cut after PR #15, merge `9bd908c`); tag `v0.40.25`.

package/package.json

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