@aragon-agent/cli 0.6.46 → 0.6.48

package/dist/ui/entries/UserEntry.d.ts

@@ -1,36 +0,0 @@
-/**
- * Render a user message entry.
- *
- * The role glyph, the gutter rail and the inter-entry spacing all belong to
- * `EntryFrame` now (§4.3), so this component renders content and nothing else.
- *
- * IT DOES TAKE `caps` AS OF tui-paste-handling (G7): the row cap below needs one
- * glyph, and a hardcoded ellipsis is the exact failure `glyphs.ts` exists to
- * prevent. That is the only reason the earlier "it has no glyph of its own left
- * to degrade" note no longer holds.
- */
-import React from 'react';
-import type { Theme } from '../theme.js';
-import type { TermCapabilities } from '../capabilities.js';
-declare function UserEntryImpl({ text, theme, caps, }: {
-    text: string;
-    theme: Theme;
-    caps: TermCapabilities;
-}): React.ReactElement;
-/**
- * Rows this component renders for a given text.
- *
- * EXPORTED SO `virtual-window.ts` AND THIS FILE CANNOT DISAGREE (I-13). The
- * render cap and the height estimate are ONE number; an over-estimated entry is
- * never mounted, so it is never measured, so the estimate never self-corrects --
- * which makes that particular disagreement permanent and silent.
- */
-export declare function userEntryRenderedRows(lineCount: number): number;
-/**
- * `React.memo` with the DEFAULT comparator (tui-render-performance L2 / R3).
- * `mapEntry` already preserves object identity for untouched entries, so the
- * array props below are stable references on a settled card, and `theme` /
- * `caps` are `useMemo`d in `App.tsx` (I-L2-1).
- */
-export declare const UserEntry: React.MemoExoticComponent<typeof UserEntryImpl>;
-export {};

package/dist/ui/entries/UserEntry.js

@@ -1,57 +0,0 @@
-import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
-/**
- * Render a user message entry.
- *
- * The role glyph, the gutter rail and the inter-entry spacing all belong to
- * `EntryFrame` now (§4.3), so this component renders content and nothing else.
- *
- * IT DOES TAKE `caps` AS OF tui-paste-handling (G7): the row cap below needs one
- * glyph, and a hardcoded ellipsis is the exact failure `glyphs.ts` exists to
- * prevent. That is the only reason the earlier "it has no glyph of its own left
- * to degrade" note no longer holds.
- */
-import React from 'react';
-import { Box, Text } from 'ink';
-import { pickGlyphs } from '../glyphs.js';
-import { USER_ENTRY_MAX_ROWS } from '../composer-limits.js';
-import { expandTabs } from '../display-tab.js';
-function UserEntryImpl({ text, theme, caps, }) {
-    const glyphs = pickGlyphs(caps);
-    // TAB IS EXPANDED HERE, AT THE RENDER BOUNDARY, AND NOWHERE ABOVE IT.
-    // The payload keeps its `\t` (the model must receive the original
-    // indentation), so `<Text>` used to hand the raw byte to the terminal and
-    // the terminal painted an EIGHT-column stop while the composer painted a
-    // FOUR-column one. Splitting first and expanding per line keeps this row
-    // identical to the row the user saw in the draft.
-    const all = text.split('\n').map((line) => expandTabs(line));
-    // A submitted 5 000-line paste otherwise asks Yoga to lay out 5 000 nodes
-    // inside a measured entry -- the hazard `render-cache.ts:37` already records
-    // in the same words ("a multi-megabyte 'code block' is almost always a pasted
-    // log"). The full text stays in `ViewState` and in the exit transcript, which
-    // is deliberately NOT capped: a replay a user pipes into an issue must be
-    // complete.
-    const hidden = Math.max(0, all.length - USER_ENTRY_MAX_ROWS);
-    const shown = hidden > 0 ? all.slice(0, USER_ENTRY_MAX_ROWS) : all;
-    return (_jsxs(Box, { flexDirection: "column", children: [shown.map((line, i) => (_jsx(Text, { color: theme.user, bold: i === 0, children: line }, i))), hidden > 0 && (
-            // The tail NAMES the number of hidden rows rather than hiding them
-            // silently, which is what makes the cap honest (D-9 / R-10).
-            _jsx(Text, { color: theme.muted, children: `${glyphs.ellipsis} +${hidden} more lines` }))] }));
-}
-/**
- * Rows this component renders for a given text.
- *
- * EXPORTED SO `virtual-window.ts` AND THIS FILE CANNOT DISAGREE (I-13). The
- * render cap and the height estimate are ONE number; an over-estimated entry is
- * never mounted, so it is never measured, so the estimate never self-corrects --
- * which makes that particular disagreement permanent and silent.
- */
-export function userEntryRenderedRows(lineCount) {
-    return lineCount > USER_ENTRY_MAX_ROWS ? USER_ENTRY_MAX_ROWS + 1 : lineCount;
-}
-/**
- * `React.memo` with the DEFAULT comparator (tui-render-performance L2 / R3).
- * `mapEntry` already preserves object identity for untouched entries, so the
- * array props below are stable references on a settled card, and `theme` /
- * `caps` are `useMemo`d in `App.tsx` (I-L2-1).
- */
-export const UserEntry = React.memo(UserEntryImpl);

package/dist/ui/exit-snapshot.d.ts

@@ -1,43 +0,0 @@
-/**
- * Module-level single-slot snapshot — the ONE way view state crosses the React
- * boundary out to `cli.tsx` (spec §4.4, review P1-3).
- *
- * Why not `useImperativeHandle` / a ref callback: two of the four restore paths
- * (`process.on('exit')` and the signal hooks) are process-level, and by the time
- * they run the component tree may already be unmounted or mid-unmount. A module
- * variable stays readable for the whole process lifetime; a React channel does
- * not.
- *
- * Writes are overwriting, not appending: `entries` is passed by reference, so
- * publishing costs one object literal per view-state change.
- */
-import type { Entry, UsageTotal } from '../agent/reducer.js';
-export interface ExitSnapshot {
-    entries: Entry[];
-    /**
-     * The session total, FORWARDED not copied.
-     *
-     * It gained `cacheReadTokens` / `cacheWriteTokens`
-     * (context-usage-gauge-accuracy §3.6) and this file needed no change for it,
-     * which is the point of referencing the reducer's type rather than restating
-     * its fields: `renderTranscriptText` reads the total through `promptTokensOf`,
-     * so the exit summary and the status bar cannot drift apart.
-     */
-    usageTotal: UsageTotal;
-    provider: string;
-    model: string;
-    startedAt: number;
-    /**
-     * Entries the retain ring removed (tui-render-performance L1).
-     *
-     * OPTIONAL so every existing caller and test is unchanged; absent means the
-     * replay says nothing, which is correct for a session that dropped nothing.
-     */
-    droppedEntries?: number;
-}
-/** Called by `App` after every view-state change. Synchronous, side-effect free. */
-export declare function publishExitSnapshot(next: ExitSnapshot): void;
-/** Called by `cli.tsx` after `restore()`. `undefined` ⇒ skip the replay entirely. */
-export declare function readExitSnapshot(): ExitSnapshot | undefined;
-/** Test-only reset so specs do not leak state into one another. */
-export declare function clearExitSnapshot(): void;

package/dist/ui/exit-snapshot.js

@@ -1,26 +0,0 @@
-/**
- * Module-level single-slot snapshot — the ONE way view state crosses the React
- * boundary out to `cli.tsx` (spec §4.4, review P1-3).
- *
- * Why not `useImperativeHandle` / a ref callback: two of the four restore paths
- * (`process.on('exit')` and the signal hooks) are process-level, and by the time
- * they run the component tree may already be unmounted or mid-unmount. A module
- * variable stays readable for the whole process lifetime; a React channel does
- * not.
- *
- * Writes are overwriting, not appending: `entries` is passed by reference, so
- * publishing costs one object literal per view-state change.
- */
-let snapshot;
-/** Called by `App` after every view-state change. Synchronous, side-effect free. */
-export function publishExitSnapshot(next) {
-    snapshot = next;
-}
-/** Called by `cli.tsx` after `restore()`. `undefined` ⇒ skip the replay entirely. */
-export function readExitSnapshot() {
-    return snapshot;
-}
-/** Test-only reset so specs do not leak state into one another. */
-export function clearExitSnapshot() {
-    snapshot = undefined;
-}

package/dist/ui/frame-differ.d.ts

@@ -1,166 +0,0 @@
-/**
- * Frame differ — F1 of tui-input-flicker-fix (§3.2).
- *
- * Ink 5.2.1 has exactly one repaint strategy: on every commit it serialises the
- * WHOLE frame and hands it to `log-update`, which writes
- * `eraseLines(previousLineCount) + frame` in a single `stdout.write`
- * (`ink/build/log-update.js:17`). `ansiEscapes.eraseLines` walks BOTTOM-UP, so
- * the composer — the last row of the frame — is erased near the start of every
- * repaint and rewritten at the very end of it. During a run that happens 15–30
- * times a second with the composer's bytes unchanged, and the user sees the
- * bottom of their screen flicker while they type (§2 R1/R2).
- *
- * This module recognises that write shape, diffs the new frame against the
- * previous one line by line, and emits only the rows that actually changed, each
- * addressed absolutely. It is PURE: no I/O, no Node globals, no event emitter —
- * `stdout-frame-writer.ts` is what binds it to a real stream. That is what keeps
- * it unit-testable with plain string literals and no TTY.
- *
- * THREE INVARIANTS LIVE HERE AND EACH ONE FAILS SILENTLY IF DROPPED:
- *
- *  - I-4 · An emitted line is `CUP · SGR0 · text · SGR0 · CSI K`, IN THAT ORDER,
- *    and it never contains `CSI 2K`. Erasing first would blank the row and refill
- *    it, which is R1's defect at 1/H the scale but on the one row the user is
- *    watching. Overwriting in place means no cell is ever presentably empty; the
- *    trailing `CSI K` removes only the residue a longer previous line left, and
- *    the trailing SGR reset before it stops a BCE terminal painting that residue
- *    in whatever background colour the line ended inside.
- *    `CSI K` IS EMITTED ONLY WHEN THE LINE IS NARROWER THAN THE TERMINAL. A row
- *    that already fills every column (the unified scrollbar paints the last one)
- *    has no residue to clear, and on terminals that keep the cursor ON the last
- *    column after writing it (a pending-wrap flag rather than a virtual column
- *    N+1) the EL would erase the cell that was just written. `cols` unknown keeps
- *    the old always-EL behaviour (`paintLine`).
- *  - I-5 · Every emitted batch ends parked on row `H+1`. Ink's own
- *    `previousLineCount` is computed from the string IT produced and is
- *    unaffected by what we actually wrote, so a later pass-through's
- *    `eraseLines(H+1)` must find the cursor exactly where log-update left it last
- *    time. Drop this and one fallback shifts the frame up a row for the rest of
- *    the session.
- *  - I-6 · Any unrecognised write invalidates the cache. Absolute addressing is
- *    valid only while nothing else writes to stdout. Full-screen mode already
- *    forbids that, but "forbidden" is not "impossible", and the failure mode of
- *    the guard being absent is a permanently misaligned screen while the failure
- *    mode of it firing spuriously is one extra full repaint.
- */
-/**
- * Rebuild `ansiEscapes.eraseLines(count)` byte for byte.
- *
- * Exported for the upgrade tripwire (`frame-differ-ink-shape.test.ts`), which
- * drives the real `ink/build/log-update.js` and asserts this reconstruction is
- * byte-equal to what it produced. If a future Ink changes the shape, that test
- * fails loudly instead of this module silently degrading to pass-through for the
- * rest of the package's life (K-2).
- */
-export declare function eraseLinesPrefix(count: number): string;
-export interface FrameDifferOptions {
-    /** Emit the DEC 2026 envelope around each batch. */
-    sync: boolean;
-    /**
-     * Live terminal height. Read on every `transform`, NEVER cached: it is the
-     * only input to the I-9 geometry guard and it changes under the differ's feet
-     * on resize. `undefined` ⇒ stand down and pass through.
-     */
-    rows: () => number | undefined;
-    /**
-     * Live terminal width, read on every paint and never cached (like `rows`).
-     * Absent or non-finite => every changed row ends in `CSI K` (the original
-     * behaviour); finite => rows whose display width is >= `cols` skip the EL so
-     * the last column (the scrollbar) is never erased (I-4).
-     */
-    cols?: () => number | undefined;
-    /** Raised once, on the 0→1 edge of `fallbacks` (§5.6). */
-    onFirstFallback?: () => void;
-    /**
-     * Raw frame lines in, lines to PAINT out. Identity when absent, and absent is
-     * the default — a session without drag-select never allocates a second array.
-     *
-     * Called AFTER the geometry stand-down and BEFORE the cache comparison, so a
-     * frame this module refuses to address never reaches the selection layer, and
-     * the diff below still compares what is actually on the screen (I-2).
-     *
-     * It MUST return the same number of lines it was given; a decorator that
-     * changes the count would desynchronise absolute addressing, so the result is
-     * discarded if it does.
-     */
-    decorate?: (lines: string[]) => string[];
-    /**
-     * Raised whenever the cache is dropped — a foreign write, a resize, a geometry
-     * stand-down, an explicit `invalidate()`.
-     *
-     * P1-7: on every one of those paths the RAW Ink frame reaches the screen
-     * verbatim, so any highlight is wiped off the terminal while the selection
-     * controller still believes it is painted and its mirror still holds the rows
-     * of the last DECORATED frame. A release would then copy text that is not on
-     * screen. I-4's "by construction" argument has exactly this hole, and one
-     * callback closes it: the controller clears the selection.
-     */
-    onInvalidate?: () => void;
-}
-export interface FrameWriterStats {
-    /** Frames the differ EMITTED — `framesDiffed + framesFull`, never pass-throughs. */
-    framesTotal: number;
-    framesDiffed: number;
-    framesFull: number;
-    linesWritten: number;
-    bytesWritten: number;
-    /**
-     * Pass-throughs caused by a write the differ did not understand.
-     *
-     * NOT INVALIDATIONS (AC-11 / K-14). A resize legitimately invalidates and shows
-     * up as `framesFull`; counting invalidations here would put AC-7 and AC-11 in
-     * direct contradiction and one of them would end up quietly relaxed. It also
-     * excludes the two pass-throughs this module inflicts on ITSELF and already
-     * knows are benign — the session's seed write and the degenerate-geometry
-     * stand-down — because `fallbacks > 0` is documented to mean "something wrote
-     * to stdout behind Ink's back" and is what raises the §5.6 notice.
-     */
-    fallbacks: number;
-    /**
-     * Self-initiated repaints — `repaint()` calls that emitted at least one row.
-     *
-     * A COUNTER OF ITS OWN, deliberately kept out of `framesTotal` /
-     * `framesDiffed` (P2-6). Those count frames INK PRODUCED, and folding a drag's
-     * highlight repaints into them would make `/perf`'s frame rate a function of
-     * how much the user moved the mouse.
-     */
-    repaints: number;
-}
-export interface FrameDiffer {
-    /**
-     * Bytes to write instead of `chunk`; `''` = write nothing; `null` = write
-     * `chunk`. The parameter is `string` and only `string` (P1-4): decoding, and
-     * the decision about what is even diffable, belong to the writer — the only
-     * place untyped input arrives.
-     */
-    transform(chunk: string): string | null;
-    /** Force the next frame to be a full repaint. */
-    invalidate(): void;
-    /** Single owner of the counters (P2-2); the writer re-exports this. */
-    stats(): FrameWriterStats;
-    /**
-     * Re-run `decorate` over the LAST RAW FRAME and emit only the rows whose paint
-     * changed; `''` when there is nothing safe to do.
-     *
-     * This is what makes a drag cost 1-3 addressed rows instead of a React commit
-     * and a whole-tree Yoga layout (D-6). `''` is a REAL state rather than an error
-     * — after an `invalidate()` there is no cache to diff against and no origin to
-     * address from — and the caller's fallback is `App`'s existing `redrawNonce`:
-     * ask for a React redraw, the next commit runs `decorate`, and the highlight
-     * appears one frame later instead of never.
-     */
-    repaint(): string;
-    /**
-     * The stream was resized. Optional (tui-native-terminal-scroll §5.1): the
-     * full-screen differ does not implement it and is invalidated instead, which is
-     * its existing behaviour; the scrollback writer keeps its cache for a reflow
-     * estimate.
-     */
-    onResize?(): void;
-    /**
-     * An own write that moves neither a cell nor the cursor (OSC 52 copy). Optional
-     * for the same reason: absent, the write invalidates the cache as before.
-     */
-    cursorNeutralWrite?(): void;
-}
-export declare function createFrameDiffer(options: FrameDifferOptions): FrameDiffer;