@aragon-agent/cli 0.6.46 → 0.6.48

package/dist/ui/overlays/team-fanout-state.js

@@ -1,155 +0,0 @@
-/**
- * Settings > Team: the pure half of the page (subagent-fanout 3.4.2, extended by
- * team-command-forced-dispatch §3.9).
- *
- * ASCII ONLY - `src/ui/**` is inside `glyphs.test.ts::inScope`.
- *
- * THE PAGE WRITES FOUR KEYS AND CANNOT BE MADE TO WRITE A FIFTH (D-17 / R-P0-1).
- * `TeamFanoutPatch` is `Pick<TeamConfig, 'enabled' | 'maxSubagents' |
- * 'maxConcurrent' | 'overseer'>`, and `stepFanoutValue` returns
- * `Partial<TeamFanoutPatch>`: a width adjustment therefore CANNOT carry `model`
- * or `modelProfileId` into `draft.patch.team`. That matters because
- * `releasedSlots` reads those two keys as "the user re-decided the subagent
- * slot", so a page that returned the whole section would silently release the
- * model a session kit had just installed - and no test would notice, because
- * every value on screen would still be right.
- *
- * FOUR KEYS BECAUSE `enabled` MOVED HERE (team-command-forced-dispatch D-3): the
- * team switch used to be reachable only as `/team on|off`, which also wrote
- * `config.json`. The switch belongs on the same page as width, concurrency and
- * supervision - they are four faces of one decision - and `/team` is now the ACT
- * ("arm this session"), never a configuration write (I-4).
- *
- * EVERYTHING HERE IS A PURE FUNCTION over the draft. The page owns exactly one
- * piece of state (its cursor); values come from the reducer, which is the same
- * discipline the rest of this screen follows.
- */
-import { clampTeamConfig, HARD_MAX_SUBAGENTS } from '../../config/schema.js';
-function clampInt(value, min, max) {
-    return Math.max(min, Math.min(max, Math.floor(value)));
-}
-/**
- * The CLAMPED team section this draft would save (R-P0-2), for display only.
- *
- * THE CLAMP IS NOT COSMETIC. Without it a patch carrying only
- * `maxSubagents: 6` renders "6 per dispatch, 8 at once" on top of an 8-wide
- * baseline, while `mergePersistedConfig` clamps the same patch to 6/6 on the way
- * to disk - so the screen and the file disagree, and every arrow key makes the
- * user reconcile them by hand.
- */
-export function teamFanoutValues(draft) {
-    return clampTeamConfig({ ...draft.baseline.team, ...draft.patch.team });
-}
-/**
- * The PATCH FRAGMENT for one arrow press, clamped exactly like `clampTeamConfig`.
- *
- * `current` must be the value the screen actually shows (`teamFanoutValues`), so
- * a step always starts from a number the user can see.
- *
- * NO WRAPAROUND: a form control is not a ring, and `Left` at 1 jumping to 10
- * would be a way to widen a dispatch while trying to narrow it.
- *
- * EVERY MEMBER IS HANDLED EXPLICITLY AND THE TAIL IS `never` (P0-1). The old
- * body was three `if`s with the `maxSubagents` branch as the FALLTHROUGH, so
- * adding `'enabled'` to the union compiled cleanly and made the new `Team mode`
- * row adjust `Max subagents` instead - every number on screen self-consistent,
- * no test red, and the user's intent to switch the team OFF arrived as a wider
- * fan-out. The `never` assignment below turns that class of mistake into a
- * compile error, which is the only place it can be caught cheaply.
- */
-export function stepFanoutValue(current, field, delta) {
-    if (field === 'enabled') {
-        // Both arrows toggle: `Team mode` has two states, and a direction has no
-        // meaning beyond "the user pressed an arrow" (the `Supervisor` rule below).
-        return { enabled: !current.enabled };
-    }
-    if (field === 'overseer') {
-        return { overseer: !current.overseer };
-    }
-    if (field === 'maxConcurrent') {
-        const ceiling = Math.min(HARD_MAX_SUBAGENTS, current.maxSubagents);
-        return { maxConcurrent: clampInt(current.maxConcurrent + delta, 1, ceiling) };
-    }
-    if (field === 'maxSubagents') {
-        const next = clampInt(current.maxSubagents + delta, 1, HARD_MAX_SUBAGENTS);
-        // THE FOLLOW-DOWN IS WRITTEN INTO THE PATCH (R-P1-9), not just rendered: a
-        // narrower population cannot keep a wider pool, but a DISPLAY-only correction
-        // would snap back the moment the user widened again, so "the change I just
-        // made" would not stick - the exact complaint this design exists to answer.
-        return current.maxConcurrent > next
-            ? { maxSubagents: next, maxConcurrent: next }
-            : { maxSubagents: next };
-    }
-    // THE EXHAUSTIVE GUARD IS THE POINT (P0-1): a new member of `TeamFanoutField`
-    // must fail to COMPILE here, not silently fall through to `maxSubagents`.
-    //
-    // IT SITS AFTER EVERY BRANCH RETURNS, not before the last one. §3.9's snippet
-    // shows it above the `maxSubagents` branch, where TypeScript rejects the file
-    // outright (`'maxSubagents' is not assignable to 'never'`) - the intent
-    // survives, the position does not.
-    const _exhaustive = field;
-    return _exhaustive;
-}
-/**
- * The page's four rows, in cursor order.
- *
- * `Team mode` IS FIRST because it is the premise of the other three: with `task`
- * out of the tool list there is no width to configure and no supervisor to run,
- * and a page that listed the numbers first would invite the user to tune a
- * capability they had switched off.
- *
- * TWO HINTS CARRY A CONDITION THE DESIGN OWNS RATHER THAN DECORATION (R-1 / C-2):
- * the default pool is 8, which is 8 simultaneous streams against one API key, and
- * the honest mitigation for an HTTP 429 storm is "lower this number" - said HERE,
- * where the number is, not only in a risk table nobody reads.
- *
- * `teamRegistered === false` (a `--no-team` session) changes TWO things on the
- * `enabled` row and nothing else: `on (next launch)` because the tool array is
- * immutable (I-7), and a hint that says why. Absent means "not disclosed",
- * which every existing fixture relies on.
- */
-export function fanoutRows(team, teamRegistered) {
-    const blocked = teamRegistered === false && team.enabled;
-    return [
-        {
-            field: 'enabled',
-            label: 'Team mode',
-            value: blocked ? 'on (next launch)' : team.enabled ? 'on' : 'off',
-            hint: blocked
-                ? '--no-team session: the task tool cannot be added live'
-                : 'off: no task tool next launch; this session may lack it',
-        },
-        {
-            field: 'maxSubagents',
-            label: 'Max subagents',
-            value: String(team.maxSubagents),
-            hint: `children per dispatch; ${HARD_MAX_SUBAGENTS} is the hard ceiling`,
-        },
-        {
-            field: 'maxConcurrent',
-            label: 'Run at once',
-            value: String(team.maxConcurrent),
-            hint: 'provider limits: lower this if you see rate-limit errors',
-        },
-        {
-            field: 'overseer',
-            label: 'Supervisor',
-            value: team.overseer ? 'on' : 'off',
-            hint: 'checks stalled children; never kills them',
-        },
-    ];
-}
-/**
- * The one-line summary the settings root row prints for this page.
- *
- * `off - no subagents` rather than the numbers, because with the capability off
- * the numbers describe nothing the user can spend. This replaced
- * `fanoutSummary()` outright instead of living beside it: two summary functions
- * over one page is two authorities for one line, and the root row would sooner or
- * later disagree with the page it summarises.
- */
-export function teamSummary(team) {
-    if (!team.enabled)
-        return 'off - no subagents';
-    return `${team.maxSubagents} per dispatch, ${team.maxConcurrent} at once`;
-}

package/dist/ui/overlays/use-model-probe.d.ts

@@ -1,30 +0,0 @@
-/**
- * The probe task hook (model-profile-connection-test §6.2).
- *
- * IT LIVES IN `SettingsScreen`, ONCE, AND NOWHERE ELSE. The editor unmounts whenever
- * the page changes (`SettingsScreen` renders it only for `page === 'editor'`), so a
- * hook inside the editor would abort its own discovery the moment `Discover models`
- * switched to the list page - the feature cancelling itself.
- *
- * TWO SLOTS, ONE IN FLIGHT. A test verdict and a discovered list answer different
- * questions, so they are stored separately: opening the list must not erase a verdict
- * the user still wants to read when they press Esc back (AC-27). Starting either task
- * aborts whatever is running - one request at a time.
- *
- * `test()` AND `discover()` NEVER REJECT. The only callers are Ink input handlers,
- * which have nowhere to await a `catch`; the hook folds every exception into an
- * `unknown` failure so no frame can be left on `testing` forever.
- *
- * ASCII ONLY (`ui/` is inside `glyphs.test.ts::inScope`).
- */
-import type { ModelProbe, ProbeTarget } from '../../agent/model-probe.js';
-import type { ProbeDiscoveryPhase, ProbeTestPhase } from './model-probe-view.js';
-export interface ModelProbeTasks {
-    test: ProbeTestPhase;
-    discovery: ProbeDiscoveryPhase;
-    busy: boolean;
-    startTest(target: ProbeTarget): void;
-    startDiscovery(target: ProbeTarget): void;
-    cancel(): void;
-}
-export declare function useModelProbe(probe?: ModelProbe): ModelProbeTasks;

package/dist/ui/overlays/use-model-probe.js

@@ -1,109 +0,0 @@
-/**
- * The probe task hook (model-profile-connection-test §6.2).
- *
- * IT LIVES IN `SettingsScreen`, ONCE, AND NOWHERE ELSE. The editor unmounts whenever
- * the page changes (`SettingsScreen` renders it only for `page === 'editor'`), so a
- * hook inside the editor would abort its own discovery the moment `Discover models`
- * switched to the list page - the feature cancelling itself.
- *
- * TWO SLOTS, ONE IN FLIGHT. A test verdict and a discovered list answer different
- * questions, so they are stored separately: opening the list must not erase a verdict
- * the user still wants to read when they press Esc back (AC-27). Starting either task
- * aborts whatever is running - one request at a time.
- *
- * `test()` AND `discover()` NEVER REJECT. The only callers are Ink input handlers,
- * which have nowhere to await a `catch`; the hook folds every exception into an
- * `unknown` failure so no frame can be left on `testing` forever.
- *
- * ASCII ONLY (`ui/` is inside `glyphs.test.ts::inScope`).
- */
-import { useCallback, useEffect, useRef, useState } from 'react';
-const TEST_FAILED_DETAIL = 'The connection test could not run.';
-const DISCOVERY_FAILED_DETAIL = 'The model list could not be fetched.';
-function unknownTest(targetId) {
-    return { ok: false, targetId, latencyMs: 0, kind: 'unknown', detail: TEST_FAILED_DETAIL };
-}
-function unknownDiscovery(connectionId) {
-    return { ok: false, connectionId, kind: 'unknown', detail: DISCOVERY_FAILED_DETAIL,
-        models: [], truncated: false, total: 0 };
-}
-/** Run one probe, guaranteeing the promise settles and no rejection escapes. */
-function settle(work, onValue, onFailure) {
-    let pending;
-    try {
-        pending = work();
-    }
-    catch {
-        onFailure();
-        return;
-    }
-    void pending.then(onValue, onFailure);
-}
-export function useModelProbe(probe) {
-    const [test, setTest] = useState({ phase: 'idle' });
-    const [discovery, setDiscovery] = useState({ phase: 'idle' });
-    const controller = useRef(null);
-    const inFlight = useRef(null);
-    const abortCurrent = useCallback(() => {
-        controller.current?.abort();
-        controller.current = null;
-        inFlight.current = null;
-    }, []);
-    useEffect(() => abortCurrent, [abortCurrent]);
-    const begin = useCallback((kind) => {
-        abortCurrent();
-        const next = new AbortController();
-        controller.current = next;
-        inFlight.current = kind;
-        return next;
-    }, [abortCurrent]);
-    /**
-     * Land one run's result and drop the in-flight refs with it.
-     *
-     * Clearing them here is what keeps `cancel()` honest: it is the ONLY caller of
-     * `abortCurrent`, and an Escape on a settled slot (a frame where `busy` is stale)
-     * must not erase a verdict the user is still reading.
-     */
-    const finish = useCallback((run, commit) => {
-        if (run.signal.aborted)
-            return;
-        controller.current = null;
-        inFlight.current = null;
-        commit();
-    }, []);
-    const startTest = useCallback((target) => {
-        if (!probe)
-            return;
-        const run = begin('test');
-        const targetId = probe.targetFingerprint(target);
-        setTest({ phase: 'testing', targetId });
-        settle(() => probe.test({ ...target, signal: run.signal }), (outcome) => {
-            finish(run, () => setTest({ phase: 'tested', outcome }));
-        }, () => {
-            finish(run, () => setTest({ phase: 'tested', outcome: unknownTest(targetId) }));
-        });
-    }, [probe, begin, finish]);
-    const startDiscovery = useCallback((target) => {
-        if (!probe)
-            return;
-        const run = begin('discovery');
-        const connectionId = probe.connectionFingerprint(target);
-        setDiscovery({ phase: 'discovering', connectionId });
-        settle(() => probe.discover({ ...target, signal: run.signal }), (outcome) => {
-            finish(run, () => setDiscovery({ phase: 'discovered', outcome }));
-        }, () => {
-            finish(run, () => setDiscovery({ phase: 'discovered',
-                outcome: unknownDiscovery(connectionId) }));
-        });
-    }, [probe, begin, finish]);
-    const cancel = useCallback(() => {
-        const kind = inFlight.current;
-        abortCurrent();
-        if (kind === 'test')
-            setTest({ phase: 'idle' });
-        if (kind === 'discovery')
-            setDiscovery({ phase: 'idle' });
-    }, [abortCurrent]);
-    const busy = test.phase === 'testing' || discovery.phase === 'discovering';
-    return { test, discovery, busy, startTest, startDiscovery, cancel };
-}

package/dist/ui/palettes.d.ts

@@ -1,112 +0,0 @@
-/**
- * Palettes (spec §4.5) — the raw hex data behind `getTheme()`, split out of
- * `theme.ts` so the color decisions live in one readable place and can be
- * contrast-tested without pulling in the degradation machinery.
- *
- * `WARM` is the new default. The old Tokyo-Night-derived palette survives under
- * its accurate name `COOL` and stays reachable via `--theme cool`, so nobody's
- * screen changes without them being able to change it back (R-4).
- *
- * Theme names describe COLOR TEMPERATURE on purpose. Naming a theme after
- * another company's product would imply an affiliation or an asset licence that
- * does not exist; `warm` / `cool` are accurate and carry no such claim.
- */
-import type { ThemeName } from '../config/schema.js';
-export interface Palette {
-    primary: string;
-    accent: string;
-    user: string;
-    assistant: string;
-    thinking: string;
-    toolPending: string;
-    toolRunning: string;
-    toolDone: string;
-    toolError: string;
-    noticeInfo: string;
-    noticeWarn: string;
-    noticeError: string;
-    muted: string;
-    border: string;
-    code: string;
-    focusBorder: string;
-    idleBorder: string;
-    hintFg: string;
-    logoShadow: string;
-    /**
-     * Drag-selection highlight (tui-selection-and-scroll-follow §4.4.4).
-     *
-     * A PAIR, not a background alone: the selected run has its inner SGR stripped
-     * before it is repainted, so whatever foreground the row had is gone by the
-     * time the highlight is applied and a background on its own would leave the
-     * text at the terminal's default colour over an arbitrary hue. The two are
-     * contrast-pinned against EACH OTHER in `palettes.test.ts` — the surface a
-     * selected glyph sits on is `selectionBg`, not `DARK_SURFACE`.
-     *
-     * Below ansi-256 these never reach the terminal at all: `highlight.ts` emits
-     * plain reverse video there, because `getTheme` has degraded them to chalk
-     * colour NAMES by then and a name is not an escape sequence.
-     */
-    selectionBg: string;
-    selectionFg: string;
-    gradient: [string, string, string];
-    gauge: {
-        track: string;
-        low: string;
-        mid: string;
-        high: string;
-    };
-    diff: {
-        add: string;
-        remove: string;
-        meta: string;
-        context: string;
-    };
-    toast: {
-        info: string;
-        warn: string;
-        error: string;
-        success: string;
-    };
-    chip: {
-        fg: string;
-        bg: string;
-    };
-    /**
-     * The GOVERN / PLAN+GOVERN posture badge, the legion panel title and the status chip
-     * (governance-mode section 10.7).
-     *
-     * A hue of its own, pinned by `palettes.test.ts`: >= 4.5:1 against THIS palette's own
-     * surface and >= 30 degrees away from the six semantic hues it must never be confused
-     * with (`primary`, `accent`, `user`, `toolDone`, `noticeWarn`, `noticeError`) - the
-     * last four because governance score gains and losses are drawn in `toolDone` /
-     * `noticeError` right beside it. The numbers below are the measured starting points.
-     */
-    governAccent: string;
-}
-/**
- * The reference dark background these palettes are contrast-checked against.
- * `palettes.test.ts` (A-7) pins `assistant` / `muted` / `hintFg` at WCAG AA
- * (>= 4.5:1) here so a later "just nudging the hue" cannot quietly make body
- * text unreadable.
- */
-export declare const DARK_SURFACE = "#1c1917";
-/**
- * The reference background of the `LIGHT` palette. `LIGHT` text is dark-on-light, so
- * contrast-checking it against `DARK_SURFACE` would pass a pair that is unreadable in
- * the only place it is ever used (the same trap `selectionBg` documents).
- */
-export declare const LIGHT_SURFACE = "#ffffff";
-/** Terracotta + amber over warm neutrals — the v0.4.0 default. */
-export declare const WARM: Palette;
-/** The v0.3.0 palette, renamed. Reachable via `--theme cool` / `theme: "dark"`. */
-export declare const COOL: Palette;
-export declare const LIGHT: Palette;
-/**
- * Resolve a theme name to its palette.
- *
- * `auto` never guesses light: terminals cannot reliably report their background
- * colour, and guessing wrong makes the app unreadable. `dark` is accepted here
- * as well as in `clampTheme` because a persisted config written by v0.3.0 can
- * still be sitting on disk when this runs.
- */
-export declare function resolvePalette(name: ThemeName | 'dark'): Palette;

package/dist/ui/palettes.js

@@ -1,130 +0,0 @@
-/**
- * Palettes (spec §4.5) — the raw hex data behind `getTheme()`, split out of
- * `theme.ts` so the color decisions live in one readable place and can be
- * contrast-tested without pulling in the degradation machinery.
- *
- * `WARM` is the new default. The old Tokyo-Night-derived palette survives under
- * its accurate name `COOL` and stays reachable via `--theme cool`, so nobody's
- * screen changes without them being able to change it back (R-4).
- *
- * Theme names describe COLOR TEMPERATURE on purpose. Naming a theme after
- * another company's product would imply an affiliation or an asset licence that
- * does not exist; `warm` / `cool` are accurate and carry no such claim.
- */
-/**
- * The reference dark background these palettes are contrast-checked against.
- * `palettes.test.ts` (A-7) pins `assistant` / `muted` / `hintFg` at WCAG AA
- * (>= 4.5:1) here so a later "just nudging the hue" cannot quietly make body
- * text unreadable.
- */
-export const DARK_SURFACE = '#1c1917';
-/**
- * The reference background of the `LIGHT` palette. `LIGHT` text is dark-on-light, so
- * contrast-checking it against `DARK_SURFACE` would pass a pair that is unreadable in
- * the only place it is ever used (the same trap `selectionBg` documents).
- */
-export const LIGHT_SURFACE = '#ffffff';
-/** Terracotta + amber over warm neutrals — the v0.4.0 default. */
-export const WARM = {
-    primary: '#d08c60',
-    accent: '#c9a227',
-    user: '#7fb08a',
-    assistant: '#e6ddd1',
-    thinking: '#a2968a',
-    toolPending: '#8a7f74',
-    toolRunning: '#c9a227',
-    toolDone: '#7fb08a',
-    toolError: '#cf6b5c',
-    noticeInfo: '#d08c60',
-    noticeWarn: '#c9a227',
-    noticeError: '#cf6b5c',
-    muted: '#a2968a',
-    border: '#4a423b',
-    code: '#c9a97a',
-    focusBorder: '#d08c60',
-    idleBorder: '#4a423b',
-    hintFg: '#9c9086',
-    logoShadow: '#4a423b',
-    selectionBg: '#e0b088',
-    selectionFg: '#1c1917',
-    gradient: ['#d08c60', '#c9a227', '#b0916a'],
-    gauge: { track: '#4a423b', low: '#7fb08a', mid: '#c9a227', high: '#cf6b5c' },
-    diff: { add: '#7fb08a', remove: '#cf6b5c', meta: '#d08c60', context: '#a2968a' },
-    toast: { info: '#d08c60', warn: '#c9a227', error: '#cf6b5c', success: '#7fb08a' },
-    chip: { fg: '#1c1917', bg: '#d08c60' },
-    governAccent: '#B79CED',
-};
-/** The v0.3.0 palette, renamed. Reachable via `--theme cool` / `theme: "dark"`. */
-export const COOL = {
-    primary: '#7aa2f7',
-    accent: '#bb9af7',
-    user: '#7dcfff',
-    assistant: '#c0caf5',
-    thinking: '#7a86b8',
-    toolPending: '#565f89',
-    toolRunning: '#e0af68',
-    toolDone: '#9ece6a',
-    toolError: '#f7768e',
-    noticeInfo: '#7aa2f7',
-    noticeWarn: '#e0af68',
-    noticeError: '#f7768e',
-    muted: '#565f89',
-    border: '#3b4261',
-    code: '#9ece6a',
-    focusBorder: '#7aa2f7',
-    idleBorder: '#3b4261',
-    hintFg: '#565f89',
-    logoShadow: '#3b4261',
-    selectionBg: '#7aa2f7',
-    selectionFg: '#1a1b26',
-    gradient: ['#7aa2f7', '#bb9af7', '#7dcfff'],
-    gauge: { track: '#3b4261', low: '#9ece6a', mid: '#e0af68', high: '#f7768e' },
-    diff: { add: '#9ece6a', remove: '#f7768e', meta: '#7aa2f7', context: '#7a86b8' },
-    toast: { info: '#7aa2f7', warn: '#e0af68', error: '#f7768e', success: '#9ece6a' },
-    chip: { fg: '#1a1b26', bg: '#7aa2f7' },
-    governAccent: '#73DACA',
-};
-export const LIGHT = {
-    primary: '#2959aa',
-    accent: '#8c4bc9',
-    user: '#0f7490',
-    assistant: '#1f2430',
-    thinking: '#6b7280',
-    toolPending: '#9aa0ab',
-    toolRunning: '#b5730f',
-    toolDone: '#2e7d32',
-    toolError: '#c62828',
-    noticeInfo: '#2959aa',
-    noticeWarn: '#b5730f',
-    noticeError: '#c62828',
-    muted: '#6b7280',
-    border: '#c8cdd6',
-    code: '#3f7f2f',
-    focusBorder: '#2959aa',
-    idleBorder: '#c8cdd6',
-    hintFg: '#6b7280',
-    logoShadow: '#c8cdd6',
-    selectionBg: '#2959aa',
-    selectionFg: '#ffffff',
-    gradient: ['#2959aa', '#8c4bc9', '#0f7490'],
-    gauge: { track: '#c8cdd6', low: '#2e7d32', mid: '#b5730f', high: '#c62828' },
-    diff: { add: '#2e7d32', remove: '#c62828', meta: '#2959aa', context: '#6b7280' },
-    toast: { info: '#2959aa', warn: '#b5730f', error: '#c62828', success: '#2e7d32' },
-    chip: { fg: '#ffffff', bg: '#2959aa' },
-    governAccent: '#A8327A',
-};
-/**
- * Resolve a theme name to its palette.
- *
- * `auto` never guesses light: terminals cannot reliably report their background
- * colour, and guessing wrong makes the app unreadable. `dark` is accepted here
- * as well as in `clampTheme` because a persisted config written by v0.3.0 can
- * still be sitting on disk when this runs.
- */
-export function resolvePalette(name) {
-    if (name === 'light')
-        return LIGHT;
-    if (name === 'cool' || name === 'dark')
-        return COOL;
-    return WARM;
-}

package/dist/ui/paste-frames.d.ts

@@ -1,91 +0,0 @@
-/**
- * Reading paste frames back out of an Ink `input` string
- * (tui-paste-handling section 5.4) -- pure.
- *
- * The stdin filter writes `PASTE_OPEN + payload + PASTE_CLOSE` inline, in stream
- * order (I-5). This module is the only place that takes those markers apart.
- */
-export interface FrameTextSegment {
-    readonly kind: 'text';
-    readonly text: string;
-}
-export interface FramePasteSegment {
-    readonly kind: 'paste';
-    readonly text: string;
-}
-/**
- * A run of one `input` string.
- *
- * NO `id` HERE. The paste id is allocated by `PromptInput` while it builds the
- * reducer's action, never by this function and never by the reducer (P1-5), so
- * the split stays a pure function of its argument and `paste-frames.test.ts` can
- * assert on its output.
- */
-export type FrameSegment = FrameTextSegment | FramePasteSegment;
-/**
- * Remove every C0 byte, DEL and C1 byte from text that arrived OUTSIDE a frame
- * (I-14). NO CR -> LF conversion, and that omission is the point.
- *
- * WHY THIS IS NOT OPTIONAL. Ink drains its whole buffer in one size-less
- * `read()` (`App.js:135`), so the `input` string carrying a frame can also carry
- * the keystroke bytes that arrived beside it -- most often the `\r` of a user who
- * pastes and immediately presses Enter, since Ink's 32 ms render throttle and a
- * large transcript's Yoga pass both outlast the filter's 15 ms burst window.
- * Splicing that run in verbatim puts a raw CR back into the draft and re-opens
- * the corruption this whole feature exists to remove.
- *
- * Note what it does NOT do. It does not turn a coalesced `\r` into a newline and
- * it does not submit: a keystroke that merged with a frame has already lost its
- * identity as a key (`parseKeypress` saw the concatenation, not the key), so the
- * only two honest options are "insert something wrong" and "drop it". Dropping is
- * recoverable and benign -- the user presses Enter again -- while inserting a
- * control byte is not. Printable characters survive untouched.
- */
-export declare function sanitiseTyped(text: string): string;
-/**
- * Split an `input` string into ordered text runs and paste runs.
- *
- * Text runs are returned already through `sanitiseTyped` (I-14); paste runs are
- * returned through `sanitisePaste`, which keeps TAB and `\n` because they are
- * content inside a payload.
- *
- * RE-SANITISING THE PAYLOAD IS DEFENCE IN DEPTH, NOT A SECOND OPINION. The
- * filter already ran `sanitisePaste` and it is idempotent, so the normal path is
- * byte-identical. What it buys is that G2 ("no pasted byte is ever executed as a
- * terminal control") becomes a property of the COMPOSER rather than a property
- * of whoever produced the frame -- which matters for the branch below, where an
- * unmatched `PASTE_OPEN` turns arbitrary trailing bytes into a paste segment.
- *
- * An unmatched `PASTE_OPEN` -- impossible from our own filter, but cheap to
- * survive -- yields its remainder as a paste segment rather than leaking NULs.
- */
-export declare function splitPasteFrames(input: string): FrameSegment[];
-/** True when this `input` carries at least one frame -- the branch guard. */
-export declare function hasPasteFrame(input: string): boolean;
-/**
- * Turn a possibly-framed `input` into plain text for a consumer that has no
- * paste model of its own: unwrap the frames, keep the payload, drop the markers,
- * and run BOTH halves through `sanitiseTyped`.
- *
- * ANY `useInput` CONSUMER THAT APPENDS `input` TO A STRING MUST CALL THIS (I-12),
- * and the list is pinned by a source scan rather than by review discipline
- * because the failure is invisible: NUL renders as nothing.
- *
- * `useInput` is a BROADCAST -- `use-input.js` re-emits every chunk to every
- * mounted handler -- so `SettingsScreen` and `QuestionOverlay` see the frame the
- * composer was sent. An API key is ~100 characters with no line break, which trips
- * Tier 2's burst rule and gets framed; nothing downstream removes the NULs
- * (`String.prototype.trim()` does not treat U+0000 as whitespace), the field is
- * rendered through `maskDot` so the damage is invisible, and the value is handed
- * to `registerSecret()` and `controller.setApiKey()`. The user is told the
- * settings were saved and every request afterwards fails to authenticate with
- * nothing on screen to explain it.
- *
- * This is strictly better than v0.6.3 for both consumers: a pasted key carrying a
- * stray CR or an ANSI sequence is now cleaned rather than stored raw. The
- * unframed branch strips escape SEQUENCES before the control sweep, because
- * deleting only the introducer left `[0m` in the stored value -- and in a
- * settings field that residue is invisible behind `maskDot` while the value
- * handed to `registerSecret()` is silently wrong.
- */
-export declare function stripPasteFrames(input: string): string;