commandmate 0.48.0 → 0.49.1

package/dist/server/src/lib/detection/prompt-detect-multiple-choice-chrome.js

@@ -0,0 +1,193 @@
+"use strict";
+/** Claude chrome (task panel, session-diff HUD, preview pane) split out of prompt-detect-multiple-choice.ts (Issue #3924). */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.SUMMARY_LINE_PATTERN = void 0;
+exports.findClaudeTaskPanelLines = findClaudeTaskPanelLines;
+exports.findClaudeChrome = findClaudeChrome;
+exports.maskClaudeChrome = maskClaudeChrome;
+const picker_chrome_1 = require("./tools/claude/picker-chrome");
+/**
+ * [Issue #704] Pattern for Claude Code v2.1.142 prompt summary lines such as
+ *   "  … +1 pending"
+ *   "  +2 pending"
+ *   "  ↑3 more"
+ *   "  ↓1 more"
+ * These lines are rendered BELOW the real options when Claude collapses the
+ * remaining choices. They are not selectable options and must be skipped by
+ * Pass 2 — otherwise NORMAL_OPTION_PATTERN matches them as option N with
+ * label "pending"/"more", and the resulting (number, label) tuple poisons
+ * isValidPrecedingOption() so that the real 1./2./3. options above are all
+ * rejected (collectedOptions ends up with length 1 and Layer 4 returns
+ * no_prompt).
+ *
+ * Scope of the pattern (FP suppression is critical):
+ *   - Anchored at line start (^) and requires the trailing keyword to be
+ *     `pending` or `more` followed by a word boundary (\b). This intentionally
+ *     prevents matching legitimate option labels that mention these words
+ *     mid-sentence (e.g. `2. Postpone (will remain pending)`,
+ *     `3. Show me more`) — those still flow through NORMAL_OPTION_PATTERN.
+ *   - Optional leading ellipsis (… U+2026) and optional collapse direction
+ *     marker (+ - ↑ ↓ ⏵ ⏷) accept the variants observed in the wild.
+ *   - [Issue #1708] `completed` joined `pending`/`more` after a live capture
+ *     (fixtures/claude-live-1708) showed the task panel collapsing FINISHED
+ *     rows as `… +2 completed`. That wording was outside the #704 guard, so it
+ *     reached Pass 2 and was collected as `option 2 / label='completed'` —
+ *     poisoning isValidPrecedingOption() exactly as `… +1 pending` used to.
+ *   - The pattern deliberately omits any free `(.+)` capture — it must
+ *     short-circuit, not extract data.
+ *
+ * Pattern shape: linear regex with no nested quantifiers — ReDoS safe (S4-001).
+ */
+exports.SUMMARY_LINE_PATTERN = /^\s*[…]?\s*[+\-↑↓⏵⏷]?\s*\d+\s+(?:pending|more|completed)\b/i;
+/**
+ * [Issue #1708] Header row of Claude Code's bottom-anchored task panel, e.g.
+ *   "  7 tasks (0 done, 1 in progress, 6 open)"
+ *
+ * The panel is an overlay pinned to the LAST rows of the pane, structurally
+ * unrelated to whatever the agent is currently blocked on. In a production pane
+ * (200x1000, alternate screen) a prompt dialog therefore renders near the top and
+ * the panel ~880 blank rows below it — rows `compactBlankRows` collapses to one,
+ * putting the panel squarely inside Pass 2's 50-line reverse-scan window.
+ *
+ * That is only harmless while something trims it away. #704/#807 trim at a
+ * footer, but the AskUserQuestion *confirmation* step ("Ready to submit your
+ * answers?") renders NEITHER footer, so nothing trims and the panel is the first
+ * thing the reverse scan meets. Measured on the live capture in
+ * fixtures/claude-live-1708/askuserquestion-submit-taskpanel.txt, two of its rows
+ * match NORMAL_OPTION_PATTERN independently:
+ *   - this header      → option 7,  label "tasks (2 done, 1 in progress, 4 open)"
+ *   - "… +2 completed" → option 2,  label "completed"
+ * Either one alone is enough to make isValidPrecedingOption() reject the real
+ * `❯ 1. Submit answers` / `2. Cancel` above it, so collectedOptions never reaches
+ * 2 and the frame is published as "no prompt" — Issue #1708's silent timeout.
+ *
+ * Anchored at line start and requires the literal `tasks (` + `<n> done`, which
+ * no option label produced by any supported CLI carries. ReDoS safe (S4-001):
+ * bounded repetition, no nesting.
+ */
+const CLAUDE_TASK_PANEL_HEADER_PATTERN = /^\s*\d{1,3}\s+tasks?\s+\(\d+\s+done\b/i;
+/**
+ * [Issue #1708] A single task row of the panel described above, e.g. "  ◼ Phase 3".
+ *
+ * Today these rows are inert — `isContinuationLine()` already absorbs them — but
+ * only because none of the observed titles begins with a digit. A title like
+ * "2. Fix the parser" would render as "  ◻ 2. Fix the parser" and be collected as
+ * option 2, reintroducing the same poisoning from a direction no single-line
+ * guard anticipates. Skipping the whole panel block closes that off structurally
+ * instead of one wording at a time.
+ *
+ * The glyph set is exactly the two forms measured on a live pane — ◼ (in
+ * progress) and ◻ (open) — and nothing else. Every extra glyph is a line this
+ * guard can delete from the frame, so the set is an allowlist of things seen,
+ * not a guess at what the family might contain:
+ *
+ *   - ❯ ● › are DEFAULT_OPTION_PATTERN's cursor indicators.
+ *   - ⏺ ⎿ ✔ ✗ are the transcript markers TURN_BOUNDARY_PATTERN reads.
+ *   - ☐ ☑ ☒ are the natural rendering of a MULTI-SELECT choice, and
+ *     AskUserQuestion has a multiSelect mode. Measured: with those in the set,
+ *     `☐ 1. Blue / ☑ 2. Green / ☐ 3. Red` under a panel header is claimed as
+ *     panel content and the prompt above it disappears entirely
+ *     (isPrompt=false, zero options) — Issue #1708's own failure, recreated by
+ *     its fix. See the regression test.
+ *
+ * A completed row never appears (the panel collapses those into `… +N
+ * completed`, which SUMMARY_LINE_PATTERN handles), so no done-marker is needed.
+ * An unmatched glyph simply ends the block, which is the safe direction: those
+ * rows go back to being handled exactly as they were before this guard existed.
+ *
+ * To widen this, capture a live pane that actually renders the new glyph and add
+ * it as a fixture. Do not widen it from the shape of the character.
+ */
+const CLAUDE_TASK_PANEL_ROW_PATTERN = /^\s*[◼◻]\s/;
+/**
+ * [Issue #2468] Claude Code 2.1.267's session-diff HUD row, in the two
+ * spellings measured on a live pane (tests/fixtures/claude-live-2468):
+ *   "No changes this session"
+ *   "+28 files edited before this session (show)"
+ *
+ * Chrome like the task panel, but a single row and RIGHT-aligned: on a
+ * 200-column pane it is ~110 columns of padding and then the text. It is
+ * therefore matched on the trimmed row — a reader that slices the row from the
+ * left sees nothing but blanks.
+ *
+ * It broke two readers. Pass 2 below parses `+2 files edited …` as option 2,
+ * which poisons the real `1. / 2.` above it the way `… +2 completed` did in
+ * #1708. And `findClaudeTranscriptTail` took it for the last transcript row, so
+ * `detectClaudeDialog` read it as the footer of the AskUserQuestion
+ * confirmation screen — a dialog that draws no footer — and refused a dialog
+ * that was open on screen: Auto-Yes, the UI's answer and `commandmate respond`
+ * all got `prompt_no_longer_active`.
+ *
+ * `files?` is the one spelling not seen on a pane: a one-file session was not
+ * captured, and the singular is accepted so that it is not the case that
+ * regresses. Everything else is literal, for the same reason the glyph set
+ * above is an allowlist. Anchored at both ends, no nested quantifiers — ReDoS
+ * safe (S4-001).
+ */
+const CLAUDE_SESSION_DIFF_HUD_PATTERN = /^(?:No changes this session|\+\d+ files? edited before this session \(show\))$/;
+/**
+ * Line indices belonging to Claude's bottom-pinned panels within [start, end).
+ *
+ * Two panels, both chrome rather than transcript or prompt:
+ *  - the task panel (#1708). Walks down from each header row for as long as
+ *    rows keep looking like panel content (task rows or the collapsed `… +N …`
+ *    summary). The first line that is neither ends the block, so a panel that
+ *    abuts other content cannot swallow it.
+ *  - the session-diff HUD (#2468), a single row claimed on its own.
+ *
+ * Pass 2 here, `findClaudeTranscriptTail` and `detectClaudeDialog`'s footer
+ * guard all read this one set — through {@link findClaudeChrome}, which adds an
+ * AskUserQuestion preview pane to it (Issue #2486) — so they cannot disagree
+ * about which rows are chrome.
+ *
+ * @param lines - Full frame, already ANSI/box stripped
+ * @param start - First index to consider (inclusive)
+ * @param end - Last index to consider (exclusive)
+ * @returns Indices Pass 2 must treat as metadata rather than options
+ */
+function findClaudeTaskPanelLines(lines, start, end) {
+    const panelLines = new Set();
+    for (let i = Math.max(0, start); i < Math.min(end, lines.length); i++) {
+        if (CLAUDE_SESSION_DIFF_HUD_PATTERN.test(lines[i].trim())) {
+            panelLines.add(i);
+            continue;
+        }
+        if (!CLAUDE_TASK_PANEL_HEADER_PATTERN.test(lines[i]))
+            continue;
+        panelLines.add(i);
+        for (let j = i + 1; j < Math.min(end, lines.length); j++) {
+            const row = lines[j];
+            if (!CLAUDE_TASK_PANEL_ROW_PATTERN.test(row) && !exports.SUMMARY_LINE_PATTERN.test(row))
+                break;
+            panelLines.add(j);
+        }
+    }
+    return panelLines;
+}
+/**
+ * Claude's chrome within [start, end). See {@link ClaudeChrome}.
+ *
+ * @param lines - Full frame, ANSI stripped; box drawing optional
+ * @param start - First index to consider (inclusive)
+ * @param end - Last index to consider (exclusive)
+ */
+function findClaudeChrome(lines, start, end) {
+    const rows = findClaudeTaskPanelLines(lines, start, end);
+    const panes = (0, picker_chrome_1.findClaudePreviewPanes)(lines, start, end);
+    for (const row of panes.rows)
+        rows.add(row);
+    return { rows, cuts: panes.cuts };
+}
+/**
+ * The frame with Claude's chrome taken out: chrome rows blank, rows shared with
+ * the preview pane cut back to the options column. Row indices are unchanged,
+ * so a reader of the result can report positions in the original frame.
+ */
+function maskClaudeChrome(lines, chrome) {
+    return lines.map((line, i) => {
+        if (chrome.rows.has(i))
+            return '';
+        const cut = chrome.cuts.get(i);
+        return cut === undefined ? line : line.slice(0, cut).trimEnd();
+    });
+}

package/dist/server/src/lib/detection/prompt-detect-multiple-choice.js

@@ -1,10 +1,7 @@
 "use strict";
 /** Multiple choice prompt detection logic extracted from prompt-detector.ts (Issue #575). */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.joinApprovalTarget = exports.findApprovalContextStart = exports.findApprovalContextRange = exports.APPROVAL_TARGET_MAX_LOOKBACK = void 0;
-exports.findClaudeTaskPanelLines = findClaudeTaskPanelLines;
-exports.findClaudeChrome = findClaudeChrome;
-exports.maskClaudeChrome = maskClaudeChrome;
+exports.maskClaudeChrome = exports.findClaudeTaskPanelLines = exports.findClaudeChrome = exports.joinApprovalTarget = exports.findApprovalContextStart = exports.findApprovalContextRange = exports.APPROVAL_TARGET_MAX_LOOKBACK = void 0;
 exports.isTypedTextFieldOption = isTypedTextFieldOption;
 exports.buildMultipleChoiceResult = buildMultipleChoiceResult;
 exports.detectMultipleChoicePrompt = detectMultipleChoicePrompt;
@@ -14,12 +11,17 @@ const patterns_1 = require("./tools/claude/patterns");
 const prompt_view_1 = require("../../lib/session/prompt-view");
 const option_recommendation_1 = require("./option-recommendation");
 const picker_chrome_1 = require("./tools/claude/picker-chrome");
+const prompt_detect_multiple_choice_chrome_1 = require("./prompt-detect-multiple-choice-chrome");
 const prompt_detect_multiple_choice_approval_context_1 = require("./prompt-detect-multiple-choice-approval-context");
 var prompt_detect_multiple_choice_approval_context_2 = require("./prompt-detect-multiple-choice-approval-context");
 Object.defineProperty(exports, "APPROVAL_TARGET_MAX_LOOKBACK", { enumerable: true, get: function () { return prompt_detect_multiple_choice_approval_context_2.APPROVAL_TARGET_MAX_LOOKBACK; } });
 Object.defineProperty(exports, "findApprovalContextRange", { enumerable: true, get: function () { return prompt_detect_multiple_choice_approval_context_2.findApprovalContextRange; } });
 Object.defineProperty(exports, "findApprovalContextStart", { enumerable: true, get: function () { return prompt_detect_multiple_choice_approval_context_2.findApprovalContextStart; } });
 Object.defineProperty(exports, "joinApprovalTarget", { enumerable: true, get: function () { return prompt_detect_multiple_choice_approval_context_2.joinApprovalTarget; } });
+var prompt_detect_multiple_choice_chrome_2 = require("./prompt-detect-multiple-choice-chrome");
+Object.defineProperty(exports, "findClaudeChrome", { enumerable: true, get: function () { return prompt_detect_multiple_choice_chrome_2.findClaudeChrome; } });
+Object.defineProperty(exports, "findClaudeTaskPanelLines", { enumerable: true, get: function () { return prompt_detect_multiple_choice_chrome_2.findClaudeTaskPanelLines; } });
+Object.defineProperty(exports, "maskClaudeChrome", { enumerable: true, get: function () { return prompt_detect_multiple_choice_chrome_2.maskClaudeChrome; } });
 // ============================================================================
 // Constants
 // ============================================================================
@@ -64,158 +66,6 @@ const DEFAULT_OPTION_PATTERN = /^\s*[\u276F\u25CF\u203A][^\d]*(\d+)(?:\.(?!\d)|\
  * Layer 4 (2+ options), and Layer 5 (SEC-001 question line validation).
  */
 const NORMAL_OPTION_PATTERN = /^\s*[^\d]{0,3}(\d+)(?:\.(?!\d)|\s+)\s*(.+)$/;
-/**
- * [Issue #1708] Header row of Claude Code's bottom-anchored task panel, e.g.
- *   "  7 tasks (0 done, 1 in progress, 6 open)"
- *
- * The panel is an overlay pinned to the LAST rows of the pane, structurally
- * unrelated to whatever the agent is currently blocked on. In a production pane
- * (200x1000, alternate screen) a prompt dialog therefore renders near the top and
- * the panel ~880 blank rows below it — rows `compactBlankRows` collapses to one,
- * putting the panel squarely inside Pass 2's 50-line reverse-scan window.
- *
- * That is only harmless while something trims it away. #704/#807 trim at a
- * footer, but the AskUserQuestion *confirmation* step ("Ready to submit your
- * answers?") renders NEITHER footer, so nothing trims and the panel is the first
- * thing the reverse scan meets. Measured on the live capture in
- * fixtures/claude-live-1708/askuserquestion-submit-taskpanel.txt, two of its rows
- * match NORMAL_OPTION_PATTERN independently:
- *   - this header      → option 7,  label "tasks (2 done, 1 in progress, 4 open)"
- *   - "… +2 completed" → option 2,  label "completed"
- * Either one alone is enough to make isValidPrecedingOption() reject the real
- * `❯ 1. Submit answers` / `2. Cancel` above it, so collectedOptions never reaches
- * 2 and the frame is published as "no prompt" — Issue #1708's silent timeout.
- *
- * Anchored at line start and requires the literal `tasks (` + `<n> done`, which
- * no option label produced by any supported CLI carries. ReDoS safe (S4-001):
- * bounded repetition, no nesting.
- */
-const CLAUDE_TASK_PANEL_HEADER_PATTERN = /^\s*\d{1,3}\s+tasks?\s+\(\d+\s+done\b/i;
-/**
- * [Issue #1708] A single task row of the panel described above, e.g. "  ◼ Phase 3".
- *
- * Today these rows are inert — `isContinuationLine()` already absorbs them — but
- * only because none of the observed titles begins with a digit. A title like
- * "2. Fix the parser" would render as "  ◻ 2. Fix the parser" and be collected as
- * option 2, reintroducing the same poisoning from a direction no single-line
- * guard anticipates. Skipping the whole panel block closes that off structurally
- * instead of one wording at a time.
- *
- * The glyph set is exactly the two forms measured on a live pane — ◼ (in
- * progress) and ◻ (open) — and nothing else. Every extra glyph is a line this
- * guard can delete from the frame, so the set is an allowlist of things seen,
- * not a guess at what the family might contain:
- *
- *   - ❯ ● › are DEFAULT_OPTION_PATTERN's cursor indicators.
- *   - ⏺ ⎿ ✔ ✗ are the transcript markers TURN_BOUNDARY_PATTERN reads.
- *   - ☐ ☑ ☒ are the natural rendering of a MULTI-SELECT choice, and
- *     AskUserQuestion has a multiSelect mode. Measured: with those in the set,
- *     `☐ 1. Blue / ☑ 2. Green / ☐ 3. Red` under a panel header is claimed as
- *     panel content and the prompt above it disappears entirely
- *     (isPrompt=false, zero options) — Issue #1708's own failure, recreated by
- *     its fix. See the regression test.
- *
- * A completed row never appears (the panel collapses those into `… +N
- * completed`, which SUMMARY_LINE_PATTERN handles), so no done-marker is needed.
- * An unmatched glyph simply ends the block, which is the safe direction: those
- * rows go back to being handled exactly as they were before this guard existed.
- *
- * To widen this, capture a live pane that actually renders the new glyph and add
- * it as a fixture. Do not widen it from the shape of the character.
- */
-const CLAUDE_TASK_PANEL_ROW_PATTERN = /^\s*[◼◻]\s/;
-/**
- * [Issue #2468] Claude Code 2.1.267's session-diff HUD row, in the two
- * spellings measured on a live pane (tests/fixtures/claude-live-2468):
- *   "No changes this session"
- *   "+28 files edited before this session (show)"
- *
- * Chrome like the task panel, but a single row and RIGHT-aligned: on a
- * 200-column pane it is ~110 columns of padding and then the text. It is
- * therefore matched on the trimmed row — a reader that slices the row from the
- * left sees nothing but blanks.
- *
- * It broke two readers. Pass 2 below parses `+2 files edited …` as option 2,
- * which poisons the real `1. / 2.` above it the way `… +2 completed` did in
- * #1708. And `findClaudeTranscriptTail` took it for the last transcript row, so
- * `detectClaudeDialog` read it as the footer of the AskUserQuestion
- * confirmation screen — a dialog that draws no footer — and refused a dialog
- * that was open on screen: Auto-Yes, the UI's answer and `commandmate respond`
- * all got `prompt_no_longer_active`.
- *
- * `files?` is the one spelling not seen on a pane: a one-file session was not
- * captured, and the singular is accepted so that it is not the case that
- * regresses. Everything else is literal, for the same reason the glyph set
- * above is an allowlist. Anchored at both ends, no nested quantifiers — ReDoS
- * safe (S4-001).
- */
-const CLAUDE_SESSION_DIFF_HUD_PATTERN = /^(?:No changes this session|\+\d+ files? edited before this session \(show\))$/;
-/**
- * Line indices belonging to Claude's bottom-pinned panels within [start, end).
- *
- * Two panels, both chrome rather than transcript or prompt:
- *  - the task panel (#1708). Walks down from each header row for as long as
- *    rows keep looking like panel content (task rows or the collapsed `… +N …`
- *    summary). The first line that is neither ends the block, so a panel that
- *    abuts other content cannot swallow it.
- *  - the session-diff HUD (#2468), a single row claimed on its own.
- *
- * Pass 2 here, `findClaudeTranscriptTail` and `detectClaudeDialog`'s footer
- * guard all read this one set — through {@link findClaudeChrome}, which adds an
- * AskUserQuestion preview pane to it (Issue #2486) — so they cannot disagree
- * about which rows are chrome.
- *
- * @param lines - Full frame, already ANSI/box stripped
- * @param start - First index to consider (inclusive)
- * @param end - Last index to consider (exclusive)
- * @returns Indices Pass 2 must treat as metadata rather than options
- */
-function findClaudeTaskPanelLines(lines, start, end) {
-    const panelLines = new Set();
-    for (let i = Math.max(0, start); i < Math.min(end, lines.length); i++) {
-        if (CLAUDE_SESSION_DIFF_HUD_PATTERN.test(lines[i].trim())) {
-            panelLines.add(i);
-            continue;
-        }
-        if (!CLAUDE_TASK_PANEL_HEADER_PATTERN.test(lines[i]))
-            continue;
-        panelLines.add(i);
-        for (let j = i + 1; j < Math.min(end, lines.length); j++) {
-            const row = lines[j];
-            if (!CLAUDE_TASK_PANEL_ROW_PATTERN.test(row) && !SUMMARY_LINE_PATTERN.test(row))
-                break;
-            panelLines.add(j);
-        }
-    }
-    return panelLines;
-}
-/**
- * Claude's chrome within [start, end). See {@link ClaudeChrome}.
- *
- * @param lines - Full frame, ANSI stripped; box drawing optional
- * @param start - First index to consider (inclusive)
- * @param end - Last index to consider (exclusive)
- */
-function findClaudeChrome(lines, start, end) {
-    const rows = findClaudeTaskPanelLines(lines, start, end);
-    const panes = (0, picker_chrome_1.findClaudePreviewPanes)(lines, start, end);
-    for (const row of panes.rows)
-        rows.add(row);
-    return { rows, cuts: panes.cuts };
-}
-/**
- * The frame with Claude's chrome taken out: chrome rows blank, rows shared with
- * the preview pane cut back to the options column. Row indices are unchanged,
- * so a reader of the result can report positions in the original frame.
- */
-function maskClaudeChrome(lines, chrome) {
-    return lines.map((line, i) => {
-        if (chrome.rows.has(i))
-            return '';
-        const cut = chrome.cuts.get(i);
-        return cut === undefined ? line : line.slice(0, cut).trimEnd();
-    });
-}
 /**
  * [Issue #2486] An indented row in the options column beside a preview pane.
  *
@@ -240,39 +90,6 @@ const QUESTION_CONTEXT_LINES = 5;
  * not selectable options and must not be parsed as numbered choices.
  */
 const COLLAPSED_OUTPUT_PATTERN = /^\s*\[[^\]]*\d+\s+lines?\]/i;
-/**
- * [Issue #704] Pattern for Claude Code v2.1.142 prompt summary lines such as
- *   "  … +1 pending"
- *   "  +2 pending"
- *   "  ↑3 more"
- *   "  ↓1 more"
- * These lines are rendered BELOW the real options when Claude collapses the
- * remaining choices. They are not selectable options and must be skipped by
- * Pass 2 — otherwise NORMAL_OPTION_PATTERN matches them as option N with
- * label "pending"/"more", and the resulting (number, label) tuple poisons
- * isValidPrecedingOption() so that the real 1./2./3. options above are all
- * rejected (collectedOptions ends up with length 1 and Layer 4 returns
- * no_prompt).
- *
- * Scope of the pattern (FP suppression is critical):
- *   - Anchored at line start (^) and requires the trailing keyword to be
- *     `pending` or `more` followed by a word boundary (\b). This intentionally
- *     prevents matching legitimate option labels that mention these words
- *     mid-sentence (e.g. `2. Postpone (will remain pending)`,
- *     `3. Show me more`) — those still flow through NORMAL_OPTION_PATTERN.
- *   - Optional leading ellipsis (… U+2026) and optional collapse direction
- *     marker (+ - ↑ ↓ ⏵ ⏷) accept the variants observed in the wild.
- *   - [Issue #1708] `completed` joined `pending`/`more` after a live capture
- *     (fixtures/claude-live-1708) showed the task panel collapsing FINISHED
- *     rows as `… +2 completed`. That wording was outside the #704 guard, so it
- *     reached Pass 2 and was collected as `option 2 / label='completed'` —
- *     poisoning isValidPrecedingOption() exactly as `… +1 pending` used to.
- *   - The pattern deliberately omits any free `(.+)` capture — it must
- *     short-circuit, not extract data.
- *
- * Pattern shape: linear regex with no nested quantifiers — ReDoS safe (S4-001).
- */
-const SUMMARY_LINE_PATTERN = /^\s*[…]?\s*[+\-↑↓⏵⏷]?\s*\d+\s+(?:pending|more|completed)\b/i;
 /**
  * [Issue #704] Pattern for the Claude Code v2.1.142 prompt footer line.
  * Example: "  Esc to cancel · Tab to amend → · Herding…"
@@ -1060,7 +877,7 @@ function collectOptions(lines, scanStart, effectiveEnd) {
     // [Issue #2486] The same reading carries an AskUserQuestion preview pane, whose
     // rows the scan likewise meets before the top border that identifies it — and
     // some of which it shares with the options column.
-    const chrome = findClaudeChrome(lines, scanStart, effectiveEnd);
+    const chrome = (0, prompt_detect_multiple_choice_chrome_1.findClaudeChrome)(lines, scanStart, effectiveEnd);
     for (let i = effectiveEnd - 1; i >= scanStart; i--) {
         // [Issue #1708] Chrome rows are metadata. Same handling as the
         // COLLAPSED_OUTPUT / SUMMARY guards below: skip without ending the scan, so
@@ -1139,7 +956,7 @@ function isMetadataRow(state, rawLine, line, paneCut) {
     // against future Claude renderings where the footer line text changes
     // (S1 still catches) or the summary line wording changes (S2 still
     // catches via footer trim).
-    if (SUMMARY_LINE_PATTERN.test(line)) {
+    if (prompt_detect_multiple_choice_chrome_1.SUMMARY_LINE_PATTERN.test(line)) {
         state.continuationLineCount++;
         return true;
     }

package/dist/server/src/lib/detection/upstream-faults.js

@@ -25,8 +25,9 @@
  * @module lib/detection/upstream-faults
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.UPSTREAM_FAULT_TRUNCATION_MARKER = exports.UPSTREAM_FAULT_EXCERPT_MAX_BYTES = exports.UPSTREAM_FAULTS = void 0;
+exports.UPSTREAM_FAULT_TRUNCATION_MARKER = exports.UPSTREAM_FAULT_EXCERPT_MAX_BYTES = exports.CODEX_ERROR_ROW_FAULT_IDS = exports.UPSTREAM_FAULTS = void 0;
 exports.matchUpstreamFault = matchUpstreamFault;
+exports.matchCodexErrorRowFault = matchCodexErrorRowFault;
 exports.findUpstreamFault = findUpstreamFault;
 const ansi_1 = require("./ansi");
 const excerpt_1 = require("./excerpt");
@@ -54,9 +55,47 @@ exports.UPSTREAM_FAULTS = [
         pattern: /\bmaximum context length is \d+ tokens\b/i,
         selfRetrying: false,
     },
+    {
+        // codex ends the turn with `Selected model is at capacity` and does not
+        // answer (Issue #3936); the same model will not, so the cue is to switch
+        // instance or model. Anchored on the sentence, not on "at capacity": the
+        // 529 line above says "The API is at capacity" and is `overloaded`.
+        //
+        // And on codex's own error row, not on the sentence alone: `■ ` at column
+        // 0, the shape codex 0.160.0 draws its errors in (measured on
+        // `■ Conversation interrupted`). A reply that names or quotes the error —
+        // this Issue, its review — is indented (`• ` / `  `), and an input echo
+        // starts with `› `; matching those would fail a healthy turn with exit 11.
+        // The capacity row itself is unmeasured (the fixture is synthetic).
+        id: 'model-capacity',
+        pattern: /^■ Selected model is at capacity\b/im,
+        selfRetrying: false,
+    },
     { id: 'limit-reached', pattern: /\blimit reached\b/i, selfRetrying: false },
-    { id: 'api-error', pattern: /\bAPI Error(?::|\s+\d{3})/i, selfRetrying: false },
+    {
+        // Anchored to a line start (Issue #3946), like `model-capacity`: only the two
+        // shapes measured for the fault itself are accepted — claude's `⏺ API Error: …`
+        // row (Issue #1839) and a bare `API Error: …` at column 0. Unanchored, it
+        // matched a healthy codex reply that quoted `• API Error: 500` on an indented
+        // continuation line, and `ask` exited 11 — twice, because the quoting turn was
+        // still inside the 100-row window when the next turn ended. A codex `• ` row,
+        // an indented continuation and a `› ` input echo are not accepted.
+        //
+        // Known limit: a claude reply that itself begins with `⏺ API Error: …` is
+        // indistinguishable from the fault, because nothing here knows who wrote a row
+        // (reply, echo, tool error) — only its leading shape.
+        id: 'api-error',
+        pattern: /^(?:⏺ )?API Error(?::|\s+\d{3})/im,
+        selfRetrying: false,
+    },
 ];
+/**
+ * The faults whose pattern is anchored to codex's own error row (`■ ` at column
+ * 0), and so the only ones safe to apply to a row outside `realtimeSnippet`
+ * (Issue #3946, {@link matchCodexErrorRowFault}). An unanchored pattern on such a
+ * row would read a quote in an old reply as a fault happening now.
+ */
+exports.CODEX_ERROR_ROW_FAULT_IDS = ['model-capacity'];
 /**
  * Bound on {@link UpstreamFaultMatch.matchedText}, in UTF-8 **bytes**.
  *
@@ -87,11 +126,23 @@ function truncateExcerpt(text) {
  * sequences on a live pane.
  */
 function matchUpstreamFault(frame) {
+    return matchFaults(frame, exports.UPSTREAM_FAULTS);
+}
+/**
+ * {@link matchUpstreamFault} restricted to {@link CODEX_ERROR_ROW_FAULT_IDS}
+ * (Issue #3946): for the one codex transcript row read from outside the window,
+ * where a quote must not count.
+ */
+function matchCodexErrorRowFault(row) {
+    return matchFaults(row, exports.UPSTREAM_FAULTS.filter((fault) => exports.CODEX_ERROR_ROW_FAULT_IDS.includes(fault.id)));
+}
+function matchFaults(frame, faults) {
     const clean = (0, ansi_1.stripAnsi)(frame);
-    for (const fault of exports.UPSTREAM_FAULTS) {
+    for (const fault of faults) {
         const match = fault.pattern.exec(clean);
-        // The patterns are unanchored and stateless (no /g), so `exec` cannot carry
-        // a lastIndex between calls — but reading `index` requires exec regardless.
+        // The patterns are stateless (no /g; `model-capacity` and `api-error` are
+        // anchored to a line start with /m), so `exec` cannot carry a lastIndex
+        // between calls — but reading `index` requires exec regardless.
         if (!match)
             continue;
         const lineStart = clean.lastIndexOf('\n', match.index) + 1;

package/dist/server/src/lib/hooks/sources/opencode/client.js

@@ -478,7 +478,7 @@ function promptSelectionBody(selection) {
  * @param sessionId - `ses_…`, the session the message belongs to
  * @param messageId - `msg_…`, from {@link newOpencodeMessageId}
  * @param parts - The message body; at least one part
- * @returns Whether the server answered `204`
+ * @returns How the POST ended ({@link OpencodePromptDispatch})
  */
 async function sendOpencodePrompt(port, sessionId, messageId, parts, selection) {
     const url = `${opencodeBaseUrl(port)}/session/${encodeURIComponent(sessionId)}/prompt_async`;
@@ -493,18 +493,24 @@ async function sendOpencodePrompt(port, sessionId, messageId, parts, selection)
             }),
             signal: AbortSignal.timeout(exports.OPENCODE_REQUEST_TIMEOUT_MS),
         });
-        if (response.status !== 204) {
-            logger.warn('opencode-prompt-rejected', { port, sessionId, status: response.status });
-            return false;
+        if (response.status === 204)
+            return 'accepted';
+        // Issue #3992: another 2xx may still have created the message (a JSON 200 /
+        // 201), so it stays unknown — except the web UI's SPA shell an unknown route
+        // answers (`200 text/html`, #1931), which never took the message.
+        if (response.status >= 200 && response.status < 300 && !hasContentType(response, 'text/html')) {
+            logger.warn('opencode-prompt-unexpected-success', { port, sessionId, status: response.status });
+            return 'unknown';
         }
-        return true;
+        logger.warn('opencode-prompt-rejected', { port, sessionId, status: response.status });
+        return 'rejected';
     }
     catch (error) {
         logger.debug('opencode-request-failed', {
             url,
             error: error instanceof Error ? error.message : String(error),
         });
-        return false;
+        return 'unknown';
     }
 }
 /**

package/dist/server/src/lib/hooks/structured-decision-response.js

@@ -465,5 +465,5 @@ async function answerStructuredDecision({ worktreeId, cliToolId, instanceId, ans
         reply: option.reply,
         delivered,
     });
-    return { kind: 'answered', decisionId: decision.id, option, delivered };
+    return { kind: 'answered', decisionId: decision.id, option, delivered, receipt: delivery };
 }

package/dist/server/src/lib/polling/auto-yes-manual-answer.js

@@ -82,8 +82,10 @@ function noteManualSendStarting(ticket, promptData) {
  *   (the manual-answer sequence moves on): one that read no hold before its
  *   last wait does not type over this one.
  *
- * An end nobody reports (the agent's API answered it, the route threw) leaves
- * the hold as it was.
+ * An end nobody reports (a send that threw saying nothing of its keys, a
+ * verdict the agent's API gave no receipt for — both only abandoned; a
+ * structured verdict `/prompt-response` refused) leaves the hold as it was. A verdict delivered over the
+ * agent's API reports its receipt like a send (Issue #3925).
  */
 function settleManualAnswer(ticket, outcome, at = Date.now()) {
     const { compositeKey, attempt } = ticket;

package/dist/server/src/lib/polling/response-checker.js

@@ -62,7 +62,7 @@ const push_1 = require("../../lib/push");
 const prompt_push_gate_1 = require("../../lib/push/prompt-push-gate");
 // Issue #2000: deep path for the same reason as the two imports above.
 const failure_push_notifier_1 = require("../../lib/push/failure-push-notifier");
-const upstream_faults_1 = require("../../lib/detection/upstream-faults");
+const realtime_snippet_1 = require("../../lib/realtime-snippet");
 const waiting_push_notifier_1 = require("../../lib/push/waiting-push-notifier");
 const waiting_episode_binding_1 = require("../../lib/session/waiting-episode-binding");
 const waiting_episode_state_1 = require("../../lib/session/waiting-episode-state");
@@ -71,19 +71,6 @@ const auto_yes_state_1 = require("../../lib/auto-yes-state");
 const auto_yes_poller_state_1 = require("./auto-yes-poller-state");
 const task_transition_service_1 = require("../../lib/tasks/task-transition-service");
 const response_checker_blank_response_1 = require("./response-checker-blank-response");
-/**
- * How many rows from the bottom of a capture the upstream-fault check reads
- * (Issue #2000).
- *
- * The same 100 as `current-output-builder`'s `realtimeSnippet`, and for the
- * reason #1839 gives there: the wider capture keeps a banner from an hour ago
- * in scope, and "is this happening now" is the only question worth ringing a
- * phone about. Keeping the two windows equal also means the notification and
- * the `upstreamFault` field an operator reads in `capture --json` are judging
- * the same rows — a fault that rang but is invisible in the payload next to it
- * is unverifiable.
- */
-const UPSTREAM_FAULT_SCAN_ROWS = 100;
 /**
  * Raise a push notification when this frame shows a NEW upstream fault
  * (Issue #2000).
@@ -100,8 +87,20 @@ const UPSTREAM_FAULT_SCAN_ROWS = 100;
  * anything, so the level can be handed over on every poll.
  */
 function observeUpstreamFaultForPush(worktreeId, cliToolId, instanceId, output) {
-    const snippet = output.split('\n').slice(-UPSTREAM_FAULT_SCAN_ROWS).join('\n');
-    const match = (0, upstream_faults_1.matchUpstreamFault)(snippet);
+    // The rows `current-output-builder` judges `upstreamFault` on (#1839: the rows
+    // it publishes as `realtimeSnippet`; #3946: plus codex's last transcript row
+    // above them on a split screen), read through the same entry
+    // (`matchPaneUpstreamFault`) rather than a copy of its window. The reason is #1839's: the wider capture keeps a banner from an
+    // hour ago in scope, and "is this happening now" is the only question worth
+    // ringing a phone about. Sharing the cut also means the notification and the
+    // `upstreamFault` an operator reads in `capture --json` judge the same rows —
+    // a fault that rang but is invisible in the payload next to it is
+    // unverifiable. Issue #3936: the plain last 100 rows (#2000) drifted from the
+    // snippet when #2768 anchored it to the last row with content, so an inline
+    // codex pane showed `model-capacity` in the capture and never rang.
+    // Issue #3946: one entry with current-output, which also reads codex's last
+    // transcript row above the window on a split screen.
+    const match = (0, realtime_snippet_1.matchPaneUpstreamFault)(output.split('\n'), cliToolId);
     // Fire-and-forget, like every other push call in this file: the poller must
     // not slow down or break because a notification could not be delivered.
     void (0, failure_push_notifier_1.notifyUpstreamFaultPush)({