@youdie006/prodex 0.40.27 → 0.40.28

package/dist/chatgpt-browser.js

@@ -844,8 +844,10 @@ 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;
+// Measured 5.2-8.5 s for the new-chat page to settle (2026-09-30), and over
+// 15 s for back-to-back sends with the host at load average 28-32 on 8 cores
+// (2026-10-06). It is only a ceiling: a ready page returns at once.
+const FRESH_CHAT_TIMEOUT_MS = 30_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) {
@@ -1750,6 +1752,13 @@ async function waitForExpressionTrue(cdp, expression, timeoutMs, intervalMs = 15
 const MENU_OPEN_TIMEOUT_MS = 5_000;
 const MENU_SETTLE_TIMEOUT_MS = 5_000;
 const PROJECT_NAVIGATION_TIMEOUT_MS = 8_000;
+/**
+ * How long the composer's own controls (model selector, tools button, file
+ * input) may take to appear after the editor. Measured over 8 s for the model
+ * selector on back-to-back sends with the host at load average 24-44
+ * (2026-10-06). It is only a ceiling: a rendered control returns at once.
+ */
+const COMPOSER_RENDER_TIMEOUT_MS = 30_000;
 export function menuOpenExpression() {
     return `Boolean(document.querySelector('[data-testid="composer-intelligence-picker-content"],[role="menu"]:has([role="slider"])'))`;
 }
@@ -2846,7 +2855,7 @@ async function selectModelReasoning(cdp, options, selectionWarnings = []) {
     // the same pattern succeeded either side of it. The neighbouring waits for
     // the same kind of render already allow six to eight.
     let button = { ok: false };
-    const buttonDeadline = Date.now() + PROJECT_NAVIGATION_TIMEOUT_MS;
+    const buttonDeadline = Date.now() + COMPOSER_RENDER_TIMEOUT_MS;
     for (;;) {
         button = await cdp.evaluate(modelButtonRectExpression());
         if (button.ok && button.x !== undefined && button.y !== undefined)
@@ -5156,7 +5165,6 @@ export function insertComposerTextInPageExpression(text) {
 export function composerFileInputSelector() {
     return 'input[type="file"]:not([accept*="image"])';
 }
-const COMPOSER_FILE_INPUT_TIMEOUT_MS = 15_000;
 const COMPOSER_TOOLS_MENU_ATTEMPTS = 3;
 export const PRODEX_ATTACH_INPUT_ATTRIBUTE = "data-prodex-attach-input";
 /**
@@ -5279,7 +5287,7 @@ export async function attachFilesToComposer(cdp, absolutePaths, options = {}) {
     // this point in that window sometimes. Wait for the input itself, before
     // the chip check (chips render with it) and before reading the DOM tree.
     const waitForComposerFileInput = async () => {
-        const inputDeadline = Date.now() + COMPOSER_FILE_INPUT_TIMEOUT_MS;
+        const inputDeadline = Date.now() + COMPOSER_RENDER_TIMEOUT_MS;
         for (;;) {
             try {
                 if (await cdp.evaluate(markComposerFileInputExpression()) === true)
@@ -5504,7 +5512,7 @@ export async function enableComposerTools(cdp, labels) {
         // The server-rendered editor shows before the app attaches the composer's
         // controls (measured 2026-10-06), so a first miss is usually just early.
         let button = await cdp.evaluate(composerToolsButtonRectExpression());
-        const buttonDeadline = Date.now() + COMPOSER_FILE_INPUT_TIMEOUT_MS;
+        const buttonDeadline = Date.now() + COMPOSER_RENDER_TIMEOUT_MS;
         while ((!button.ok || button.x === undefined || button.y === undefined) && Date.now() < buttonDeadline) {
             await sleep(500);
             button = await cdp.evaluate(composerToolsButtonRectExpression());

package/docs/releasing.md

@@ -16,6 +16,58 @@ 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.
 
+## Browser Container Rebuild 2026-10-06 (afternoon)
+
+**Patches now committed**
+- The patches the container runs on top of `feat/headless-browser-compatibility` `b5eac7d` are now committed on their own branch, `container/redesign-patches`:
+  - `0c3a9cc`: every patch from 2026-09-30 to 2026-10-06.
+  - `1233603`: the 30 s composer-render ceiling from this change.
+- They had lived only in a scratch worktree.
+- `feat/headless-browser-compatibility` itself is unchanged.
+
+**Image**
+- `sha256:ce0240c0e8a4` was built from `1233603`, and the branch suite passed (2002).
+- The swap was gated on the send lock being free.
+
+**Verified**
+- Three back-to-back `--model Pro --pro-mode` new-chat sends answered (42-50 s each).
+- Before this, a real consult from another session had been refused as `composer_not_ready` (`task_20261006_050125`) under host load average 24-44.
+
+**Host load**
+- The load came from an unrelated container, `apo-neo4j`, which had restarted 57,058 times because it could not resolve its own hostname. The user is handling it.
+
+## 0.40.27 Release Record
+
+Release commit `f84ce2b` on `main` (cut after PR #17, merge `9dad219`); tag `v0.40.27`.
+
+**Publishing**
+- `publish.yml` run 37419470087 passed all six platforms on the first attempt, then npm publish with SLSA v1 provenance and the GitHub Release (2026-10-06 05:57 UTC).
+- `npm run release:verify` on the release commit passed on its second run. The first failed in package smoke, where the fake DevTools endpoint did not answer within 500 ms while the host load average was about 30 (8 cores).
+
+**What it fixes**
+- Source pills in page-read answers are spelled out as markdown links or `[label]`.
+- Recovery waits for the thread's turns instead of refusing its own request right after navigating.
+
+**Installation on 2026-10-06**
+- Global npm, each verified with `prodex --version` = 0.40.27.
+- WSL, M3, Mac mini: installed. Running services were not restarted: 5 stdio MCP servers on WSL and 4 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.27, shared WSL browser)**
+- All answered:
+  - a new-chat attachment
+  - a web-search answer, ending in a markdown source link
+  - a project send
+  - `pro browser recover` with the tab on another conversation, which returned the answer
+
+**Browser container, same day**
+- The pill and recovery fixes were adapted to the branch code.
+- A consult from another session (task `task_20261006_050125`, 05:01 UTC) had been refused with `composer_not_ready`. Back-to-back `--model Pro` new-chat sends reproduced a related failure, `fresh_chat_not_ready`: the new-chat page took more than 15 s to settle with the host load average at 28-32. The branch's new-chat ceiling was raised to 30 s. It is only a ceiling.
+- Image `sha256:2b76266ad524`. The earlier interrupted-looking consult `task_20261006_050200` had finished at 05:07, before the swap.
+- The swap was gated on the send lock being free.
+- Two branch tests failed in the pre-build run, and the build script did not stop on test failures, so the image was built and swapped anyway. One test advanced a fake clock 25 s against the new 30 s ceiling; it was fixed. The other was a load-sensitive project-sidebar test, which passed on rerun. After that, the full branch suite passed (2002). The image's runtime code is the code that passed.
+- Verified: three back-to-back `--model Pro --pro-mode` new-chat sends answered (44-50 s each).
+
 ## 0.40.26 Release Record
 
 Release commit `b413c24` on `main` (cut after PR #16, merge `af5cf20`); tag `v0.40.26`.

package/package.json

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