@aragon-agent/cli 0.5.6 → 0.5.9

package/dist/ui/layout/regions.d.ts

@@ -1,55 +0,0 @@
-/**
- * Wheel band hit-testing (mouse-wheel-region-routing §4.5) — pure, React-free.
- *
- * The requirement is stated in terms of REGIONS ("scrolling over the agent area
- * scrolls the transcript; scrolling over the input box steps prompt history"),
- * so the router needs to turn a reported terminal row into one of two bands.
- *
- * The boundary is MEASURED, never computed from `budget.ts`. That arithmetic
- * describes the PLANNED chrome, but the real bottom chrome grows and shrinks at
- * run time: the toast row comes and goes, the hint row is dropped below
- * `HINT_MIN_ROWS`, and the autocomplete popup adds up to nine rows. Routing off
- * the plan would put the boundary in the wrong place exactly when the popup is
- * open — the moment precision matters most (D-5 / D-16).
- */
-export type WheelBand = 'content' | 'composer';
-export interface FrameGeometry {
-    /**
-     * 1-based row of the frame's first row. 1 in the alternate screen.
-     *
-     * This is DERIVED, not assumed, and it has a named dependency: it holds
-     * because the full-screen transcript renders no `<Static>`
-     * (`Transcript.tsx`), so Ink's `log-update` writes `frameHeight(rows) = rows-1`
-     * lines plus a newline into a `rows`-row buffer — nothing scrolls, and the
-     * frame sits at rows `1 … rows-1` with the cursor parked on the undrawn last
-     * row. Reintroducing `<Static>` into the full-screen path pushes the frame
-     * down the screen and silently biases every hit test; whoever does that has
-     * to change `top` here at the same time.
-     */
-    top: number;
-    /** Rows the frame occupies — `frameHeight(rows)`. */
-    height: number;
-    /** Measured rows of the bottom chrome (toast + composer + status). */
-    bottom: number;
-}
-/**
- * The "I do not know where the frame is" value.
- *
- * `App` writes it into the geometry ref on every render path that does NOT
- * render the full-screen `AppShell` — the terminal-too-small placeholder and
- * inline mode — so a stale measurement can never outlive the frame it
- * described. There is deliberately no arithmetic fallback: an unmeasured frame
- * routes to `'content'`, which is the band that cannot destroy anything, and
- * one invisible frame after a resize is a better failure than a wrong band
- * (§4.5, P1-5 / D-16).
- */
-export declare const UNMEASURED_GEOMETRY: FrameGeometry;
-/**
- * Which band does terminal row `y` belong to?
- *
- * Fails toward `'content'`: the whole point of this feature is that a wheel
- * notch must never edit the user's draft (I-3), so every degenerate input —
- * nothing measured yet, a row outside the frame, a chrome measurement that
- * swallowed the screen — resolves to the harmless direction.
- */
-export declare function hitTestWheel(y: number, geometry: FrameGeometry): WheelBand;

package/dist/ui/layout/regions.js

@@ -1,52 +0,0 @@
-/**
- * Wheel band hit-testing (mouse-wheel-region-routing §4.5) — pure, React-free.
- *
- * The requirement is stated in terms of REGIONS ("scrolling over the agent area
- * scrolls the transcript; scrolling over the input box steps prompt history"),
- * so the router needs to turn a reported terminal row into one of two bands.
- *
- * The boundary is MEASURED, never computed from `budget.ts`. That arithmetic
- * describes the PLANNED chrome, but the real bottom chrome grows and shrinks at
- * run time: the toast row comes and goes, the hint row is dropped below
- * `HINT_MIN_ROWS`, and the autocomplete popup adds up to nine rows. Routing off
- * the plan would put the boundary in the wrong place exactly when the popup is
- * open — the moment precision matters most (D-5 / D-16).
- */
-/**
- * The "I do not know where the frame is" value.
- *
- * `App` writes it into the geometry ref on every render path that does NOT
- * render the full-screen `AppShell` — the terminal-too-small placeholder and
- * inline mode — so a stale measurement can never outlive the frame it
- * described. There is deliberately no arithmetic fallback: an unmeasured frame
- * routes to `'content'`, which is the band that cannot destroy anything, and
- * one invisible frame after a resize is a better failure than a wrong band
- * (§4.5, P1-5 / D-16).
- */
-export const UNMEASURED_GEOMETRY = { top: 1, height: 0, bottom: 0 };
-/**
- * Which band does terminal row `y` belong to?
- *
- * Fails toward `'content'`: the whole point of this feature is that a wheel
- * notch must never edit the user's draft (I-3), so every degenerate input —
- * nothing measured yet, a row outside the frame, a chrome measurement that
- * swallowed the screen — resolves to the harmless direction.
- */
-export function hitTestWheel(y, geometry) {
-    const { top, height } = geometry;
-    if (!Number.isFinite(height) || height <= 0)
-        return 'content';
-    if (!Number.isFinite(y))
-        return 'content';
-    // Clamp into the frame so the one undrawn bottom row — and any off-by-one
-    // from a terminal that reports 0-based rows — lands on a real band instead of
-    // being dropped.
-    const row = Math.min(Math.max(Math.floor(y), top), top + height - 1);
-    // I-6: at least one content row always survives. This clamp is a backstop
-    // that should never fire, and that is checkable rather than hopeful: the
-    // completion popup is capped at `viewportRows(rows) - 4`, so the measured
-    // chrome tops out at `rows - 6` against a frame of `rows - 1` — five content
-    // rows survive the worst case the layout can produce.
-    const bottom = Math.min(Math.max(Math.floor(geometry.bottom) || 0, 0), height - 1);
-    return row >= top + height - bottom ? 'composer' : 'content';
-}