@aragon-agent/cli 0.6.7 → 0.6.9

package/dist/config/env.js

@@ -77,8 +77,6 @@ export function readEnvConfig() {
     if (process.env.ARAGON_THINKING) {
         partial.thinkingLevel = clampThinkingLevel(process.env.ARAGON_THINKING.trim(), 'off');
     }
-    // Parsed by the POSITIVE list, like ARAGON_FULLSCREEN: anything else is left
-    // ABSENT so the config file underneath still wins.
     const showThinking = process.env.ARAGON_SHOW_THINKING?.trim().toLowerCase();
     if (showThinking !== undefined && showThinking.length > 0) {
         partial.showThinking =
@@ -130,16 +128,7 @@ export function readEnvConfig() {
     if (process.env.ARAGON_THEME) {
         partial.theme = clampTheme(process.env.ARAGON_THEME.trim(), 'auto');
     }
-    // ARAGON_FULLSCREEN=0|1 — the one channel that works where neither a flag nor
     // a config file is reachable (containers, SSH, being spawned by another tool).
-    const fullscreen = process.env.ARAGON_FULLSCREEN?.trim().toLowerCase();
-    if (fullscreen !== undefined && fullscreen.length > 0) {
-        partial.fullscreen = fullscreen === '1' || fullscreen === 'true' || fullscreen === 'on' || fullscreen === 'yes';
-    }
-    // ARAGON_MOUSE=0 turns off wheel region routing. Parsed by the POSITIVE list
-    // above, exactly as ARAGON_FULLSCREEN is — NOT by `envBool` below, which uses
-    // a negative list. The two disagree on `ARAGON_MOUSE=disable`, and `mouse` is
-    // modelled on `--fullscreen`, so it uses the reader `--fullscreen` uses.
     const mouse = process.env.ARAGON_MOUSE?.trim().toLowerCase();
     if (mouse !== undefined && mouse.length > 0) {
         partial.mouse = mouse === '1' || mouse === 'true' || mouse === 'on' || mouse === 'yes';
@@ -174,8 +163,6 @@ export function readEnvConfig() {
         if (Number.isFinite(n) && n >= 0)
             partial.scrollResumeMs = n;
     }
-    // ARAGON_PLAN=1 starts the session in PLAN mode — the same channel story as
-    // ARAGON_FULLSCREEN, for terminals reached through a wrapper that owns argv.
     const plan = process.env.ARAGON_PLAN?.trim().toLowerCase();
     if (plan !== undefined && plan.length > 0) {
         partial.planModeDefault = plan === '1' || plan === 'true' || plan === 'on' || plan === 'yes';
@@ -191,12 +178,6 @@ export function readEnvConfig() {
             enabled: !(skills === '0' || skills === 'false' || skills === 'off' || skills === 'no'),
         };
     }
-    // ARAGON_TEAM=0 turns team mode off; ARAGON_TEAM_MAX=<n> overrides the fan-out
-    // width. Parsed by the POSITIVE list, exactly as ARAGON_FULLSCREEN /
-    // ARAGON_MOUSE / ARAGON_PLAN are — NOT by `envBool` below, which uses a
-    // negative list. The two readers disagree on `ARAGON_TEAM=disable`, and the
-    // documented-but-dead outcome of copying the wrong one is what `load.ts`
-    // records for `ARAGON_MOUSE`.
     const team = process.env.ARAGON_TEAM?.trim().toLowerCase();
     const teamMax = process.env.ARAGON_TEAM_MAX?.trim();
     if ((team !== undefined && team.length > 0) || (teamMax !== undefined && teamMax.length > 0)) {
@@ -217,27 +198,6 @@ export function readEnvConfig() {
         if (Object.keys(section).length > 0)
             partial.team = section;
     }
-    // ARAGON_TODO=0 turns todo planning off entirely (no tool, no rail). Parsed by
-    // the POSITIVE list, exactly as ARAGON_FULLSCREEN / ARAGON_MOUSE / ARAGON_PLAN
-    // / ARAGON_TEAM are — NOT by `envBool` below, which uses a negative list. The
-    // two readers disagree on values like `ARAGON_TODO=disable`, and this file
-    // already records that once for team mode.
-    //
-    // There is no `ARAGON_TODO_PANEL`: the panel is a per-machine display
-    // preference, which is what `config.json` is for, and every env var here
-    // exists because a flag and a config file are BOTH unreachable in the channel
-    // it serves (containers, SSH, being spawned by another tool).
-    //
-    // ARAGON_TODO_FOLLOW=notify|auto|off PASSES THAT SAME TEST (D-18), which is
-    // why it exists where `ARAGON_TODO_PANEL` does not: follow-through is exactly
-    // the knob an unattended `-p` run in a container with a fixed entrypoint needs
-    // and can reach no other way.
-    //
-    // ONE ACCUMULATED SECTION, ASSIGNED ONCE — the shape the `team` branch above
-    // already uses, and NOT two `if` blocks each assigning `partial.todo` (P1-4).
-    // THE CAST IS WHAT WOULD MAKE THAT MISTAKE SILENT: a second assignment
-    // compiles clean and drops `enabled`, so `ARAGON_TODO=0 ARAGON_TODO_FOLLOW=auto`
-    // would quietly re-enable the tool the user turned off.
     const todo = process.env.ARAGON_TODO?.trim().toLowerCase();
     const todoFollow = process.env.ARAGON_TODO_FOLLOW?.trim().toLowerCase();
     if ((todo !== undefined && todo.length > 0) ||
@@ -260,24 +220,6 @@ export function readEnvConfig() {
         if (Object.keys(section).length > 0)
             partial.todo = section;
     }
-    // ARAGON_BASH_BACKGROUND=0 turns background services off entirely (no
-    // `background` param, no `bash_output`/`bash_kill`, no prompt block, no chip);
-    // ARAGON_BASH_AUTO_BACKGROUND=0 keeps them but stops the classifier firing on
-    // an unset `background`. Parsed by the POSITIVE list, exactly as
-    // ARAGON_FULLSCREEN / ARAGON_MOUSE / ARAGON_PLAN / ARAGON_TEAM / ARAGON_TODO
-    // are - NOT by `envBool` below, which uses a negative list.
-    //
-    // Both pass the test every env var in this file has to pass: an unattended run
-    // in a container with a fixed entrypoint can reach neither a flag nor a config
-    // file, and "do not leave a dev server running in my CI job" is exactly the
-    // kind of decision that channel needs to make.
-    //
-    // ONE ACCUMULATED SECTION, ASSIGNED ONCE - the shape the `team` and `todo`
-    // branches above already use, and NOT two `if` blocks each assigning
-    // `partial.bash` (the `todo` P1-4 trap). THE CAST IS WHAT WOULD MAKE THAT
-    // MISTAKE SILENT: a second assignment compiles clean and drops the first key,
-    // so `ARAGON_BASH_BACKGROUND=0 ARAGON_BASH_AUTO_BACKGROUND=0` would quietly
-    // re-register the tools the user turned off.
     const bashBackground = process.env.ARAGON_BASH_BACKGROUND?.trim().toLowerCase();
     const bashAuto = process.env.ARAGON_BASH_AUTO_BACKGROUND?.trim().toLowerCase();
     if ((bashBackground !== undefined && bashBackground.length > 0) ||
@@ -300,22 +242,6 @@ export function readEnvConfig() {
         if (Object.keys(section).length > 0)
             partial.bash = section;
     }
-    // ARAGON_RETRY=0 is the kill switch for API retry; ARAGON_RETRY_MAX=<n>
-    // overrides the count. Parsed by the POSITIVE list, exactly as
-    // ARAGON_FULLSCREEN / ARAGON_MOUSE / ARAGON_PLAN / ARAGON_TEAM / ARAGON_TODO
-    // are — NOT by `envBool` below, which uses a negative list.
-    //
-    // TWO VARS ONLY, and no third for the delays: every env var in this file exists
-    // because a flag and a config file are BOTH unreachable in the channel it
-    // serves, and nobody tunes a backoff multiplier from a container entrypoint.
-    //
-    // `>= 0`, NOT `> 0`, and the difference is the whole point (R-16).
-    // `ARAGON_TEAM_MAX` above guards `parsed > 0`, which is right for a fan-out
-    // width and wrong here: `0` is this key's documented floor AND its kill switch,
-    // so a `> 0` guard would drop `ARAGON_RETRY_MAX=0` on the floor and leave the
-    // user with the default 10. "Left ABSENT when unparseable" still holds and
-    // still matters — an unparseable value must not look permanently supplied, or
-    // the config file can never win again.
     const retry = process.env.ARAGON_RETRY?.trim().toLowerCase();
     const retryMax = process.env.ARAGON_RETRY_MAX?.trim();
     if ((retry !== undefined && retry.length > 0) || (retryMax !== undefined && retryMax.length > 0)) {
@@ -333,26 +259,6 @@ export function readEnvConfig() {
         if (Object.keys(section).length > 0)
             partial.retry = section;
     }
-    // ARAGON_FAST=1 turns the fast model tier on; the other three name it
-    // (fast-model-tier §4.3). Parsed by the POSITIVE list, exactly as
-    // ARAGON_FULLSCREEN / ARAGON_MOUSE / ARAGON_PLAN / ARAGON_TEAM / ARAGON_TODO /
-    // ARAGON_RETRY are — NOT by `envBool` below, whose NEGATIVE list disagrees with
-    // it on values like `ARAGON_FAST=disable`.
-    //
-    // FOUR VARS, AND DELIBERATELY NO `ARAGON_FAST_REVIEW_EVERY` / `_MAX_CHARS` /
-    // `_DELEGATE` (D-14). The rule this file states is that an environment variable
-    // exists only where a flag AND a config file are BOTH unreachable — a
-    // container, an ssh session, being spawned by another tool. "Which model, and
-    // is it on" passes that test; tuning a review cadence does not, and every key
-    // that fails it is documentation debt plus a fifth place for the value to
-    // disagree with itself.
-    //
-    // ONE ACCUMULATED SECTION, ASSIGNED ONCE — the shape the `team`, `todo` and
-    // `retry` branches above all use, and NOT four `if` blocks each assigning
-    // `partial.fast`. THE CAST IS WHAT WOULD MAKE THAT MISTAKE SILENT: a second
-    // assignment compiles clean and drops `enabled`, so
-    // `ARAGON_FAST=1 ARAGON_FAST_MODEL=x` would quietly resolve with the tier off
-    // (the P1-4 defect this file records for `todo`).
     const fast = process.env.ARAGON_FAST?.trim().toLowerCase();
     const fastProvider = process.env.ARAGON_FAST_PROVIDER?.trim();
     const fastModel = process.env.ARAGON_FAST_MODEL?.trim();
@@ -376,25 +282,6 @@ export function readEnvConfig() {
         if (Object.keys(section).length > 0)
             partial.fast = section;
     }
-    // ARAGON_COMPACTION=0 turns context compaction off; the other two tune it
-    // (context-auto-compaction §4.3). Parsed by the POSITIVE list, exactly as
-    // ARAGON_FULLSCREEN / ARAGON_MOUSE / ARAGON_PLAN / ARAGON_TEAM / ARAGON_TODO /
-    // ARAGON_RETRY / ARAGON_FAST are — NOT by `envBool` below, whose NEGATIVE list
-    // disagrees with it on values like `ARAGON_COMPACTION=disable`.
-    //
-    // THREE VARS, AND DELIBERATELY NO `ARAGON_COMPACTION_ON_FAILURE` /
-    // `_USE_FAST_TIER` / `_WARN_THRESHOLD`. The rule this file states is that an
-    // environment variable exists only where a flag AND a config file are BOTH
-    // unreachable — a container, an ssh session, being spawned by another tool.
-    // "Is it on, when does it fire, and how much does it keep" passes that test;
-    // "what should it do if the summarizer 500s" does not, and every key that fails
-    // it is documentation debt plus a fifth place for the value to disagree with
-    // itself.
-    //
-    // ONE ACCUMULATED SECTION, ASSIGNED ONCE — the shape the four branches above
-    // all use, and NOT three `if` blocks each assigning `partial.compaction`. THE
-    // CAST IS WHAT WOULD MAKE THAT MISTAKE SILENT: a second assignment compiles
-    // clean and drops `enabled`.
     const compaction = process.env.ARAGON_COMPACTION?.trim().toLowerCase();
     const compactionThreshold = process.env.ARAGON_COMPACTION_THRESHOLD?.trim();
     const compactionKeepTurns = process.env.ARAGON_COMPACTION_KEEP_TURNS?.trim();
@@ -471,23 +358,12 @@ export function readEnvConfig() {
             partial.update = { mode };
         }
     }
-    // Render bounds (tui-render-performance §5.3). Same channel story as
-    // ARAGON_FULLSCREEN: a container or a wrapper that owns argv can reach neither
-    // a flag nor a config file, and a session that freezes is exactly the case
-    // where the user needs a knob they can turn from the outside.
-    //
-    // ARAGON_TRANSCRIPT_RETAIN / ARAGON_MAX_RENDER_INTERVAL_MS are left ABSENT
-    // when unparseable rather than written as a default, so the config file can
-    // still win — the rule `ARAGON_TEAM_MAX` above records.
     const retain = process.env.ARAGON_TRANSCRIPT_RETAIN?.trim();
     if (retain !== undefined && retain.length > 0) {
         const parsed = Number.parseInt(retain, 10);
         if (Number.isFinite(parsed) && parsed > 0)
             partial.transcriptRetain = parsed;
     }
-    // Parsed by the POSITIVE list, exactly as ARAGON_FULLSCREEN / ARAGON_MOUSE /
-    // ARAGON_PLAN / ARAGON_TEAM / ARAGON_TODO are — NOT by `envBool` below, which
-    // uses a negative list. The two readers disagree on `ARAGON_RENDER_GOVERNOR=disable`.
     const governor = process.env.ARAGON_RENDER_GOVERNOR?.trim().toLowerCase();
     if (governor !== undefined && governor.length > 0) {
         partial.renderGovernor =
@@ -499,12 +375,6 @@ export function readEnvConfig() {
         if (Number.isFinite(parsed) && parsed > 0)
             partial.maxRenderIntervalMs = parsed;
     }
-    // ARAGON_DIFF_RENDER=0 restores the pre-fix full-frame repaint;
-    // ARAGON_SYNC_OUTPUT=0 drops the DEC 2026 envelope (tui-input-flicker-fix
-    // §5.3). Parsed by the POSITIVE list, exactly as ARAGON_FULLSCREEN /
-    // ARAGON_MOUSE / ARAGON_PLAN / ARAGON_TEAM / ARAGON_TODO / ARAGON_RENDER_GOVERNOR
-    // are — NOT by `envBool` below, whose NEGATIVE list disagrees with it on values
-    // like `ARAGON_DIFF_RENDER=disable`.
     const diffRender = process.env.ARAGON_DIFF_RENDER?.trim().toLowerCase();
     if (diffRender !== undefined && diffRender.length > 0) {
         partial.diffRender =

package/dist/config/load.d.ts

@@ -19,8 +19,6 @@ export interface CliFlags {
     confirm?: boolean;
     toolTimeout?: string | number;
     idleTimeout?: string | number;
-    /** `--fullscreen` ⇒ true, `--no-fullscreen` ⇒ false, absent ⇒ undefined. */
-    fullscreen?: boolean;
     /** `--no-exit-transcript` ⇒ false. */
     exitTranscript?: boolean;
     /** `--compact` ⇒ true, `--no-compact` ⇒ false, absent ⇒ undefined. */

package/dist/config/load.js

@@ -23,32 +23,11 @@ function envFlagTrue(value) {
     const v = value.trim().toLowerCase();
     return v === '1' || v === 'true' || v === 'on' || v === 'yes';
 }
-/**
- * Resolve the tri-state full-screen preference (see `CliConfig.fullscreen`).
- * Only a flag or the env var counts as an explicit FORCE; a config file holding
- * the default `true` must not disable the automatic downgrades.
- */
-function resolveFullscreen(flags, env, file) {
-    if (flags.fullscreen !== undefined)
-        return flags.fullscreen;
-    if (env.fullscreen !== undefined)
-        return env.fullscreen;
-    if (file.fullscreen === false)
-        return false;
-    return undefined;
-}
 /**
  * Resolve wheel region routing: flag › env › file › default `true`.
  *
- * THIS NEEDS ITS OWN RESOLVER; it does not "match every other boolean" in this
- * file. `hints` is `flags.hints !== undefined ? … : file.hints ?? DEFAULT` and
- * reads NO ENV AT ALL — copying that line would ship `ARAGON_MOUSE` as
- * documented-but-dead (P1-9). Only `fullscreen` has an env layer, and only
- * because `resolveFullscreen` above was written to give it one.
- *
- * Unlike `fullscreen` this is a plain boolean rather than a tri-state: there
- * are no heuristics for an explicit `true` to override, so a persisted `true`
- * is just a value and not an opinion that has to be told apart from silence.
+ * Unlike `hints`, mouse routing accepts an environment override. Keep that
+ * layer explicit so ARAGON_MOUSE works even when a wrapper owns the arguments.
  */
 function resolveMouse(flags, env, file) {
     if (flags.mouse !== undefined)
@@ -463,12 +442,6 @@ export function loadConfig(flags = {}) {
     const read = readConfigFile();
     const file = read.config ?? {};
     const env = readEnvConfig();
-    // A config file that exists but will not parse used to reset EVERY setting
-    // with nothing anywhere explaining it. The fallback is unchanged; what is new
-    // is that it leaves a trace. The record alone is not the explanation, so the
-    // two owners of a user-visible channel say it too: `main()` writes one stderr
-    // line (headless, inline and every subcommand) and `App.tsx` raises a toast
-    // (full-screen, where the alternate screen wipes that line away).
     if (read.parseError) {
         getLogger().error('config', 'config_parse_failed', { error: read.parseError });
     }
@@ -580,7 +553,6 @@ export function loadConfig(flags = {}) {
         contextWindow,
         theme,
         reducedMotion,
-        fullscreen: resolveFullscreen(flags, env.partial, file),
         exitTranscript: flags.exitTranscript !== undefined
             ? flags.exitTranscript
             : file.exitTranscript ?? DEFAULT_CONFIG.exitTranscript,
@@ -658,7 +630,6 @@ function recordResolvedConfig(config) {
         // "why is my output truncated" was unanswerable after the fact.
         maxTokens: config.maxTokens ?? 'auto',
         theme: config.theme,
-        fullscreen: config.fullscreen,
         toolTimeoutMs: config.toolTimeoutMs,
         idleTimeoutMs: config.idleTimeoutMs,
         historyEnabled: config.historyEnabled,

package/dist/config/schema.d.ts

@@ -729,7 +729,6 @@ export interface PersistedConfig {
     /** Replace spinners with a static glyph for calmer, low-motion output. */
     reducedMotion: boolean;
     /** Full-screen TUI (still subject to the automatic downgrades in §4.1). */
-    fullscreen: boolean;
     /** Replay a plain-text session summary after leaving the alternate screen. */
     exitTranscript: boolean;
     /** Entries reachable by scrolling; older ones show the "collapsed" line (I-3). */
@@ -767,8 +766,7 @@ export interface PersistedConfig {
      * transcript, whatever row the pointer is on (wheel-scrolls-transcript-only
      * §4.1).
      *
-     * A PLAIN BOOLEAN, not a `fullscreen`-style tri-state: there are no
-     * heuristics for an explicit `true` to override (D-10).
+     * A plain boolean: persisted values and per-run overrides use the same meaning.
      */
     mouse: boolean;
     /**
@@ -881,17 +879,6 @@ export interface CliConfig {
     contextWindow: number | null;
     theme: ThemeName;
     reducedMotion: boolean;
-    /**
-     * TRI-STATE, and deliberately so (spec §4.1 vs §6.2):
-     *   `false`     — an explicit opt-out from any layer; always inline.
-     *   `true`      — an explicit FORCE, only from `--fullscreen` / `ARAGON_FULLSCREEN=1`;
-     *                 overrides the TERM/CI/size heuristics.
-     *   `undefined` — no explicit choice (including a config file holding the
-     *                 default `true`); full-screen with the heuristics live.
-     * Folding the persisted default into `true` would turn every user's config
-     * file into a permanent "ignore the CI and TERM=dumb downgrades" switch.
-     */
-    fullscreen?: boolean;
     /** Replay a plain-text summary on exit (full-screen only — see §4.4). */
     exitTranscript: boolean;
     /** Entries reachable by scrolling; older ones show the "collapsed" line (I-3). */

package/dist/config/schema.js

@@ -879,7 +879,6 @@ export const DEFAULT_CONFIG = {
     contextWindow: null,
     theme: 'auto',
     reducedMotion: false,
-    fullscreen: true,
     exitTranscript: true,
     transcriptWindow: DEFAULT_TRANSCRIPT_WINDOW,
     transcriptRetain: DEFAULT_TRANSCRIPT_RETAIN,

package/dist/config/store.js

@@ -69,6 +69,8 @@ export function readConfigFile() {
         const raw = readFileSync(file, 'utf-8');
         const parsed = JSON.parse(raw);
         if (parsed && typeof parsed === 'object') {
+            // Retired layout preference: tolerate old files without restoring a UI mode.
+            delete parsed.fullscreen;
             return { config: parsed };
         }
         return { config: null, parseError: `${file} does not contain a JSON object` };

package/dist/input/interrupt-gesture.d.ts

@@ -0,0 +1,18 @@
+/** Confirmation window for two independent decoded Escape events. */
+export declare const INTERRUPT_CONFIRM_MS = 1500;
+export type InterruptGestureState = {
+    phase: 'ready';
+} | {
+    phase: 'armed';
+    armedAt: number;
+} | {
+    phase: 'stopping';
+};
+export interface InterruptGestureResult {
+    state: InterruptGestureState;
+    action: 'hint' | 'abort' | 'force-stop';
+}
+/** Advance using a monotonic clock; the caller owns the current run's lifetime. */
+export declare function advanceInterruptGesture(state: InterruptGestureState, now: number): InterruptGestureResult;
+/** Other input cancels confirmation, but cannot undo an already requested stop. */
+export declare function cancelInterruptConfirmation(state: InterruptGestureState): InterruptGestureState;

package/dist/input/interrupt-gesture.js

@@ -0,0 +1,19 @@
+/** Confirmation window for two independent decoded Escape events. */
+export const INTERRUPT_CONFIRM_MS = 1500;
+/** Advance using a monotonic clock; the caller owns the current run's lifetime. */
+export function advanceInterruptGesture(state, now) {
+    if (state.phase === 'stopping') {
+        return { state: { phase: 'ready' }, action: 'force-stop' };
+    }
+    if (state.phase === 'armed') {
+        const elapsed = now - state.armedAt;
+        if (elapsed >= 0 && elapsed <= INTERRUPT_CONFIRM_MS) {
+            return { state: { phase: 'stopping' }, action: 'abort' };
+        }
+    }
+    return { state: { phase: 'armed', armedAt: now }, action: 'hint' };
+}
+/** Other input cancels confirmation, but cannot undo an already requested stop. */
+export function cancelInterruptConfirmation(state) {
+    return state.phase === 'armed' ? { phase: 'ready' } : state;
+}

package/dist/input/pointer-router.d.ts

@@ -0,0 +1,11 @@
+import type { MouseEvent } from './mouse-events.js';
+import type { MouseSource } from './stdin-filter.js';
+export interface PointerRouter {
+    selectionSource: MouseSource;
+    dispose(): void;
+}
+/** Deliver each button gesture to the scrollbar before the selection source. */
+export declare function createPointerRouter(options: {
+    source: MouseSource;
+    handle(event: MouseEvent): boolean;
+}): PointerRouter;

package/dist/input/pointer-router.js

@@ -0,0 +1,14 @@
+/** Deliver each button gesture to the scrollbar before the selection source. */
+export function createPointerRouter(options) {
+    const listeners = new Set();
+    const unsubscribe = options.source.subscribe((event) => {
+        if (event.kind !== 'wheel' && options.handle(event))
+            return;
+        for (const listener of listeners)
+            listener(event);
+    });
+    return { selectionSource: { subscribe: (listener) => {
+                listeners.add(listener);
+                return () => { listeners.delete(listener); };
+            } }, dispose: () => { unsubscribe(); listeners.clear(); } };
+}

package/dist/logging/install.d.ts

@@ -25,7 +25,7 @@
  *       Adding a listener suppresses it, turning a crash into a silent hang.
  *
  *   `SIGINT` / `SIGTERM` / `SIGHUP` — the handlers in `runInteractive()` exist
- *       ONLY in its full-screen branch, so inline mode, `-p`, and every
+ *       ONLY in its full-screen branch, so `-p` and every
  *       subcommand had no handler at all and took Node's default termination,
  *       which does not run `'exit'` listeners: the whole queue was lost. But a
  *       signal listener registered here runs BEFORE the one `runInteractive`
@@ -45,7 +45,7 @@ import { Logger, type LogScope } from './logger.js';
 export declare function setScreenRestore(fn: () => void): void;
 /**
  * Replace what a signal does after the flush. The default (a bare
- * `exit(128 + signo)`) is correct for headless, inline and every subcommand;
+ * `exit(128 + signo)`) is correct for headless and every subcommand;
  * full-screen substitutes one that restores the terminal first.
  *
  * A TERMINATOR MAY NOW RETURN WITHOUT EXITING, AND THAT IS A CONTRACT CHANGE

package/dist/logging/install.js

@@ -25,7 +25,7 @@
  *       Adding a listener suppresses it, turning a crash into a silent hang.
  *
  *   `SIGINT` / `SIGTERM` / `SIGHUP` — the handlers in `runInteractive()` exist
- *       ONLY in its full-screen branch, so inline mode, `-p`, and every
+ *       ONLY in its full-screen branch, so `-p` and every
  *       subcommand had no handler at all and took Node's default termination,
  *       which does not run `'exit'` listeners: the whole queue was lost. But a
  *       signal listener registered here runs BEFORE the one `runInteractive`
@@ -63,7 +63,7 @@ export function setScreenRestore(fn) {
 }
 /**
  * Replace what a signal does after the flush. The default (a bare
- * `exit(128 + signo)`) is correct for headless, inline and every subcommand;
+ * `exit(128 + signo)`) is correct for headless and every subcommand;
  * full-screen substitutes one that restores the terminal first.
  *
  * A TERMINATOR MAY NOW RETURN WITHOUT EXITING, AND THAT IS A CONTRACT CHANGE

package/dist/todo/follow-through.d.ts

@@ -84,10 +84,6 @@ export type FollowThroughDecision = {
 };
 /** The zero budget. A fresh App, a fresh headless run, and every cleared list. */
 export declare function emptyBudget(): FollowThroughBudget;
-/**
- * The decision. EVALUATED IN THIS ORDER, AND THE ORDER IS SEMANTICS, NOT STYLE —
- * the same sentence `decideRenderMode` carries.
- */
 export declare function decideFollowThrough(input: FollowThroughInput): FollowThroughDecision;
 /**
  * Fold a finished run into the budget. Called BEFORE `decideFollowThrough`, on

package/dist/todo/follow-through.js

@@ -36,10 +36,6 @@ function legacyUnfinishedNotice(left) {
 function advise(interactive, text) {
     return interactive ? ` ${text}` : '';
 }
-/**
- * The decision. EVALUATED IN THIS ORDER, AND THE ORDER IS SEMANTICS, NOT STYLE —
- * the same sentence `decideRenderMode` carries.
- */
 export function decideFollowThrough(input) {
     const { mode, snapshot, runEnd, budget, interactive } = input;
     // 1. Nothing is unfinished. `beginUserTurn` already drops a fully-completed

package/dist/todo/limits.d.ts

@@ -38,16 +38,6 @@ export declare const TODO_LIMITS: {
     readonly panelFullRows: 6;
     /** Below this many terminal columns the status-bar counter degrades to `[3/7]`. */
     readonly statusCompactCols: 100;
-    /**
-     * Below this many columns the inline strip drops its `+N done` suffix
-     * (todo-plan-followthrough §3.7 / D-19).
-     *
-     * NAMED RATHER THAN INLINED, and the reason is that it sits between two other
-     * real bounds — `statusCompactCols` (100) above and `MIN_FULLSCREEN_COLS` (40)
-     * in `frame.ts` — with nothing to tell a reader whether a bare `80` in the
-     * component was a third policy or a typo for one of them.
-     */
-    readonly stripDoneCols: 80;
     /**
      * 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

@@ -38,16 +38,6 @@ export const TODO_LIMITS = {
     panelFullRows: 6,
     /** Below this many terminal columns the status-bar counter degrades to `[3/7]`. */
     statusCompactCols: 100,
-    /**
-     * Below this many columns the inline strip drops its `+N done` suffix
-     * (todo-plan-followthrough §3.7 / D-19).
-     *
-     * NAMED RATHER THAN INLINED, and the reason is that it sits between two other
-     * real bounds — `statusCompactCols` (100) above and `MIN_FULLSCREEN_COLS` (40)
-     * in `frame.ts` — with nothing to tell a reader whether a bare `80` in the
-     * component was a third policy or a typo for one of them.
-     */
-    stripDoneCols: 80,
     /**
      * 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/prompt.d.ts

@@ -22,21 +22,6 @@
 import { TODO_BLOCK_VERSION } from './limits.js';
 export { TODO_BLOCK_VERSION };
 export interface TodoBlockParams {
-    /**
-     * Whether this session can actually render the rail.
-     *
-     * FOUR SUPPORTED PATHS HAVE THE TOOL AND NO PANEL — `-p` (§3.12), inline mode
-     * (non-goal 4), `--no-todo-panel` (§4.3), and a terminal under 80 columns or 6
-     * viewport rows (§6.4) — and in the first three the answer is fixed for the
-     * whole session, before the prompt is composed. Telling the model about a
-     * panel the user does not have is the same error `composeSystemPrompt` already
-     * guards against for team mode with its TWO flags (P1-6 / D-24).
-     *
-     * Dropping the block instead would be wrong: the planning discipline is worth
-     * having without the column, which is precisely why `enabled` and `panel` are
-     * separate config keys, and a screen-reader user is the case that argument was
-     * written for.
-     */
     panelVisible: boolean;
 }
 /**

package/dist/todo/store.d.ts

@@ -9,15 +9,9 @@
  * is why `AgentController` can own this object as unconditionally as it owns
  * `TeamRuntime`.
  *
- * INVARIANT I-2 — the list is a PROJECTION OF WHAT THE MODEL BELIEVES, and
- * nothing that does not tell the model may change it — EXCEPT AN EXPLICIT USER
- * INSTRUCTION, which is the rule's standing exception and is marked
- * `TodoClearReason = 'user'`. Two commands come through that door: `/todo clear`
- * and `/clear`. Neither tells the model anything, and that is fine, because what
- * they leave behind is "panel absent, model still remembers" - the direction I-9
- * below calls safe, and one the model's next full-replacement write heals on its
- * own. `/reset` (reason `'reset'`) remains the only clear caused by the belief
- * itself being destroyed, because it clears `messages`.
+ * The list projects the current plan. Explicit clear/reset and a new TUI task
+ * may remove that projection while the model still remembers the old plan.
+ * Continuations preserve it; legacy callers retain completion/staleness rules.
  *
  * Every write is a FULL REPLACEMENT and every clear is a FULL REMOVAL - there is
  * no partial update anywhere, which is what makes I-9 ("the panel is never a
@@ -73,11 +67,12 @@ export declare class TodoStore {
      * asymmetry for free, which is the behaviour you want: a steer must not age
      * out the plan it is steering.
      *
-     * A FULLY-COMPLETED LIST IS DROPPED HERE rather than at `agent_end`. Ending
-     * the run is exactly when the user wants to see `7/7 done`; wiping it there
-     * would replace a moment of feedback with a blank column (D-6).
+     * A new TUI task drops the old plan here, while a continuation preserves it.
+     * With no policy, legacy callers retain completed/stale-plan expiration.
+     * Clearing at `agent_end` would erase the final progress before the user can
+     * inspect it and remove the plan that automatic continuation still needs.
      */
-    beginUserTurn(): void;
+    beginUserTurn(policy?: 'new-task' | 'continue'): void;
     /**
      * Report a refusal that never reached `write()` (§3.3 steps 1 and 2).
      *

package/dist/todo/store.js

@@ -9,15 +9,9 @@
  * is why `AgentController` can own this object as unconditionally as it owns
  * `TeamRuntime`.
  *
- * INVARIANT I-2 — the list is a PROJECTION OF WHAT THE MODEL BELIEVES, and
- * nothing that does not tell the model may change it — EXCEPT AN EXPLICIT USER
- * INSTRUCTION, which is the rule's standing exception and is marked
- * `TodoClearReason = 'user'`. Two commands come through that door: `/todo clear`
- * and `/clear`. Neither tells the model anything, and that is fine, because what
- * they leave behind is "panel absent, model still remembers" - the direction I-9
- * below calls safe, and one the model's next full-replacement write heals on its
- * own. `/reset` (reason `'reset'`) remains the only clear caused by the belief
- * itself being destroyed, because it clears `messages`.
+ * The list projects the current plan. Explicit clear/reset and a new TUI task
+ * may remove that projection while the model still remembers the old plan.
+ * Continuations preserve it; legacy callers retain completion/staleness rules.
  *
  * Every write is a FULL REPLACEMENT and every clear is a FULL REMOVAL - there is
  * no partial update anywhere, which is what makes I-9 ("the panel is never a
@@ -137,13 +131,18 @@ export class TodoStore {
      * asymmetry for free, which is the behaviour you want: a steer must not age
      * out the plan it is steering.
      *
-     * A FULLY-COMPLETED LIST IS DROPPED HERE rather than at `agent_end`. Ending
-     * the run is exactly when the user wants to see `7/7 done`; wiping it there
-     * would replace a moment of feedback with a blank column (D-6).
+     * A new TUI task drops the old plan here, while a continuation preserves it.
+     * With no policy, legacy callers retain completed/stale-plan expiration.
+     * Clearing at `agent_end` would erase the final progress before the user can
+     * inspect it and remove the plan that automatic continuation still needs.
      */
-    beginUserTurn() {
-        if (this.items.length === 0)
+    beginUserTurn(policy) {
+        if (this.items.length === 0 || policy === 'continue')
+            return;
+        if (policy === 'new-task') {
+            this.clear('turn');
             return;
+        }
         if (this.items.every((item) => item.status === 'completed')) {
             this.clear('turn');
             return;

package/dist/todo/types.d.ts

@@ -45,7 +45,8 @@ export interface TodoSnapshot {
  *   `user`  - `/todo clear`, or `/clear`. Both are an explicit user instruction,
  *             which is I-2's standing exception; neither touches `messages`.
  *   `reset` - `/reset`, or a `/resume` whose file carried no list (§3.13).
- *   `turn`  - every item was completed when the next user turn started.
+ *   `turn`  - a new TUI task started, or a legacy caller began a turn after
+ *             every item was completed.
  *   `stale` - unfinished, and unwritten for more than `TODO_LIMITS.staleTurns`
  *             consecutive turns (§3.2 / P1-7).
  */