@aragon-agent/cli 0.6.46 → 0.6.48

package/dist/update/service.d.ts

@@ -24,10 +24,10 @@
  * `update/`.
  */
 import type { ScopedLogger } from '../logging/logger.js';
-import type { UpdateConfig } from '../config/schema.js';
+import type { UpdateConfig } from '@aragon-agent/tui/model/config/schema';
 import { type NpmViewDeps } from './npm-view.js';
 import { type InstallDeps, type SpawnImpl } from './installer.js';
-import type { InstallSource, UpdateCommandPort, UpdateSnapshot } from './types.js';
+import type { InstallSource, UpdateCommandPort, UpdateSnapshot } from '@aragon-agent/tui/model/update/types';
 /** A timer handle we only ever cancel and `unref`. */
 interface TimerHandle {
     unref?: () => void;

package/dist/update/service.js

@@ -27,10 +27,10 @@ import process from 'node:process';
 import { getLogger } from '../logging/logger.js';
 import { adviceFor, classifyInstallSource, isAutoInstallable, isReportableSource, probeWritable, readSelfManifest, selfPackageRoot, } from './install-source.js';
 import { classifyInstallFailure } from './classify-failure.js';
-import { UPDATE_LIMITS } from './limits.js';
+import { UPDATE_LIMITS } from '@aragon-agent/tui/model/update/limits';
 import { fetchLatestViaNpm } from './npm-view.js';
 import { fetchLatestManifest, resolveRegistryUrl } from './registry.js';
-import { decideUpdate, STRICT_VERSION_RE } from './semver.js';
+import { decideUpdate, STRICT_VERSION_RE } from '@aragon-agent/tui/model/update/semver';
 import { tryAcquireInstallLock } from './install-lock.js';
 import { runNpmInstall } from './installer.js';
 import { readUpdateState, updateUpdateState } from './state.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aragon-agent/cli",
-  "version": "0.6.46",
+  "version": "0.6.48",
   "description": "AragonAgent CLI — a Claude-Code / Codex-style interactive terminal UI (TUI) on top of the @aragon-agent/core engine. Installable and runnable via npm / npx.",
   "license": "MIT",
   "author": "AragonAgent contributors",
@@ -48,33 +48,33 @@
     "access": "public"
   },
   "scripts": {
-    "build": "node -e \"require('fs').rmSync('dist',{recursive:true,force:true})\" && tsc -p tsconfig.json && node scripts/prepend-shebang.mjs",
+    "build": "node -e \"require('fs').rmSync('dist',{recursive:true,force:true})\" && tsc -p tsconfig.json && node scripts/prepend-shebang.mjs && node ../../scripts/ensure-built.mjs --stamp cli",
     "dev": "tsc -p tsconfig.json --watch",
+    "pretypecheck": "node ../../scripts/ensure-built.mjs core tui",
     "typecheck": "tsc -p tsconfig.json --noEmit && tsc -p tsconfig.test.json --noEmit",
+    "pretest": "node ../../scripts/ensure-built.mjs core tui",
     "test": "vitest run",
     "start": "node dist/cli.js",
     "prepublishOnly": "npm run build"
   },
   "dependencies": {
-    "@aragon-agent/core": "^0.2.58",
-    "chalk": "^5.6.2",
-    "cli-highlight": "^2.0.0",
+    "@aragon-agent/core": "^0.2.60",
+    "@aragon-agent/tui": "0.0.1",
     "commander": "^12.1.0",
     "dotenv": "^16.6.1",
     "env-paths": "^3.0.0",
     "fflate": "^0.8.3",
     "ink": "^5.0.1",
     "ink-select-input": "^6.0.0",
-    "ink-spinner": "^5.0.0",
     "react": "^18.3.1",
     "string-width": "^7.2.0",
-    "strip-ansi": "^7.1.0",
     "tinyglobby": "^0.2.17"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",
     "@types/react": "^18.3.0",
     "ink-testing-library": "^4.0.0",
+    "strip-ansi": "^7.1.0",
     "typescript": "^5.9.3",
     "vitest": "4.1.9"
   }

package/dist/agent/agent-mode.d.ts

@@ -1,108 +0,0 @@
-/**
- * Agent mode vocabulary (plan-mode §5.1).
- *
- * Pure: no React, no I/O, no `node:*`. Imported by the controller, the tool
- * gate, the prompt builder, the slash command and four UI components, which is
- * exactly why it must stay free of every one of their dependencies.
- *
- * `PLAN_MODE_BLOCKED_TOOLS` is deliberately NOT here. It lives in
- * `tools/index.ts` beside `SKILL_TOOL_FLOOR`, because the invariant worth having
- * is that the two sets PARTITION `HOST_TOOL_NAMES` — and a partition test is
- * only as trustworthy as the distance between the two definitions. This file
- * owns the mode vocabulary; that file owns which tools the modes act on.
- *
- * ASCII ONLY in every string literal below. `agent/` is inside the glyph
- * scanner's scope (`glyphs.test.ts`), so a stray ellipsis here fails the build —
- * which is why `OTHER_OPTION_LABEL` is a bare word and the ellipsis is appended
- * at render time from `glyphs.ellipsis`.
- */
-export type AgentMode = 'build' | 'plan';
-export declare const AGENT_MODES: readonly AgentMode[];
-/** The user-visible word for each mode. English, per the repo convention. */
-export declare const MODE_LABEL: Record<AgentMode, string>;
-/**
- * The next mode in the cycle.
- *
- * Written as a cycle rather than a boolean flip so that adding Claude Code's
- * "auto-accept edits" as a third posture is a one-line change to `AGENT_MODES`
- * and nothing else. Two ship today (§1 non-goals).
- */
-export declare function nextMode(current: AgentMode): AgentMode;
-/**
- * The keys that toggle the mode, as the user sees them written
- * (shift-tab-mode-toggle-still-dead-on-windows, C2).
- *
- * `fallback` exists because `primary` CANNOT be made to work everywhere. On a
- * Windows console without `ENABLE_VIRTUAL_TERMINAL_INPUT`, libuv takes the
- * character branch for `VK_TAB` and drops the modifier wholesale, so `Shift+Tab`
- * and `Ctrl+Tab` both arrive as a bare `0x09` - byte-identical to `Tab`. C1
- * turns that bit back on where it can, but it has three known ways to fail that
- * are outside this package (an old conhost refusing the bit, a locked-down
- * PowerShell, a foreign process resetting the mode), so a rung that depends on
- * NOTHING has to exist underneath it.
- *
- * `ctrl+n` IS MEASURED, not guessed. On the lossy path it arrives as `0x0e`,
- * because Windows generates a real control character for `Ctrl+<letter>` and
- * libuv's character branch forwards it untouched; `Alt+M` produces no bytes at
- * all and `Ctrl+Tab` collapses exactly like `Shift+Tab` (analysis section 3.6).
- * Any idle `Ctrl+<letter>` in the `0x01-0x1A` range would work; this one is free
- * throughout the package - `keymap.ts` claims a/e/w/u/k, `App` claims c/g/k/l/o/r/t,
- * and `PromptInput` returns early on every `key.ctrl` - so binding it takes no
- * behaviour away from anyone. `Ctrl+B` survives the same path but is tmux's
- * default prefix, and this binding is unconditional and cross-platform, so it
- * would be silently dead for a whole class of macOS and Linux users.
- *
- * THIS KEY MOVED FROM `ctrl+p`, WHICH NOW OPENS THE PROMPT LIBRARY
- * (quick-prompt-library D-1). The requirement names `ctrl+p` as the first entry
- * to a feature users will build muscle memory for, and a key that is sometimes
- * the prompt library and sometimes the mode switch is a key nobody can learn.
- * `ctrl+n` was the only idle C0 byte left that survives the same lossy path, and
- * it carries no conflicting behaviour: readline's `next-history` is `Up`/`Down`
- * in this product.
- *
- * `^N` IS NOT AN ACCEPTABLE SPELLING OF IT, ANYWHERE. `^N` is already this
- * product's word for TRANSCRIPT LINE OFFSET - the header's scroll chip reads
- * `^<n>` and the help overlay has a `^N` row about the distance from the bottom -
- * while every other `^X` in the same row is a key. Writing the mode fallback as
- * `^N` would put two meanings of `^` on one line, so the header, the help
- * overlay, `doctor`, the README and the one-shot migration notice all spell out
- * `Ctrl+N`.
- *
- * BOUND UNCONDITIONALLY, on every platform. A binding that only exists where it
- * is needed cannot be documented in one place, cannot be taught by muscle
- * memory, and is missing on precisely the machine whose capability probe was
- * wrong.
- *
- * THESE ARE THE LABELS, NOT THE BINDING. Editing a value here changes only what
- * the user is TOLD to press - the hint row, the startup notice, `doctor`. The
- * key that is actually listened for is `input === 'n'` in `App`'s `useInput`,
- * and the help overlay and README spell both keys out in their own title case.
- * Change one without the others and the product advertises a key it ignores.
- */
-export declare const MODE_TOGGLE_KEYS: {
-    readonly primary: "shift+tab";
-    readonly fallback: "ctrl+n";
-};
-/** The two tools that only exist because a human is attached. */
-export declare const PLAN_TOOL_NAMES: readonly ["ask_user", "submit_plan"];
-/**
- * The synthetic free-text option appended to every question.
- *
- * Plain `Other`, with no ellipsis: this module is inside the glyph scanner's
- * scope, and the overlay appends `glyphs.ellipsis` itself so the label degrades
- * to `Other...` on a terminal without Unicode.
- */
-export declare const OTHER_OPTION_LABEL = "Other";
-/**
- * Why a mutating tool was refused in plan mode.
- *
- * The wording carries weight beyond politeness (§3.9). A run that flips
- * `build -> plan` mid-flight keeps its original system prompt to the end — the
- * loop reads `ctx.systemPrompt`, which was copied by value when the run
- * started — so for the rest of that run this refusal is the ONLY place the
- * model learns that plan mode is on. A bare "not permitted" reads as a tool
- * malfunction and gets retried.
- */
-export declare function planRefusal(tool: string): string;
-/** Why `submit_plan` was refused outside plan mode. */
-export declare function submitPlanRefusal(): string;

package/dist/agent/agent-mode.js

@@ -1,121 +0,0 @@
-/**
- * Agent mode vocabulary (plan-mode §5.1).
- *
- * Pure: no React, no I/O, no `node:*`. Imported by the controller, the tool
- * gate, the prompt builder, the slash command and four UI components, which is
- * exactly why it must stay free of every one of their dependencies.
- *
- * `PLAN_MODE_BLOCKED_TOOLS` is deliberately NOT here. It lives in
- * `tools/index.ts` beside `SKILL_TOOL_FLOOR`, because the invariant worth having
- * is that the two sets PARTITION `HOST_TOOL_NAMES` — and a partition test is
- * only as trustworthy as the distance between the two definitions. This file
- * owns the mode vocabulary; that file owns which tools the modes act on.
- *
- * ASCII ONLY in every string literal below. `agent/` is inside the glyph
- * scanner's scope (`glyphs.test.ts`), so a stray ellipsis here fails the build —
- * which is why `OTHER_OPTION_LABEL` is a bare word and the ellipsis is appended
- * at render time from `glyphs.ellipsis`.
- */
-export const AGENT_MODES = ['build', 'plan'];
-/** The user-visible word for each mode. English, per the repo convention. */
-export const MODE_LABEL = { build: 'BUILD', plan: 'PLAN' };
-/**
- * The next mode in the cycle.
- *
- * Written as a cycle rather than a boolean flip so that adding Claude Code's
- * "auto-accept edits" as a third posture is a one-line change to `AGENT_MODES`
- * and nothing else. Two ship today (§1 non-goals).
- */
-export function nextMode(current) {
-    const index = AGENT_MODES.indexOf(current);
-    return AGENT_MODES[(index + 1) % AGENT_MODES.length];
-}
-/**
- * The keys that toggle the mode, as the user sees them written
- * (shift-tab-mode-toggle-still-dead-on-windows, C2).
- *
- * `fallback` exists because `primary` CANNOT be made to work everywhere. On a
- * Windows console without `ENABLE_VIRTUAL_TERMINAL_INPUT`, libuv takes the
- * character branch for `VK_TAB` and drops the modifier wholesale, so `Shift+Tab`
- * and `Ctrl+Tab` both arrive as a bare `0x09` - byte-identical to `Tab`. C1
- * turns that bit back on where it can, but it has three known ways to fail that
- * are outside this package (an old conhost refusing the bit, a locked-down
- * PowerShell, a foreign process resetting the mode), so a rung that depends on
- * NOTHING has to exist underneath it.
- *
- * `ctrl+n` IS MEASURED, not guessed. On the lossy path it arrives as `0x0e`,
- * because Windows generates a real control character for `Ctrl+<letter>` and
- * libuv's character branch forwards it untouched; `Alt+M` produces no bytes at
- * all and `Ctrl+Tab` collapses exactly like `Shift+Tab` (analysis section 3.6).
- * Any idle `Ctrl+<letter>` in the `0x01-0x1A` range would work; this one is free
- * throughout the package - `keymap.ts` claims a/e/w/u/k, `App` claims c/g/k/l/o/r/t,
- * and `PromptInput` returns early on every `key.ctrl` - so binding it takes no
- * behaviour away from anyone. `Ctrl+B` survives the same path but is tmux's
- * default prefix, and this binding is unconditional and cross-platform, so it
- * would be silently dead for a whole class of macOS and Linux users.
- *
- * THIS KEY MOVED FROM `ctrl+p`, WHICH NOW OPENS THE PROMPT LIBRARY
- * (quick-prompt-library D-1). The requirement names `ctrl+p` as the first entry
- * to a feature users will build muscle memory for, and a key that is sometimes
- * the prompt library and sometimes the mode switch is a key nobody can learn.
- * `ctrl+n` was the only idle C0 byte left that survives the same lossy path, and
- * it carries no conflicting behaviour: readline's `next-history` is `Up`/`Down`
- * in this product.
- *
- * `^N` IS NOT AN ACCEPTABLE SPELLING OF IT, ANYWHERE. `^N` is already this
- * product's word for TRANSCRIPT LINE OFFSET - the header's scroll chip reads
- * `^<n>` and the help overlay has a `^N` row about the distance from the bottom -
- * while every other `^X` in the same row is a key. Writing the mode fallback as
- * `^N` would put two meanings of `^` on one line, so the header, the help
- * overlay, `doctor`, the README and the one-shot migration notice all spell out
- * `Ctrl+N`.
- *
- * BOUND UNCONDITIONALLY, on every platform. A binding that only exists where it
- * is needed cannot be documented in one place, cannot be taught by muscle
- * memory, and is missing on precisely the machine whose capability probe was
- * wrong.
- *
- * THESE ARE THE LABELS, NOT THE BINDING. Editing a value here changes only what
- * the user is TOLD to press - the hint row, the startup notice, `doctor`. The
- * key that is actually listened for is `input === 'n'` in `App`'s `useInput`,
- * and the help overlay and README spell both keys out in their own title case.
- * Change one without the others and the product advertises a key it ignores.
- */
-export const MODE_TOGGLE_KEYS = { primary: 'shift+tab', fallback: 'ctrl+n' };
-/** The two tools that only exist because a human is attached. */
-export const PLAN_TOOL_NAMES = ['ask_user', 'submit_plan'];
-/**
- * The synthetic free-text option appended to every question.
- *
- * Plain `Other`, with no ellipsis: this module is inside the glyph scanner's
- * scope, and the overlay appends `glyphs.ellipsis` itself so the label degrades
- * to `Other...` on a terminal without Unicode.
- */
-export const OTHER_OPTION_LABEL = 'Other';
-/** Read-only alternatives named in every refusal, so the model has somewhere to go. */
-const READ_ONLY_ALTERNATIVES = 'read_file / list_dir / glob / grep';
-/**
- * Why a mutating tool was refused in plan mode.
- *
- * The wording carries weight beyond politeness (§3.9). A run that flips
- * `build -> plan` mid-flight keeps its original system prompt to the end — the
- * loop reads `ctx.systemPrompt`, which was copied by value when the run
- * started — so for the rest of that run this refusal is the ONLY place the
- * model learns that plan mode is on. A bare "not permitted" reads as a tool
- * malfunction and gets retried.
- */
-export function planRefusal(tool) {
-    const extra = tool === 'bash'
-        ? ' bash is refused in full, including read-only commands like "git status":' +
-            ' a shell string cannot be classified reliably, and a gate that is right' +
-            ' most of the time is worse than one that is always right.'
-        : '';
-    return (`Plan mode is active, so ${tool} is refused.${extra}` +
-        ` Use ${READ_ONLY_ALTERNATIVES} to research, then call submit_plan.` +
-        ' Do not try to work around this; finish the plan instead.');
-}
-/** Why `submit_plan` was refused outside plan mode. */
-export function submitPlanRefusal() {
-    return ('submit_plan is only available in Plan mode. You are in Build mode - ' +
-        'just do the work and summarize when you are done.');
-}

package/dist/agent/entry-limits.d.ts

@@ -1,65 +0,0 @@
-/**
- * Bounded view state (tui-render-performance L1 / R5).
- *
- * `ViewState.entries` used to grow without any ceiling: `argsRaw`, assistant
- * `text` and `thinking` all concatenated forever, and the entry array was never
- * trimmed. That makes the per-frame cost of the renderer proportional to the
- * total number of characters the session has ever produced, because Ink's
- * `renderNodeToOutput` walks and measures every mounted text node whether or not
- * `overflow: hidden` clips it.
- *
- * Two bounds live here, both pure and React-free:
- *   - `appendBounded` caps one field by eliding its MIDDLE, and
- *   - `trimEntries` ring-trims the entry array itself.
- *
- * ASCII ONLY. This module is produced outside `src/ui/**`, where no terminal
- * capabilities are available, so the elision marker has to be safe on a legacy
- * `cmd.exe` -- the same rule `PREVIEW_TRUNCATION_MARK` in `reducer.ts` records.
- */
-import type { Entry } from './reducer.js';
-export interface EntryLimits {
-    /** Assistant answer text ceiling, in characters. */
-    text: number;
-    /** Assistant thinking ceiling. */
-    thinking: number;
-    /** Streamed tool-argument JSON ceiling. */
-    argsRaw: number;
-}
-/**
- * The per-field ceilings.
- *
- * `text` is the generous one on purpose: a 256 KiB answer is already far past
- * anything a terminal can usefully show, and the middle is what gets elided, so
- * both the opening and the live cursor survive. `argsRaw` is the tight one --
- * it is a streamed JSON fragment rendered as a 60-character card summary, so
- * anything past a few KiB is invisible by construction.
- */
-export declare const ENTRY_LIMITS: EntryLimits;
-/** Marker inserted at the elision point. ASCII -- produced outside `src/ui/**`. */
-export declare const ELISION_MARK_PREFIX = "\n[... ";
-export declare const ELISION_MARK_SUFFIX = " characters elided ...]\n";
-/**
- * Append `delta` to `prev`, keeping the result at or below `cap` by eliding the
- * MIDDLE. Head and tail are both preserved: the head is the answer's opening,
- * the tail is where the cursor is. Idempotent -- re-eliding an already elided
- * string collapses the two markers into one.
- *
- * The returned string is NEVER longer than `cap` (AC-7). The marker's own digit
- * count is bounded before the tail budget is computed, so the arithmetic cannot
- * overshoot by a digit the way a naive `cap - marker.length` would.
- */
-export declare function appendBounded(prev: string, delta: string, cap: number): string;
-export interface TrimResult {
-    entries: Entry[];
-    dropped: number;
-}
-/**
- * Ring-trim to `retain` entries; returns the SAME array reference when no-op.
- *
- * The identity return is load-bearing: the reducer spreads this result into a
- * new `ViewState` on every append, and a fresh array on every action would
- * defeat the `React.memo` boundaries L2 installs on the transcript.
- */
-export declare function trimEntries(entries: Entry[], retain: number): TrimResult;
-export declare function setEntryRetain(value: number): void;
-export declare function entryRetain(): number;

package/dist/agent/entry-limits.js

@@ -1,133 +0,0 @@
-/**
- * Bounded view state (tui-render-performance L1 / R5).
- *
- * `ViewState.entries` used to grow without any ceiling: `argsRaw`, assistant
- * `text` and `thinking` all concatenated forever, and the entry array was never
- * trimmed. That makes the per-frame cost of the renderer proportional to the
- * total number of characters the session has ever produced, because Ink's
- * `renderNodeToOutput` walks and measures every mounted text node whether or not
- * `overflow: hidden` clips it.
- *
- * Two bounds live here, both pure and React-free:
- *   - `appendBounded` caps one field by eliding its MIDDLE, and
- *   - `trimEntries` ring-trims the entry array itself.
- *
- * ASCII ONLY. This module is produced outside `src/ui/**`, where no terminal
- * capabilities are available, so the elision marker has to be safe on a legacy
- * `cmd.exe` -- the same rule `PREVIEW_TRUNCATION_MARK` in `reducer.ts` records.
- */
-import { DEFAULT_TRANSCRIPT_RETAIN } from '../config/schema.js';
-/**
- * The per-field ceilings.
- *
- * `text` is the generous one on purpose: a 256 KiB answer is already far past
- * anything a terminal can usefully show, and the middle is what gets elided, so
- * both the opening and the live cursor survive. `argsRaw` is the tight one --
- * it is a streamed JSON fragment rendered as a 60-character card summary, so
- * anything past a few KiB is invisible by construction.
- */
-export const ENTRY_LIMITS = {
-    text: 262_144,
-    thinking: 65_536,
-    argsRaw: 16_384,
-};
-/** Marker inserted at the elision point. ASCII -- produced outside `src/ui/**`. */
-export const ELISION_MARK_PREFIX = '\n[... ';
-export const ELISION_MARK_SUFFIX = ' characters elided ...]\n';
-/** Matches a marker this module wrote, so re-elision collapses rather than nests. */
-const ELISION_RE = /\n\[\.\.\. (\d+) characters elided \.\.\.\]\n/;
-/** Fixed cost of the marker, before the digits of the count. */
-const MARKER_FIXED = ELISION_MARK_PREFIX.length + ELISION_MARK_SUFFIX.length;
-/**
- * Fraction of the cap reserved for the HEAD. The tail gets the rest because that
- * is where the cursor is; the head exists so the answer still starts where the
- * model started it.
- */
-const HEAD_FRACTION = 4;
-/** Undo one elision, so a second one merges into it rather than nesting. */
-function splitElided(prev) {
-    const m = ELISION_RE.exec(prev);
-    if (!m)
-        return { head: '', elided: 0, tail: prev };
-    const index = m.index;
-    return {
-        head: prev.slice(0, index),
-        elided: Number.parseInt(m[1], 10) || 0,
-        tail: prev.slice(index + m[0].length),
-    };
-}
-/**
- * Append `delta` to `prev`, keeping the result at or below `cap` by eliding the
- * MIDDLE. Head and tail are both preserved: the head is the answer's opening,
- * the tail is where the cursor is. Idempotent -- re-eliding an already elided
- * string collapses the two markers into one.
- *
- * The returned string is NEVER longer than `cap` (AC-7). The marker's own digit
- * count is bounded before the tail budget is computed, so the arithmetic cannot
- * overshoot by a digit the way a naive `cap - marker.length` would.
- */
-export function appendBounded(prev, delta, cap) {
-    if (!Number.isFinite(cap) || cap <= 0)
-        return '';
-    const split = splitElided(prev);
-    let head = split.head;
-    let tail = split.tail + delta;
-    let elided = split.elided;
-    // Fast path: nothing has ever been elided and it still fits. This is the path
-    // every ordinary answer takes, so it must allocate nothing beyond the concat.
-    if (elided === 0 && tail.length <= cap)
-        return tail;
-    const headBudget = Math.max(0, Math.min(Math.floor(cap / HEAD_FRACTION), cap - MARKER_FIXED - 1));
-    if (elided === 0) {
-        // First elision: the head has to be carved out of the accumulated text.
-        head = tail.slice(0, headBudget);
-        tail = tail.slice(headBudget);
-    }
-    else if (head.length > headBudget) {
-        // A later `cap` reduction can leave the stored head oversized; charge the
-        // difference to the elision count rather than silently keeping it.
-        elided += head.length - headBudget;
-        head = head.slice(0, headBudget);
-    }
-    if (head.length + MARKER_FIXED >= cap) {
-        // Degenerate cap (only reachable from a hand-written test): keep the tail.
-        return tail.slice(Math.max(0, tail.length - cap));
-    }
-    // `elided + tail.length` is an UPPER BOUND on the final count, so its digit
-    // count is an upper bound on the marker's width. Budgeting against the bound
-    // is what makes the `<= cap` guarantee hold without a second pass.
-    const digitBound = String(elided + tail.length).length;
-    const markerBound = MARKER_FIXED + digitBound;
-    const tailKeep = Math.max(0, Math.min(tail.length, cap - head.length - markerBound));
-    const total = elided + (tail.length - tailKeep);
-    return `${head}${ELISION_MARK_PREFIX}${total}${ELISION_MARK_SUFFIX}${tail.slice(tail.length - tailKeep)}`;
-}
-/**
- * Ring-trim to `retain` entries; returns the SAME array reference when no-op.
- *
- * The identity return is load-bearing: the reducer spreads this result into a
- * new `ViewState` on every append, and a fresh array on every action would
- * defeat the `React.memo` boundaries L2 installs on the transcript.
- */
-export function trimEntries(entries, retain) {
-    const keep = Math.max(1, Math.floor(retain));
-    if (entries.length <= keep)
-        return { entries, dropped: 0 };
-    return { entries: entries.slice(entries.length - keep), dropped: entries.length - keep };
-}
-// ---------------------------------------------------------------------------
-// The resolved retain ceiling
-// ---------------------------------------------------------------------------
-/**
- * `viewReducer` is pure and takes no config, so the resolved `transcriptRetain`
- * reaches it through a module-level singleton -- the shape `prompt-history.ts`
- * already uses for `setHistoryEnabled`. `load.ts` is the ONLY writer.
- */
-let resolvedRetain = DEFAULT_TRANSCRIPT_RETAIN;
-export function setEntryRetain(value) {
-    if (Number.isFinite(value) && value > 0)
-        resolvedRetain = Math.floor(value);
-}
-export function entryRetain() {
-    return resolvedRetain;
-}

package/dist/agent/governance-view.d.ts

@@ -1,40 +0,0 @@
-/**
- * The governance slice of the view model: the small pure folds `reducer.ts` delegates to
- * (governance-mode section 14.4).
- *
- * Pure: no React, no I/O. ASCII ONLY (`agent/` is glyph-scanned).
- *
- * WHY A FILE OF ITS OWN. `reducer.ts` is already past the file-size ceiling and the repo
- * rule is "wiring-style growth only": each governance `case` in the reducer is a line or
- * two that calls a function here, so the logic is unit-testable without a `ViewState`.
- */
-import type { AgentMode } from './agent-mode.js';
-import type { GovernanceSnapshot } from '../governance/types.js';
-import { type Posture } from '../governance/posture.js';
-/** The posture half of a `setAgentMode` action. */
-export interface AdoptedPostureInput {
-    mode: AgentMode;
-    pending: AgentMode | null;
-    /** Written from the controller's adopted state; absent for callers that predate postures. */
-    posture?: Posture;
-    pendingPosture?: Posture | null;
-}
-/**
- * The pair of posture fields one `setAgentMode` dispatch writes.
- *
- * "NEVER DISPATCH THE REQUESTED VALUE, ONLY THE ADOPTED ONE" (spec 4.3): the controller
- * reports all four values together and the reducer mirrors them, so the badge and the gate
- * cannot disagree. A dispatch that carries only the gate mode (every pre-governance call
- * site) keeps the governance dimension the view already has and swaps the mode half, which
- * is exactly what such a caller meant.
- */
-export declare function adoptPosture(current: Posture, action: AdoptedPostureInput): {
-    posture: Posture;
-    pendingPosture: Posture | null;
-};
-/**
- * Fold a pushed snapshot into the view: a snapshot OLDER than the one held, for the same
- * run, is dropped (the wiring throttles, and a late flush must not roll the panel back).
- * Returns the held object unchanged when nothing should change.
- */
-export declare function foldGovernanceSnapshot(held: GovernanceSnapshot | null, incoming: GovernanceSnapshot): GovernanceSnapshot;

package/dist/agent/governance-view.js

@@ -1,40 +0,0 @@
-/**
- * The governance slice of the view model: the small pure folds `reducer.ts` delegates to
- * (governance-mode section 14.4).
- *
- * Pure: no React, no I/O. ASCII ONLY (`agent/` is glyph-scanned).
- *
- * WHY A FILE OF ITS OWN. `reducer.ts` is already past the file-size ceiling and the repo
- * rule is "wiring-style growth only": each governance `case` in the reducer is a line or
- * two that calls a function here, so the logic is unit-testable without a `ViewState`.
- */
-import { composePosture, isGovernancePosture } from '../governance/posture.js';
-/**
- * The pair of posture fields one `setAgentMode` dispatch writes.
- *
- * "NEVER DISPATCH THE REQUESTED VALUE, ONLY THE ADOPTED ONE" (spec 4.3): the controller
- * reports all four values together and the reducer mirrors them, so the badge and the gate
- * cannot disagree. A dispatch that carries only the gate mode (every pre-governance call
- * site) keeps the governance dimension the view already has and swaps the mode half, which
- * is exactly what such a caller meant.
- */
-export function adoptPosture(current, action) {
-    const governed = isGovernancePosture(current);
-    const posture = action.posture ?? composePosture(action.mode, governed);
-    const pendingPosture = action.pendingPosture !== undefined
-        ? action.pendingPosture
-        : action.pending === null
-            ? null
-            : composePosture(action.pending, governed);
-    return { posture, pendingPosture };
-}
-/**
- * Fold a pushed snapshot into the view: a snapshot OLDER than the one held, for the same
- * run, is dropped (the wiring throttles, and a late flush must not roll the panel back).
- * Returns the held object unchanged when nothing should change.
- */
-export function foldGovernanceSnapshot(held, incoming) {
-    if (held !== null && held.runId === incoming.runId && incoming.rev < held.rev)
-        return held;
-    return incoming;
-}

package/dist/agent/invocation-card.d.ts

@@ -1,77 +0,0 @@
-/**
- * Invocation cards (tui-invocation-cards): what a transcript shows INSTEAD of the
- * system prompt a command submitted on the user's behalf.
- *
- * Pure and total: no IO, no React, no Ink, nothing but `import type`. ASCII ONLY -
- * `src/agent/**` new files sit inside the `glyphs.test.ts` scan scope.
- *
- * ONE CONSTRUCTOR (I-3). `buildInvocationCard` is the only function that turns raw
- * command-layer material into a card, `App.submitMessage` is its only caller, and
- * `sanitizeInvocationCard` (the session-load path) shares its normaliser so a card
- * written today and a card read back tomorrow cannot drift apart.
- *
- * ORDER IS REDACT -> NORMALISE -> LIMIT, and it is the load-bearing part (I-6). Cut
- * first and a secret that straddles the cut leaves a prefix shorter than the
- * redaction patterns' minimum length: the half-key sails through into the
- * transcript, the session file and the exit replay.
- */
-export type InvocationVariant = 'skill' | 'team' | 'todo' | 'govern';
-/** Everything one card needs; persisted, queued and rendered in this one shape. */
-export interface InvocationCard {
-    readonly variant: InvocationVariant;
-    /** Skill name / 'continue' / 'resume'; '' for team. */
-    readonly name: string;
-    /** What the user typed (or its equivalent), redacted and capped; also `Entry.text`. */
-    readonly commandLine: string;
-    /** The user's own words (args / brief), redacted and trimmed; may be ''. */
-    readonly input: string;
-    /** Characters cut from `input`; 0 when nothing was cut. */
-    readonly inputHidden: number;
-    /** Fact fragments, each at most `factMaxChars`, at most `factsMax` of them. */
-    readonly facts: readonly string[];
-    /** One disclosure sentence. */
-    readonly note?: string;
-}
-/**
- * The renderer, the height estimate and the loader all read THESE numbers (I-4).
- * A card's height is a function of its data and these limits, so it is bounded:
- * header + `inputMaxLines` + hidden tail + note.
- */
-export declare const INVOCATION_LIMITS: {
-    readonly commandLineMaxChars: 2000;
-    readonly inputMaxChars: 480;
-    readonly inputMaxLines: 8;
-    readonly nameMaxChars: 64;
-    readonly factsMax: 5;
-    readonly factMaxChars: 28;
-    readonly noteMaxChars: 140;
-};
-/**
- * Raw material from the command layer: NOT redacted, NOT trimmed. Commands must not
- * cut or scrub it themselves - both happen exactly once, in `buildInvocationCard`.
- */
-export interface InvocationCardInput {
-    variant: InvocationVariant;
-    name?: string;
-    commandLine: string;
-    input?: string;
-    facts?: readonly string[];
-    note?: string;
-}
-/**
- * Total, never throws. `redact` is injected (the same closure `Command:` echo uses) so
- * this module depends on nothing; the default is the identity for tests and the loader.
- */
-export declare function buildInvocationCard(input: InvocationCardInput, redact?: (text: string) => string): InvocationCard;
-/**
- * Session-load path: `null` for anything that is not a plausible card, so the caller
- * drops the field and the entry degrades to a plain user message (I-7). Re-derives
- * `inputHidden` from nothing - it trusts the stored count only when it is a sane integer.
- */
-export declare function sanitizeInvocationCard(value: unknown): InvocationCard | null;
-/**
- * Emergency kill switch (`ARAGON_NO_INVOCATION_CARDS=1`): every command and the App fall
- * back to the pre-card behaviour. Read at call time, not import time, so a test (or a
- * wrapper script) that sets the variable after load is honoured.
- */
-export declare function invocationCardsEnabled(env?: NodeJS.ProcessEnv): boolean;