commandmate 0.31.1 → 0.31.3

package/dist/server/src/lib/detection/tools/antigravity/detect.js

@@ -3,16 +3,17 @@
  * Antigravity (agy) status detector (Issue #1927, 方針書 §4 D2).
  *
  * A verbatim lift of the `cliToolId === 'antigravity'` blocks (priorities 0.9
- * and 2.8) out of `detectSessionStatus`.
+ * and 2.8) out of `detectSessionStatus`, plus the Issue #2364 dialog reading in
+ * `beforePrompt`.
  *
  * No `readIdleEvidence`: agy's idle branch reads the same always-visible `> `
- * input box that #1885 showed is not evidence on its own, and no IDLE agy frame
- * has been captured to measure a better rule from. (Issue #2270 added live
- * 1.1.25 captures, but only of the permission dialog and the `/model` picker —
- * both `waiting`.) Per §4 D1 決定 1's tool-by-tool rollout (DR2-002) a tool
- * without a measured rule keeps the pre-#1927 reading, and its rule must be read
- * off ITS OWN frames rather than inferred from another tool's — which is exactly
- * the mistake #1979 corrected.
+ * input box that #1885 showed is not evidence on its own. Issue #2364 captured
+ * the first live IDLE agy frame (`antigravity-live-2364/boot-idle.txt`: a bare
+ * `>` between two rules over a `? for shortcuts` status row), so a rule could
+ * now be measured — but it has not been, and per §4 D1 決定 1's tool-by-tool
+ * rollout (DR2-002) a tool without a measured rule keeps the pre-#1927 reading.
+ * Its rule must be read off ITS OWN frames rather than inferred from another
+ * tool's — which is exactly the mistake #1979 corrected.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.antigravityStatusDetector = exports.VERIFIED_AGAINST = void 0;
@@ -20,12 +21,66 @@ const cli_patterns_1 = require("../../cli-patterns");
 const status_reason_1 = require("../../status-reason");
 const run_detection_1 = require("../run-detection");
 const verified_against_1 = require("../verified-against");
-/** agy build these rules were read off (Issue #988 / #995; value in ../verified-against, #1929). */
+const dialog_1 = require("./dialog");
+/** agy build these rules were read off (Issue #988 / #995 / #2364; value in ../verified-against, #1929). */
 exports.VERIFIED_AGAINST = verified_against_1.ANTIGRAVITY_VERIFIED_AGAINST;
+/**
+ * An agy screen only the terminal can drive: the `/model` picker, the folder
+ * trust screen, the slash-command popup — and the post-answer survey.
+ *
+ * `hasActivePrompt: false` with a reason in `SELECTION_LIST_REASONS` is what
+ * puts NavigationButtons (and the chat surface's "drive it from the terminal"
+ * card) on screen, and what makes `wait` stop with exit 10 instead of hanging.
+ */
+const SELECTION_LIST_VERDICT = {
+    status: 'waiting',
+    confidence: 'high',
+    reason: status_reason_1.STATUS_REASON.ANTIGRAVITY_SELECTION_LIST,
+    hasActivePrompt: false,
+    evidence: 'positive',
+};
+/**
+ * How close to the bottom of the content the survey row must be to count as
+ * open: itself, a blank row and the `? for shortcuts` status row.
+ */
+const SURVEY_TAIL_ROWS = 3;
+/**
+ * Is the post-answer survey the live screen, rather than a row of it left in
+ * the scrollback? (Issue #2364)
+ *
+ * agy retains scrollback, so the guard is positional: the `[1] Good … [0] Skip`
+ * row is the survey only while it sits within the last few content rows and
+ * no bare `>` composer has been drawn below it — the composer is what replaces
+ * it once the digit is typed.
+ */
+function isAntigravitySurveyOpen(contentLines) {
+    const tail = contentLines.slice(-SURVEY_TAIL_ROWS);
+    const surveyAt = tail.findIndex(row => cli_patterns_1.ANTIGRAVITY_SURVEY_PATTERN.test(row));
+    if (surveyAt < 0)
+        return false;
+    const { promptPattern } = (0, cli_patterns_1.getCliToolPatterns)('antigravity');
+    return !tail.slice(surveyAt + 1).some(row => promptPattern.test(row));
+}
 exports.antigravityStatusDetector = (0, run_detection_1.createToolStatusDetector)({
     tool: 'antigravity',
     verifiedAgainst: exports.VERIFIED_AGAINST,
     beforePrompt(frame) {
+        // 0.85. Issue #2364: the survey agy draws in place of its composer after a
+        // tool decision — `[1] Good  [2] Fine  [3] Bad  [0] Skip` under `How's the
+        // CLI experience so far?`. Nothing else on that frame is readable: there is
+        // no `↑/↓ Navigate` footer and no bare `>` row, so it used to reach the
+        // `default` floor as `running`, and the chat surface showed "generating"
+        // over a screen waiting for a keypress.
+        //
+        // Published as a selection list rather than as a `multiple_choice` prompt
+        // on purpose. The screen takes a TYPED digit (`0` closes it), while
+        // `sendPromptAnswer` drives every numeric agy answer with arrow keys +
+        // Enter (Issue #999) — a `0. Skip` button on PromptPanel would send `Up`,
+        // `Enter` to a screen that does not navigate. As a selection list the
+        // frame is `waiting`, `wait` returns, the waiting push fires, and the chat
+        // surface's card points at the terminal, where a single `0` is the answer.
+        if (isAntigravitySurveyOpen(frame.contentLines))
+            return SELECTION_LIST_VERDICT;
         // 0.9. Antigravity: selection list detection BEFORE thinking detection (Issue #995)
         // agy's "Switch Model" (and other) selection TUIs render an "esc to cancel"
         // footer that ANTIGRAVITY_THINKING_PATTERN also matches, so the generic thinking
@@ -35,7 +90,7 @@ exports.antigravityStatusDetector = (0, run_detection_1.createToolStatusDetector
         // Codex early-detection pattern.
         if (!cli_patterns_1.ANTIGRAVITY_SELECTION_LIST_PATTERN.test(frame.lastLines))
             return null;
-        // Issue #2270: except when the frame is the NUMBERED permission dialog.
+        // Issue #2270 / #2364: except when the frame is a NUMBERED dialog.
         //
         // #997 widened the pattern above to the bare `↑/↓ Navigate` footer so the
         // "Do you want to proceed?" menu would reach this branch — but this branch
@@ -47,23 +102,48 @@ exports.antigravityStatusDetector = (0, run_detection_1.createToolStatusDetector
         // with four `multiple_choice` options and the push notification sent
         // `kind: 'prompt'` — one screen, two answers.
         //
-        // Returning null hands the frame to priority 1, where `detectPrompt` with
-        // `buildDetectPromptOptions('antigravity')` already reads it as that same
-        // 4-option `multiple_choice` (Issue #999). That is what puts
-        // `hasActivePrompt: true` and `promptData` on the wire, so PromptPanel and
-        // the legacy Auto-Yes path both work and all three producers agree.
+        // #2270 returned null here and let priority 1's generic `detectPrompt` read
+        // the frame. That held for the one dialog it measured and broke on the next
+        // two (#2364): the file-creation menu never passed its `Do you want to
+        // proceed?` discriminator, and a Bash approval whose option labels wrap —
+        // agy prints the command inside the label, so most of them do — passed it
+        // and then failed in the one-row-per-option parser, after which the `esc
+        // to cancel` status row matched the thinking pattern and the pane went out
+        // as `running` / `thinking_indicator`. So the discriminator is structural
+        // now (`isAntigravityNumberedDialog`), the frame is read by agy's own
+        // reader (`./dialog.ts`), and a frame the reader cannot parse is published
+        // as UNCLASSIFIED — never as a picker, and never as "generating", which is
+        // the worst answer a waiting dialog can get: `wait` never returns from it.
+        //
+        // `stripBoxDrawing` here, as priority 1 applies it before `detectPrompt`,
+        // so this verdict and the response poller's (`detectPromptWithOptions`,
+        // which reads the same helper over the same spelling) carry one question,
+        // one option list and one `instructionText` for one screen.
         //
         // #995's own case is untouched: the Switch Model picker carries no numbered
-        // rows, so it still resolves here and still keeps NavigationButtons.
-        if ((0, cli_patterns_1.isAntigravityNumberedDialog)(frame.lastLines))
-            return null;
-        return {
-            status: 'waiting',
-            confidence: 'high',
-            reason: status_reason_1.STATUS_REASON.ANTIGRAVITY_SELECTION_LIST,
-            hasActivePrompt: false,
-            evidence: 'positive',
-        };
+        // rows, so it still resolves below and still keeps NavigationButtons.
+        const text = (0, cli_patterns_1.stripBoxDrawing)(frame.clean);
+        if ((0, cli_patterns_1.isAntigravityNumberedDialog)(text)) {
+            const promptDetection = (0, dialog_1.detectAntigravityNumberedDialogPrompt)(text);
+            if (promptDetection !== null) {
+                return {
+                    status: 'waiting',
+                    confidence: 'high',
+                    reason: status_reason_1.STATUS_REASON.PROMPT_DETECTED,
+                    hasActivePrompt: true,
+                    evidence: 'positive',
+                    promptDetection,
+                };
+            }
+            return {
+                status: 'running',
+                confidence: 'low',
+                reason: status_reason_1.STATUS_REASON.UNKNOWN_FRAME,
+                hasActivePrompt: false,
+                evidence: 'none',
+            };
+        }
+        return SELECTION_LIST_VERDICT;
     },
     afterThinking(frame) {
         // 2.8. Antigravity (agy) footer-based detection (Issue #988)

package/dist/server/src/lib/detection/tools/antigravity/dialog.js

@@ -0,0 +1,233 @@
+"use strict";
+/**
+ * Antigravity (agy)'s numbered permission dialogs, read on their own terms
+ * (Issue #2364).
+ *
+ * ## What was measured (agy 1.1.27, pane 200x1000, 2026-09-06)
+ *
+ * `tests/fixtures/antigravity-live-2364/` holds the frames. The two that this
+ * module exists for:
+ *
+ * | frame                     | question                        | options | shape                              |
+ * |---------------------------|---------------------------------|---------|------------------------------------|
+ * | `dialog-create-file.txt`  | `Allow creation of this file?`   | 2       | diff preview above the question    |
+ * | `dialog-bash-wrapped.txt` | `Do you want to proceed?`        | 4       | options 2 and 3 wrap onto 3 rows   |
+ *
+ * Before this Issue the first resolved as `antigravity_selection_list`
+ * (`hasActivePrompt: false`, so the chat surface drew an arrow pad and no
+ * yes/no panel) because Issue #2270's discriminator was the sentence `Do you
+ * want to proceed?`; the second passed the discriminator and then failed in the
+ * generic multiple-choice parser, which reads one row per option, so the
+ * `esc to cancel` status row fell through to the thinking pattern and the pane
+ * was published as `running` / `thinking_indicator` — "generating", with `wait`
+ * never returning. agy prints the command text inside the option label, so
+ * every Bash approval of a multi-line command takes the second shape.
+ *
+ * ## What this reads
+ *
+ * The block between the nearest boundary row and the `↑/↓ Navigate` footer
+ * ({@link locateAntigravityDialogRegion}), through the shared
+ * {@link findNumberedOptionBlock}: a run of `N. label` rows descending to `1.`,
+ * every non-numbered row folded into the label above it, the `>` gutter naming
+ * the highlighted option. The question is the one `?`-terminated row directly
+ * above option 1 — NOT the five rows the generic parser joins, which on the
+ * file-creation menu put the diff preview into the question
+ * (`…hello-agy.txt +1 1 + hello from antigravity Allow creation of this file?`).
+ * The diff, the command and the panel header go to `instructionText`, where the
+ * prompt panels render them as context.
+ *
+ * ## Who calls it
+ *
+ * Both producers of the wire, so that they cannot disagree about one screen:
+ * `antigravity/detect.ts` (the status verdict `/current-output` publishes) and
+ * `polling/response-checker.ts` (the `prompt` row the poller stores and the
+ * push notification it raises). The Auto-Yes poller is deliberately NOT a
+ * caller: with Auto-Yes on, agy's `PreToolUse` hook answers the permission
+ * request before the dialog is drawn (Issue #1779), so the dialogs this module
+ * reads only appear when nothing is going to auto-answer them.
+ *
+ * Deliberately NOT a change to the generic multiple-choice parser: folding
+ * continuation rows there would change what every other tool's dialogs read
+ * as, and each of those readings is pinned to its own live captures.
+ *
+ * ## Input contract
+ *
+ * ANSI-stripped text; box drawing optional (the poller's copy has been through
+ * `stripBoxDrawing`, the status path's has not, and the block is bounded the
+ * same way on both — see {@link ANTIGRAVITY_DIALOG_BOUNDARY_PATTERN}).
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.readAntigravityNumberedDialog = readAntigravityNumberedDialog;
+exports.detectAntigravityNumberedDialogPrompt = detectAntigravityNumberedDialogPrompt;
+const cli_patterns_1 = require("../../cli-patterns");
+const prompt_detect_multiple_choice_1 = require("../../prompt-detect-multiple-choice");
+const tui_detection_frame_1 = require("../../tui-detection-frame");
+const dialog_block_1 = require("../dialog-block");
+/**
+ * How many non-blank rows above option 1 may be searched for the question.
+ *
+ * On every measured frame the question is the row directly above option 1;
+ * the allowance is for a blank row or a wrapped question, not for reaching up
+ * into the diff preview.
+ */
+const QUESTION_SCAN_ROWS = 3;
+/**
+ * How far above the question the panel header may sit.
+ *
+ * The `●` tool-call row that opens the panel is what `instructionText` starts
+ * under; the cap keeps a frame with no such row from carrying the whole
+ * transcript into the panel text.
+ */
+const INSTRUCTION_LOOKBACK_ROWS = 40;
+/**
+ * How many non-blank rows under the bottom option row may be its wrapped tail.
+ *
+ * Handed to {@link findNumberedOptionBlock} as its footer scan, because the
+ * region this reader hands it ends above the real footer. Sized well past the
+ * three-row labels agy 1.1.27 draws; a command long enough to exceed it is
+ * elided by agy itself (`pr...'`).
+ */
+const LAST_OPTION_TAIL_ROWS = 12;
+/** The `●` tool-call row that opens every measured agy permission panel. */
+const TOOL_CALL_ROW_PATTERN = /^\s*●\s/;
+/** A horizontal rule; dropped from `instructionText`, where a 200-column rule is noise. */
+const RULE_ROW_PATTERN = /^\s*─{3,}\s*$/;
+/** A row that asks something — the shape the question row takes on every measured dialog. */
+const QUESTION_ROW_PATTERN = /[?？]\s*$/;
+/**
+ * The same tail limits `prompt-detector.ts` applies to `rawContent`
+ * (`RAW_CONTENT_MAX_LINES` / `RAW_CONTENT_MAX_CHARS`), restated because that
+ * helper is private to it. A prompt row stores this text as its message body,
+ * so an unbounded 1000-row pane must not go in.
+ */
+const RAW_CONTENT_MAX_LINES = 200;
+const RAW_CONTENT_MAX_CHARS = 5000;
+function truncateRawContent(content) {
+    const lines = content.split('\n');
+    const tail = lines.length > RAW_CONTENT_MAX_LINES ? lines.slice(-RAW_CONTENT_MAX_LINES) : lines;
+    const joined = tail.join('\n');
+    return joined.length > RAW_CONTENT_MAX_CHARS ? joined.slice(-RAW_CONTENT_MAX_CHARS) : joined;
+}
+/**
+ * Read agy's numbered dialog off ANSI-stripped rows.
+ *
+ * Null when the frame has no `↑/↓ Navigate` footer, when the rows above it do
+ * not form a numbered run reaching `1.` (the Switch Model picker, the trust
+ * screen, the slash popup), or when the block sits under a `Switch Model`
+ * header. A caller that has already passed `isAntigravityNumberedDialog` and
+ * still gets null here is looking at a numbered dialog this reader cannot
+ * parse — which is an unclassified frame, not a picker.
+ */
+function readAntigravityNumberedDialog(lines) {
+    const region = (0, cli_patterns_1.locateAntigravityDialogRegion)(lines);
+    if (region === null)
+        return null;
+    const regionRows = lines.slice(region.start, region.footer);
+    if (regionRows.some(row => cli_patterns_1.ANTIGRAVITY_SWITCH_MODEL_HEADER_PATTERN.test(row)))
+        return null;
+    // The slice stops ABOVE the footer row, so the rows the block reader files
+    // as `footer` — the non-option rows between the bottom option and the region
+    // end — are the wrapped tail of the LAST option, not chrome: agy 1.1.27 draws
+    // `6. No, and always deny for commands that start with '<cmd>` over three
+    // rows on a repeated denial (`dialog-bash-wrapped-six.txt`), and the
+    // `↑/↓ Navigate` footer this region is anchored on already vouched for the
+    // block. Every other row of the region above the block is question / preview
+    // and never reached (the run stops at `1.`).
+    const block = (0, dialog_block_1.findNumberedOptionBlock)(regionRows, regionRows.length, LAST_OPTION_TAIL_ROWS);
+    if (block === null)
+        return null;
+    const options = [...block.options];
+    if (block.footer !== '') {
+        const last = options.length - 1;
+        options[last] = [options[last], ...block.footer.split('\n')].join(' ').trim();
+    }
+    const firstOptionRow = region.start + block.firstRow;
+    // The question: the nearest `?`-terminated row above option 1, looking past
+    // blank rows and at most QUESTION_SCAN_ROWS non-blank ones, none of which
+    // may be a boundary (that would be the previous turn, not this panel).
+    let questionRow = -1;
+    let fallbackRow = -1;
+    let scanned = 0;
+    for (let i = firstOptionRow - 1; i >= region.start && scanned < QUESTION_SCAN_ROWS; i--) {
+        const row = lines[i];
+        if (row.trim() === '')
+            continue;
+        if (cli_patterns_1.ANTIGRAVITY_DIALOG_BOUNDARY_PATTERN.test(row) || RULE_ROW_PATTERN.test(row))
+            break;
+        scanned++;
+        if (fallbackRow < 0)
+            fallbackRow = i;
+        if (QUESTION_ROW_PATTERN.test(row)) {
+            questionRow = i;
+            break;
+        }
+    }
+    if (questionRow < 0)
+        questionRow = fallbackRow;
+    return {
+        question: questionRow < 0 ? 'Please select an option:' : lines[questionRow].trim(),
+        options,
+        selectedIndex: block.selectedIndex,
+        questionRow: questionRow < 0 ? firstOptionRow : questionRow,
+        firstOptionRow,
+        footerRow: region.footer,
+    };
+}
+/**
+ * The panel text above the options, for the prompt panels' context box.
+ *
+ * From the row under the `●` tool-call row that opened the panel (`Command`,
+ * `Create file`, the `Requesting permission for:` block, the diff preview),
+ * through the question, the options and the footer — rules dropped. Falls back
+ * to the dialog region when no tool-call row is within reach.
+ */
+function extractInstructionText(lines, dialog) {
+    const region = (0, cli_patterns_1.locateAntigravityDialogRegion)(lines);
+    let start = region?.start ?? dialog.questionRow;
+    const floor = Math.max(0, dialog.questionRow - INSTRUCTION_LOOKBACK_ROWS);
+    for (let i = dialog.questionRow - 1; i >= floor; i--) {
+        if (TOOL_CALL_ROW_PATTERN.test(lines[i])) {
+            start = i + 1;
+            break;
+        }
+    }
+    const text = lines
+        .slice(start, dialog.footerRow + 1)
+        .filter(row => !RULE_ROW_PATTERN.test(row))
+        .map(row => row.trimEnd())
+        .join('\n')
+        .trim();
+    return text.length > 0 ? text : undefined;
+}
+/**
+ * Read agy's numbered dialog as the `multiple_choice` prompt the rest of the
+ * system consumes, or null when the frame does not carry one.
+ *
+ * The result has the same shape `detectPrompt` produces for a numbered dialog
+ * — `promptData.type === 'multiple_choice'`, `options[].isDefault` on the
+ * highlighted row, `instructionText` / `approvalTarget` / `rawContent` filled
+ * the way Issues #235 and #1699 defined them — so `PromptPanel`,
+ * `MobilePromptSheet`, `respond`, the deny patterns and the prompt-history
+ * writers all read it unchanged.
+ *
+ * @param text - ANSI-stripped capture, box drawing optional
+ */
+function detectAntigravityNumberedDialogPrompt(text) {
+    const normalized = (0, tui_detection_frame_1.normalizeTuiFrameForDetection)(text);
+    const lines = normalized.split('\n');
+    const dialog = readAntigravityNumberedDialog(lines);
+    if (dialog === null)
+        return null;
+    return (0, prompt_detect_multiple_choice_1.buildMultipleChoiceResult)(dialog.question, dialog.options.map((label, index) => ({
+        number: index + 1,
+        label,
+        isDefault: index === dialog.selectedIndex,
+    })), {
+        instructionText: extractInstructionText(lines, dialog),
+        // Issue #1699's machine-facing surface: bounded above at the previous
+        // turn's boundary and below at the footer, so the command in the
+        // `Requesting permission for:` block and in the labels is judged and
+        // nothing from an earlier, already-answered approval is.
+        approvalTarget: (0, prompt_detect_multiple_choice_1.joinApprovalTarget)(lines, (0, prompt_detect_multiple_choice_1.findApprovalContextStart)(lines, dialog.questionRow), dialog.footerRow),
+    }, normalized, truncateRawContent);
+}

package/dist/server/src/lib/detection/tools/verified-against.js

@@ -74,35 +74,35 @@ exports.OPENCODE_VERIFIED_AGAINST = {
     paneGeometry: '80x200',
 };
 /**
- * agy these rules were read off (#988 / #995 footer + selection rules, re-read
- * against the #2270 live panes).
+ * agy these rules were read off (#988 / #995 footer + selection rules, #2270's
+ * numbered-dialog carve-out, re-measured and re-captured by #2364).
  *
- * Bumped from `0.4.x` / `2026-07-30` / `inline` because the frames were
- * RE-CAPTURED, not because the binary moved: #2270 drove agy 1.1.25 on a private
- * tmux socket at the production geometry and kept both panes inline in
- * `tests/unit/status-detector-selection.test.ts`
- * (`AGY_1125_PERMISSION_PANE`, `AGY_1125_SWITCH_MODEL_PANE`) under the banner
- * `Antigravity CLI 1.1.25`, trailing pane padding included. The
- * `Do you want to proceed?` + `N. label` rules were measured off those frames,
- * and `ANTIGRAVITY_SELECTION_LIST_PATTERN` (#995 / #997) was re-checked against
- * them and left unchanged.
+ * Bumped from 1.1.25 because the frames were RE-CAPTURED and the rules CHANGED:
+ * #2364 drove agy 1.1.27 on a private tmux socket at the production geometry and
+ * kept the frames in `tests/fixtures/antigravity-live-2364/` — the file-creation
+ * menu (`Allow creation of this file?`, two options), the Bash approval whose
+ * option labels wrap onto three rows each, the one-row Bash approval #2270 had
+ * measured on 1.1.25, the `/model` picker, the folder-trust screen, the
+ * slash-command popup, and the first live IDLE agy frame. The numbered-dialog
+ * discriminator (`isAntigravityNumberedDialog`) was rewritten off those frames
+ * from a question-line match to the footer + numbered-row structure, and the
+ * dialogs are now read by `tools/antigravity/dialog.ts` rather than by the
+ * generic multiple-choice parser. `ANTIGRAVITY_SELECTION_LIST_PATTERN`
+ * (#995 / #997) was re-checked against every frame and left unchanged.
  *
- * `paneGeometry` leaves `inline` because the 1.1.25 permission dialog draws no
- * composer row at all — it reproduces only at the 200x1000 pane the server
- * captures, and a fixture without the ~970 blank padding rows exercises a
- * different `lastLines` slice than production does. That is a statement about
- * the capture condition, not about agy: the scrollback-retained rendering the
- * `afterThinking` footer rules rest on (#988) is unchanged, and the 1.1.25
- * dialog still ends on `esc to cancel`.
+ * The #2270 1.1.25 panes stay where they are
+ * (`tests/unit/status-detector-selection.test.ts`) and the rules still answer
+ * for both builds.
  *
- * What this stamp does NOT claim: #2270 captured `waiting` frames only, so the
- * idle (`? for shortcuts`) and generating (spinner) branches are carried over
- * from the 0.4 captures rather than re-measured. A live IDLE 1.1.25 frame is
- * still uncaptured — see the `readIdleEvidence` note in `antigravity/detect.ts`.
+ * What this stamp does NOT claim: the generating (spinner) branch is still
+ * carried over from the 0.4 captures rather than re-measured, and the
+ * post-answer survey (`[1] Good … [0] Skip`) was seen once on the production
+ * server and reconstructed from its cleaned rows — the raw frame is not in the
+ * fixture directory (see its README).
  */
 exports.ANTIGRAVITY_VERIFIED_AGAINST = {
-    version: '1.1.25',
-    capturedAt: '2026-09-04',
+    version: '1.1.27',
+    capturedAt: '2026-09-06',
     paneGeometry: '200x1000',
 };
 /**

package/dist/server/src/lib/hooks/hook-settings-generator.js

@@ -64,6 +64,7 @@ const path_1 = require("path");
 const safe_directory_1 = require("../../config/safe-directory");
 const env_1 = require("../../lib/env");
 const types_1 = require("../../lib/cli-tools/types");
+const model_switch_1 = require("../../lib/hooks/sources/claude/model-switch");
 const tool_id_1 = require("../../lib/hooks/sources/claude/tool-id");
 const permission_request_payload_1 = require("../../lib/hooks/permission-request-payload");
 const logger_1 = require("../../lib/logger");
@@ -343,6 +344,17 @@ function buildSessionStartCommand(target, options = {}) {
  * hook and nothing here delivers it — Claude enforces it itself, before any
  * `PermissionRequest` exists — which is precisely why it belongs next to the
  * hook that Auto-Yes answers rather than in the contract layer above it.
+ *
+ * `PostModelSwitch` (Issue #2363) is the structured report of a `/model` or
+ * `/fast` switch, measured on 2.1.263 to reach a `type: "http"` hook injected
+ * through this very file (`lib/hooks/sources/claude/model-switch` has the
+ * payload). It posts to the event receiver with no matcher: the event fires
+ * only when the model actually changes, so there is nothing to narrow. Its
+ * `PreModelSwitch` twin is deliberately NOT registered — it is a decision hook
+ * whose reply can block the switch, the probe's second session saw it fire
+ * twice per switch with inconsistent `from_model` values, and the `Post` event
+ * alone says what happened. The omission is pinned by
+ * `tests/unit/lib/hooks/hook-settings-post-model-switch-2363.test.ts`.
  */
 function buildAgentHookSettings(target, options = {}) {
     const url = buildAgentEventUrl(target, options);
@@ -369,6 +381,10 @@ function buildAgentHookSettings(target, options = {}) {
             // Issue #1726. The event receiver, not the permission one: observation.
             PreToolUse: [{ matcher: exports.TOOL_USE_MATCHER, hooks: [http()] }],
             PostToolUse: [{ matcher: exports.TOOL_USE_MATCHER, hooks: [http()] }],
+            // Issue #2363. The model the session is now on, on every `/model` and
+            // `/fast` that changes it. Observation, so the event receiver; and only
+            // the `Post` half — see the function comment.
+            [model_switch_1.CLAUDE_POST_MODEL_SWITCH_EVENT_NAME]: [{ hooks: [http()] }],
             // Issue #1724. Points at its own receiver, not the event one.
             PermissionRequest: [{ hooks: [permissionHttp()] }],
         },