@aragon-agent/cli 0.6.1 → 0.6.3

package/dist/team/types.d.ts

@@ -78,6 +78,14 @@ export interface SubagentRun {
     error?: string;
     /** Hit `team.maxTurnsPerSubagent` and was stopped mid-work. */
     truncated?: boolean;
+    /**
+     * Compactions this child performed on its OWN history
+     * (context-auto-compaction-hardening §3.4.4 / W3).
+     *
+     * OPTIONAL, so every existing construction site and fixture compiles
+     * unchanged. Absent and `0` mean the same thing to every reader.
+     */
+    compactions?: number;
     /**
      * Prose the child is writing right now, sanitized and clamped to
      * `TEAM_LIMITS.activityChars`. Set only between tool calls; cleared on

package/dist/ui/ActivityLine.d.ts

@@ -74,7 +74,25 @@ export interface ActivityLineProps {
      * not calm, it is wrong.
      */
     runningTool?: string;
+    /**
+     * A context compaction is in flight (context-auto-compaction §6.1).
+     *
+     * HIGHEST PRECEDENCE IN THE LABEL LADDER, above `runningTool` and above the
+     * rotating phrase. Compaction happens BEFORE `turn_start`, i.e. at a moment
+     * when `status` is `'running'` but no tool is in flight — precisely the window
+     * in which the phrase rotation would say something false, and it can last
+     * tens of seconds. `runningTool` already established the principle one step
+     * back: a UI that says "Pondering" while `npm test` runs is not calm, it is
+     * wrong, and one that says it while a 30 k-token summarization runs is the same
+     * error.
+     *
+     * STILL NO SECOND SPINNER. `single-spinner-while-running`'s D-1 stands: this
+     * row owns the only animation while it is mounted, and the compaction card
+     * follows `FastCard` in taking a `reducedMotion` that `App` has already
+     * widened.
+     */
+    compacting?: boolean;
     theme: Theme;
     caps: TermCapabilities;
 }
-export declare function ActivityLine({ startedAt, elapsedMs, reducedMotion, runningTool, theme, caps, }: ActivityLineProps): React.ReactElement;
+export declare function ActivityLine({ startedAt, elapsedMs, reducedMotion, runningTool, compacting, theme, caps, }: ActivityLineProps): React.ReactElement;

package/dist/ui/ActivityLine.js

@@ -21,7 +21,7 @@ import { pickActivityPhrase } from './activity-phrases.js';
 export function liveSpinner(reducedMotion, caps) {
     return caps.unicode && !reducedMotion ? _jsx(Spinner, { type: "dots" }) : null;
 }
-export function ActivityLine({ startedAt, elapsedMs, reducedMotion, runningTool, theme, caps, }) {
+export function ActivityLine({ startedAt, elapsedMs, reducedMotion, runningTool, compacting, theme, caps, }) {
     const glyphs = pickGlyphs(caps);
     // PURE AND DERIVED FROM `(startedAt, now)`, so the sequence does not need to
     // keep rotating underneath the tool label: when the tool settles the phrase
@@ -31,7 +31,15 @@ export function ActivityLine({ startedAt, elapsedMs, reducedMotion, runningTool,
     // SECOND registry of tool names, and `toolGlyph` is already the one place that
     // knows them. Everything round 1 legislated for this row survives — one row,
     // no digits, no `esc abort`, no width ladder, ASCII only.
-    const label = runningTool ? `Running ${runningTool}` : `${phrase}${glyphs.ellipsis}`;
+    // THREE RUNGS, MOST SPECIFIC FIRST. `Compacting context` outranks a tool name
+    // because compaction can be the only thing happening, and it outranks the
+    // phrase for the reason `runningTool` does. ASCII only, and the ellipsis comes
+    // from `pickGlyphs` like every other one on this row.
+    const label = compacting
+        ? `Compacting context${glyphs.ellipsis}`
+        : runningTool
+            ? `Running ${runningTool}`
+            : `${phrase}${glyphs.ellipsis}`;
     // The IDENTICAL branch `Transcript.tsx` uses for the assistant role marker, and
     // it must stay identical: braille dots are both an animation AND a Unicode-only
     // glyph, so reduced motion and an ASCII terminal fall back to the same marker.

package/dist/ui/App.d.ts

@@ -11,6 +11,7 @@ import { type Overlay, type ToastLevel } from '../agent/reducer.js';
 import type { UpdateBridge } from '../update/types.js';
 import { type RenderMode } from './layout/frame.js';
 import type { MouseSource } from '../input/stdin-mouse-filter.js';
+import type { SelectionBridge } from './selection/selection-controller.js';
 import type { HumanInputBridge } from '../tools/human-input.js';
 export interface ConfirmBridge {
     handler: ((req: ConfirmRequest) => Promise<boolean>) | null;
@@ -72,5 +73,51 @@ export interface AppProps {
      * 'off'`, on a non-TTY, in CI, and in every test that does not exercise it.
      */
     updateBridge?: UpdateBridge;
+    /**
+     * The terminal-facing services `cli.tsx` owns and this component cannot build
+     * (tui-selection-and-scroll-follow §4.4).
+     *
+     * ONE PROP RATHER THAN FOUR, and every FIELD of it is independently optional,
+     * so `--no-mouse`, `--no-diff-render` and inline mode each drop exactly the
+     * services they do not have. Absent altogether on a non-TTY and in every test
+     * that does not exercise selection, which is what keeps those trees
+     * byte-identical.
+     */
+    terminal?: TerminalBridge;
+}
+/**
+ * Terminal-level services, almost all of which exist only in a full-screen TTY
+ * session — `writeForeign` is the exception, because `/copy` is available in
+ * inline mode too and OSC 52 is what makes it work over SSH (§4.4.5).
+ *
+ * `selection` is a LATE-BOUND BRIDGE for the reason `updateBridge` above is one:
+ * the controller is constructed before `render()` and must not hold React state,
+ * while the toast sink and the redraw nonce only exist once this component has
+ * mounted. The effect below assigns both and clears them on unmount.
+ */
+export interface TerminalBridge {
+    /** Whether drag-select is on for this session (`mouseSelect` + a filter). */
+    mouseSelect: boolean;
+    /** Release the mouse to the terminal, or take it back (`/mouse`, G3). */
+    setMouseCapture?: (on: boolean) => void;
+    /** Whether the mouse is captured right now — read at command time. */
+    isMouseCaptured?: () => boolean;
+    /**
+     * Write bytes that are ours but are not a frame (OSC 52).
+     *
+     * IT MUST NOT BE `stdout.write` WITH THE DIFFER IN FRONT OF STDOUT (P1-6):
+     * that goes through the frame-writer proxy, which does not recognise an OSC 52
+     * chunk, counts it as a foreign write and prints `FRAME_FALLBACK_NOTICE` at
+     * the user the first time they copy anything. Without a differ — inline mode,
+     * `--no-diff-render` — stdout IS the real stream and `cli.tsx` supplies a
+     * direct write instead.
+     *
+     * Absent only when there is no terminal to accept it at all. It is never a
+     * function that writes nowhere: `copyText` reports `'osc52'` whenever its door
+     * took the text, so a no-op door would make the toast name a mechanism that
+     * was never attempted.
+     */
+    writeForeign?: (text: string) => void;
+    selection?: SelectionBridge;
 }
-export declare function App({ controller, version, mode, initialOverlay, initialPrompt, confirmBridge, humanInputBridge, mouseSource, vtInputWarning, updateBridge, }: AppProps): React.ReactElement;
+export declare function App({ controller, version, mode, initialOverlay, initialPrompt, confirmBridge, humanInputBridge, mouseSource, vtInputWarning, updateBridge, terminal, }: AppProps): React.ReactElement;