@aragon-agent/cli 0.6.46 → 0.6.48

package/dist/agent/reducer.d.ts

@@ -1,837 +0,0 @@
-/**
- * Pure event → view reducer (spec §3.4 / §6.2).
- *
- * `reduceEvent(event)` maps a raw core `AgentEvent` into zero or more view
- * actions; `viewReducer(state, action)` folds an action into the immutable
- * `ViewState`. Keeping this pure lets the whole UI be tested without a live LLM.
- *
- * Two load-bearing behaviors from R2 (silent-failure surfacing) live here:
- *   - the `error` StreamEvent is rendered as an error notice, and
- *   - `agent_end` after a turn that produced no `turn_end` and no error notice
- *     synthesizes a generic error notice (a swallowed throw is never a no-op).
- */
-import type { PendingSteering } from './queued-messages.js';
-import type { InvocationCard } from './invocation-card.js';
-import type { AgentEvent, ModelCost, ToolResult, TokenUsage } from '@aragon-agent/core';
-import type { AgentMode } from './agent-mode.js';
-import type { DispatchOutcome, SubagentRun, SubagentSpec, TeamSnapshot } from '../team/types.js';
-import type { FastReview, FastSnapshot } from '../fast/types.js';
-import type { CompactionMode, CompactionPhase, CompactionRecord, CompactionSnapshot, CompactionUiTrigger, ContextUsageSnapshot } from '../compaction/types.js';
-import type { AcceptanceSnapshot, TodoItem, TodoSnapshot } from '../todo/types.js';
-import type { JobKind, ServiceSnapshot, ServiceStatus } from '../proc/types.js';
-import type { RetryPhase } from './retry-view.js';
-import type { FilePatch } from '../tools/patch.js';
-import type { TaskSummaryView } from '../fast/task-summary-types.js';
-import type { GovernanceCardData, GovernanceSnapshot } from '../governance/types.js';
-import type { Posture } from '../governance/posture.js';
-export type NoticeLevel = 'info' | 'warn' | 'error';
-export type ToastLevel = NoticeLevel | 'success';
-export type Overlay = null | 'settings' | 'model' | 'help' | 'queue' | 'confirm' | 'question' | 'plan' | 'kit' | 'prompts' | 'prompt-pick' | 'agents' | 'governance'
-/**
- * tui-shortcut-drawer-and-task-summary §4.5: the keyboard drawer (`Ctrl+G` /
- * `/keys`). A single field, so the drawer and `/help` cannot both hold the
- * keyboard - which is also why `Ctrl+G` TAKES OVER from another overlay instead
- * of being swallowed while one is open (P2-3).
- */
- | 'shortcuts';
-export type ToolStatus = 'pending' | 'running' | 'done' | 'error';
-/** Ephemeral, auto-dismissed acknowledgement (spec §3.9). */
-export interface Toast {
-    id: string;
-    level: ToastLevel;
-    text: string;
-    ttlMs: number;
-}
-/** Default auto-dismiss window for a toast. */
-export declare const DEFAULT_TOAST_TTL_MS = 2500;
-export type Entry = {
-    id: string;
-    kind: 'user';
-    text: string;
-    invocation?: InvocationCard;
-}
-/**
- * A message submitted while a run was in flight (tui-shift-enter-copy-queue
- * 5.2). It renders as `Queue: <first line>` and is rewritten IN PLACE, same
- * id, into the `user` entry above by the matching receipt that proves Core
- * accepted it -- so the id-based height cache re-measures rather than
- * freezes, and the settled boundary (positional, monotonic) never moves.
- *
- * NOT A LIVE TARGET: no id pointer in `ViewState` names it, so the trim
- * ring and the `appendEntry` assertions need no new member.
- */
- | {
-    id: string;
-    kind: 'queued';
-    text: string;
-    queueId?: string;
-    invocation?: InvocationCard;
-} | {
-    id: string;
-    kind: 'assistant';
-    text: string;
-    thinking?: string;
-    thinkingOpen: boolean;
-    streaming: boolean;
-    aborted?: boolean;
-    usage?: TokenUsage;
-    /**
-     * Epoch ms the turn started reasoning (agent-activity-presentation §3.1.2).
-     * Set by `thinkingStart`, cleared by `streamRestart`.
-     */
-    thinkingStartedAt?: number;
-    /**
-     * Wall-clock reasoning time, SEALED ONCE — at the first text delta, or at
-     * turn/run end for a turn that thought and then called a tool without
-     * emitting any text.
-     *
-     * With thinking hidden this is the only thing the collapsed marker can say
-     * that the user could not otherwise know, which is the whole argument for
-     * having a marker at all (§1.2).
-     */
-    thinkingMs?: number;
-} | {
-    id: string;
-    kind: 'tool';
-    toolCallId: string;
-    name: string;
-    label: string;
-    argsRaw: string;
-    args?: Record<string, unknown>;
-    status: ToolStatus;
-    preview?: string;
-    durationMs?: number;
-    isError?: boolean;
-    /**
-     * The structured file diff (agent-activity-presentation §3.3), or absent.
-     *
-     * IMMUTABLE AND WRITTEN ONCE, by `toolExecEnd`. `ToolCard` is `React.memo`'d
-     * with the DEFAULT comparator, so this object is only free while its
-     * reference is stable — which it is, because the reducer never rebuilds it
-     * and `mapEntry` preserves identity for untouched entries. A future action
-     * that recomputed or normalized a patch would turn that memo boundary into
-     * a no-op WITH NOTHING FAILING (P2-9).
-     *
-     * Needs no clause in `normalizeLoadedEntries` (D-9): the four that exist
-     * are all about a LIVE flag that would never settle, and a patch is settled
-     * by construction.
-     */
-    patch?: FilePatch;
-    /**
-     * The sanitised live tail while the tool runs
-     * (agent-activity-presentation-live §3.3.1). Cleared at settle (D-23), and
-     * cleared again by EVERY path that reaches `status: 'idle'` (D-35).
-     *
-     * REDUCER STATE RATHER THAN A STORE READ DURING RENDER, and that is the
-     * load-bearing decision of the round (D-22): `entryRevision` is what tells
-     * the height cache an entry's rendered output changed, and an entry mutated
-     * outside `ViewState` keeps its revision and freezes at a stale height AND
-     * a stale subtree with nothing anywhere reporting it (I-L3-1).
-     */
-    live?: readonly string[];
-    /**
-     * Monotonic counter -- the revision term for a NON-APPEND mutation (D-22).
-     *
-     * A COUNTER AND NOT `live.length`: a fixed-size tail evicting its oldest
-     * row while appending a new one of the same width leaves the joined length
-     * unchanged, which is exactly the lossy case `virtual-window.ts` says the
-     * reducer cannot produce today and that this round introduces.
-     */
-    liveSeq?: number;
-    /** Epoch ms of the last output row, for the stall row (§3.3.4). */
-    lastOutputAt?: number;
-} | {
-    id: string;
-    kind: 'notice';
-    level: NoticeLevel;
-    text: string;
-} | {
-    id: string;
-    kind: 'governance';
-    at: number;
-    card: GovernanceCardData;
-} | {
-    id: string;
-    kind: 'team';
-    dispatchId: string;
-    requested: number;
-    runs: SubagentRun[];
-    aborted: boolean;
-    durationMs?: number;
-    active: boolean;
-} | {
-    id: string;
-    kind: 'todo';
-    items: TodoItem[];
-    doneCount: number;
-    total: number;
-    /**
-     * The acceptance projection, copied from `TodoSnapshot.acceptance` on every
-     * `todoUpdate` (todo-acceptance-criteria §6.10).
-     *
-     * OPTIONAL, NOT `AcceptanceSnapshot | null` REQUIRED, and that asymmetry with
-     * the snapshot is deliberate (P1-4): `TodoSnapshot` has exactly one writer, so
-     * it can fail closed; an `Entry` does not - its sources include `entries` read
-     * back from a session file written before this feature existed, where the key
-     * is simply absent.
-     */
-    acceptance?: AcceptanceSnapshot | null;
-    /** The turn that owns this card is still running, so it may be rewritten. */
-    live: boolean;
-    /**
-     * Set by `normalizeLoadedEntries` on a card saved while its run was live
-     * (P2-6). The todo analogue of the team entry's `aborted`, and true for the
-     * same reason: the run behind it died with the process. Absent on every
-     * card this session produced.
-     */
-    interrupted?: boolean;
-} | {
-    id: string;
-    kind: 'retry';
-    /** 1-based retry index of the LATEST attempt this card has seen. */
-    attempt: number;
-    maxRetries: number;
-    errorType: string;
-    message: string;
-    delayMs: number;
-    /** Epoch ms the next attempt fires; the UI ticks against this. */
-    resumeAt?: number;
-    phase: RetryPhase;
-    startedAt: number;
-    /** Filled on settle. */
-    totalRetries?: number;
-    elapsedMs?: number;
-} | {
-    id: string;
-    kind: 'fast';
-    /** 1-based within the session, so the card can name itself. */
-    reviewIndex: number;
-    model: string;
-    status: 'running' | 'ok' | 'advice' | 'empty' | 'failed' | 'dropped';
-    /** Present only for `advice`. */
-    text?: string;
-    /** Failure / drop reason, shown as one muted line. */
-    detail?: string;
-    turn: number;
-    durationMs?: number;
-    live: boolean;
-} | {
-    id: string;
-    kind: 'compaction';
-    decision?: CompactionRecord['decision'];
-    memoryVersion?: CompactionRecord['memoryVersion'];
-    /** 1-based within the session, so the card can name itself. */
-    index: number;
-    trigger: CompactionUiTrigger;
-    mode: CompactionMode;
-    applied: boolean;
-    reason?: string;
-    messagesBefore: number;
-    messagesAfter: number;
-    tokensBefore: number;
-    tokensAfter: number;
-    summary?: string;
-    model: string;
-    durationMs?: number;
-    /**
-     * When the live card opened, so the elapsed counter has an origin
-     * (context-auto-compaction-hardening §3.6 / W5).
-     *
-     * JSON-SERIALIZABLE like every other field here, and harmless on reload:
-     * `session/persist.ts` normalizes `live` to false, and a settled card
-     * renders `durationMs` rather than an elapsed figure.
-     */
-    startedAt?: number;
-    /** Set when tail relief clipped the retained turns (W2). */
-    tailRelief?: {
-        messages: number;
-        charsRemoved: number;
-    };
-    /**
-     * The stage the LIVE card is in (context-compaction-never-fires C).
-     *
-     * Absent on a settled card and on every card written before this field
-     * existed, which is why the renderer treats it as optional and falls back to
-     * the old `summarizing with <model>` line.
-     */
-    phase?: CompactionPhase;
-    /** Set when the cut relaxed `keepRecentTurns` to exist at all (B). */
-    keepRelaxed?: boolean;
-    retainedTurns?: number;
-    /** Messages the relaxed cut left verbatim - the number the card states. */
-    retainedMessages?: number;
-    keepRecentTurnsUsed?: number;
-    /** Messages the digest left out, so they cannot be quoted (A1). */
-    elidedMessages?: number;
-    live: boolean;
-} | {
-    id: string;
-    kind: 'service';
-    /** `s1`, `s2`, ... — the id the model quotes back. */
-    serviceId: string;
-    command: string;
-    status: ServiceStatus;
-    url?: string;
-    port?: number;
-    exitCode: number | null;
-    startedAt: number;
-    readyAt?: number;
-    endedAt?: number;
-    rows: readonly string[];
-    /**
-     * MONOTONIC row cursor — the revision term, NEVER `rows.length` (P0-3).
-     *
-     * The tail is a FIXED-SIZE RING: it evicts its oldest row while appending
-     * a new one, so the joined length is unchanged while the content is not.
-     * That is verbatim the non-append mutation the `tool` branch's `liveSeq`
-     * comment was written for, and a length term would go on matching while
-     * the card changed underneath it.
-     */
-    rowsSeen: number;
-    /** The one-row entry a terminal transition appends (D-11). */
-    terminal?: boolean;
-    /** The stop reported the pid still alive afterwards (R-2 / P2-6). */
-    killIncomplete?: boolean;
-    /**
-     * WHICH KIND OF JOB THIS CARD DRAWS (long-task-jobs §4.9 / I-2).
-     *
-     * It changes the NOUN and the status wording only. Renaming the entry kind
-     * from `service` to `job` would be a pure regression: ordinary assertions pin
-     * `[background] service s1 started` word for word, `bg-command.test.ts` pins
-     * `/bg stop`'s `Stopped N services` toast, and there are no snapshot files in
-     * this package to absorb the churn. The few strings that DID move to "job"
-     * are the model-facing unknown-id messages in `proc-tools.ts`, which name an
-     * id space that now holds both kinds.
-     */
-    jobKind: JobKind;
-    /** Latest extracted progress line; one extra row when present. */
-    progress?: string;
-    /** When output last arrived, so `stalled` can be evaluated at render time. */
-    lastOutputAt: number;
-    /** Derived at snapshot time by the supervisor, carried here so it survives a save. */
-    stalled?: boolean;
-    /** Where the on-disk mirror wrote this job's full log. */
-    logPath?: string;
-};
-export interface UsageTotal {
-    inputTokens: number;
-    outputTokens: number;
-    /**
-     * Cache read hits (context-usage-gauge-accuracy §3.6 / P1-3).
-     *
-     * `occupiedTokens` counts them and `computeCost` PRICES them, so a session
-     * total that omits them makes the status bar's `^` read lower than the `$`
-     * next to it - on the same row, from the same turns. That was three units on
-     * one line, and this field plus its sibling are what collapse them to one.
-     */
-    cacheReadTokens: number;
-    cacheWriteTokens: number;
-    costUsd: number;
-}
-/**
- * The ephemeral retry projection held in `ViewState.retry` (§9).
- *
- * Only the two IN-FLIGHT phases exist here: once a card settles the projection is
- * `null`, because the settled card IS the history and a chip that reported a
- * finished retry would never go away.
- */
-export interface RetrySnapshot {
-    attempt: number;
-    maxRetries: number;
-    resumeAt?: number;
-    phase: 'waiting' | 'retrying';
-    errorType: string;
-}
-export interface ViewState {
-    entries: Entry[];
-    pendingSteering: PendingSteering[];
-    seenSteeringIds: ReadonlySet<string>;
-    runPhase: 'idle' | 'starting' | 'waiting' | 'thinking' | 'generating' | 'preparing-tool' | 'tool';
-    activeTool?: {
-        toolCallId: string;
-        name: string;
-    };
-    runOutcome: 'none' | 'ended' | 'interrupted' | 'failed';
-    status: 'idle' | 'running';
-    usageTotal: UsageTotal;
-    /**
-     * Context occupancy, as published by `AgentController`'s `ContextMeter`.
-     *
-     * ITS ONLY WRITER IS `case 'contextUsage'` (I-1), and that is the structural
-     * half of the P0-1 fix. It replaced `contextTokens` + `contextTokensEstimated`,
-     * which between them had THREE writing branches (`turnEnd`,
-     * `contextTokensEstimated`, `resetConversation`) fed by two competing
-     * upstreams. Two writers in one synchronous fan-out means the later one wins,
-     * and the later one was the stale `snapshot` carrying the PRE-compaction
-     * figure - so the bar fell and bounced straight back, every time, with nothing
-     * logging a fault. `context-one-writer.test.ts` scans this file to keep it
-     * that way.
-     */
-    context: ContextUsageSnapshot;
-    overlay: Overlay;
-    thinkingVisible: boolean;
-    /** Ephemeral acks; auto-dismissed by App (spec §3.9). */
-    toasts: Toast[];
-    /** Which tool cards are expanded to their full stored preview (spec §3.7). */
-    expandedToolIds: Record<string, true>;
-    /**
-     * MIRROR of the controller's effective mode, for rendering only (plan-mode
-     * §3.1). Written exclusively from what `controller.setAgentMode()` reports it
-     * adopted — never from what the UI asked for.
-     */
-    agentMode: AgentMode;
-    /** Set only by a DEFERRED `plan -> build`; drives the `PLAN -> BUILD` readout. */
-    pendingAgentMode: AgentMode | null;
-    /**
-     * The user-visible posture and its deferred twin (governance-mode 4.3). Written in the
-     * SAME dispatch as `agentMode` / `pendingAgentMode` and only from what the controller
-     * adopted, so the badge and the gate cannot diverge. `agentMode` keeps gating.
-     */
-    posture: Posture;
-    pendingPosture: Posture | null;
-    /**
-     * The live governed-run snapshot, or `null` when there is no run.
-     *
-     * NEVER PERSISTED, like `team`: `/save` writes `entries` (the settlement cards are the
-     * history) and a resumed session has no live run to show.
-     */
-    governance: GovernanceSnapshot | null;
-    /**
-     * The live team roster, or `null` when no dispatch is running.
-     *
-     * NEVER PERSISTED. `/save` writes `entries`, and the settled `team` entry is
-     * the history; this field is the ephemeral panel, and a resumed session has no
-     * live dispatch to show (§6.4).
-     */
-    team: TeamSnapshot | null;
-    /**
-     * The live todo list, or `null` when there is none.
-     *
-     * NEVER PERSISTED HERE — `entries` is the history and `SavedSession.todos` is
-     * the list (§3.13). `null` is what leaves the rail unmounted entirely, which
-     * is why a session that never plans has byte-identical layout to a pre-feature
-     * build (AC-24).
-     */
-    todos: TodoSnapshot | null;
-    /**
-     * The live retry projection, or `null` when nothing is retrying.
-     *
-     * NEVER PERSISTED — `entries` is the history and the settled card is the
-     * record. It drives the status-bar chip and the 1 Hz tick, and it is nulled on
-     * every settle path. Same contract as `team`.
-     */
-    retry: RetrySnapshot | null;
-    /**
-     * The live fast-tier projection, or `null` when the tier is off for this
-     * session (fast-model-tier §5.2).
-     *
-     * NEVER PERSISTED — `entries` is the history and the settled cards are the
-     * record. It drives the status chip and `/fast status`'s totals. `null` is
-     * what leaves an ordinary session's status bar byte-identical (AC-4).
-     */
-    fast: FastSnapshot | null;
-    /**
-     * The live compaction projection, or `null` when the feature is off for this
-     * session (context-auto-compaction §5.5).
-     *
-     * NEVER PERSISTED — `entries` is the history and the settled cards are the
-     * record. It drives the status chip, the gauge's marks and `/compact status`'s
-     * totals. `null` is what leaves an ordinary session's status bar unchanged.
-     */
-    compaction: CompactionSnapshot | null;
-    /**
-     * The session's task label, or `null` while there is none
-     * (tui-shortcut-drawer-and-task-summary D-13).
-     *
-     * PURE VIEW STATE: never persisted, never in the conversation history, never in
-     * `config.json`. It lives here because the header and the drawer must read the
-     * SAME field - two copies would be two labels for one task.
-     *
-     * THE TWO WRITERS ARE `taskSummaryPending` / `taskSummaryReady`, and the two
-     * CLEARERS are `resetConversation` and `restoreEntries`: clearing is the
-     * reducer's job (it is the only place that knows a task ended), while
-     * REBUILDING after `/resume` is the App wrapper's job, because only it can see
-     * the restored entries before they are reduced.
-     */
-    taskSummary: TaskSummaryView | null;
-    /** A summary call is in flight. Drives the drawer's `summarizing` line and `/task`. */
-    taskSummaryPending: boolean;
-    seq: number;
-    /** The `kind: 'team'` entry the live dispatch is writing into. */
-    teamEntryId?: string;
-    /** The `kind: 'todo'` entry this turn is writing into. */
-    todoEntryId?: string;
-    /** The `kind: 'retry'` entry this turn is writing into. */
-    retryEntryId?: string;
-    /** The `kind: 'fast'` entry the in-flight review is writing into. */
-    fastEntryId?: string;
-    /** The `kind: 'compaction'` entry the in-flight compaction is writing into. */
-    compactionEntryId?: string;
-    streamingId?: string;
-    turnProduced: boolean;
-    errorNoticed: boolean;
-    /** The current run was aborted by the user (suppresses the failure guard). */
-    aborted: boolean;
-    /**
-     * Entries removed by `transcriptRetain` (tui-render-performance L1).
-     *
-     * Rendered by `transcript-text` and reported by `/perf`; NEVER PERSISTED —
-     * `SavedSession` keeps `{ model, messages, entries, todos }` exactly as it is,
-     * so `/save` and `/resume` need no format change and old files load unchanged.
-     */
-    droppedEntries: number;
-}
-/**
- * The zero session total.
- *
- * ONE LITERAL FOR TWO SITES (`initialViewState` and `resetConversation`). They
- * used to spell the object out twice, which is how `cacheReadTokens` would have
- * been added to one of them and not the other.
- */
-export declare const EMPTY_USAGE_TOTAL: UsageTotal;
-export interface ViewStateSeed {
-    /** Start with thinking blocks expanded. Defaults to FALSE, the product default. */
-    thinkingVisible?: boolean;
-}
-/**
- * The initial view state, optionally seeded from config.
- *
- * THE DEFAULT IS `false`, NOT `true`, AND THAT IS THE WHOLE SAFETY ARGUMENT
- * (D-2). There is exactly one production call site — `App`'s `useReducer`, which
- * passes `cfg.showThinking`. Every other caller is a test. A future call site
- * that forgets the seed fails CLOSED, toward the product default, rather than
- * silently restoring the reasoning firehose for one code path with nothing
- * reporting it.
- *
- * The seed is a PARAMETER rather than a post-mount dispatch so that `/resume`
- * cannot flash a restored thinking block on frame 1.
- */
-export declare function initialViewState(seed?: ViewStateSeed): ViewState;
-export type ViewAction = {
-    type: 'submit';
-    text: string;
-    invocation?: InvocationCard;
-}
-/**
- * `controller.steer` was accepted; append the persistent queue marker
- * (5.2.2). Dispatched from exactly one place -- `App.submitMessage`'s
- * running branch -- beside the `controller.steer` call it mirrors.
- */
- | {
-    type: 'steerQueued';
-    queueId: string;
-    text: string;
-    invocation?: InvocationCard;
-} | {
-    type: 'steeringAccepted';
-    ids: readonly string[];
-} | {
-    type: 'runStart';
-} | {
-    type: 'runStarting';
-} | {
-    type: 'runError';
-} | {
-    type: 'turnStart';
-} | {
-    type: 'thinkingStart';
-} | {
-    type: 'thinkingDelta';
-    delta: string;
-} | {
-    type: 'textDelta';
-    delta: string;
-} | {
-    type: 'toolCallStart';
-    toolCallId: string;
-    toolName: string;
-    label?: string;
-} | {
-    type: 'toolCallDelta';
-    toolCallId: string;
-    argsDelta: string;
-} | {
-    type: 'toolCallEnd';
-    toolCallId: string;
-    args: Record<string, unknown>;
-} | {
-    type: 'toolExecStart';
-    toolCallId: string;
-    toolName?: string;
-} | {
-    type: 'toolExecEnd';
-    toolCallId: string;
-    isError: boolean;
-    duration: number;
-    preview: string;
-    /** A fully-built, immutable diff, so the reducer stays pure (§3.3.7). */
-    patch?: FilePatch;
-}
-/**
- * A running tool's live tail (agent-activity-presentation-live §3.3.1).
- *
- * `rows` IS THE WHOLE TAIL, not an increment: the store replaces it on every
- * chunk, which is what lets `mergeDeltas` keep only the last action per
- * `toolCallId` (D-30). `at` is read in `App`'s listener rather than here, so
- * this reducer stays pure.
- */
- | {
-    type: 'toolOutputDelta';
-    toolCallId: string;
-    rows: readonly string[];
-    at: number;
-} | {
-    type: 'turnEnd';
-    usage: TokenUsage;
-    costDelta: number;
-} | {
-    type: 'runEnd';
-} | {
-    type: 'notice';
-    level: NoticeLevel;
-    text: string;
-} | {
-    type: 'abortMark';
-} | {
-    type: 'clearTranscript';
-} | {
-    type: 'resetConversation';
-}
-/**
- * Zero the session's spend WITHOUT touching the conversation
- * (tui-session-id-resume D-10 / R-9 / T-45).
- *
- * A separate action rather than `resetConversation`, because the two mean
- * different things: `/clear` ends the conversation and the spend together,
- * while an in-TUI `/resume` adopts another conversation and starts a NEW id -
- * so the counter must restart, but the entries that were just restored must
- * not be thrown away with it. `context` is left untouched for the reason
- * `resetConversation` records: the meter, not the reducer, owns occupancy.
- */
- | {
-    type: 'resetUsage';
-} | {
-    type: 'setOverlay';
-    overlay: Overlay;
-} | {
-    type: 'toggleThinking';
-} | {
-    type: 'pushToast';
-    level: ToastLevel;
-    text: string;
-    ttlMs?: number;
-} | {
-    type: 'dismissToast';
-    id: string;
-} | {
-    type: 'toggleExpand';
-    id: string;
-} | {
-    type: 'restoreEntries';
-    entries: Entry[];
-}
-/**
- * The task label lifecycle (tui-shortcut-drawer-and-task-summary §7.1).
- *
- * TWO ACTIONS, because "a call started" and "a call finished" are different
- * facts and the drawer reports them differently (`summarizing` vs the label).
- * `taskSummaryReady` carries `null` in exactly one case: the call failed AND
- * `taskSummary.fallback` is off, which is a deliberate "show nothing" rather
- * than an empty string that would read as a broken feature.
- */
- | {
-    type: 'taskSummaryPending';
-} | {
-    type: 'taskSummaryReady';
-    view: TaskSummaryView | null;
-} | {
-    type: 'setAgentMode';
-    mode: AgentMode;
-    pending: AgentMode | null;
-    posture?: Posture;
-    pendingPosture?: Posture | null;
-} | {
-    type: 'govSnapshot';
-    snapshot: GovernanceSnapshot;
-} | {
-    type: 'govEnd';
-} | {
-    type: 'governanceCard';
-    card: GovernanceCardData;
-    at?: number;
-} | {
-    type: 'teamStart';
-    dispatchId: string;
-    requested: number;
-    specs: SubagentSpec[];
-} | {
-    type: 'teamUpdate';
-    snapshot: TeamSnapshot;
-} | {
-    type: 'teamUsage';
-    usage: TokenUsage;
-    costDelta: number;
-} | {
-    type: 'teamEnd';
-    outcome: DispatchOutcome;
-} | {
-    type: 'todoUpdate';
-    snapshot: TodoSnapshot;
-} | {
-    type: 'todoCleared';
-} | {
-    type: 'retryScheduled';
-    attempt: number;
-    maxRetries: number;
-    delayMs: number;
-    resumeAt: number;
-    errorType: string;
-    message: string;
-} | {
-    type: 'retryAttempt';
-    attempt: number;
-    maxRetries: number;
-} | {
-    type: 'streamRestart';
-    discardedToolCallIds: string[];
-}
-/**
- * The 1 Hz countdown tick. NO STATE OF ITS OWN — it bumps `seq` so the frame
- * re-renders and the card recomputes `resumeAt - Date.now()`. `App` runs the
- * interval ONLY while `state.retry?.phase === 'waiting'`, so an idle session has
- * no timer at all.
- */
- | {
-    type: 'retryTick';
-} | {
-    type: 'fastStart';
-    index: number;
-    turn: number;
-    model: string;
-} | {
-    type: 'fastEnd';
-    review: FastReview;
-}
-/**
- * Review spend.
- *
- * `costDelta` IS PRECOMPUTED BY THE CALLER, exactly as `teamUsage`'s is: the
- * reducer stays pure and cost-table-free, which is the property that makes it
- * testable — and the fast tier has a DIFFERENT cost table from the lead, so a
- * reducer that computed its own would have to know about both (§3.6 / R-7).
- */
- | {
-    type: 'fastUsage';
-    usage: TokenUsage;
-    costDelta: number;
-} | {
-    type: 'fastTier';
-    snapshot: FastSnapshot;
-} | {
-    type: 'compactionStart';
-    index: number;
-    trigger: CompactionUiTrigger;
-    model: string;
-} | {
-    type: 'compactionEnd';
-    record: CompactionRecord;
-}
-/**
- * The live card's stage (context-compaction-never-fires C).
- *
- * Its own action rather than a field on `compactionStart` because the phases
- * arrive AFTER it, one per step, and because a phase must be able to land on a
- * card that a previous attempt already settled into the same entry id.
- */
- | {
-    type: 'compactionPhase';
-    index: number;
-    phase: CompactionPhase;
-}
-/**
- * Compaction spend.
- *
- * `costDelta` IS PRECOMPUTED BY THE CALLER, exactly as `teamUsage`'s and
- * `fastUsage`'s are: the reducer stays pure and cost-table-free. It matters
- * MORE here than for either of those, because the summarizer may be a
- * different model from the lead AND from the fast tier, so a reducer that
- * computed its own would have to know about three price tables.
- */
- | {
-    type: 'compactionUsage';
-    usage: TokenUsage;
-    costDelta: number;
-} | {
-    type: 'compactionSnapshot';
-    snapshot: CompactionSnapshot;
-}
-/**
- * The occupancy reading, from `AgentController.subscribeContextUsage`.
- *
- * THE ONLY ACTION THAT WRITES `state.context`, AND IT IS DISPATCHED FROM
- * EXACTLY ONE PLACE (I-1 / T11). It replaced `contextTokensEstimated`, which
- * `App` fired from two branches of the compaction stream while `turnEnd` wrote
- * the same field from the agent stream - three writers, two upstreams, one
- * number, and the P0-1 bounce as the result.
- */
- | {
-    type: 'contextUsage';
-    snapshot: ContextUsageSnapshot;
-} | {
-    type: 'serviceStart';
-    service: ServiceSnapshot;
-} | {
-    type: 'serviceUpdate';
-    service: ServiceSnapshot;
-} | {
-    type: 'serviceEnd';
-    service: ServiceSnapshot;
-};
-export declare const STORED_PREVIEW_CHARS = 8000;
-export declare const STORED_PREVIEW_LINES = 200;
-/**
- * Marker appended to a truncated tool preview. ASCII on purpose: this string is
- * produced outside `src/ui/**`, where no terminal capabilities are available, so
- * it must be safe on a legacy `cmd.exe` (spec §4.1 tier A). `ToolPreview` dims
- * this line and imports the constant rather than re-spelling it — the two used
- * to be a matched pair of `…` literals, and splitting the spelling would break
- * the dimming silently.
- */
-export declare const PREVIEW_TRUNCATION_MARK = "...";
-/**
- * Flatten a ToolResult into a stored preview string. Truncation appends
- * `PREVIEW_TRUNCATION_MARK` (line- or char-based) so a card footer never
- * over-promises how much more is expandable.
- */
-export declare function buildToolPreview(result: ToolResult): string;
-/**
- * Where a `FilePatch` is collected from on `tool_execution_end`.
- *
- * Supplying one makes `reduceEvent` CONSUME-ONCE rather than pure, which is safe
- * because `App.tsx` calls it exactly once per event and `mergeDeltas` only ever
- * merges `textDelta` / `thinkingDelta`, never `toolExecEnd`.
- */
-export interface PatchSource {
-    take(toolCallId: string): FilePatch | undefined;
-}
-/**
- * Map one core `AgentEvent` to view actions. `cost` (the active model's cost
- * table) lets `turn_end` accumulate USD cost; omit it in tests that only assert
- * token totals. `patches` is the CLI-local diff side channel (§3.3.7); omitting
- * it — every existing test, and headless mode — produces byte-identical actions.
- */
-export declare function reduceEvent(event: AgentEvent, cost?: ModelCost, patches?: PatchSource): ViewAction[];
-/**
- * The opening words of the `context_overflow` banner.
- *
- * A SHARED CONSTANT RATHER THAN TWO LITERALS, because `compactionStart` matches
- * on it to rewrite the notice a successful reactive recovery would otherwise
- * leave behind (P1-4). Two spellings that must agree, with nothing checking that
- * they do, is how that rewrite silently stops matching — at which point the red
- * "start over" banner comes back and only on the recovery path, which is the one
- * place nobody re-tests.
- */
-export declare const CONTEXT_OVERFLOW_NOTICE_PREFIX = "Context length exceeded";
-/** Turn a provider error into a friendly banner, mapping LLMError.errorType. */
-export declare function formatStreamError(error: Error): string;
-export declare function viewReducer(state: ViewState, action: ViewAction): ViewState;