commandmate 0.21.4 → 0.22.0

package/dist/server/src/lib/session/agent-event-state.js

@@ -1,29 +1,103 @@
 "use strict";
 /**
- * In-memory record of the last structured "the agent stopped" event (#1549).
+ * In-memory record of the structured lifecycle events an agent has reported,
+ * and the session status they imply (#1549, #1722, promoted in #1723, extended
+ * with the open-dialog state machine in #1725).
  *
- * The agent CLI telling us it stopped is a different kind of fact from the
- * screen-scraped status: it is exact, but it only exists when someone wired a
- * hook up. So this is kept beside the detector's output rather than folded into
- * it — `buildCurrentOutput` exposes the timestamp, and nothing in the completion
- * decision reads it yet. Phase 3-2 is deliberately observation only; swapping
- * the wait/poller verdict from string matching to hook events before there is
- * field data on how often hooks actually fire would trade a known failure mode
- * for an unknown one.
+ * The agent CLI telling us what it did is a different kind of fact from the
+ * screen-scraped status: it is exact, but it only exists where hooks actually
+ * fire. #1549 and #1722 therefore kept it strictly beside the detector's
+ * output. #1723 promotes it to a first-class source — {@link
+ * getStructuredSessionState} answers with a `SessionStatus`, and
+ * `current-output-builder` prefers that answer to the scraper's — while
+ * `detectSessionStatus()` stays a pure function of the terminal frame and stays
+ * in charge wherever no event has arrived.
+ *
+ * Three things bound how far that trust extends, because a hook is an
+ * unreliable channel by design (every failure is fail-open):
+ *
+ *  - **generation** — events are keyed by (worktree, tool, instance), a key a
+ *    recreated session reuses, so a generation marker fences off the previous
+ *    process's events. See {@link beginAgentEventGeneration}.
+ *  - **age** — see {@link STRUCTURED_STATE_MAX_AGE_MS}, which bounds the damage
+ *    of a `Stop` that never arrived.
+ *  - **liveness** — a dead tmux session has no structured state; the caller
+ *    establishes that before asking.
+ *
+ * #1725 adds a second, independent state alongside the status verdict: whether
+ * a dialog is open. It is separate because it is released by different things —
+ * there is no "the human answered" event, so the scraper has to be part of the
+ * rule — and because `lastAgentEvent` holds only the newest event, which cannot
+ * express "a dialog is still up" once anything else has arrived. See
+ * {@link getStructuredPromptWaiting}.
  *
  * In-memory and not in SQLite for the same reason `auto-yes-state` is: the value
  * describes a live tmux session, and a session does not survive a server restart
- * for the timestamp to still be about.
+ * for the timestamp to still be about. Losing it on restart is safe precisely
+ * because the scraper is still there to answer.
  *
  * @module lib/session/agent-event-state
  */
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.STRUCTURED_PROMPT_PROVISIONAL_MAX_AGE_MS = exports.STRUCTURED_STATE_MAX_AGE_MS = exports.AGENT_EVENT_DEDUP_WINDOW_MS = void 0;
 exports.recordAgentStopEvent = recordAgentStopEvent;
 exports.getLastStopEventAt = getLastStopEventAt;
+exports.recordAgentEvent = recordAgentEvent;
+exports.getLastAgentEvent = getLastAgentEvent;
+exports.beginAgentEventGeneration = beginAgentEventGeneration;
+exports.getAgentEventGenerationStartedAt = getAgentEventGenerationStartedAt;
+exports.discardAgentEventState = discardAgentEventState;
+exports.getStructuredSessionState = getStructuredSessionState;
+exports.reportPermissionRequestPending = reportPermissionRequestPending;
+exports.getStructuredPromptWaiting = getStructuredPromptWaiting;
+exports.corroborateStructuredPromptWaiting = corroborateStructuredPromptWaiting;
+exports.markStructuredPromptRecorded = markStructuredPromptRecorded;
+exports.clearStructuredPromptWaiting = clearStructuredPromptWaiting;
+exports.recordAskUserQuestion = recordAskUserQuestion;
+exports.getAskUserQuestion = getAskUserQuestion;
+exports.clearAskUserQuestion = clearAskUserQuestion;
+exports.isDuplicateAgentEvent = isDuplicateAgentEvent;
+exports.getRecentEventKeyCount = getRecentEventKeyCount;
 exports.clearAgentStopEvents = clearAgentStopEvents;
 const auto_yes_state_1 = require("../../lib/auto-yes-state");
+const permission_request_payload_1 = require("../../lib/hooks/permission-request-payload");
+const status_mapping_1 = require("../../lib/session/status-mapping");
+const structured_prompt_1 = require("../../lib/session/structured-prompt");
 /** compositeKey -> epoch ms of the most recent stop event. */
-const lastStopEventAt = new Map();
+const lastStopEventAt = globalThis.__agentEventLastStopAt ??
+    (globalThis.__agentEventLastStopAt = new Map());
+/** compositeKey -> the most recent event of any kind. */
+const lastAgentEvent = globalThis.__agentEventLast ??
+    (globalThis.__agentEventLast = new Map());
+/** compositeKey -> epoch ms the current generation began. See {@link beginAgentEventGeneration}. */
+const generationStartedAt = globalThis.__agentEventGenerationStartedAt ??
+    (globalThis.__agentEventGenerationStartedAt = new Map());
+/** compositeKey -> the open dialog the structured layer knows about (#1725). */
+const promptWaiting = globalThis.__agentEventPromptWaiting ??
+    (globalThis.__agentEventPromptWaiting = new Map());
+/** compositeKey -> the `AskUserQuestion` call currently in flight (#1726). */
+const askUserQuestion = globalThis.__agentEventAskUserQuestion ??
+    (globalThis.__agentEventAskUserQuestion = new Map());
+/** dedup key -> epoch ms it was first seen. See {@link isDuplicateAgentEvent}. */
+const recentEventKeys = globalThis.__agentEventRecentKeys ??
+    (globalThis.__agentEventRecentKeys = new Map());
+/**
+ * How long two identical events count as one delivery.
+ *
+ * Issue #1722 injects hooks at session start, and `--settings` hooks are
+ * *concatenated* with the user's own rather than replacing them, so anyone who
+ * followed the #1549 manual setup now has two `Stop` hooks posting the same
+ * turn. `applyAgentStopEvent` is idempotent for the timestamp, but
+ * `applyTaskEvent` is not: each delivery writes its own `agent_idle` row, and a
+ * reader counting rows would see one turn as two.
+ *
+ * A turn cannot end twice in three seconds, and both deliveries carry the same
+ * `session_id`, so the window is generous relative to the real signal and tight
+ * relative to anything it could wrongly swallow.
+ */
+exports.AGENT_EVENT_DEDUP_WINDOW_MS = 3000;
+/** Cap on retained dedup keys, so a long-lived server cannot grow one per turn. */
+const MAX_RECENT_EVENT_KEYS = 512;
 /**
  * Record that `instanceId` reported it stopped.
  *
@@ -40,7 +114,534 @@ function recordAgentStopEvent(worktreeId, cliToolId, instanceId, at = Date.now()
 function getLastStopEventAt(worktreeId, cliToolId, instanceId) {
     return lastStopEventAt.get((0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId)) ?? null;
 }
+/**
+ * Record any structured event against an instance (Issue #1722).
+ *
+ * Deliberately does not touch `lastStopEventAt`: that timestamp belongs to
+ * `applyAgentStopEvent`, which writes it alongside the task transition it drives
+ * so the two cannot disagree.
+ */
+function recordAgentEvent(worktreeId, cliToolId, instanceId, record) {
+    const key = (0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId);
+    lastAgentEvent.set(key, record);
+    applyAskUserQuestionTransition(key, record);
+    if (record.event === 'session_start') {
+        // The agent restarting inside a pane CommandMate never touched — `claude`
+        // relaunched by hand, or a `/clear` (which emits SessionEnd then
+        // SessionStart on a live session) — is a new generation just as much as a
+        // new tmux session is. Recorded from the event's own timestamp, so the
+        // event that opens a generation is never stale against it.
+        generationStartedAt.set(key, record.at);
+    }
+    applyPromptWaitingTransition(key, record);
+}
+/**
+ * The `prompt_waiting` half of the state machine, driven by the same events
+ * (Issue #1725).
+ *
+ * | event                             | effect on prompt_waiting |
+ * |-----------------------------------|--------------------------|
+ * | `notification(permission_prompt)` | **open**, confirmed      |
+ * | `notification(idle_prompt)`       | release                  |
+ * | `notification(other/none)`        | unchanged                |
+ * | `stop`                            | release                  |
+ * | `user_prompt_submit`              | release                  |
+ * | `session_start` / `session_end`   | release                  |
+ * | `pre_tool_use`                    | unchanged                |
+ * | `post_tool_use`                   | release                  |
+ *
+ * `pre_tool_use` leaves this half alone on purpose (Issue #1726). It is the
+ * `AskUserQuestion` invocation, and a picker being *about to be drawn* is not
+ * the kind of fact this state can carry: nothing marks the picker as answered
+ * (§5.6 measured total silence through the selection and confirmation screens),
+ * so an open record from this source would keep asserting `waiting` for up to
+ * {@link STRUCTURED_STATE_MAX_AGE_MS} after a human answered in the terminal.
+ * Whether that screen is up stays the scraper's question; what Issue #1726 adds
+ * is the *content* of the question, kept in a separate record that decides no
+ * status. The `PermissionRequest` `AskUserQuestion` also raises still opens a
+ * provisional record here, exactly as it did in #1725 — unchanged.
+ *
+ * The release set is the one the spike could actually justify. `Stop` is
+ * *measured*: answering an `AskUserQuestion` resumed the turn and delivered a
+ * `Stop` (§5.6, received 23 → 24). `PostToolUse` — which Issue #1725's text
+ * proposed — was **not** observed at all in the spike, so it is not wired up
+ * here; the route does not even map it to a lifecycle event.
+ * `user_prompt_submit` is release by construction: a prompt was typed at the
+ * composer, so no dialog was in front of it. `session_start` / `session_end`
+ * are generation changes, and a dialog does not survive one.
+ *
+ * `idle_prompt` releases for the same reason it maps to `ready`: the agent
+ * reporting it is sitting at the composer waiting for input is the agent saying
+ * nothing is in front of that composer.
+ *
+ * What is deliberately absent is a timer that closes it. There is no event for
+ * "the human answered the dialog" — Claude emits none (§5.6) — so the other
+ * half of the release rule lives in `current-output-builder`, where the scraper
+ * can be asked whether the frame it saw a moment ago is still blocking.
+ */
+function applyPromptWaitingTransition(key, record) {
+    switch (record.event) {
+        case 'notification':
+            if (record.detail === 'permission_prompt') {
+                openPromptWaiting(key, {
+                    source: 'notification',
+                    message: record.message ?? null,
+                    at: record.at,
+                });
+            }
+            else if (record.detail === 'idle_prompt') {
+                promptWaiting.delete(key);
+            }
+            return;
+        case 'stop':
+        case 'user_prompt_submit':
+        case 'session_start':
+        case 'session_end':
+            promptWaiting.delete(key);
+            return;
+        case 'post_tool_use':
+            // The tool call the dialog was gating has finished, so somebody answered
+            // it (Issue #1726). This is the release #1725 could not have: it had no
+            // event meaning "the human answered", only `Stop` meaning "the turn
+            // ended", which can be minutes later.
+            promptWaiting.delete(key);
+            return;
+        case 'pre_tool_use':
+            return;
+        default:
+            // exhaustive check: a new AgentEventType must decide its transition here
+            record.event;
+            return;
+    }
+}
+/**
+ * @returns The last structured event reported by this instance, or null when it
+ *   has reported none.
+ */
+function getLastAgentEvent(worktreeId, cliToolId, instanceId) {
+    return lastAgentEvent.get((0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId)) ?? null;
+}
+/**
+ * How long a structured verdict is trusted after the event that produced it
+ * (Issue #1723).
+ *
+ * Hooks are fail-open by design: a timeout or a refused connection costs the
+ * event and never the agent's turn (`agent-hooks-live-verification.md` §1.1).
+ * A *lost* `Stop` is therefore possible, and without a bound it would leave
+ * this layer asserting `running` for a session that finished — `commandmate
+ * wait` would then poll until `--timeout` on a session the scraper could have
+ * called done. The bound converts "forever" into "at most this long", after
+ * which the scraper takes the session back.
+ *
+ * Deliberately generous. A single agent turn running past 30 minutes is
+ * ordinary for the workloads this tool exists to babysit, and expiring a live
+ * verdict mid-turn costs the whole benefit of the two-layer split. Expiry is
+ * not a failure mode: it is exactly the pre-#1723 behaviour.
+ */
+exports.STRUCTURED_STATE_MAX_AGE_MS = 30 * 60 * 1000;
+/**
+ * Open a new generation for this instance, invalidating everything reported
+ * before now (Issue #1723).
+ *
+ * Called from the session *creation* path, not from every start: a
+ * `startClaudeSession()` that finds a healthy session and returns is the same
+ * generation, and bumping there would throw away a still-valid verdict on
+ * every reconnect.
+ *
+ * The failure this prevents is specific. Events live in a Map keyed by
+ * (worktree, tool, instance) — a key a recreated session reuses exactly — so
+ * without a generation the last `user_prompt_submit` of the *previous* Claude
+ * process would be read as the current one's, and a freshly started session
+ * would report `running` before anybody had typed anything into it.
+ *
+ * @param at - Epoch ms; defaults to now
+ */
+function beginAgentEventGeneration(worktreeId, cliToolId, instanceId, at = Date.now()) {
+    const key = (0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId);
+    generationStartedAt.set(key, at);
+    // A dialog belongs to the process that drew it (Issue #1725). The generation
+    // bound in `getStructuredPromptWaiting` would already hide it, but leaving the
+    // record behind means a later `corroborate`/`markRecorded` would mutate a
+    // dead episode.
+    promptWaiting.delete(key);
+    // Same reasoning for the question that dialog was asking (Issue #1726).
+    askUserQuestion.delete(key);
+}
+/**
+ * @returns Epoch ms the current generation began, or null when no generation
+ *   has been opened — the ordinary case for a session that predates this
+ *   server process, whose events are then judged on age alone.
+ */
+function getAgentEventGenerationStartedAt(worktreeId, cliToolId, instanceId) {
+    return generationStartedAt.get((0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId)) ?? null;
+}
+/**
+ * Discard the structured state for one instance — the session it described is
+ * gone (Issue #1723).
+ *
+ * `lastStopEventAt` is deliberately left alone. It is #1549's observational
+ * timestamp with its own published meaning ("when did this agent last say it
+ * stopped"), it decides nothing, and clearing it here would silently change
+ * what the field has always reported.
+ */
+function discardAgentEventState(worktreeId, cliToolId, instanceId) {
+    const key = (0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId);
+    lastAgentEvent.delete(key);
+    generationStartedAt.delete(key);
+    promptWaiting.delete(key);
+    askUserQuestion.delete(key);
+}
+/**
+ * The status this instance's structured events imply, or null when they imply
+ * nothing (Issue #1723).
+ *
+ * Null is the answer for every session on a machine where hooks never fire,
+ * which is what keeps the unconfigured environment on exactly the behaviour it
+ * had before this Issue. It is also the answer when:
+ *
+ *  - the last event carries no verdict (`session_start`, `session_end`, a
+ *    `Notification` of an unrecognised type) — see `agentEventToSessionStatus`;
+ *  - the event predates the current generation, i.e. it belongs to a previous
+ *    Claude process in a reused pane;
+ *  - the event is older than {@link STRUCTURED_STATE_MAX_AGE_MS}.
+ *
+ * Whether the tmux session is alive is NOT checked here — the caller
+ * (`buildCurrentOutput`) has already answered that question with the CLI tool's
+ * own `isRunning()` and returned early, and asking twice would mean a second
+ * tmux round-trip on the hot path for an answer it is holding.
+ *
+ * @param now - Epoch ms; defaults to now
+ */
+function getStructuredSessionState(worktreeId, cliToolId, instanceId, now = Date.now()) {
+    const key = (0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId);
+    const record = lastAgentEvent.get(key);
+    if (!record)
+        return null;
+    const generation = generationStartedAt.get(key);
+    if (generation !== undefined && record.at < generation)
+        return null;
+    if (now - record.at >= exports.STRUCTURED_STATE_MAX_AGE_MS)
+        return null;
+    const verdict = (0, status_mapping_1.agentEventToSessionStatus)(record.event, record.detail);
+    if (verdict === null)
+        return null;
+    return { ...verdict, event: record.event, at: record.at, detail: record.detail };
+}
+/**
+ * How long a `permission-request`-sourced record survives without
+ * corroboration (Issue #1725).
+ *
+ * The two sources differ in kind. `Notification(permission_prompt)` fires ~6 s
+ * *after* the dialog is drawn and only when one is (§5.5): its arrival is proof.
+ * A no-decision `PermissionRequest` fires *before* the dialog, so it is a
+ * prediction — an accurate one (D5 measured `{}` landing in the ordinary TUI
+ * approval flow), but a prediction about a version of Claude, a permission mode
+ * and a rule set this server does not get to see in full.
+ *
+ * A prediction that nothing confirms must expire, because the cost of it
+ * sticking is a `wait --on-prompt agent` that exits 10 on a session with no
+ * dialog in it — a worker aborted for nothing. 20 s is generous against both
+ * confirmations: the `Notification` lands at ~6 s, and the scraper reads the
+ * pane through a 5 s capture cache on a 5 s poll. Expiring is not a failure
+ * mode; it is the pre-#1725 behaviour for a dialog neither layer ever saw.
+ */
+exports.STRUCTURED_PROMPT_PROVISIONAL_MAX_AGE_MS = 20_000;
+/** Open, or refresh, the prompt-waiting record for one instance. */
+function openPromptWaiting(key, input) {
+    const existing = promptWaiting.get(key);
+    const confirmed = input.source === 'notification';
+    if (existing) {
+        // The same dialog, reported twice: `PermissionRequest` predicted it and the
+        // `Notification` then proved it. Keep the earliest `at` — that is when the
+        // human was first blocked, and it is what the scraper-release grace and the
+        // age bound are measured from — and take the confirmation.
+        existing.message = input.message ?? existing.message;
+        existing.toolName = input.toolName ?? existing.toolName;
+        if (confirmed) {
+            existing.source = 'notification';
+            existing.confirmedAt ??= input.at;
+        }
+        return;
+    }
+    promptWaiting.set(key, {
+        at: input.at,
+        source: input.source,
+        message: input.message
+            ? input.message.slice(0, structured_prompt_1.MAX_STRUCTURED_PROMPT_MESSAGE_LENGTH)
+            : null,
+        toolName: input.toolName ?? null,
+        confirmedAt: confirmed ? input.at : null,
+        scraperCorroborated: false,
+        recorded: false,
+    });
+}
+/**
+ * Report that a dialog is open because the agent asked us to adjudicate one and
+ * we declined to (Issue #1725, Auto-Yes v2's no-decision path).
+ *
+ * Provisional: see {@link STRUCTURED_PROMPT_PROVISIONAL_MAX_AGE_MS}.
+ *
+ * @param at - Epoch ms; defaults to now
+ */
+function reportPermissionRequestPending(worktreeId, cliToolId, instanceId, toolName, at = Date.now()) {
+    openPromptWaiting((0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId), {
+        source: 'permission-request',
+        message: null,
+        toolName,
+        at,
+    });
+}
+/**
+ * The open dialog this instance's structured events imply, or null.
+ *
+ * Bounded exactly like {@link getStructuredSessionState}: a record from a
+ * previous generation is not this session's, and one older than
+ * {@link STRUCTURED_STATE_MAX_AGE_MS} has outlived the fact it describes. An
+ * unconfirmed `permission-request` record expires far sooner — see
+ * {@link STRUCTURED_PROMPT_PROVISIONAL_MAX_AGE_MS}.
+ *
+ * The returned object is the live record, not a copy: `current-output-builder`
+ * marks corroboration and the history write on it.
+ *
+ * @param now - Epoch ms; defaults to now
+ */
+function getStructuredPromptWaiting(worktreeId, cliToolId, instanceId, now = Date.now()) {
+    const key = (0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId);
+    const state = promptWaiting.get(key);
+    if (!state)
+        return null;
+    const generation = generationStartedAt.get(key);
+    if (generation !== undefined && state.at < generation)
+        return null;
+    if (now - state.at >= exports.STRUCTURED_STATE_MAX_AGE_MS)
+        return null;
+    if (state.confirmedAt === null &&
+        now - state.at >= exports.STRUCTURED_PROMPT_PROVISIONAL_MAX_AGE_MS) {
+        return null;
+    }
+    return state;
+}
+/**
+ * Record that the scraper has seen a blocking frame while this dialog is open
+ * (Issue #1725).
+ *
+ * Two effects, both needed: it confirms a provisional record, and it arms the
+ * only release rule the scraper is entitled to apply. See
+ * {@link StructuredPromptWaitingState.scraperCorroborated}.
+ *
+ * @param at - Epoch ms; defaults to now
+ */
+function corroborateStructuredPromptWaiting(worktreeId, cliToolId, instanceId, at = Date.now()) {
+    const state = promptWaiting.get((0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId));
+    if (!state)
+        return;
+    state.scraperCorroborated = true;
+    state.confirmedAt ??= at;
+}
+/** Note that this episode's prompt-history row has been written. */
+function markStructuredPromptRecorded(worktreeId, cliToolId, instanceId) {
+    const state = promptWaiting.get((0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId));
+    if (state)
+        state.recorded = true;
+}
+/**
+ * Release the prompt-waiting record — the dialog is gone (Issue #1725).
+ *
+ * Called from the event transitions above and from `current-output-builder`
+ * when the scraper reports that the frame it corroborated has cleared.
+ */
+function clearStructuredPromptWaiting(worktreeId, cliToolId, instanceId) {
+    promptWaiting.delete((0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId));
+}
+/**
+ * When the in-flight question is released (Issue #1726).
+ *
+ * | event                             | effect on the question |
+ * |-----------------------------------|------------------------|
+ * | `pre_tool_use(AskUserQuestion)`   | unchanged (this IS it) |
+ * | `pre_tool_use(any other tool)`    | release                |
+ * | `post_tool_use`                   | release                |
+ * | `notification(permission_prompt)` | **unchanged**          |
+ * | `notification(idle_prompt)`       | release                |
+ * | `notification(other)`             | unchanged              |
+ * | `stop`                            | release                |
+ * | `user_prompt_submit`              | release                |
+ * | `session_start` / `session_end`   | release                |
+ *
+ * `PostToolUse` is the precise release — "this tool call is over" — and `Stop`
+ * is the backstop for a delivery that never arrives. Issue #1726's text proposed
+ * `PostToolUse` and the #1721 spike recorded it as never observed, so this Issue
+ * measured it directly on a live v2.1.223 session (2026-08-06):
+ *
+ * ```
+ * 15:36:04.112  PreToolUse   AskUserQuestion
+ * 15:36:28.643  PostToolUse  AskUserQuestion   <- the human answered
+ * 15:36:29.992  Stop
+ * ```
+ *
+ * It fires, 1.3 s ahead of `Stop` here — and much further ahead whenever the
+ * agent keeps working after the answer, which is the case that matters: `Stop`
+ * alone would leave a finished question in place for the whole rest of the turn.
+ *
+ * A `PostToolUse` for any other tool releases as well: the agent could not have
+ * finished another tool call while this question was still on screen.
+ *
+ * **`Notification(permission_prompt)` keeping the question is a live
+ * measurement, not a guess.** The #1721 report says the picker emits no events
+ * while it is displayed (§5.6), and a first cut of this module read that as "any
+ * event means the picker is gone". Driving a real v2.1.223 session through the
+ * server on 2026-08-06 disproved it:
+ *
+ * ```
+ * 15:29:18.099  PreToolUse(AskUserQuestion)
+ * 15:29:18.109  PermissionRequest(AskUserQuestion) -> no decision
+ * 15:29:24.128  Notification(permission_prompt)      <- picker still on screen
+ * ```
+ *
+ * The notification lands ~6 s after the dialog is drawn (§5.5's timing exactly),
+ * which is *inside* the window §5.6 was counting rather than outside it. Under
+ * the first rule it deleted the question six seconds after it arrived, and the
+ * options went back to being the screen's — which is the whole feature, silently
+ * off, on every real session.
+ *
+ * `idle_prompt` still releases: the agent reporting it is sitting at the
+ * composer is the agent saying no picker is in front of it. An unrecognised
+ * notification type changes nothing, because nothing is known about it.
+ */
+function applyAskUserQuestionTransition(key, record) {
+    switch (record.event) {
+        case 'pre_tool_use':
+            // A `PreToolUse` for anything else means the agent has moved on to another
+            // tool, so whatever question was in flight has been answered. Only
+            // reachable when the operator's own settings.json registers a wider
+            // matcher than the injected `AskUserQuestion` one — the two files are
+            // concatenated, not substituted (#1722).
+            if (record.detail !== permission_request_payload_1.ASK_USER_QUESTION_TOOL)
+                askUserQuestion.delete(key);
+            return;
+        case 'notification':
+            if (record.detail === 'idle_prompt')
+                askUserQuestion.delete(key);
+            return;
+        case 'post_tool_use':
+        case 'stop':
+        case 'user_prompt_submit':
+        case 'session_start':
+        case 'session_end':
+            askUserQuestion.delete(key);
+            return;
+        default:
+            // exhaustive check: a new AgentEventType must decide its transition here
+            record.event;
+            return;
+    }
+}
+/**
+ * Record the `AskUserQuestion` invocation reported for one instance.
+ *
+ * Idempotent by construction: the same call is reported twice on every session
+ * — once by `PreToolUse` and once by the `PermissionRequest` that
+ * `AskUserQuestion` also raises with a byte-identical `tool_input` — and the
+ * second delivery simply overwrites the first with the same content.
+ *
+ * @param at - Epoch ms; defaults to now
+ */
+function recordAskUserQuestion(worktreeId, cliToolId, instanceId, spec, at = Date.now()) {
+    askUserQuestion.set((0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId), { at, spec });
+}
+/**
+ * The `AskUserQuestion` call in flight for this instance, or null.
+ *
+ * Bounded exactly like {@link getStructuredSessionState}: a record from a
+ * previous generation belongs to a Claude process that no longer exists, and one
+ * older than {@link STRUCTURED_STATE_MAX_AGE_MS} has outlived the screen it
+ * describes. There is no provisional bound — unlike a `PermissionRequest`, a
+ * `PreToolUse(AskUserQuestion)` is not a prediction that a dialog *might*
+ * appear: allowing the permission request does not dismiss the picker (§5.6), so
+ * the picker is drawn unconditionally.
+ *
+ * @param now - Epoch ms; defaults to now
+ */
+function getAskUserQuestion(worktreeId, cliToolId, instanceId, now = Date.now()) {
+    const key = (0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId);
+    const episode = askUserQuestion.get(key);
+    if (!episode)
+        return null;
+    const generation = generationStartedAt.get(key);
+    if (generation !== undefined && episode.at < generation)
+        return null;
+    if (now - episode.at >= exports.STRUCTURED_STATE_MAX_AGE_MS)
+        return null;
+    return episode;
+}
+/** Drop the in-flight question for one instance. */
+function clearAskUserQuestion(worktreeId, cliToolId, instanceId) {
+    askUserQuestion.delete((0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId));
+}
+/**
+ * Whether this event is a second copy of one already handled, and should be
+ * dropped.
+ *
+ * Only events that name a `sessionId` can be deduplicated, and calling this
+ * *claims* the key: a first call answers false and marks it, so the caller must
+ * ask once per request and act on the answer. Events with no session id are
+ * never suppressed — a caller that omits it (the #1549 relay run without a hook
+ * payload, a hand-rolled `curl`) has given us nothing to tell two deliveries of
+ * one turn from two genuine turns, and inventing a match there would silently
+ * drop real events.
+ *
+ * The subtype is part of the key (Issue #1726). It has to be, now that
+ * `pre_tool_use` exists: that event's subtype is the tool name, several tool
+ * calls a second is ordinary, and a key without it would read a `Bash` call and
+ * the `AskUserQuestion` that follows it as one delivery and drop the second. The
+ * same correction applies to two `Notification`s of different types inside the
+ * window, which were previously collapsed as well.
+ *
+ * @param at - Epoch ms; defaults to now
+ * @param detail - The event's subtype, when it has one
+ */
+function isDuplicateAgentEvent(worktreeId, cliToolId, instanceId, event, sessionId, at = Date.now(), detail = null) {
+    if (!sessionId)
+        return false;
+    const key = [
+        (0, auto_yes_state_1.buildCompositeKey)(worktreeId, cliToolId, instanceId),
+        event,
+        detail ?? '',
+        sessionId,
+    ].join(' ');
+    const seenAt = recentEventKeys.get(key);
+    if (seenAt !== undefined && at - seenAt < exports.AGENT_EVENT_DEDUP_WINDOW_MS) {
+        return true;
+    }
+    recentEventKeys.set(key, at);
+    pruneRecentEventKeys(at);
+    return false;
+}
+/** Drop keys past the window, then the oldest survivors if still over the cap. */
+function pruneRecentEventKeys(now) {
+    for (const [key, seenAt] of recentEventKeys) {
+        if (now - seenAt >= exports.AGENT_EVENT_DEDUP_WINDOW_MS) {
+            recentEventKeys.delete(key);
+        }
+    }
+    // Map iterates in insertion order, so the head is the oldest.
+    while (recentEventKeys.size > MAX_RECENT_EVENT_KEYS) {
+        const oldest = recentEventKeys.keys().next();
+        if (oldest.done)
+            break;
+        recentEventKeys.delete(oldest.value);
+    }
+}
+/** How many dedup keys are currently retained. Test seam for the bound above. */
+function getRecentEventKeyCount() {
+    return recentEventKeys.size;
+}
 /** Drop every recorded event. Test seam. */
 function clearAgentStopEvents() {
     lastStopEventAt.clear();
+    lastAgentEvent.clear();
+    recentEventKeys.clear();
+    generationStartedAt.clear();
+    promptWaiting.clear();
+    askUserQuestion.clear();
 }