@aragon-agent/cli 0.6.40 → 0.6.43

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

@@ -1,10 +1,11 @@
 /**
- * Settings > Team fan-out: the pure half of the page (subagent-fanout 3.4.2).
+ * Settings > Team: the pure half of the page (subagent-fanout 3.4.2, extended by
+ * team-command-forced-dispatch §3.9).
  *
  * 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' |
+ * THE PAGE WRITES FOUR KEYS AND CANNOT BE MADE TO WRITE A FIFTH (D-17 / R-P0-1).
+ * `TeamFanoutPatch` is `Pick<TeamConfig, 'enabled' | 'maxSubagents' |
  * 'maxConcurrent' | 'overseer'>`, and `stepFanoutValue` returns
  * `Partial<TeamFanoutPatch>`: a width adjustment therefore CANNOT carry `model`
  * or `modelProfileId` into `draft.patch.team`. That matters because
@@ -13,20 +14,26 @@
  * model a session kit had just installed - and no test would notice, because
  * every value on screen would still be right.
  *
+ * FOUR KEYS BECAUSE `enabled` MOVED HERE (team-command-forced-dispatch D-3): the
+ * team switch used to be reachable only as `/team on|off`, which also wrote
+ * `config.json`. The switch belongs on the same page as width, concurrency and
+ * supervision - they are four faces of one decision - and `/team` is now the ACT
+ * ("arm this session"), never a configuration write (I-4).
+ *
  * 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';
+export type TeamFanoutField = 'enabled' | '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 type TeamFanoutPatch = Pick<TeamConfig, 'enabled' | 'maxSubagents' | 'maxConcurrent' | 'overseer'>;
 export interface TeamFanoutRow {
     field: TeamFanoutField;
     label: string;
@@ -36,7 +43,7 @@ export interface TeamFanoutRow {
     hint: string;
 }
 export interface TeamFanoutView {
-    /** Exactly three, in the fixed order the cursor indexes. */
+    /** Exactly four, in the fixed order the cursor indexes. */
     rows: TeamFanoutRow[];
     error?: string;
 }
@@ -58,16 +65,42 @@ export declare function teamFanoutValues(draft: ModelSettingsDraft): TeamConfig;
  *
  * 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.
+ *
+ * EVERY MEMBER IS HANDLED EXPLICITLY AND THE TAIL IS `never` (P0-1). The old
+ * body was three `if`s with the `maxSubagents` branch as the FALLTHROUGH, so
+ * adding `'enabled'` to the union compiled cleanly and made the new `Team mode`
+ * row adjust `Max subagents` instead - every number on screen self-consistent,
+ * no test red, and the user's intent to switch the team OFF arrived as a wider
+ * fan-out. The `never` assignment below turns that class of mistake into a
+ * compile error, which is the only place it can be caught cheaply.
  */
 export declare function stepFanoutValue(current: TeamConfig, field: TeamFanoutField, delta: -1 | 1): Partial<TeamFanoutPatch>;
 /**
- * The page's three rows.
+ * The page's four rows, in cursor order.
+ *
+ * `Team mode` IS FIRST because it is the premise of the other three: with `task`
+ * out of the tool list there is no width to configure and no supervisor to run,
+ * and a page that listed the numbers first would invite the user to tune a
+ * capability they had switched off.
  *
  * 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.
+ * the default pool is 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.
+ *
+ * `teamRegistered === false` (a `--no-team` session) changes TWO things on the
+ * `enabled` row and nothing else: `on (next launch)` because the tool array is
+ * immutable (I-7), and a hint that says why. Absent means "not disclosed",
+ * which every existing fixture relies on.
+ */
+export declare function fanoutRows(team: TeamConfig, teamRegistered?: boolean): TeamFanoutRow[];
+/**
+ * The one-line summary the settings root row prints for this page.
+ *
+ * `off - no subagents` rather than the numbers, because with the capability off
+ * the numbers describe nothing the user can spend. This replaced
+ * `fanoutSummary()` outright instead of living beside it: two summary functions
+ * over one page is two authorities for one line, and the root row would sooner or
+ * later disagree with the page it summarises.
  */
-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;
+export declare function teamSummary(team: TeamConfig): string;

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

@@ -1,10 +1,11 @@
 /**
- * Settings > Team fan-out: the pure half of the page (subagent-fanout 3.4.2).
+ * Settings > Team: the pure half of the page (subagent-fanout 3.4.2, extended by
+ * team-command-forced-dispatch §3.9).
  *
  * 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' |
+ * THE PAGE WRITES FOUR KEYS AND CANNOT BE MADE TO WRITE A FIFTH (D-17 / R-P0-1).
+ * `TeamFanoutPatch` is `Pick<TeamConfig, 'enabled' | 'maxSubagents' |
  * 'maxConcurrent' | 'overseer'>`, and `stepFanoutValue` returns
  * `Partial<TeamFanoutPatch>`: a width adjustment therefore CANNOT carry `model`
  * or `modelProfileId` into `draft.patch.team`. That matters because
@@ -13,6 +14,12 @@
  * model a session kit had just installed - and no test would notice, because
  * every value on screen would still be right.
  *
+ * FOUR KEYS BECAUSE `enabled` MOVED HERE (team-command-forced-dispatch D-3): the
+ * team switch used to be reachable only as `/team on|off`, which also wrote
+ * `config.json`. The switch belongs on the same page as width, concurrency and
+ * supervision - they are four faces of one decision - and `/team` is now the ACT
+ * ("arm this session"), never a configuration write (I-4).
+ *
  * 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.
@@ -41,36 +48,77 @@ export function teamFanoutValues(draft) {
  *
  * 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.
+ *
+ * EVERY MEMBER IS HANDLED EXPLICITLY AND THE TAIL IS `never` (P0-1). The old
+ * body was three `if`s with the `maxSubagents` branch as the FALLTHROUGH, so
+ * adding `'enabled'` to the union compiled cleanly and made the new `Team mode`
+ * row adjust `Max subagents` instead - every number on screen self-consistent,
+ * no test red, and the user's intent to switch the team OFF arrived as a wider
+ * fan-out. The `never` assignment below turns that class of mistake into a
+ * compile error, which is the only place it can be caught cheaply.
  */
 export function stepFanoutValue(current, field, delta) {
+    if (field === 'enabled') {
+        // Both arrows toggle: `Team mode` has two states, and a direction has no
+        // meaning beyond "the user pressed an arrow" (the `Supervisor` rule below).
+        return { enabled: !current.enabled };
+    }
     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 };
+    if (field === 'maxSubagents') {
+        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 EXHAUSTIVE GUARD IS THE POINT (P0-1): a new member of `TeamFanoutField`
+    // must fail to COMPILE here, not silently fall through to `maxSubagents`.
+    //
+    // IT SITS AFTER EVERY BRANCH RETURNS, not before the last one. §3.9's snippet
+    // shows it above the `maxSubagents` branch, where TypeScript rejects the file
+    // outright (`'maxSubagents' is not assignable to 'never'`) - the intent
+    // survives, the position does not.
+    const _exhaustive = field;
+    return _exhaustive;
 }
 /**
- * The page's three rows.
+ * The page's four rows, in cursor order.
+ *
+ * `Team mode` IS FIRST because it is the premise of the other three: with `task`
+ * out of the tool list there is no width to configure and no supervisor to run,
+ * and a page that listed the numbers first would invite the user to tune a
+ * capability they had switched off.
  *
  * 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.
+ * the default pool is 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.
+ *
+ * `teamRegistered === false` (a `--no-team` session) changes TWO things on the
+ * `enabled` row and nothing else: `on (next launch)` because the tool array is
+ * immutable (I-7), and a hint that says why. Absent means "not disclosed",
+ * which every existing fixture relies on.
  */
-export function fanoutRows(team) {
+export function fanoutRows(team, teamRegistered) {
+    const blocked = teamRegistered === false && team.enabled;
     return [
+        {
+            field: 'enabled',
+            label: 'Team mode',
+            value: blocked ? 'on (next launch)' : team.enabled ? 'on' : 'off',
+            hint: blocked
+                ? '--no-team session: the task tool cannot be added live'
+                : 'off: no task tool next launch; this session may lack it',
+        },
         {
             field: 'maxSubagents',
             label: 'Max subagents',
@@ -91,7 +139,17 @@ export function fanoutRows(team) {
         },
     ];
 }
-/** The one-line summary the settings root row prints for this page. */
-export function fanoutSummary(team) {
+/**
+ * The one-line summary the settings root row prints for this page.
+ *
+ * `off - no subagents` rather than the numbers, because with the capability off
+ * the numbers describe nothing the user can spend. This replaced
+ * `fanoutSummary()` outright instead of living beside it: two summary functions
+ * over one page is two authorities for one line, and the root row would sooner or
+ * later disagree with the page it summarises.
+ */
+export function teamSummary(team) {
+    if (!team.enabled)
+        return 'off - no subagents';
     return `${team.maxSubagents} per dispatch, ${team.maxConcurrent} at once`;
 }

package/package.json

@@ -1,81 +1,81 @@
-{
-  "name": "@aragon-agent/cli",
-  "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",
-  "keywords": [
-    "agent",
-    "ai-agent",
-    "llm",
-    "cli",
-    "tui",
-    "terminal",
-    "ink",
-    "anthropic",
-    "openai",
-    "google",
-    "aragonagent",
-    "exec",
-    "headless",
-    "automation",
-    "ci"
-  ],
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/xdrshjr/AragonAgent.git",
-    "directory": "packages/cli"
-  },
-  "homepage": "https://github.com/xdrshjr/AragonAgent#readme",
-  "bugs": {
-    "url": "https://github.com/xdrshjr/AragonAgent/issues"
-  },
-  "type": "module",
-  "bin": {
-    "aragon": "./dist/launcher.js"
-  },
-  "files": [
-    "dist",
-    "runtime",
-    "skills",
-    "README.md",
-    "CHANGELOG.md"
-  ],
-  "engines": {
-    "node": ">=18"
-  },
-  "publishConfig": {
-    "access": "public"
-  },
-  "scripts": {
-    "build": "node -e \"require('fs').rmSync('dist',{recursive:true,force:true})\" && tsc -p tsconfig.json && node scripts/prepend-shebang.mjs",
-    "dev": "tsc -p tsconfig.json --watch",
-    "typecheck": "tsc -p tsconfig.json --noEmit && tsc -p tsconfig.test.json --noEmit",
-    "test": "vitest run",
-    "start": "node dist/cli.js",
-    "prepublishOnly": "npm run build"
-  },
-  "dependencies": {
-    "@aragon-agent/core": "^0.2.52",
-    "chalk": "^5.6.2",
-    "cli-highlight": "^2.0.0",
-    "commander": "^12.1.0",
-    "dotenv": "^16.6.1",
-    "env-paths": "^3.0.0",
-    "fflate": "^0.8.3",
-    "ink": "^5.0.1",
-    "ink-select-input": "^6.0.0",
-    "ink-spinner": "^5.0.0",
-    "react": "^18.3.1",
-    "string-width": "^7.2.0",
-    "strip-ansi": "^7.1.0",
-    "tinyglobby": "^0.2.17"
-  },
-  "devDependencies": {
-    "@types/node": "^22.0.0",
-    "@types/react": "^18.3.0",
-    "ink-testing-library": "^4.0.0",
-    "typescript": "^5.9.3",
-    "vitest": "4.1.9"
-  }
-}
+{
+  "name": "@aragon-agent/cli",
+  "version": "0.6.43",
+  "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",
+  "keywords": [
+    "agent",
+    "ai-agent",
+    "llm",
+    "cli",
+    "tui",
+    "terminal",
+    "ink",
+    "anthropic",
+    "openai",
+    "google",
+    "aragonagent",
+    "exec",
+    "headless",
+    "automation",
+    "ci"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/xdrshjr/AragonAgent.git",
+    "directory": "packages/cli"
+  },
+  "homepage": "https://github.com/xdrshjr/AragonAgent#readme",
+  "bugs": {
+    "url": "https://github.com/xdrshjr/AragonAgent/issues"
+  },
+  "type": "module",
+  "bin": {
+    "aragon": "./dist/launcher.js"
+  },
+  "files": [
+    "dist",
+    "runtime",
+    "skills",
+    "README.md",
+    "CHANGELOG.md"
+  ],
+  "engines": {
+    "node": ">=18"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "build": "node -e \"require('fs').rmSync('dist',{recursive:true,force:true})\" && tsc -p tsconfig.json && node scripts/prepend-shebang.mjs",
+    "dev": "tsc -p tsconfig.json --watch",
+    "typecheck": "tsc -p tsconfig.json --noEmit && tsc -p tsconfig.test.json --noEmit",
+    "test": "vitest run",
+    "start": "node dist/cli.js",
+    "prepublishOnly": "npm run build"
+  },
+  "dependencies": {
+    "@aragon-agent/core": "^0.2.55",
+    "chalk": "^5.6.2",
+    "cli-highlight": "^2.0.0",
+    "commander": "^12.1.0",
+    "dotenv": "^16.6.1",
+    "env-paths": "^3.0.0",
+    "fflate": "^0.8.3",
+    "ink": "^5.0.1",
+    "ink-select-input": "^6.0.0",
+    "ink-spinner": "^5.0.0",
+    "react": "^18.3.1",
+    "string-width": "^7.2.0",
+    "strip-ansi": "^7.1.0",
+    "tinyglobby": "^0.2.17"
+  },
+  "devDependencies": {
+    "@types/node": "^22.0.0",
+    "@types/react": "^18.3.0",
+    "ink-testing-library": "^4.0.0",
+    "typescript": "^5.9.3",
+    "vitest": "4.1.9"
+  }
+}