@aragon-agent/cli 0.6.47 → 0.6.48

package/dist/ui/stdout-frame-writer.js

@@ -1,155 +0,0 @@
-/**
- * Stdout frame writer — the `Proxy` that binds `frame-differ.ts` to a real
- * stream (tui-input-flicker-fix §3.2 / §5.5).
- *
- * Ink offers no hook for "how to write a frame": `Ink#log` is constructed
- * internally and `log-update` is a private module. It DOES accept a `stdout` in
- * `render()`'s options, so the whole interposition is one `Proxy` whose only
- * trapped behaviour is `write` — everything else is the real stream.
- *
- * THREE THINGS IN HERE ARE LOAD-BEARING:
- *
- *  - The `get` trap MUST bind non-`write` function members to the REAL stream.
- *    Without the bind, `stdout.on('resize', …)` executes with `this === proxy`,
- *    and `useTerminalSize` registers and removes its listener against a
- *    different `_events` object than the one Node emits on — the frame stops
- *    resizing and nothing reports why.
- *  - The UNTYPED BOUNDARY LIVES HERE, not in the differ (P1-4). A `Uint8Array`
- *    chunk, and any `write` whose `encoding` is present and is not UTF-8, is
- *    passed straight through after `invalidate()`: in both cases the bytes on
- *    the wire are not the string a differ could reason about, and diffing one
- *    encoding while writing another is the kind of bug that only shows up on
- *    someone else's machine.
- *  - The `'resize'` SUBSCRIPTION (I-8 / P0-2). Ink renders SYNCHRONOUSLY from its
- *    own `'resize'` handler while the frame's height is still the pre-resize one
- *    — `useTerminalSize` debounces by 50 ms — so the line count is unchanged
- *    across that window and the differ's line-count guard cannot see the resize.
- *    Meanwhile the emulator has re-flowed the alternate screen, so every row the
- *    differ believes unchanged is a row it will not repaint, for the rest of the
- *    drag. It goes on the REAL stream, not the `Proxy`, and `dispose()` removes
- *    it.
- */
-/** The only encodings for which the chunk string IS the bytes on the wire. */
-function isUtf8Encoding(encoding) {
-    const e = encoding.toLowerCase();
-    return e === 'utf8' || e === 'utf-8';
-}
-/**
- * DEC private mode 25 set/reset — hide / show the cursor.
- *
- * Ink 5.2.1's own root `<App>` writes these two EXACT strings through the
- * render stdout on mount and unmount (`ink/build/components/App.js` →
- * `cli-cursor`), which is this proxy, not the process stream. Cursor
- * VISIBILITY changes no cell and moves no row, so the differ's
- * absolute-addressing cache survives them untouched — yet `transform` cannot
- * recognise them and answers `passThrough(true)`: counted, `onFirstFallback`
- * raised (the warning fired on EVERY launch), cache dropped for nothing. Worse,
- * in the real CLI the mount write arrives FIRST, so it also consumes the
- * session's one seed-write exemption (`firstChunk`, P1-1) and the seed frame
- * itself becomes the counted fallback.
- *
- * Absorbed here instead: straight to the real stream — no transform, no
- * `invalidate()`, no fallback count, no exemption consumed. The match is
- * exact on the whole chunk, so a future Ink that mixes the sequence into a
- * longer write simply misses and falls back to today's conservative handling;
- * a missed absorb costs one extra repaint, never a swallowed desync.
- */
-const CURSOR_HIDE = '\x1b[?25l';
-const CURSOR_SHOW = '\x1b[?25h';
-export function wrapStdoutForFrames(stdout, differ) {
-    const bound = new Map();
-    const writeReal = (chunk, encoding, cb) => {
-        if (encoding !== undefined)
-            return stdout.write(chunk, encoding, cb);
-        return stdout.write(chunk, cb);
-    };
-    /**
-     * All three Node overloads: `write(chunk)`, `write(chunk, cb)`,
-     * `write(chunk, encoding, cb)`.
-     */
-    const write = (chunk, encodingOrCb, maybeCb) => {
-        const encoding = typeof encodingOrCb === 'string' ? encodingOrCb : undefined;
-        const cb = typeof encodingOrCb === 'function'
-            ? encodingOrCb
-            : typeof maybeCb === 'function'
-                ? maybeCb
-                : undefined;
-        // Foreign by construction: Ink never writes Buffers, and a non-UTF-8
-        // encoding means the string is not the bytes (P1-4).
-        if (typeof chunk !== 'string' || (encoding !== undefined && !isUtf8Encoding(encoding))) {
-            differ.invalidate();
-            return writeReal(chunk, encoding, cb);
-        }
-        // Ink's own cursor-mode pair (see CURSOR_HIDE / CURSOR_SHOW above): not a
-        // frame and not a desync — the bytes reach the terminal untransformed,
-        // uncounted, and without touching the cache or the seed exemption.
-        if (chunk === CURSOR_HIDE || chunk === CURSOR_SHOW) {
-            return writeReal(chunk, encoding, cb);
-        }
-        const out = differ.transform(chunk);
-        if (out === null)
-            return writeReal(chunk, encoding, cb);
-        // Nothing to write, but the callback is still part of the contract — a
-        // skipped `cb` strands whatever was waiting on the drain.
-        if (out.length === 0) {
-            cb?.();
-            return true;
-        }
-        return writeReal(out, encoding, cb);
-    };
-    // Optional differ hooks keep the full-screen path byte-identical: a differ that
-    // does not implement them is invalidated exactly as before.
-    const onResize = () => {
-        if (differ.onResize)
-            differ.onResize();
-        else
-            differ.invalidate();
-    };
-    stdout.on('resize', onResize);
-    let disposed = false;
-    const proxy = new Proxy(stdout, {
-        get(target, prop) {
-            if (prop === 'write')
-                return write;
-            const value = Reflect.get(target, prop, target);
-            if (typeof value !== 'function')
-                return value;
-            // Cached so repeated property access does not allocate a new bound
-            // function on a hot path (K-9).
-            let fn = bound.get(prop);
-            if (fn === undefined) {
-                fn = value.bind(target);
-                bound.set(prop, fn);
-            }
-            return fn;
-        },
-    });
-    return {
-        stdout: proxy,
-        stats: () => differ.stats(),
-        repaint() {
-            if (disposed)
-                return false;
-            const payload = differ.repaint();
-            if (payload.length === 0)
-                return false;
-            writeReal(payload);
-            return true;
-        },
-        writeForeign(text) {
-            if (differ.cursorNeutralWrite)
-                differ.cursorNeutralWrite();
-            else
-                differ.invalidate();
-            if (disposed || text.length === 0)
-                return;
-            writeReal(text);
-        },
-        dispose() {
-            if (disposed)
-                return;
-            disposed = true;
-            stdout.off('resize', onResize);
-        },
-    };
-}

package/dist/ui/team-status.d.ts

@@ -1,166 +0,0 @@
-/**
- * Team status — the ONE authority that answers "what state is this child in, and
- * how is that drawn / counted / timed" (tui-subagent-double-roster A-1).
- *
- * WHY THIS FILE EXISTS. The phase -> glyph / colour / count question used to be
- * answered by nine copies in seven files, and they disagreed. The transcript card
- * asked `isOk(run) ? toolDone : toolError`, so six of the eight phases - every
- * child that was still working - were painted with the FAILURE glyph, and an
- * aborted child was counted as a failed one forever. That is not a palette
- * mistake, it is a judgement implemented in the wrong number of places.
- *
- * THE VOCABULARY IS THE DOMAIN'S (analysis A-1' item 3). `ChildStatus` reuses
- * `SubagentPhase`'s own words - `queued` / `running` / `done` / `failed` /
- * `aborted` - and never invents a second dictionary (`pending` was proposed and
- * rejected: `SubagentPhase` does not have it, and two words for one state is how
- * the tenth copy gets written).
- *
- * FIVE STATES, NOT FOUR (A-1' item 2). `aborted` is NOT a failure. The runtime
- * distinguishes them on purpose (`Runtime.settlePhase`: aborted first, then the
- * timeout, then the error), and a user pressing Esc must not read their own
- * action back as "3 failed". So `aborted` takes `glyphs.warn` and
- * `theme.noticeWarn`, which collide with neither the done tick nor the failed
- * cross in either glyph tier.
- *
- * ASCII ONLY: `src/ui/**` is inside `glyphs.test.ts`'s static scan, so every
- * symbol here is injected through `pickGlyphs(caps)`.
- */
-import type { Entry } from '../agent/reducer.js';
-import type { SubagentRun } from '../team/types.js';
-import type { Glyphs } from './glyphs.js';
-import type { Theme } from './theme.js';
-/**
- * The five readings a child can have on screen. A TOTAL mapping of
- * `SubagentPhase`, which is why `childStatus` needs no guard clauses: `starting`,
- * `thinking`, `tool` and `waiting` are all "this child is working right now", and
- * the per-row activity column is what tells them apart.
- */
-export type ChildStatus = 'queued' | 'running' | 'done' | 'failed' | 'aborted';
-/**
- * The status of one child.
- *
- * A LOOKUP TABLE RATHER THAN A SWITCH, because the mapping is the whole content
- * of this function: a `Record` keyed by the phase union is exhaustive at compile
- * time (a new phase is a missing-key error) and cannot drift from the type.
- */
-export declare function childStatus(run: SubagentRun): ChildStatus;
-/** Per-status totals of a roster. `total` is the roster size, not the sum. */
-export interface RosterCounts {
-    queued: number;
-    running: number;
-    done: number;
-    failed: number;
-    aborted: number;
-    total: number;
-}
-/**
- * Count a roster once, by status.
- *
- * THE HEADER, THE CARD HEADLINE AND THE STATUS CHIP ALL READ THIS. Before it
- * existed the header filtered `phase !== 'queued' && ...` for "running" and the
- * card subtracted `runs.length - isOk(runs)`, so the same dispatch reported
- * `0 running` above two rows reading `queued` and `1 failed` for a child that had
- * never started.
- */
-export declare function rosterCounts(runs: readonly SubagentRun[]): RosterCounts;
-/** True while the child is doing something - the only state that animates. */
-export declare function isRunningStatus(status: ChildStatus): boolean;
-/** True once the child's outcome is final, whatever it is. */
-export declare function isSettledStatus(status: ChildStatus): boolean;
-/**
- * The static marker for a status.
- *
- * `running` gets `spinnerStill` because the animated `<Spinner>` is the caller's
- * job: it needs `reducedMotion` and `caps.unicode`, and a component that owns its
- * own `ink-spinner` is what `spinner-census.test.ts` counts. The caller swaps this
- * glyph for the spinner when it may animate.
- */
-export declare function statusGlyph(status: ChildStatus, glyphs: Glyphs): string;
-/**
- * The widest marker this terminal's tier can produce (1 in Unicode, 4 in ASCII).
- *
- * EXPORTED (tui-subagent-panel §4.2.1): the panel row's geometry has to know how
- * many columns the marker cell spends before it can divide the rest, and the cell
- * width is a property of the TIER rather than of a status. `statusMarkerCell`
- * keeps using it, so the padder and the measurer can never disagree.
- */
-export declare function statusMarkerWidth(glyphs: Glyphs): number;
-/**
- * The marker padded to the tier's widest one, for the leading cell of a row.
- *
- * THE PADDING IS NOT COSMETIC (A-1'a): the ASCII tier spells `[ok]` (4), `[x]` (3)
- * and `!` (1), so an unpadded marker cell starts every label at a different
- * column and the roster stops reading as a table. `TodoPanel` pads its marker cell
- * for the same reason. The Unicode tier's markers are all one cell wide, so the
- * padding is a no-op there.
- */
-export declare function statusMarkerCell(status: ChildStatus, glyphs: Glyphs): string;
-/**
- * The colour of a status. One reading for the roster row, the card row and the
- * card's rail marker.
- *
- * `aborted` deliberately does NOT share `toolError` with `failed`: an abort is the
- * user's own Esc, and the analysis found that painting it red made a cancelled
- * dispatch permanently unreadable in the history.
- */
-export declare function statusColor(status: ChildStatus, theme: Theme): string | undefined;
-/**
- * How long this child has been (or was) working, in ms.
- *
- * `endedAt ?? now`, NOT `endedAt ?? 0`. The transcript card used the latter, which
- * made every RUNNING child read `0ms` while the roster beside it read `1m05s` for
- * the same child - the pair of contradictory readouts the reporter screenshotted.
- */
-export declare function childElapsedMs(run: SubagentRun, now: number): number;
-/**
- * The roster header's count section, e.g. `2 running · 0 done · 1 queued`.
- *
- * `queued` IS COUNTED (the old `isRunning` excluded it, so a fresh dispatch
- * announced `0 running · 0 done` above five rows that each said `queued`), and a
- * non-zero bucket is always named even when nothing is running - a roster whose
- * children are all `aborted` must say so rather than `0 running · 0 done`.
- *
- * WIDTH LADDER: narrow terminals drop the least urgent clause first, in the order
- * `done`, `aborted`, `failed`, `queued`; `running` is never dropped. The order is
- * a product decision, not a detail: while a dispatch is live, what is happening
- * now outranks what has already finished, and the per-row activity column carries
- * the finished children's own facts anyway.
- */
-export declare function rosterHeadline(counts: RosterCounts, glyphs: Glyphs, cols: number): string;
-/**
- * The settled card's outcome buckets, e.g. `2 ok, 1 aborted, 1 failed`.
- *
- * `ok` is always shown (it is the denominator a reader compares against) and a
- * zero bucket is omitted, so a clean dispatch still reads `3 ok` and a failed one
- * no longer claims that a cancelled child failed.
- */
-export declare function outcomePhrase(counts: RosterCounts): string;
-/**
- * Whether this entry is the transcript card of a dispatch that is STILL RUNNING,
- * i.e. the second live surface the reporter saw beside the roster.
- *
- * ONE PREDICATE, FOUR CONSUMERS (analysis A-2'): the transcript's `case 'team'`
- * and `estimateEntryRows` (so the virtual window and the frame agree), the tail
- * window and `LiveTail` (so the pump's print plan and the box agree), and the
- * `Ctrl+O` finder plus `reprintExpanded` (so a keypress cannot print a stale
- * snapshot of a card that is still being rewritten). `state.entries` is NEVER
- * filtered: the entry's lifecycle and `session/persist.ts`'s `interrupted`
- * normalisation depend on it staying there.
- */
-export declare function isLiveTeamCard(entry: Entry): boolean;
-/**
- * The MOST RECENT dispatch card in the transcript, live or settled.
- *
- * ONE PREDICATE, TWO CONSUMERS (tui-subagent-panel §6.4): the `/agents` command
- * and `App`'s `Ctrl+B` branch both have to answer "is there anything to show?"
- * before opening the board, and the board itself falls back to this entry when a
- * dispatch has already ended and `state.team` is `null` (`resolveBoardSource`).
- * Asking the question in one place is what stops the key and the command from
- * disagreeing about whether the board exists.
- *
- * Scans BACKWARDS and returns the first match: the newest card is the last one in
- * `entries`, and a dispatch-heavy session can hold hundreds of them.
- */
-export declare function lastTeamEntry(entries: readonly Entry[]): Extract<Entry, {
-    kind: 'team';
-}> | null;

package/dist/ui/team-status.js

@@ -1,252 +0,0 @@
-/**
- * Team status — the ONE authority that answers "what state is this child in, and
- * how is that drawn / counted / timed" (tui-subagent-double-roster A-1).
- *
- * WHY THIS FILE EXISTS. The phase -> glyph / colour / count question used to be
- * answered by nine copies in seven files, and they disagreed. The transcript card
- * asked `isOk(run) ? toolDone : toolError`, so six of the eight phases - every
- * child that was still working - were painted with the FAILURE glyph, and an
- * aborted child was counted as a failed one forever. That is not a palette
- * mistake, it is a judgement implemented in the wrong number of places.
- *
- * THE VOCABULARY IS THE DOMAIN'S (analysis A-1' item 3). `ChildStatus` reuses
- * `SubagentPhase`'s own words - `queued` / `running` / `done` / `failed` /
- * `aborted` - and never invents a second dictionary (`pending` was proposed and
- * rejected: `SubagentPhase` does not have it, and two words for one state is how
- * the tenth copy gets written).
- *
- * FIVE STATES, NOT FOUR (A-1' item 2). `aborted` is NOT a failure. The runtime
- * distinguishes them on purpose (`Runtime.settlePhase`: aborted first, then the
- * timeout, then the error), and a user pressing Esc must not read their own
- * action back as "3 failed". So `aborted` takes `glyphs.warn` and
- * `theme.noticeWarn`, which collide with neither the done tick nor the failed
- * cross in either glyph tier.
- *
- * ASCII ONLY: `src/ui/**` is inside `glyphs.test.ts`'s static scan, so every
- * symbol here is injected through `pickGlyphs(caps)`.
- */
-const STATUS_BY_PHASE = {
-    queued: 'queued',
-    starting: 'running',
-    thinking: 'running',
-    tool: 'running',
-    waiting: 'running',
-    done: 'done',
-    failed: 'failed',
-    aborted: 'aborted',
-};
-/**
- * The status of one child.
- *
- * A LOOKUP TABLE RATHER THAN A SWITCH, because the mapping is the whole content
- * of this function: a `Record` keyed by the phase union is exhaustive at compile
- * time (a new phase is a missing-key error) and cannot drift from the type.
- */
-export function childStatus(run) {
-    return STATUS_BY_PHASE[run.phase];
-}
-/**
- * Count a roster once, by status.
- *
- * THE HEADER, THE CARD HEADLINE AND THE STATUS CHIP ALL READ THIS. Before it
- * existed the header filtered `phase !== 'queued' && ...` for "running" and the
- * card subtracted `runs.length - isOk(runs)`, so the same dispatch reported
- * `0 running` above two rows reading `queued` and `1 failed` for a child that had
- * never started.
- */
-export function rosterCounts(runs) {
-    const counts = {
-        queued: 0, running: 0, done: 0, failed: 0, aborted: 0, total: runs.length,
-    };
-    for (const run of runs)
-        counts[childStatus(run)] += 1;
-    return counts;
-}
-/** True while the child is doing something - the only state that animates. */
-export function isRunningStatus(status) {
-    return status === 'running';
-}
-/** True once the child's outcome is final, whatever it is. */
-export function isSettledStatus(status) {
-    return status === 'done' || status === 'failed' || status === 'aborted';
-}
-/**
- * The static marker for a status.
- *
- * `running` gets `spinnerStill` because the animated `<Spinner>` is the caller's
- * job: it needs `reducedMotion` and `caps.unicode`, and a component that owns its
- * own `ink-spinner` is what `spinner-census.test.ts` counts. The caller swaps this
- * glyph for the spinner when it may animate.
- */
-export function statusGlyph(status, glyphs) {
-    switch (status) {
-        case 'queued':
-            return glyphs.toolPending;
-        case 'running':
-            return glyphs.spinnerStill;
-        case 'done':
-            return glyphs.toolDone;
-        case 'failed':
-            return glyphs.toolError;
-        case 'aborted':
-            return glyphs.warn;
-    }
-}
-/**
- * The widest marker this terminal's tier can produce (1 in Unicode, 4 in ASCII).
- *
- * EXPORTED (tui-subagent-panel §4.2.1): the panel row's geometry has to know how
- * many columns the marker cell spends before it can divide the rest, and the cell
- * width is a property of the TIER rather than of a status. `statusMarkerCell`
- * keeps using it, so the padder and the measurer can never disagree.
- */
-export function statusMarkerWidth(glyphs) {
-    return Math.max(glyphs.toolPending.length, glyphs.spinnerStill.length, glyphs.toolDone.length, glyphs.toolError.length, glyphs.warn.length);
-}
-/**
- * The marker padded to the tier's widest one, for the leading cell of a row.
- *
- * THE PADDING IS NOT COSMETIC (A-1'a): the ASCII tier spells `[ok]` (4), `[x]` (3)
- * and `!` (1), so an unpadded marker cell starts every label at a different
- * column and the roster stops reading as a table. `TodoPanel` pads its marker cell
- * for the same reason. The Unicode tier's markers are all one cell wide, so the
- * padding is a no-op there.
- */
-export function statusMarkerCell(status, glyphs) {
-    return statusGlyph(status, glyphs).padEnd(statusMarkerWidth(glyphs));
-}
-/**
- * The colour of a status. One reading for the roster row, the card row and the
- * card's rail marker.
- *
- * `aborted` deliberately does NOT share `toolError` with `failed`: an abort is the
- * user's own Esc, and the analysis found that painting it red made a cancelled
- * dispatch permanently unreadable in the history.
- */
-export function statusColor(status, theme) {
-    switch (status) {
-        case 'queued':
-            return theme.toolPending;
-        case 'running':
-            return theme.toolRunning;
-        case 'done':
-            return theme.toolDone;
-        case 'failed':
-            return theme.toolError;
-        case 'aborted':
-            return theme.noticeWarn;
-    }
-}
-/**
- * How long this child has been (or was) working, in ms.
- *
- * `endedAt ?? now`, NOT `endedAt ?? 0`. The transcript card used the latter, which
- * made every RUNNING child read `0ms` while the roster beside it read `1m05s` for
- * the same child - the pair of contradictory readouts the reporter screenshotted.
- */
-export function childElapsedMs(run, now) {
-    if (run.startedAt === undefined)
-        return 0;
-    return Math.max(0, (run.endedAt ?? now) - run.startedAt);
-}
-/**
- * Columns the roster header spends on `team` (plus its marker) and on the
- * incoming-message badge, so the count clauses are planned against what is left.
- */
-const HEADER_RESERVED_COLS = 16;
-const HEADER_MIN_CLAUSE_COLS = 12;
-function joinClauses(clauses, glyphs) {
-    return clauses.map((clause) => clause.text).join(` ${glyphs.midDot} `);
-}
-/** Drop the clause that can be spared first, keeping display order intact. */
-function dropLowestPriority(clauses) {
-    let victim = 0;
-    for (let index = 1; index < clauses.length; index += 1) {
-        if (clauses[index].priority < clauses[victim].priority)
-            victim = index;
-    }
-    return clauses.filter((_, index) => index !== victim);
-}
-/**
- * The roster header's count section, e.g. `2 running · 0 done · 1 queued`.
- *
- * `queued` IS COUNTED (the old `isRunning` excluded it, so a fresh dispatch
- * announced `0 running · 0 done` above five rows that each said `queued`), and a
- * non-zero bucket is always named even when nothing is running - a roster whose
- * children are all `aborted` must say so rather than `0 running · 0 done`.
- *
- * WIDTH LADDER: narrow terminals drop the least urgent clause first, in the order
- * `done`, `aborted`, `failed`, `queued`; `running` is never dropped. The order is
- * a product decision, not a detail: while a dispatch is live, what is happening
- * now outranks what has already finished, and the per-row activity column carries
- * the finished children's own facts anyway.
- */
-export function rosterHeadline(counts, glyphs, cols) {
-    const clauses = [
-        { priority: 5, text: `${counts.running} running` },
-        { priority: 1, text: `${counts.done} done` },
-    ];
-    if (counts.queued > 0)
-        clauses.push({ priority: 4, text: `${counts.queued} queued` });
-    if (counts.failed > 0)
-        clauses.push({ priority: 3, text: `${counts.failed} failed` });
-    if (counts.aborted > 0)
-        clauses.push({ priority: 2, text: `${counts.aborted} aborted` });
-    const budget = Math.max(HEADER_MIN_CLAUSE_COLS, cols - HEADER_RESERVED_COLS);
-    let kept = clauses;
-    while (kept.length > 1 && joinClauses(kept, glyphs).length > budget) {
-        kept = dropLowestPriority(kept);
-    }
-    return joinClauses(kept, glyphs);
-}
-/**
- * The settled card's outcome buckets, e.g. `2 ok, 1 aborted, 1 failed`.
- *
- * `ok` is always shown (it is the denominator a reader compares against) and a
- * zero bucket is omitted, so a clean dispatch still reads `3 ok` and a failed one
- * no longer claims that a cancelled child failed.
- */
-export function outcomePhrase(counts) {
-    const parts = [`${counts.done} ok`];
-    if (counts.aborted > 0)
-        parts.push(`${counts.aborted} aborted`);
-    if (counts.failed > 0)
-        parts.push(`${counts.failed} failed`);
-    return parts.join(', ');
-}
-/**
- * Whether this entry is the transcript card of a dispatch that is STILL RUNNING,
- * i.e. the second live surface the reporter saw beside the roster.
- *
- * ONE PREDICATE, FOUR CONSUMERS (analysis A-2'): the transcript's `case 'team'`
- * and `estimateEntryRows` (so the virtual window and the frame agree), the tail
- * window and `LiveTail` (so the pump's print plan and the box agree), and the
- * `Ctrl+O` finder plus `reprintExpanded` (so a keypress cannot print a stale
- * snapshot of a card that is still being rewritten). `state.entries` is NEVER
- * filtered: the entry's lifecycle and `session/persist.ts`'s `interrupted`
- * normalisation depend on it staying there.
- */
-export function isLiveTeamCard(entry) {
-    return entry.kind === 'team' && entry.active === true;
-}
-/**
- * The MOST RECENT dispatch card in the transcript, live or settled.
- *
- * ONE PREDICATE, TWO CONSUMERS (tui-subagent-panel §6.4): the `/agents` command
- * and `App`'s `Ctrl+B` branch both have to answer "is there anything to show?"
- * before opening the board, and the board itself falls back to this entry when a
- * dispatch has already ended and `state.team` is `null` (`resolveBoardSource`).
- * Asking the question in one place is what stops the key and the command from
- * disagreeing about whether the board exists.
- *
- * Scans BACKWARDS and returns the first match: the newest card is the last one in
- * `entries`, and a dispatch-heavy session can hold hundreds of them.
- */
-export function lastTeamEntry(entries) {
-    for (let index = entries.length - 1; index >= 0; index -= 1) {
-        const entry = entries[index];
-        if (entry?.kind === 'team')
-            return entry;
-    }
-    return null;
-}

package/dist/ui/terminal-plan.d.ts

@@ -1,52 +0,0 @@
-/**
- * Terminal plan — the ONE decision point for how the interactive TUI occupies the
- * terminal (tui-native-terminal-scroll §4.1 / D10).
- *
- * `cli.tsx::runInteractive` used to derive `wantMouse`, `mouseOn`, `wantSelect`,
- * `pasteOn` and `enhancedKeysOn` inline, each with its own comment about why the
- * others must agree. Adding a second screen mode multiplies that surface, so the
- * agreement is computed here, once, and the call site only READS the result.
- *
- * PURE: no I/O, no `process` access, so every row of the rules below is a table
- * test with plain literals.
- *
- * I-S9 · `app` reproduces the pre-feature expressions term for term. The
- * regression test diffs this function against a verbatim copy of those
- * expressions, because "the same by inspection" is how mouse and paste drifted
- * apart the last time.
- */
-import type { ScrollMode } from '../config/schema.js';
-export type { ScrollMode } from '../config/schema.js';
-export interface TerminalPlanInput {
-    /** The resolved `scrollMode` config value. */
-    scrollMode: ScrollMode;
-    configMouse: boolean;
-    configMouseSelect: boolean;
-    configPaste: boolean;
-    configKeyboardEnhancement: boolean;
-    configDiffRender: boolean;
-    stdinIsTTY: boolean;
-    stdoutIsTTY: boolean;
-    platform: NodeJS.Platform;
-    /** Measured on win32 (`forceVtInputForThisConsole`); irrelevant elsewhere. */
-    vtInputSupported: boolean;
-}
-export interface TerminalPlan {
-    scrollMode: ScrollMode;
-    /** `app`: enter the alternate screen. `native`: never. */
-    altScreen: boolean;
-    /** Whether the terminal is asked for SGR mouse reports (and a mouse filter is wanted). */
-    mouseReporting: boolean;
-    /** Application-drawn drag selection. Always `false` in native mode (the terminal selects). */
-    dragSelect: boolean;
-    bracketedPaste: boolean;
-    enhancedKeys: boolean;
-    /**
-     * Which frame writer fronts Ink's stdout. `native` ALWAYS needs the scrollback
-     * writer, even with `diffRender` off: static rows are injected through it.
-     */
-    differ: 'fullscreen' | 'scrollback' | 'none';
-    /** Native + `diffRender:false` — every frame rewrites the whole live region. */
-    fullEveryFrame: boolean;
-}
-export declare function resolveTerminalPlan(input: TerminalPlanInput): TerminalPlan;

package/dist/ui/terminal-plan.js

@@ -1,49 +0,0 @@
-/**
- * Terminal plan — the ONE decision point for how the interactive TUI occupies the
- * terminal (tui-native-terminal-scroll §4.1 / D10).
- *
- * `cli.tsx::runInteractive` used to derive `wantMouse`, `mouseOn`, `wantSelect`,
- * `pasteOn` and `enhancedKeysOn` inline, each with its own comment about why the
- * others must agree. Adding a second screen mode multiplies that surface, so the
- * agreement is computed here, once, and the call site only READS the result.
- *
- * PURE: no I/O, no `process` access, so every row of the rules below is a table
- * test with plain literals.
- *
- * I-S9 · `app` reproduces the pre-feature expressions term for term. The
- * regression test diffs this function against a verbatim copy of those
- * expressions, because "the same by inspection" is how mouse and paste drifted
- * apart the last time.
- */
-export function resolveTerminalPlan(input) {
-    const bothTty = input.stdinIsTTY && input.stdoutIsTTY;
-    // Paste and keyboard enhancement ride the stdin filter and say nothing about
-    // scrolling, so the two modes agree on them (rule 3).
-    const bracketedPaste = input.configPaste && input.stdinIsTTY;
-    const enhancedKeys = input.configKeyboardEnhancement &&
-        input.stdinIsTTY &&
-        (input.platform !== 'win32' || input.vtInputSupported);
-    if (input.scrollMode === 'native') {
-        return {
-            scrollMode: 'native',
-            altScreen: false,
-            mouseReporting: false,
-            dragSelect: false,
-            bracketedPaste,
-            enhancedKeys,
-            differ: 'scrollback',
-            fullEveryFrame: !input.configDiffRender,
-        };
-    }
-    const mouseReporting = input.configMouse && bothTty && input.vtInputSupported;
-    return {
-        scrollMode: 'app',
-        altScreen: true,
-        mouseReporting,
-        dragSelect: mouseReporting && input.configMouseSelect,
-        bracketedPaste,
-        enhancedKeys,
-        differ: input.configDiffRender ? 'fullscreen' : 'none',
-        fullEveryFrame: false,
-    };
-}