@songsid/agend 2.3.1 → 2.3.2-beta.10

package/dist/backend/kiro.d.ts

@@ -1,5 +1,7 @@
-import { type BackendAgentSwitch, type CliBackend, type CliBackendConfig, type ErrorPattern, type StartupDialog, type RuntimeDialog, type SteerComposerMode } from "./types.js";
+import { type BackendAgentSwitch, type CliBackend, type CliBackendConfig, type ErrorPattern, type StartupDialog, type RuntimeDialog, type RemoteInputCard, type RemoteQuestionCard, type SteerComposerMode } from "./types.js";
+import { type KiroModelErrorVerdict } from "./kiro-retired-model.js";
 import type { KiroLogLaunch } from "../kiro-log-gate.js";
+import type { KiroTranscriptLaunch } from "../transcript-sources.js";
 export declare const KIRO_LEGACY_UI_MIN = "1.27.0";
 export declare const KIRO_EFFORT_FLAG_MIN = "2.6.0";
 /** Oldest kiro-cli AgEnD claims: older ones still launch, with a warning. */
@@ -14,7 +16,7 @@ export declare const KIRO_INSTANCE_AGENT_MIN = "2.21.0";
  * the binary's own --help instead of the version table, and the operator is
  * told the version is unverified.
  */
-export declare const KIRO_TESTED_MAX = "2.33.0";
+export declare const KIRO_TESTED_MAX = "2.34.0";
 /**
  * kiro-cli versions, per TUI front-end, whose mid-turn steering AgEnD drives (#1405). Only kiro's TUI steers — typed
  * input while a turn runs is injected into it ("steer", the default) or held for its end ("queue", Ctrl+S toggles); the
@@ -22,6 +24,8 @@ export declare const KIRO_TESTED_MAX = "2.33.0";
  * queued message mid-tool — has been captured (tests/fixtures/kiro-steer-1405, 2026-10-08: 2.27.1 `--tui
  * --agent-engine=v2` and `--v3`, 2.28.0 `--tui --agent-engine=v2`; identical rows on all three). Any other version,
  * 2.28.0's v3, the legacy UI and an undetected version all deliver a steer as an ordinary message after the turn.
+ * 2.34.0 TUI was checked on the user-authorized #2598 D5 run (tests/fixtures/kiro-2.34.0-tui-d5):
+ * native steer during a read-only tool, a fleet message queued mid-tool, and a native queue entry in the busy turn.
  */
 export declare const KIRO_STEER_VERIFIED: Readonly<Record<string, ReadonlyArray<"tui" | "v3">>>;
 export declare function readKiroSteerComposer(pane: string): SteerComposerMode | null;
@@ -59,6 +63,41 @@ export declare function kiroTrustPromptState(pane: string): KiroLaunchPromptStat
  * mid-session "cancel" and notice variants, and any other shape, are active with an unknown cursor — held, never keyed.
  */
 export declare function kiroWorkspaceTrustState(pane: string): KiroLaunchPromptState;
+/**
+ * #2587: kiro-cli 2.34.0's V3 engine answers an MCP server's `elicitation/create` (a tool asking the user for input)
+ * with a card in place of the composer: a divider, `Input requested · <server>`, a divider, the server's message and
+ * one row per form field then Submit / Decline (form mode) — or Host, URL and Open in browser / Copy URL / I'll open it
+ * myself / Decline / Cancel (url mode) — with exactly one `❯` cursor row, a divider, and the key hints as the last row
+ * (tests/fixtures/kiro-2.34.0-audit). Bottom-anchored: the card is live only while it is what the pane ends with. The
+ * answer can carry credentials or a sign-in, so it is the person's: never a key, and no delivery's Enter may land in it.
+ */
+export declare function kiroMcpInputRequestActive(pane: string): boolean;
+/**
+ * #2592: kiro's V3 engine shows the agent's question to the user (`question_request`) as a card in place of the
+ * composer: a divider, `Question` (or `<name> > Question`), the question, numbered options (a description row under
+ * one, `(recommended)` after one) and `Type a different answer…`, a divider, and the key hints as the last row — or, in
+ * an option's sub-options, `[✓] <title>` rows and `esc to go back · … · space to toggle · ↵ to submit`
+ * (tests/fixtures/kiro-question-2592; unchanged from 2.33.1 to 2.34.0). Any typed character turns the card into a free
+ * answer and Enter submits it, so a delivered message would become the answer to a question nobody read. The person
+ * answers it in the pane (the user's decision on #2592); it is never keyed. Bottom-anchored like
+ * kiroMcpInputRequestActive: the header is the row right under the nearest divider above the key hints' divider.
+ */
+export declare function kiroQuestionCardActive(pane: string): boolean;
+/**
+ * #2675: the live Question card (see kiroQuestionCardActive), read for a person to answer from the chat: the question,
+ * the numbered options (`(recommended)` and the description row under one), the typed-answer row, and where the `❯`
+ * is (tui.js `A0`; tests/fixtures/kiro-question-2592). On a sub-options page the rows are the `[✓]` boxes; while an
+ * answer is being typed the last row is `❯ <text>`. A row the shapes above do not account for is a wrapped title (the
+ * card's own indent) or description (deeper), joined to the row it continues; one before any option belongs to the
+ * question. Null when the card is not live, or when it is in a shape this reader does not know.
+ */
+export declare function readKiroQuestionCard(pane: string): RemoteQuestionCard | null;
+/**
+ * #2675: the live MCP `Input requested` card (see kiroMcpInputRequestActive), read for the chat: the server, the body
+ * as painted, with the `URL:` row masked (a sign-in link stays in the pane), its action rows, and the `❯` row. Its
+ * identity is the server, the mode, the message's first row and the actions: moving or filling in a field keeps it.
+ */
+export declare function readKiroMcpInputCard(pane: string): RemoteInputCard | null;
 /**
  * Kiro's service-unavailable path opens the same picker as `/model`, but only
  * the former needs incident escalation. The runtime scanner and delivery gate
@@ -116,6 +155,15 @@ export declare const KIRO_CLASSIC_NUDGE_V3: KiroLaunchPromptSpec;
  * flag; the quoted names in its description are the fallback.
  */
 export declare function parseKiroAgentEngines(help: string): string[] | null;
+/**
+ * #2598 (D1): kiro-cli-chat skips its self-update when this is set (2.30.0 and 2.34.0 both read it). AgEnD pins the
+ * kiro version it has audited; an in-place update can swap the engine a running fleet depends on (3.0 drops legacy).
+ * Every chat AgEnD starts carries it: the instance launch (a shell prefix) and the probes (their child env). The
+ * host-wide `app.disableAutoupdates` setting is the operator's half; this holds even where that was never set.
+ */
+export declare const KIRO_NO_AUTO_UPDATE = "KIRO_NO_AUTO_UPDATE";
+/** A kiro child's environment: the given one (default: ours) with self-update off. */
+export declare function kiroChildEnv(base?: NodeJS.ProcessEnv): NodeJS.ProcessEnv;
 /**
  * Probe once per binary generation. A version AgEnD has run (<= TESTED_MAX)
  * is answered from the table without a second CLI call; anything newer, or a
@@ -211,6 +259,8 @@ export declare class KiroBackend implements CliBackend {
     private activeTrustAll;
     /** Version-gate notice for the launch just built (consumeLaunchWarning). */
     private launchWarning;
+    /** #2648: what this launch's model came from, for a model error to be judged by (decideKiroModelError). */
+    private launchModels;
     /**
      * What this launch attempt resumes and as which agent (#906), resolved once per attempt in writeConfig — it claims
      * conversations and records fresh starts — and read by the buildCommand that follows it.
@@ -221,6 +271,8 @@ export declare class KiroBackend implements CliBackend {
     /** #1218: the last launch built in full (cleared when a build starts, set only when it returns). */
     private builtLaunch;
     private preparedV2Store;
+    /** #2648: the saved model of the v2 conversation this instance has recorded, read in prepareLaunch (off the loop). */
+    private preparedV2Model;
     private storePreparation;
     private storeKey;
     private readPreparedV2Store;
@@ -273,6 +325,18 @@ export declare class KiroBackend implements CliBackend {
     private agentSpec;
     /** A shared file AgEnD could not bring to the state isolation needs: said, never reported as isolated. */
     private noteShared;
+    /**
+     * #2648 steps 1 and 3: the model a resumed conversation is launched on instead of its saved one, or null to launch as
+     * before. Only for an instance with no model of its own. The conversation's current saved model decides, every
+     * launch: one kiro's cached list no longer has is switched to kiro's default; one it has — or, without a list, one
+     * other than the model that failed (a later /model choice, or the default kiro saved after a switch) — is launched
+     * as saved, even after an earlier switch (#2649 review). Only when the saved model cannot be read does a recorded
+     * switch (step 2's restart) still apply. Announced once per conversation; the record also keeps that dedupe.
+     */
+    private retiredModelFallback;
+    private saveModelRecords;
+    /** #2648 steps 2 and 4: what a model error on this launch should do (records it); null before any launch. */
+    onModelError(): KiroModelErrorVerdict | null;
     private addLaunchWarning;
     /**
      * The launch plan of one attempt (#906, design §2/§5): the engine the plan pins, and — when this kiro-cli has
@@ -319,6 +383,11 @@ export declare class KiroBackend implements CliBackend {
     getRuntimeDialogs(): RuntimeDialog[];
     getContextUsage(): number | null;
     logLaunch(): KiroLogLaunch | null;
+    /**
+     * #2598 B1: the store is the launch's engine's (v1 = the classic sqlite store, v2 = the TUI's session files), and the
+     * conversation is the one the launch resumed by id. A fresh or legacy-mode launch owns no id yet.
+     */
+    transcriptLaunch(): KiroTranscriptLaunch | null;
     getSessionId(): string | null;
     getQuitCommand(): string;
     getCompactCommand(): string;