@youdie006/prodex 0.40.49 → 0.40.51

package/dist/tui.js

@@ -120,10 +120,13 @@ export function projectsWithIdsExpression() {
   return out;
 })()`;
 }
-/** The conversations that live inside a project, or all of them without one. */
+/**
+ * The conversations that live inside a project. A project whose id is unknown
+ * claims none: returning all of them listed unrelated chats under its name.
+ */
 export function conversationsInProject(conversations, projectId) {
     if (!projectId)
-        return conversations;
+        return [];
     return conversations.filter((conversation) => conversation.gizmoId === projectId);
 }
 /**
@@ -358,12 +361,26 @@ export function renderProgressBar(input) {
     // Saying how to abort belongs on the waiting line itself: a consult can run
     // for many minutes and the only other thing on screen is the bar.
     const stop = "ctrl-c to stop";
-    if (!input.budgetMs || input.budgetMs <= 0)
-        return `${spinner} ${input.label}  ${elapsed}  ${stop}`;
-    const width = Math.max(4, input.width ?? 28);
-    const ratio = input.elapsedMs / input.budgetMs;
-    const filled = Math.min(width, Math.round(Math.min(ratio, 1) * width));
-    const bar = `${"#".repeat(filled)}${"-".repeat(width - filled)}`;
-    const over = ratio > 1 ? "  over budget" : "";
-    return `${spinner} [${bar}] ${elapsed} / ${formatElapsed(input.budgetMs)}  ${input.label}${over}  ${stop}`;
+    let compose;
+    if (!input.budgetMs || input.budgetMs <= 0) {
+        compose = (label) => `${spinner} ${label}  ${elapsed}  ${stop}`;
+    }
+    else {
+        const width = Math.max(4, input.width ?? 28);
+        const ratio = input.elapsedMs / input.budgetMs;
+        const filled = Math.min(width, Math.round(Math.min(ratio, 1) * width));
+        const bar = `${"#".repeat(filled)}${"-".repeat(width - filled)}`;
+        const over = ratio > 1 ? "  over budget" : "";
+        const budget = formatElapsed(input.budgetMs);
+        compose = (label) => `${spinner} [${bar}] ${elapsed} / ${budget}  ${label}${over}  ${stop}`;
+    }
+    const line = compose(input.label);
+    if (input.columns === undefined || displayWidth(line) < input.columns)
+        return line;
+    // The line is redrawn in place, and one that wraps leaves a row behind on
+    // every redraw (found 2026-11-09: 102 columns at 80, a new row every 250
+    // ms). The label gives way first; a terminal too narrow even for the rest
+    // gets the line cut.
+    const room = input.columns - 1 - displayWidth(compose(""));
+    return truncateToWidth(compose(room > 0 ? truncateToWidth(input.label, room) : ""), input.columns - 1);
 }

package/docs/clients.md

@@ -52,12 +52,17 @@ follow-up checkpoint (integer 0-1000; default 5). For example:
 PRODEX_MAX_AUTO_FOLLOWUPS = "8"
 ```
 
-The initial fresh consult is not a follow-up. Reservations are counted before sends
-and persist across reconnects, older task references, and different session keys in
-the same bridge and conversation. Failed/uncertain attempts count too. At the limit,
+The initial fresh consult is not a follow-up. A follow-up is reserved once its prompt
+is typed, right before it is submitted, and reservations persist across reconnects,
+older task references, and different session keys in the same bridge and
+conversation. A send refused before that point, such as `composer_not_ready`, does
+not count; an attempt that fails or is uncertain after submitting does. At the limit,
 the tool returns `status: "awaiting_user"`, `task_id: null`, the intended continuation
 arguments, and `followup_budget: {limit, used, remaining}` without creating a consult
-task or sending a prompt. This response-only status is not a ledger task status.
+task or sending a prompt. This response-only status is not a ledger task status. If
+another follow-up in the same conversation uses the last of the budget while this one
+waits for the browser, this one stops before submitting with the same response, and
+its consult task is recorded as blocked with `followup_approval_required`.
 
 Ask the user whether to continue. Only after an explicit user request/approval may
 the caller send that continuation with `user_approved: true`. This human-directed
@@ -86,6 +91,17 @@ ChatGPT is still generating. Recover that marked request instead of resending it
 The separate `prodex start` HTTP server runs in the foreground and also needs its
 own process kept alive; neither command installs a background service.
 
+Cancelling a `pro_consult` (Esc in the client, or the client's own tool timeout,
+both of which send `notifications/cancelled`) stops it while its prompt has not been
+submitted: nothing is sent, the consult is recorded as blocked with
+`consult_cancelled`, and a follow-up spends none of its budget. After the prompt is
+submitted, cancelling changes nothing on prodex's side: the answer is still waited
+for and saved to the consult's record.
+
+One stdio message may be up to 128 MiB, which covers the largest call any tool
+accepts. A larger one ends the server with exit code 1 and a one-line reason on
+stderr, so the client sees the server go away instead of waiting on it.
+
 ## Claude Code
 
 See [claude.md](claude.md), or:

package/docs/http-mcp.md

@@ -19,6 +19,7 @@ Typical use:
 
 The server is personal and local-first. Do not expose it as a shared service.
 HTTP MCP requests are bounded: malformed JSON returns `400`, and request bodies over 1 MiB are rejected with `413`.
+Sessions are bounded too. A session with no request for 30 minutes and no stream open is closed, and at most 100 sessions are kept: initializing one more closes the least recently used. A request carrying a closed session's `Mcp-Session-Id` gets `404`, as an unknown id does, and MCP clients answer that by initializing a new session.
 
 ## Build And Prepare
 
@@ -193,8 +194,9 @@ The HTTP server exposes the same tool catalog as stdio MCP:
 Writes are deliberately gated and require a git worktree with a committed HEAD:
 
 1. `repo_write_file_dry_run` previews replacing an existing repo-relative text file. It records the diff, git HEAD, preimage hash, and a replacement-text artifact under `.bridge/artifacts/repo-writes/`.
+   The file keeps its CRLF line endings, UTF-8 BOM and final newline when the new content leaves them out, and apply keeps its file mode, so an edited script stays executable. A file that is not UTF-8 text (EUC-KR, Latin-1, UTF-16) is refused rather than re-encoded.
 2. `repo_write_file_apply` applies that exact receipt only if git HEAD, file path, preimage hash, and artifact content still match.
-3. `repo_stage_reviewed_paths` stages only files backed by matching applied write receipts.
+3. `repo_stage_reviewed_paths` stages only files backed by matching applied write receipts. Their paths reach git literally, so a name such as `pages/[id].tsx` stages that file and nothing it would match as a pattern.
 
 There is no direct ungated write tool and no shell execution tool.
 

package/docs/releasing.md

@@ -16,6 +16,145 @@ 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.50 Release Record
+
+Release commit `759065f` on `main` (cut after PRs #84-#87, last merge `d8333f2`); tag `v0.40.50`, published 2026-11-04. Released on the user's go-ahead as a batch, together with the container swaps:
+- #84: session ids carried the start of the prompt.
+- #85: the model lookup took an open "Edit message" editor for the composer.
+- #86: the tool-state check read a hidden workspace's composer.
+- #87: an MCP follow-up refused before submitting still spent the automatic follow-up budget.
+
+**Publishing**
+- `npm run release:verify` passed on the release commit after a build.
+- `publish.yml` run 41746949557 passed. It published to npm with SLSA v1 provenance and created the GitHub Release, which lists the four entries from `CHANGELOG.md`.
+
+**Installed**
+- WSL, M3, Mac mini: `prodex --version` reports 0.40.50.
+- The maintainer watchdog checkout was pulled to `759065f` and rebuilt.
+- MacBook M4: not installed. `ssh m4` timed out before the cut and again after the publish, so it stays on 0.40.49 until it can be reached.
+- No host-side `prodex mcp` was found running on WSL, M3 or the Mac mini. The MCP entries on WSL and M3 relay into the browser containers. Those relays reconnected into the new containers when they were swapped, at 00:24:39 UTC on M3 and 00:50:51 UTC on WSL.
+
+**Container**
+- `container/redesign-patches` `c7c9f35` ports #87, on top of the ports of #85 (`8ce48b9`) and #86 (`e8e3c68`); #84 was ported in `f2d13e6`.
+  - tsc, the full suite (2179 passed, 3 skipped) and `release:verify` pass on it.
+- The agent ran both build-and-swap scripts this time; the user had asked for the swaps.
+- M3 (colima `prodex-check`): image `5760b1464db6`, started 00:24:41 UTC.
+  - It came up healthy with the 1024 process limit, using 193.
+  - `pro browser check` reported logged in with a composer, and the model selection was verified.
+  - `pro browser smoke` answered `PRODEX_PRO_SMOKE_OK` with its request verified.
+- WSL: image `ea56b6ee0f42`, recreated 00:51 UTC.
+  - Another session's send held the browser lock about 25 minutes before the swap. The swap script recreates the container only once the lock is free.
+  - It came up healthy with the 1024 process limit, using 298, and logged no thread errors.
+  - `pro browser check` reported logged in with a composer.
+
+**Verified live on the WSL container (#87)**
+- The check was run through `performBrowserConsultForMcp` in a fresh chat with no project, budget 5. It sent two prompts.
+  - Root: answered `ALPHA`.
+  - A follow-up naming a tool the menu does not offer was refused before anything was typed (`tool_not_offered`).
+  - The next follow-up answered `BETA` and reported `followup_budget` used 1 of 5.
+- The ledger holds a single reservation for that conversation, written at 00:52:49 UTC. That is three seconds after the second follow-up's task was created, right before it was submitted. Before #87 the refused follow-up would have been reservation 1, and this one reservation 2.
+
+## 0.40.49 Release Record
+
+Release commit `74b9c4d` on `main` (cut after PRs #79-#83, last merge `be947df`, docs `7b6a3bd`); tag `v0.40.49`, published 2026-11-01. Released on the user's go-ahead as a batch: #79 (the page's render error saved as the answer), #80 (blank `--tool`), #81 (`--continue` matching a project by the end of its name) and #83 (projects behind the sidebar's "Show more"). #82 changed a test only and has no changelog entry.
+
+**Before the cut**
+- `main` CI on `7b6a3bd` (docs only) failed on macOS Intel: `npm test` ran past the release check's 15-minute budget on a slow runner, with no failing test. On the four runs before it that step took 10.5 to 11.8 minutes. The failed job was rerun and passed.
+
+**Publishing**
+- `npm run release:verify` passed on the release commit after a build.
+- `publish.yml` run 41283791768 passed all six platforms, then npm publish with SLSA v1 provenance and the GitHub Release, which lists the four entries from `CHANGELOG.md`.
+
+**Installed**
+- WSL, M3, Mac mini: `prodex --version` reports 0.40.49.
+- The maintainer watchdog checkout was pulled to `74b9c4d` and rebuilt.
+- MacBook M4 (`m4`), added to the install targets this release. It had two copies:
+  - `~/.local/bin/prodex`, which its Codex MCP entry runs directly, links into `~/.gemini/harness-antigravity/runtime-prodex` (an npm project, 0.40.32). It was updated there with `npm i @youdie006/prodex@0.40.49`.
+  - A global copy under `/opt/homebrew` (0.40.0) was updated with `npm i -g --prefix /opt/homebrew`.
+  - The link pointed at `dist/cli.js`, which is not executable in the new install, because the package's executable has been `prodex.mjs` since 0.40.18. Run directly, it failed with "permission denied", so Codex could not have started the MCP server again. The link now points at the runtime's `node_modules/.bin/prodex`. Through it, `--version` reports 0.40.49 and `prodex mcp` answers `initialize` as 0.40.49.
+- Running services were not restarted. They keep the old code until their client starts them again:
+  - M4: Codex's `prodex mcp`, started before the install.
+  - M3: a `prodex mcp` running since 2026-09-15.
+  - Mac mini and WSL: none on the host. WSL's MCP entry goes through the browser container.
+
+**Verified live on installed 0.40.49 (WSL host browser, scratch repo)**
+- `pro browser projects` listed 25 projects; 0.40.48 listed 9 of the same 25.
+- `pro browser smoke` returned `requestVerified: true`.
+
+**After the release**
+- PR #84 (merge `b7b5d61`, unreleased): session ids no longer carry the start of the prompt.
+
+**Container**
+- `container/redesign-patches` `f2d13e6` ports #84 on top of the ports of #79-#83 (`f93b63f`, `661b2c6`, `106bd0a`, `facd4fd`) and the 1024 process limit (`55f2f3e`). tsc, the full suite (2161 tests) and `release:verify` pass on it.
+- The agent's permission classifier refused the WSL `docker compose build`, so the user ran the build-and-swap scripts. Both images were built from `f2d13e6`. Both swaps waited for the container's send lock to be free.
+- M3 (colima `prodex-check`): image `4bc8fac19752`, started 07:57 UTC.
+  - It came up healthy with the 1024 process limit, using 146.
+  - `pro browser check` reported logged in with a composer.
+  - `pro browser smoke` answered `PRODEX_PRO_SMOKE_OK` with its request verified.
+  - A dry-run `pro ask "Draft the payroll memo"` (nothing sent) got the id `sess_20261101_075935_93598ff4`, with no prompt words in it.
+- WSL: image `e2e3523b640a`.
+  - The first run built the image but did not swap, because a Pro consult from another session had held the send lock since 07:54 UTC.
+  - The swap waited for that consult, which finished `done`. The lock cleared at 08:06:32, and the container was recreated at 08:06:35.
+  - It came up healthy with the 1024 process limit, using 177, and logged no thread errors.
+  - `pro browser check`, `smoke` and the dry-run id check gave the same results as on M3 (id `sess_20261101_080804_33e445d8`).
+  - The swap dropped every MCP client of the WSL container, so each WSL Claude Code session needs `/mcp`.
+- Both containers' `prodex --version` still prints 0.40.18, because the container branch never bumps its version.
+
+**MCP clients kept connected across container swaps (2026-11-01, after the swaps)**
+- Both swaps had dropped every MCP client of their container: `scripts/container-client.mjs mcp` piped the client into `docker exec` and ended with it, so each Claude Code session needed `/mcp` typed by hand.
+- `container/redesign-patches` `964b847` turns that command into a relay that reconnects:
+  - it answers requests in flight with an error that names `pro_recover`;
+  - it runs `docker exec` again until the container is back, holding new requests for up to 60 seconds;
+  - it replays the client's handshake, tells the client its tools may have changed, and then passes the held requests on.
+- Verified:
+  - 6 new tests; suite 2167 passed; `release:verify` ok.
+  - On a throwaway container from the same image, one client connection listed 20 tools, survived a restart and then a delete-and-recreate, and listed 20 tools again each time.
+- WSL deployment:
+  - The prodex MCP entries used to run the script from `/mnt/d/myproject/gptprouse`, a checkout another task keeps on its own branch.
+  - Three Claude configs now run it from a checkout pinned for this purpose, `~/.local/share/prodex-maint/container-src` at `964b847`: `~/.claude.json` and the two swapdex slot configs that had the entry.
+  - The Codex config (`~/.codex/config.toml`) was changed the same way.
+  - `claude mcp get prodex` reports Connected. A handshake through it reached the WSL container (server 0.40.18, 20 tools).
+- M3 deployment:
+  - Its Claude and Codex configs run an installed copy, `~/.local/share/prodex/container-installed-8d7a094-wP3RK2/container-client.mjs`.
+  - That file was replaced in place with `964b847`'s; the old one is kept beside it as `container-client.mjs.8d7a094.bak`. The configs are unchanged.
+  - A handshake through it reached the M3 container.
+- Sessions that were open during the swaps still need one `/mcp`. After that, a container restart or swap no longer disconnects them.
+- When `container-client.mjs` changes again, both copies must be updated:
+  - WSL: move the pinned checkout to the new commit;
+  - M3: replace the installed copy.
+
+## Container consults ran on the last model selected (2026-11-01)
+
+**What happened**
+- The user reported that some sessions' consults did not use Pro but whatever model the browser last had.
+- In the WSL container's results, 20 consults since 2026-10-10 carry `model_selection_warning: no model/effort was selected`. Today's 07:54 UTC Pro consult from another session is one of them.
+- Cause: a consult that names no model, with no saved or environment default, keeps the picker's current selection. That is the designed fallback, but in a shared browser the current selection is whatever another session (or an Instant smoke test) picked last.
+  - The container's MCP server had neither default. `container-client.mjs mcp` passed no variables into the container, so an MCP entry's env block could not reach it, and the bridge in the container had no saved config.
+  - The host entries on WSL that run `prodex mcp` directly set `PRODEX_DEFAULT_MODEL=Pro` and were not affected.
+
+**Fixes**
+- `container/redesign-patches` `cd3b671`: `mcp` passes the client's `PRODEX_DEFAULT_MODEL`, `_EFFORT`, `_PRO_MODE` and `_PROJECT` into the container, and adds `PRODEX_DEFAULT_MODEL=Pro` when none of them names a model or a reasoning step. A consult's own `model` or `effort` still wins.
+  - Verified: 3 new tests, suite 2170 passed, `release:verify` ok.
+  - In the container, the resolved defaults went from `null` to `{"model":"Pro"}`.
+  - A consult that named no model, sent through the new client, came back done.
+- Deployed to the WSL pinned checkout (`~/.local/share/prodex-maint/container-src` at `cd3b671`) and to the M3 installed copy.
+- The 16 WSL sessions had reconnected (17:35-17:37 KST) before `cd3b671` was in place, so their relays still run the version without the default.
+  - So the bridge inside each container now saves Pro: `setup --cwd /home/node/bridge --model Pro` on WSL and M3. That writes `.bridge/config.local.json` with a loopback HTTP profile; no HTTP server runs there.
+  - Each consult reads this default, so it applies to connected clients at once. A consult through one of the old relays, naming no model, came back done from Pro.
+- Each such consult carries the warning `model_is_now_an_effort`, because the current picker has Pro as an effort step. The model default is kept because a model or effort the consult names itself overrides it. A saved effort default would be applied on top of a model the consult names.
+
+**M4 and Mac mini (host `prodex mcp`, 2026-11-03)**
+- Neither machine's Claude or Codex entry set `PRODEX_DEFAULT_MODEL`. On M4, `.bridge/results` held one consult of five with the no-model warning (`~/.gemini/harness-antigravity/verification`).
+- M4:
+  - `~/.claude.json` now has `env: {PRODEX_DEFAULT_MODEL: Pro}`, set with `claude mcp remove` and `add-json`.
+  - `~/.codex/config.toml` `[mcp_servers.prodex]` now has `env = { PRODEX_DEFAULT_MODEL = "Pro" }`. A backup is kept as `config.toml.bak-prodex-default-20261103`, and `codex mcp get prodex` parses it.
+  - The three running `prodex mcp` processes keep their old environment until their clients restart them.
+- Mac mini: the same change, made on the user's explicit request after the first attempt was refused:
+  - Claude `~/.claude.json` now carries `env: {PRODEX_DEFAULT_MODEL: Pro}`.
+  - Codex `~/.codex/config.toml` has the same `env` line, with the backup `config.toml.bak-prodex-default-20261103`. `codex mcp get prodex` shows the variable set.
+  - No `prodex mcp` was running there, so the next client start uses it.
+- A WSL Codex session started on 2026-10-28 still runs the client from the old path until it restarts. Its config, `~/.codex/config.toml` (linked from every swapdex slot), already points at the pinned checkout.
+
 ## Browser Incident 2026-10-30: WSL browser container out of threads
 
 **What happened**

package/package.json

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