@aragon-agent/cli 0.6.39 → 0.6.40

package/dist/ui/overlays/team-fanout-state.d.ts

@@ -0,0 +1,73 @@
+/**
+ * Settings > Team fan-out: the pure half of the page (subagent-fanout 3.4.2).
+ *
+ * ASCII ONLY - `src/ui/**` is inside `glyphs.test.ts::inScope`.
+ *
+ * THE PAGE WRITES THREE KEYS AND CANNOT BE MADE TO WRITE A FOURTH (D-17 /
+ * R-P0-1). `TeamFanoutPatch` is `Pick<TeamConfig, 'maxSubagents' |
+ * 'maxConcurrent' | 'overseer'>`, and `stepFanoutValue` returns
+ * `Partial<TeamFanoutPatch>`: a width adjustment therefore CANNOT carry `model`
+ * or `modelProfileId` into `draft.patch.team`. That matters because
+ * `releasedSlots` reads those two keys as "the user re-decided the subagent
+ * slot", so a page that returned the whole section would silently release the
+ * model a session kit had just installed - and no test would notice, because
+ * every value on screen would still be right.
+ *
+ * EVERYTHING HERE IS A PURE FUNCTION over the draft. The page owns exactly one
+ * piece of state (its cursor); values come from the reducer, which is the same
+ * discipline the rest of this screen follows.
+ */
+import type { TeamConfig } from '../../config/schema.js';
+import type { ModelSettingsDraft } from '../../config/model-profile-store.js';
+export type TeamFanoutField = 'maxSubagents' | 'maxConcurrent' | 'overseer';
+/**
+ * THE ONLY KEYS THIS PAGE MAY WRITE (R-P0-1).
+ *
+ * Not `Partial<TeamConfig>`: a fragment that could carry `model` would make a
+ * width adjustment read as a model decision at save time.
+ */
+export type TeamFanoutPatch = Pick<TeamConfig, 'maxSubagents' | 'maxConcurrent' | 'overseer'>;
+export interface TeamFanoutRow {
+    field: TeamFanoutField;
+    label: string;
+    /** The value as the page prints it (`'8'` / `'on'`). */
+    value: string;
+    /** One line, <= 60 columns: WHY this number, not a restatement of the label. */
+    hint: string;
+}
+export interface TeamFanoutView {
+    /** Exactly three, in the fixed order the cursor indexes. */
+    rows: TeamFanoutRow[];
+    error?: string;
+}
+/**
+ * The CLAMPED team section this draft would save (R-P0-2), for display only.
+ *
+ * THE CLAMP IS NOT COSMETIC. Without it a patch carrying only
+ * `maxSubagents: 6` renders "6 per dispatch, 8 at once" on top of an 8-wide
+ * baseline, while `mergePersistedConfig` clamps the same patch to 6/6 on the way
+ * to disk - so the screen and the file disagree, and every arrow key makes the
+ * user reconcile them by hand.
+ */
+export declare function teamFanoutValues(draft: ModelSettingsDraft): TeamConfig;
+/**
+ * The PATCH FRAGMENT for one arrow press, clamped exactly like `clampTeamConfig`.
+ *
+ * `current` must be the value the screen actually shows (`teamFanoutValues`), so
+ * a step always starts from a number the user can see.
+ *
+ * NO WRAPAROUND: a form control is not a ring, and `Left` at 1 jumping to 10
+ * would be a way to widen a dispatch while trying to narrow it.
+ */
+export declare function stepFanoutValue(current: TeamConfig, field: TeamFanoutField, delta: -1 | 1): Partial<TeamFanoutPatch>;
+/**
+ * The page's three rows.
+ *
+ * TWO HINTS CARRY A CONDITION THE DESIGN OWNS RATHER THAN DECORATION (R-1 / C-2):
+ * the default pool is now 8, which is 8 simultaneous streams against one API key,
+ * and the honest mitigation for an HTTP 429 storm is "lower this number" - said
+ * HERE, where the number is, not only in a risk table nobody reads.
+ */
+export declare function fanoutRows(team: TeamConfig): TeamFanoutRow[];
+/** The one-line summary the settings root row prints for this page. */
+export declare function fanoutSummary(team: TeamConfig): string;

package/dist/ui/overlays/team-fanout-state.js

@@ -0,0 +1,97 @@
+/**
+ * Settings > Team fan-out: the pure half of the page (subagent-fanout 3.4.2).
+ *
+ * ASCII ONLY - `src/ui/**` is inside `glyphs.test.ts::inScope`.
+ *
+ * THE PAGE WRITES THREE KEYS AND CANNOT BE MADE TO WRITE A FOURTH (D-17 /
+ * R-P0-1). `TeamFanoutPatch` is `Pick<TeamConfig, 'maxSubagents' |
+ * 'maxConcurrent' | 'overseer'>`, and `stepFanoutValue` returns
+ * `Partial<TeamFanoutPatch>`: a width adjustment therefore CANNOT carry `model`
+ * or `modelProfileId` into `draft.patch.team`. That matters because
+ * `releasedSlots` reads those two keys as "the user re-decided the subagent
+ * slot", so a page that returned the whole section would silently release the
+ * model a session kit had just installed - and no test would notice, because
+ * every value on screen would still be right.
+ *
+ * EVERYTHING HERE IS A PURE FUNCTION over the draft. The page owns exactly one
+ * piece of state (its cursor); values come from the reducer, which is the same
+ * discipline the rest of this screen follows.
+ */
+import { clampTeamConfig, HARD_MAX_SUBAGENTS } from '../../config/schema.js';
+function clampInt(value, min, max) {
+    return Math.max(min, Math.min(max, Math.floor(value)));
+}
+/**
+ * The CLAMPED team section this draft would save (R-P0-2), for display only.
+ *
+ * THE CLAMP IS NOT COSMETIC. Without it a patch carrying only
+ * `maxSubagents: 6` renders "6 per dispatch, 8 at once" on top of an 8-wide
+ * baseline, while `mergePersistedConfig` clamps the same patch to 6/6 on the way
+ * to disk - so the screen and the file disagree, and every arrow key makes the
+ * user reconcile them by hand.
+ */
+export function teamFanoutValues(draft) {
+    return clampTeamConfig({ ...draft.baseline.team, ...draft.patch.team });
+}
+/**
+ * The PATCH FRAGMENT for one arrow press, clamped exactly like `clampTeamConfig`.
+ *
+ * `current` must be the value the screen actually shows (`teamFanoutValues`), so
+ * a step always starts from a number the user can see.
+ *
+ * NO WRAPAROUND: a form control is not a ring, and `Left` at 1 jumping to 10
+ * would be a way to widen a dispatch while trying to narrow it.
+ */
+export function stepFanoutValue(current, field, delta) {
+    if (field === 'overseer') {
+        // Both arrows toggle: `Supervisor` has two states, so a direction has no
+        // meaning beyond "the user pressed an arrow".
+        return { overseer: !current.overseer };
+    }
+    if (field === 'maxConcurrent') {
+        const ceiling = Math.min(HARD_MAX_SUBAGENTS, current.maxSubagents);
+        return { maxConcurrent: clampInt(current.maxConcurrent + delta, 1, ceiling) };
+    }
+    const next = clampInt(current.maxSubagents + delta, 1, HARD_MAX_SUBAGENTS);
+    // THE FOLLOW-DOWN IS WRITTEN INTO THE PATCH (R-P1-9), not just rendered: a
+    // narrower population cannot keep a wider pool, but a DISPLAY-only correction
+    // would snap back the moment the user widened again, so "the change I just
+    // made" would not stick - the exact complaint this design exists to answer.
+    return current.maxConcurrent > next
+        ? { maxSubagents: next, maxConcurrent: next }
+        : { maxSubagents: next };
+}
+/**
+ * The page's three rows.
+ *
+ * TWO HINTS CARRY A CONDITION THE DESIGN OWNS RATHER THAN DECORATION (R-1 / C-2):
+ * the default pool is now 8, which is 8 simultaneous streams against one API key,
+ * and the honest mitigation for an HTTP 429 storm is "lower this number" - said
+ * HERE, where the number is, not only in a risk table nobody reads.
+ */
+export function fanoutRows(team) {
+    return [
+        {
+            field: 'maxSubagents',
+            label: 'Max subagents',
+            value: String(team.maxSubagents),
+            hint: `children per dispatch; ${HARD_MAX_SUBAGENTS} is the hard ceiling`,
+        },
+        {
+            field: 'maxConcurrent',
+            label: 'Run at once',
+            value: String(team.maxConcurrent),
+            hint: 'provider limits: lower this if you see rate-limit errors',
+        },
+        {
+            field: 'overseer',
+            label: 'Supervisor',
+            value: team.overseer ? 'on' : 'off',
+            hint: 'checks stalled children; never kills them',
+        },
+    ];
+}
+/** The one-line summary the settings root row prints for this page. */
+export function fanoutSummary(team) {
+    return `${team.maxSubagents} per dispatch, ${team.maxConcurrent} at once`;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aragon-agent/cli",
-  "version": "0.6.39",
+  "version": "0.6.40",
   "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.51",
+    "@aragon-agent/core": "^0.2.52",
     "chalk": "^5.6.2",
     "cli-highlight": "^2.0.0",
     "commander": "^12.1.0",