@aragon-agent/cli 0.6.3 → 0.6.7

package/dist/session/persist.js

@@ -59,6 +59,24 @@ function stripLiveToolOutput(entries) {
         ? { ...e, live: undefined, liveSeq: undefined, lastOutputAt: undefined }
         : e);
 }
+/**
+ * Drop the service tail on the way to disk, beside `stripLiveToolOutput` and for
+ * the same three reasons (background-service-supervision §6).
+ *
+ * A resumed card's tail describes a PROCESS THAT NO LONGER EXISTS - it died with
+ * the session, because nothing in this package outlives the CLI by design. The
+ * tail is also the only unbounded field a service entry carries, and dropping it
+ * keeps a saved session's size a function of how many services ran rather than
+ * of how chatty they were.
+ *
+ * `rowsSeen` IS KEPT. It is the revision cursor, not display data, and a
+ * restored card that reported 0 rows seen while `normalizeLoadedEntries` was
+ * flipping its status would produce a revision collision with a live card that
+ * genuinely has none.
+ */
+function stripServiceTail(entries) {
+    return entries.map((e) => (e.kind === 'service' && e.rows.length > 0 ? { ...e, rows: [] } : e));
+}
 /**
  * `data` GAINS `todos`, AND WIDENING `SavedSession` ALONE IS NOT ENOUGH (P0-2):
  * the writer below builds its payload from THIS parameter, not from the type, so
@@ -81,7 +99,7 @@ export function saveSession(filePath, data) {
         savedAt: Date.now(),
         model: data.model,
         messages: data.messages,
-        entries: stripLiveToolOutput(data.entries),
+        entries: stripServiceTail(stripLiveToolOutput(data.entries)),
         todos: data.todos,
         ...(data.meta ? { meta: data.meta } : {}),
     };
@@ -158,6 +176,23 @@ export function normalizeLoadedEntries(entries) {
                 reason: 'interrupted (session resumed)',
             };
         }
+        // THE SIXTH CLAUSE (background-service-supervision §6 / R-7). A card saved
+        // while its service was up resumes claiming to be running while nothing is -
+        // the process died with the session, because nothing here outlives the CLI.
+        //
+        // AND `starting` IS THE ONE THAT ACTUALLY COSTS: it is the single service
+        // status that blocks `Transcript`'s MONOTONIC settled boundary (D-11), so a
+        // restored `starting` card would never settle and every frame for the rest of
+        // the session would re-render the whole tail. `ready` / `running` would
+        // "only" be a lie; this one is a lie that gets slower.
+        //
+        // `stopped` rather than `exited`: we did not observe an exit code, and
+        // claiming one would be inventing a number. The terminal record the session
+        // may also carry is already terminal and is left alone.
+        if (entry.kind === 'service' &&
+            (entry.status === 'starting' || entry.status === 'ready' || entry.status === 'running')) {
+            return { ...entry, status: 'stopped', rows: [] };
+        }
         return entry;
     });
 }

package/dist/todo/limits.d.ts

@@ -32,13 +32,10 @@ export declare const TODO_LIMITS: {
      * there (§3.3 step 2).
      */
     readonly minFreshItems: 2;
-    /** Rows the in-progress row may wrap to. Every other row truncates. */
-    readonly activeWrapRows: 2;
-    /**
-     * Below this many AVAILABLE rail rows (`todoRailRows`, NOT `viewportBudget`)
-     * the rail is not mounted at all.
-     */
-    readonly panelMinRows: 6;
+    /** Minimum shared middle rows for the compact rail. */
+    readonly panelMinRows: 3;
+    /** Full rail includes a blank separator and separate overflow markers. */
+    readonly panelFullRows: 6;
     /** Below this many terminal columns the status-bar counter degrades to `[3/7]`. */
     readonly statusCompactCols: 100;
     /**
@@ -51,16 +48,6 @@ export declare const TODO_LIMITS: {
      * component was a third policy or a typo for one of them.
      */
     readonly stripDoneCols: 80;
-    /**
-     * Rows `todoRailRows()` subtracts while a team dispatch is live (§3.9 / P1-3).
-     *
-     * `TEAM_LIMITS.panelMaxRows` (5) + header + `+N more` + the mail line = 8, and
-     * this is deliberately the FULL worst case rather than a measurement: an
-     * over-subtraction costs one item row, an under-subtraction eats the `+N
-     * below` marker - the one row whose absence is indistinguishable from "the
-     * list is short" - and those two mistakes are not equally bad.
-     */
-    readonly railReservedRows: 8;
     /**
      * Consecutive user turns an UNFINISHED list survives without a `todo_write`
      * before `beginUserTurn()` drops it (§3.2 / P1-7). Three keeps the common

package/dist/todo/limits.js

@@ -32,13 +32,10 @@ export const TODO_LIMITS = {
      * there (§3.3 step 2).
      */
     minFreshItems: 2,
-    /** Rows the in-progress row may wrap to. Every other row truncates. */
-    activeWrapRows: 2,
-    /**
-     * Below this many AVAILABLE rail rows (`todoRailRows`, NOT `viewportBudget`)
-     * the rail is not mounted at all.
-     */
-    panelMinRows: 6,
+    /** Minimum shared middle rows for the compact rail. */
+    panelMinRows: 3,
+    /** Full rail includes a blank separator and separate overflow markers. */
+    panelFullRows: 6,
     /** Below this many terminal columns the status-bar counter degrades to `[3/7]`. */
     statusCompactCols: 100,
     /**
@@ -51,16 +48,6 @@ export const TODO_LIMITS = {
      * component was a third policy or a typo for one of them.
      */
     stripDoneCols: 80,
-    /**
-     * Rows `todoRailRows()` subtracts while a team dispatch is live (§3.9 / P1-3).
-     *
-     * `TEAM_LIMITS.panelMaxRows` (5) + header + `+N more` + the mail line = 8, and
-     * this is deliberately the FULL worst case rather than a measurement: an
-     * over-subtraction costs one item row, an under-subtraction eats the `+N
-     * below` marker - the one row whose absence is indistinguishable from "the
-     * list is short" - and those two mistakes are not equally bad.
-     */
-    railReservedRows: 8,
     /**
      * Consecutive user turns an UNFINISHED list survives without a `todo_write`
      * before `beginUserTurn()` drops it (§3.2 / P1-7). Three keeps the common

package/dist/todo/panel-rows.d.ts

@@ -37,17 +37,19 @@ export interface TodoRowSelection {
 export declare function todoAnchorIndex(items: TodoItem[]): number;
 /**
  * @param maxRows Rows available for the item rows AND the two overflow markers
- *                together. `todoRailRows()` upstream is what makes this number
- *                honest while a team dispatch is live (I-10 / P1-3).
+ *                together. The shared layout subtracts actual team/menu rows.
  *
  * THE ANCHOR IS ALWAYS VISIBLE, and that beats the row bound when the two
  * conflict. They can only conflict below `maxRows` 3 with overflow on BOTH
  * sides — one item plus two markers is three rows — where this returns the
  * anchor and lets the caller's `overflow="hidden"` clip a marker. Hiding the
  * one row the user is watching in order to keep a `+N above` would be the wrong
- * trade. `TODO_LIMITS.panelMinRows` (6) gates the mount and leaves `TodoPanel`
- * at least 4 item rows, so the case is unreachable from the rail; a future
- * caller with a smaller budget should read this paragraph before assuming
- * otherwise.
+ * trade. The full rail has at least four item rows. The compact rail uses
+ * `selectCompactTodoRows` with a single merged footer instead.
  */
 export declare function selectTodoRows(items: TodoItem[], maxRows: number): TodoRowSelection;
+/** Select an anchored contiguous window without reserving overflow-marker rows.
+ * maxItemRows is a row count; invalid/nonpositive values return an empty window
+ * with every item counted below it. Does not mutate the list or throw.
+ */
+export declare function selectCompactTodoRows(items: TodoItem[], maxItemRows: number): TodoRowSelection;

package/dist/todo/panel-rows.js

@@ -58,18 +58,15 @@ function windowFor(count, anchor, slots) {
 }
 /**
  * @param maxRows Rows available for the item rows AND the two overflow markers
- *                together. `todoRailRows()` upstream is what makes this number
- *                honest while a team dispatch is live (I-10 / P1-3).
+ *                together. The shared layout subtracts actual team/menu rows.
  *
  * THE ANCHOR IS ALWAYS VISIBLE, and that beats the row bound when the two
  * conflict. They can only conflict below `maxRows` 3 with overflow on BOTH
  * sides — one item plus two markers is three rows — where this returns the
  * anchor and lets the caller's `overflow="hidden"` clip a marker. Hiding the
  * one row the user is watching in order to keep a `+N above` would be the wrong
- * trade. `TODO_LIMITS.panelMinRows` (6) gates the mount and leaves `TodoPanel`
- * at least 4 item rows, so the case is unreachable from the rail; a future
- * caller with a smaller budget should read this paragraph before assuming
- * otherwise.
+ * trade. The full rail has at least four item rows. The compact rail uses
+ * `selectCompactTodoRows` with a single merged footer instead.
  */
 export function selectTodoRows(items, maxRows) {
     const count = items.length;
@@ -101,3 +98,19 @@ export function selectTodoRows(items, maxRows) {
         visible.push({ item: items[i], index: i });
     return { visible, hiddenAbove: start, hiddenBelow: count - end };
 }
+/** Select an anchored contiguous window without reserving overflow-marker rows.
+ * maxItemRows is a row count; invalid/nonpositive values return an empty window
+ * with every item counted below it. Does not mutate the list or throw.
+ */
+export function selectCompactTodoRows(items, maxItemRows) {
+    const slots = Number.isFinite(maxItemRows) ? Math.max(0, Math.floor(maxItemRows)) : 0;
+    if (slots === 0 || items.length === 0) {
+        return { visible: [], hiddenAbove: 0, hiddenBelow: items.length };
+    }
+    const { start, end } = windowFor(items.length, todoAnchorIndex(items), slots);
+    return {
+        visible: items.slice(start, end).map((item, offset) => ({ item, index: start + offset })),
+        hiddenAbove: start,
+        hiddenBelow: items.length - end,
+    };
+}

package/dist/tools/bash-tool.d.ts

@@ -1,12 +1,61 @@
 /**
- * bash tool — run a shell command at full permission (spec §3.6).
+ * bash tool — run a shell command at full permission (spec §3.6), and, since
+ * background-service-supervision, supervise the ones that do not exit.
  *
  * Shell selection: Windows uses `process.env.ComSpec` (cmd.exe by default);
  * POSIX uses `/bin/sh -c`. The command's stdout+stderr and exit code are
  * captured. The `timeout?` param can only SHRINK within the executor ceiling
  * (the core ToolExecutor owns the real timeout + 100 KB truncation — R4), so
  * this tool does not re-implement an output cap.
+ *
+ * I-1 — THIS TOOL NEVER LEAVES ITS PROMISE PENDING. Every exit path goes through
+ * `settle`, and `settle` is reachable from FIVE places: `'error'`, `'close'`,
+ * `'exit'` plus a drain timer, an abort plus a kill grace, and the `timeout`
+ * param plus the same grace. That is the whole of W1, and each of the five
+ * closes a way the old implementation could hang:
+ *
+ *   1. It settled on `'close'`, which fires only when the process has exited AND
+ *      every stdio stream is closed. A child that spawns a detached grandchild
+ *      inheriting the pipe — `Start-Process`, `&`, `nohup`, and every
+ *      `npm run dev` that re-execs — keeps that pipe open after the shell is
+ *      long gone. The shell exited; the promise did not.
+ *   2. `stdio` defaulted to `'pipe'` for stdin, so a command that PROMPTS —
+ *      `npm init`, a package manager asking to install something, `sudo`, a git
+ *      credential prompt — blocked on a read that could never be satisfied.
+ *   3. An abort killed the tree and then went on waiting for a `'close'` that a
+ *      detached grandchild was still holding.
+ *
+ * The happy path is BYTE-IDENTICAL to the pre-change build: `$ cmd\n<output>\n
+ * [exit code N]`, same truncation, same footer. That is what keeps the existing
+ * `bash` assertions meaningful rather than rewritten.
  */
 import { type AgentTool } from '@aragon-agent/core';
+import type { ProcSupervisorPort } from '../proc/types.js';
 import type { ToolDeps } from './fs-tools.js';
-export declare function makeBash(deps: ToolDeps): AgentTool;
+export interface BashToolOptions {
+    /**
+     * Present only when background launches are on for this session.
+     *
+     * ITS ABSENCE IS WHAT MAKES I-2 CHECKABLE: no `background` property in the
+     * schema, no supervisor call, no readiness timer, and a description string
+     * identical to the pre-feature one.
+     */
+    supervisor?: ProcSupervisorPort;
+    /** `cfg.bash.autoBackground`, read LIVE. */
+    autoBackground?: () => boolean;
+    /** `cfg.bash.startupSettleMs`, read LIVE. */
+    startupSettleMs?: () => number;
+    /**
+     * Whether a card can be rendered and a user can keep a service alive (D-15 /
+     * P1-8).
+     *
+     * FALSE IN `aragon exec` AND `-p`. It suppresses only the CLASSIFIER: an
+     * explicit `background: true` is still honoured — the model asked for it —
+     * and the result then carries one extra line saying the service dies with the
+     * run. Without this rule `aragon -p "npm run dev"` would background a server,
+     * return in `startupSettleMs`, and reap it at process exit with no card, no
+     * `/bg`, no event and nothing in the result saying so.
+     */
+    interactive?: boolean;
+}
+export declare function makeBash(deps: ToolDeps, options?: BashToolOptions): AgentTool;