@aragon-agent/cli 0.6.7 → 0.6.9

package/dist/ui/use-startup-notices.d.ts

@@ -40,53 +40,7 @@ export declare const MOUSE_NOTICE_VERSION = 1;
  * that offered only `/plan`, recorded back when this was a boolean.
  */
 export declare const VT_INPUT_NOTICE_VERSION = 1;
-/**
- * The `shift-tab-and-mouse-wheel-dead-on-some-terminals` notice (F1'). Shown at
- * most once per `VT_INPUT_NOTICE_VERSION`, and only on a Windows console that
- * cannot deliver either input — see `ui/win-vt-input.ts` for why that is a
- * property of the Node version rather than of the terminal.
- *
- * IT NAMES WHAT THE KEY DOES NOW, not merely that it is unavailable, and that
- * is the load-bearing half of the text. `Shift+Tab` on these machines is not
- * inert: the modifier is lost inside libuv, so Ink sees an ordinary `Tab` and
- * the `/` palette or an `@` popup completes its selection over the user's
- * draft. A user told only "this key does not work" keeps pressing it and keeps
- * losing text without ever connecting the two.
- *
- * THE FALLBACK KEY COMES BEFORE `/plan` IN BOTH BRANCHES, and it is named from
- * `MODE_TOGGLE_KEYS` rather than spelled out, so the four consumers of that
- * constant cannot drift apart. This notice is the last one of them to be wired
- * up, and it is also the only channel that reaches the affected user without
- * being asked to: the composer hint does not exist at all in inline mode and is
- * switched off by a short terminal or `hints: false` in full-screen, and
- * `/help` has to be typed by someone whose current belief is "the key does
- * nothing" rather than "I should read the help". Ordering follows cost — one
- * keystroke before four and a return.
- *
- * `Shift+Up` / `Shift+Down` is the scroll workaround named here because it is
- * the only one PROVEN to survive: both Node versions emit `\x1b[1;2A` for it,
- * byte for byte, in the probe data. `PgUp` / `PgDn` is expected to work too but
- * was never injected, so it is left out rather than promised.
- *
- * THE WHEEL HALF IS FULL-SCREEN ONLY, and dropping it inline is not a detail.
- * `Shift+Tab` is broken in both modes — the modifier dies inside libuv, well
- * below anything this app chooses — but the wheel is only ours to lose in
- * full-screen: inline never asks the console to report it (`mode` is a conjunct
- * of `cli.tsx::wantMouse`), so the wheel goes on scrolling the terminal's own
- * scrollback exactly as it always has. And `Shift+Up` / `Shift+Down` are handled
- * inside `App`'s `if (fullscreen)` branch, so recommending them inline names a
- * key that does nothing. Telling an inline user their working wheel is dead and
- * then handing them an inert workaround is the same failure this notice exists
- * to end — advice about a mode that is not running — merely pointed the other
- * way.
- *
- * EXPORTED FOR ITS TEST, unlike the two notices above it. Asserting this text
- * through a rendered frame does not work: the transcript wraps a notice at two
- * columns wider than it displays it, so any phrase landing on a wrap boundary
- * loses a character or two on the way to `lastFrame()` and the assertion fails
- * for a reason that has nothing to do with the text.
- */
-export declare function vtInputDeadNotice(nodeVersion: string, fullscreen: boolean): string;
+export declare function vtInputDeadNotice(nodeVersion: string): string;
 /**
  * `{ requested, resolved }` when the raise happened, `undefined` otherwise —
  * i.e. `cfg.transcriptRetainRequested` and `cfg.transcriptRetain`.
@@ -132,16 +86,6 @@ export interface MouseNoticeOptions {
 export interface VtInputNoticeOptions {
     /** `process.versions.node`, quoted back so the user can act on it. */
     nodeVersion: string;
-    /**
-     * Whether this run owns the alternate screen, i.e. `App`'s own `fullscreen`.
-     *
-     * Selects which half of the text applies: inline keeps the wheel and loses the
-     * full-screen scroll keys, so it is told about `Shift+Tab` and nothing else
-     * (see `vtInputDeadNotice`). Taken from the caller rather than re-derived here
-     * for the same reason the version is — one source, no chance of the notice and
-     * the renderer disagreeing about which mode is running.
-     */
-    fullscreen: boolean;
     /**
      * Record that `VT_INPUT_NOTICE_VERSION` was shown (`state.json`). Called once,
      * after dispatch — and it must write that constant, not `true`: the gate

package/dist/ui/use-startup-notices.js

@@ -80,61 +80,11 @@ function retainRaisedNotice(requested, resolved) {
  * that offered only `/plan`, recorded back when this was a boolean.
  */
 export const VT_INPUT_NOTICE_VERSION = 1;
-/**
- * The `shift-tab-and-mouse-wheel-dead-on-some-terminals` notice (F1'). Shown at
- * most once per `VT_INPUT_NOTICE_VERSION`, and only on a Windows console that
- * cannot deliver either input — see `ui/win-vt-input.ts` for why that is a
- * property of the Node version rather than of the terminal.
- *
- * IT NAMES WHAT THE KEY DOES NOW, not merely that it is unavailable, and that
- * is the load-bearing half of the text. `Shift+Tab` on these machines is not
- * inert: the modifier is lost inside libuv, so Ink sees an ordinary `Tab` and
- * the `/` palette or an `@` popup completes its selection over the user's
- * draft. A user told only "this key does not work" keeps pressing it and keeps
- * losing text without ever connecting the two.
- *
- * THE FALLBACK KEY COMES BEFORE `/plan` IN BOTH BRANCHES, and it is named from
- * `MODE_TOGGLE_KEYS` rather than spelled out, so the four consumers of that
- * constant cannot drift apart. This notice is the last one of them to be wired
- * up, and it is also the only channel that reaches the affected user without
- * being asked to: the composer hint does not exist at all in inline mode and is
- * switched off by a short terminal or `hints: false` in full-screen, and
- * `/help` has to be typed by someone whose current belief is "the key does
- * nothing" rather than "I should read the help". Ordering follows cost — one
- * keystroke before four and a return.
- *
- * `Shift+Up` / `Shift+Down` is the scroll workaround named here because it is
- * the only one PROVEN to survive: both Node versions emit `\x1b[1;2A` for it,
- * byte for byte, in the probe data. `PgUp` / `PgDn` is expected to work too but
- * was never injected, so it is left out rather than promised.
- *
- * THE WHEEL HALF IS FULL-SCREEN ONLY, and dropping it inline is not a detail.
- * `Shift+Tab` is broken in both modes — the modifier dies inside libuv, well
- * below anything this app chooses — but the wheel is only ours to lose in
- * full-screen: inline never asks the console to report it (`mode` is a conjunct
- * of `cli.tsx::wantMouse`), so the wheel goes on scrolling the terminal's own
- * scrollback exactly as it always has. And `Shift+Up` / `Shift+Down` are handled
- * inside `App`'s `if (fullscreen)` branch, so recommending them inline names a
- * key that does nothing. Telling an inline user their working wheel is dead and
- * then handing them an inert workaround is the same failure this notice exists
- * to end — advice about a mode that is not running — merely pointed the other
- * way.
- *
- * EXPORTED FOR ITS TEST, unlike the two notices above it. Asserting this text
- * through a rendered frame does not work: the transcript wraps a notice at two
- * columns wider than it displays it, so any phrase landing on a wrap boundary
- * loses a character or two on the way to `lastFrame()` and the assertion fails
- * for a reason that has nothing to do with the text.
- */
-export function vtInputDeadNotice(nodeVersion, fullscreen) {
+export function vtInputDeadNotice(nodeVersion) {
     const cause = `Node ${nodeVersion} on Windows does not turn on the console's VT input mode, so `;
     const cost = 'it will not switch mode, and with the / palette or an @ popup open it completes that ' +
         'instead, overwriting your draft. ';
     const toggle = `Press ${MODE_TOGGLE_KEYS.fallback} to switch mode instead (or /plan)`;
-    if (!fullscreen) {
-        return (`${cause}Shift+Tab never arrives: it comes through as a PLAIN TAB - ${cost}` +
-            `${toggle}. Node 22.17.0+ (or 24.2.0+) restores it.`);
-    }
     return (`${cause}two keys never arrive: the wheel sends nothing at all, and Shift+Tab arrives ` +
         `as a PLAIN TAB - ${cost}${toggle}, and Shift+Up / Shift+Down to scroll. ` +
         'Node 22.17.0+ (or 24.2.0+) restores both.');
@@ -199,7 +149,6 @@ export function useStartupNotices(dispatch, mouseNotice, retainNotice, vtInputNo
     const vtNoticeRef = useRef(vtInputNotice);
     vtNoticeRef.current = vtInputNotice;
     const vtNodeVersion = vtInputNotice?.nodeVersion;
-    const vtFullscreen = vtInputNotice?.fullscreen ?? false;
     const vtNoticeShown = useRef(false);
     useEffect(() => {
         if (vtNodeVersion === undefined || vtNoticeShown.current)
@@ -210,10 +159,10 @@ export function useStartupNotices(dispatch, mouseNotice, retainNotice, vtInputNo
         dispatch({
             type: 'notice',
             level: 'warn',
-            text: vtInputDeadNotice(vtNodeVersion, vtFullscreen),
+            text: vtInputDeadNotice(vtNodeVersion),
         });
         vtNoticeRef.current?.onSeen();
-    }, [vtNodeVersion, vtFullscreen, dispatch]);
+    }, [vtNodeVersion, dispatch]);
     // A `warn` notice rather than a toast: it is about a value the user typed, so
     // it belongs in the transcript where it can be scrolled back to, not in a row
     // that expires. DEPENDS ON THE TWO SCALARS, never on the options object —

package/dist/ui/use-wheel-routing.d.ts

@@ -30,7 +30,9 @@ import type { ScrollIntent } from './layout/scroll.js';
  */
 export declare const OVERLAY_PAGE = 8;
 export interface WheelRoutingOptions {
-    /** Absent when mouse support is off, in inline mode, or on a non-TTY. */
+    isPointerCaptured?: () => boolean;
+    isActive?: () => boolean;
+    /** Absent when mouse support is off, or on a non-TTY. */
     mouseSource?: MouseSource;
     /** Read at EVENT time for the routing branch, and again at FLUSH time (P1-3). */
     getOverlay: () => Overlay | null;

package/dist/ui/use-wheel-routing.js

@@ -61,6 +61,8 @@ export function useWheelRouting(options) {
         accumulator.current = null;
         if (!pending)
             return;
+        if (optionsRef.current.isPointerCaptured?.() || optionsRef.current.isActive?.() === false)
+            return;
         // P1-3: THE DECISION BELONGS AT FLUSH TIME, not at event time, because the
         // event-time decision is the one that goes stale. `App` swaps
         // `ScrollViewport` out for an overlay, and 16 ms is more than wide enough
@@ -93,6 +95,10 @@ export function useWheelRouting(options) {
         if (event.kind !== 'wheel')
             return;
         const current = optionsRef.current;
+        if (current.isPointerCaptured?.() || current.isActive?.() === false) {
+            clearCoalescer();
+            return;
+        }
         const overlay = current.getOverlay();
         // THE OVERLAY BRANCH IS EVALUATED FIRST AND RETURNS FOR EVERY OVERLAY IT
         // RECOGNIZES — the same two ordering rules the keyboard handler follows,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aragon-agent/cli",
-  "version": "0.6.7",
+  "version": "0.6.9",
   "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",
@@ -56,7 +56,7 @@
     "prepublishOnly": "npm run build"
   },
   "dependencies": {
-    "@aragon-agent/core": "^0.2.19",
+    "@aragon-agent/core": "^0.2.21",
     "chalk": "^5.6.2",
     "cli-highlight": "^2.0.0",
     "commander": "^12.1.0",

package/dist/ui/TodoStrip.d.ts

@@ -1,36 +0,0 @@
-/**
- * TodoStrip — the inline-mode plan surface (todo-plan-followthrough §3.7 / W2).
- *
- * ASCII ONLY: every glyph comes from `pickGlyphs`; a literal here bypasses the
- * capability probe and shows mojibake on a legacy console. This file is inside
- * the glyph scanner's scope because it is under `ui/`, NOT because of the
- * `todo/` clause (C-4) — moving it would not move the guard rail with it.
- *
- * WHY A STRIP AND NOT THE RAIL. `decideRenderMode` picks inline for every pipe,
- * every `CI=1`, every `TERM=dumb` and every terminal under 12 rows, and inline
- * has no fixed frame to hang a column off (round 1's non-goal 4). Before this,
- * such a session had the tool and a `todo 3/7` counter in the status bar, and no
- * way at all to see WHICH step was running (OQ-1).
- *
- * WHY NOT IN THE STATUS BAR. The bar's left cluster is `flexShrink={0}` and its
- * own comment records what happens when the row over-subscribes: Ink drops a
- * character from EACH cluster and it renders `idl` / `? hel`. A variable-length
- * step title cannot go there (C-7), which is what forces this into its own row.
- *
- * EXACTLY ONE RENDERED ROW, ALWAYS (AC-29). A strip that wrapped would push the
- * composer down by an unpredictable number of rows on every keystroke, which is
- * the worst possible behaviour for the mode with no frame to absorb it — hence
- * `wrap="truncate"` inside a `flexGrow`/`flexShrink` box and no exceptions.
- */
-import React from 'react';
-import type { Theme } from './theme.js';
-import type { TermCapabilities } from './capabilities.js';
-import type { TodoSnapshot } from '../todo/types.js';
-export interface TodoStripProps {
-    snapshot: TodoSnapshot;
-    /** Full terminal width; the strip spans the row in inline mode. */
-    cols: number;
-    theme: Theme;
-    caps: TermCapabilities;
-}
-export declare function TodoStrip({ snapshot, cols, theme, caps }: TodoStripProps): React.ReactElement;

package/dist/ui/TodoStrip.js

@@ -1,32 +0,0 @@
-import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
-import { Box, Text } from 'ink';
-import { pickGlyphs } from './glyphs.js';
-import { TODO_LIMITS } from '../todo/limits.js';
-import { todoAnchorIndex } from '../todo/panel-rows.js';
-export function TodoStrip({ snapshot, cols, theme, caps }) {
-    const glyphs = pickGlyphs(caps);
-    // THE SAME FUNCTION THE RAIL USES (R-9 / AC-30). Two surfaces that each decide
-    // for themselves which step is "current" is two surfaces that disagree, and
-    // this one is on screen in exactly the mode where the rail is not, so the
-    // disagreement would never be seen side by side and never be reported.
-    const anchor = todoAnchorIndex(snapshot.items);
-    const item = snapshot.items[anchor];
-    const active = item?.status === 'in_progress';
-    // `activeForm` while in progress, `content` otherwise — `TodoPanel`'s rule.
-    const label = item ? (active ? item.activeForm : item.content) : '';
-    // The same degradation the status bar already applies, so the two counters can
-    // never disagree about how much room they need.
-    const counter = cols >= TODO_LIMITS.statusCompactCols
-        ? `todo ${snapshot.doneCount}/${snapshot.total}`
-        : `[${snapshot.doneCount}/${snapshot.total}]`;
-    const showDone = snapshot.doneCount > 0 && cols >= TODO_LIMITS.stripDoneCols;
-    return (
-    // `width` IS LOAD-BEARING, exactly as it is on `TodoPanel` and for a related
-    // reason. Inline mode has no fixed frame, so nothing upstream constrains
-    // this row: without an explicit width the flexible middle cell is sized by
-    // whatever the parent offers, and a long item overflows the terminal and
-    // WRAPS — the one thing this component exists not to do. Pinning it here
-    // makes the truncation deterministic and self-contained rather than a
-    // property of the tree above.
-    _jsxs(Box, { flexDirection: "row", width: cols, overflow: "hidden", children: [_jsx(Box, { flexShrink: 0, children: _jsx(Text, { wrap: "truncate", color: theme.accent, children: counter }) }), _jsx(Box, { flexShrink: 0, children: _jsxs(Text, { wrap: "truncate", color: theme.muted, children: [' ', glyphs.arrowRight, ' '] }) }), _jsx(Box, { flexGrow: 1, flexShrink: 1, overflow: "hidden", children: _jsx(Text, { wrap: "truncate", color: active ? theme.primary : theme.muted, bold: active, children: label }) }), showDone && (_jsx(Box, { flexShrink: 0, children: _jsxs(Text, { wrap: "truncate", color: theme.muted, children: [' ', "+", snapshot.doneCount, " done"] }) }))] }));
-}