/** * wait Command - stderr notices about Auto-Yes and pane obstructions * Issue #3964: split out of wait.ts; wait.ts re-exports what it exported. */ import type { CurrentOutputResponse } from '../types/api-responses'; /** * The cause sentence to append when the frame carries a pane obstruction, or '' * (Issue #2095). * * Appended rather than substituted, and no exit code moves: the frame is * genuinely unclassified and `wait` was already right to stop on it. What it * could not say before is WHY, which left an operator with `capture --pane` and * a screenful of box drawing to work it out from. * * Empty for a server too old to publish the field, which is the same output * `wait` produced before this Issue. */ export declare function describePaneObstruction(data: CurrentOutputResponse): string; type LastSuppression = NonNullable['lastSuppression']>; /** * The suppression currently blocking this session, or null. * * Issue #3863: with the Auto-Yes answer mode in effect (`autoYesAnswerMode`) * when the server publishes one — what `question-left-to-human` and * `recommended-option-unidentified` depend on. */ export declare function activeSuppression(data: CurrentOutputResponse, now: number): { suppression: LastSuppression; ageSeconds: number; answerMode?: string; } | null; /** * One stderr line naming what is holding this prompt (Issue #1699). * * `wait` used to print only "Waiting for human response...", which reads the * same whether a human was always going to answer or whether Auto-Yes silently * refused to. That ambiguity is what let a deny pattern matching a finished turn * stall two workers unnoticed; the pattern and the reason code belong on screen. * * Issue #1843: the cause is chosen per reason rather than asserted. `reason=` is * in the payload either way, so the prefix is the only part that can lie — and it * did, for every non-contract suppression. */ export declare function formatSuppressionNotice(suppression: LastSuppression, ageSeconds: number, answerMode?: string): string; /** * One stderr line saying Auto-Yes is off on this instance because the server * restarted (Issue #3730), or null. * * Only words: the prompt was going to be reported either way — an instance * whose grant the restart released is an instance with Auto-Yes off, and exit * 10 for it is exactly the hand-back it always was. What this adds is the WHY, * so a delegating agent re-enables Auto-Yes instead of guessing. A server * older than the reason sends none, and nothing is printed. * * The command it suggests names the instance this wait is about: without * `--instance`, `auto-yes --enable` arms the worktree's default primary, which * for an alias (or a non-default tool) is another instance — the waited-on one * would stay off while a grant went somewhere nobody asked for. The instance is * the resolved `--instance` when one was given, else the CLI tool the server * answered for (a primary's instance ID is its tool ID). * * @param instanceId - The resolved `--instance` of this wait, if any */ export declare function formatRestartReleaseNotice(worktreeId: string, data: CurrentOutputResponse, instanceId?: string): string | null; /** * One stderr line saying Auto-Yes pressed Enter on THIS prompt (Issue #3397), or * null when the record is absent or about another screen. * * The prompt is one CommandMate could not read (the window offers direct input * for it). `sent` — Auto-Yes confirmed whatever was selected; `no-effect` — the * same screen outlived the Enter, no second one was sent, and it is a human's * again. An outcome this CLI does not know is named verbatim (#1843's rule). * `currentPrompt` is the server's judgement that the record is about the * `promptData` of the same response, so an Enter sent to an earlier screen is * never reported against this one. */ export declare function formatEnterFallbackNotice(data: CurrentOutputResponse, now: number): string | null; /** * Issue #3821: the server's own word that Auto-Yes left this prompt to a human * (`autoYesDecision.state === 'withheld'`) — `server-poller-inactive` when no * poller runs for the instance, or a stop the suppression record does not * carry. Read only when the server publishes the field; an older one leaves * `wait` holding as before. */ export declare function decisionWithheldReason(data: CurrentOutputResponse): string | null; export {}; //# sourceMappingURL=wait-notices.d.ts.map