@aragon-agent/cli 0.6.39 → 0.6.40

package/dist/agent/reducer.js

@@ -1134,12 +1134,11 @@ export function viewReducer(state, action) {
         case 'fastTier':
             return { ...state, fast: action.snapshot };
         // --- Context compaction (context-auto-compaction §5.5) ----------------
-        // NOT A TOTAL FUNCTION OVER COMPACTION ATTEMPTS (quiet-noop §3.1). A
-        // `pressure` compaction that declines before calling a model or changing the
-        // history dispatches NOTHING - no `compactionStart`, no `compactionEnd`, no
-        // entry - exactly as a checkpoint below the threshold dispatches nothing.
-        // Counting cards here counts compactions that RAN, never checkpoints that
-        // fired; `/compact status` and the diagnostic log are where the attempts are.
+        // THE TRANSCRIPT NOW CARRIES ONE CARD PER ATTEMPT (context-compaction-never-
+        // fires C). Before this change a declined `pressure` checkpoint dispatched
+        // NOTHING, which is what made "95 % and nothing happens" unreportable: the
+        // feature was trying, failing and saying nothing. The flood the old rule
+        // feared is bounded by `maxPerRun` / `stuckLimit` in `compaction/limits.ts`.
         case 'compactionStart': {
             const { id, seq } = nextId(state);
             let entries = state.entries;
@@ -1189,6 +1188,7 @@ export function viewReducer(state, action) {
                 tokensAfter: 0,
                 model: action.model,
                 startedAt: Date.now(),
+                phase: 'planning',
                 live: true,
             };
             return {
@@ -1217,6 +1217,16 @@ export function viewReducer(state, action) {
                     ...(record.tailRelief ? { tailRelief: record.tailRelief } : {}),
                     ...(record.decision ? { decision: record.decision } : {}),
                     ...(record.memoryVersion ? { memoryVersion: record.memoryVersion } : {}),
+                    ...(record.keepRelaxed ? { keepRelaxed: record.keepRelaxed } : {}),
+                    ...(record.retainedTurns !== undefined
+                        ? { retainedTurns: record.retainedTurns } : {}),
+                    ...(record.retainedMessages !== undefined
+                        ? { retainedMessages: record.retainedMessages } : {}),
+                    ...(record.retainedMessages !== undefined
+                        ? { retainedMessages: record.retainedMessages } : {}),
+                    ...(record.keepRecentTurnsUsed !== undefined
+                        ? { keepRecentTurnsUsed: record.keepRecentTurnsUsed } : {}),
+                    ...(record.elidedMessages ? { elidedMessages: record.elidedMessages } : {}),
                     model: record.model,
                     durationMs: record.durationMs,
                     // SETTLED. `Transcript`'s boundary is monotonic, so a card that
@@ -1253,12 +1263,30 @@ export function viewReducer(state, action) {
                 ...(record.tailRelief ? { tailRelief: record.tailRelief } : {}),
                 ...(record.decision ? { decision: record.decision } : {}),
                 ...(record.memoryVersion ? { memoryVersion: record.memoryVersion } : {}),
+                ...(record.keepRelaxed ? { keepRelaxed: record.keepRelaxed } : {}),
+                ...(record.retainedTurns !== undefined ? { retainedTurns: record.retainedTurns } : {}),
+                ...(record.keepRecentTurnsUsed !== undefined
+                    ? { keepRecentTurnsUsed: record.keepRecentTurnsUsed } : {}),
+                ...(record.elidedMessages ? { elidedMessages: record.elidedMessages } : {}),
                 model: record.model,
                 durationMs: record.durationMs,
                 live: false,
             };
             return { ...state, seq, ...appendEntry(state, state.entries, entry) };
         }
+        case 'compactionPhase': {
+            // THE LIVE CARD'S STAGE, AND NOTHING ELSE. It must not open a card (a phase
+            // can arrive for an entry that a fast settle already closed) and must not
+            // resurrect a settled one: `live` is left untouched, so a late phase on a
+            // settled card changes nothing the renderer shows.
+            if (!state.compactionEntryId)
+                return state;
+            const phase = action.phase;
+            return {
+                ...state,
+                entries: mapEntry(state.entries, state.compactionEntryId, (e) => e.kind === 'compaction' && e.live ? { ...e, phase } : e),
+            };
+        }
         case 'compactionUsage':
             // `usageTotal` AND NOTHING ELSE, exactly as `teamUsage` and `fastUsage`. In
             // particular NOT `context`: that gauge shows the LEAD's context

package/dist/agent/skill-triage-prompt.d.ts

@@ -0,0 +1,42 @@
+/**
+ * The `<skill_triage>` system-prompt block (skill-triage-and-unbounded-ask §4.2.3).
+ *
+ * WHY A PROTOCOL BLOCK AT ALL. The capability this feature fixes already existed:
+ * the Level 1 catalog is in every prompt, `skill(name)` loads a body, and
+ * `README.md` has claimed since the Skills feature landed that "the model decides
+ * on its own whether a task matches a skill". What was missing is any instruction
+ * that the decision has to HAPPEN, before the work rather than after it. The
+ * catalog's own opening paragraph is a STATEMENT ("if a task matches one, call the
+ * skill tool"), not a step in an order of operations, and a statement the model
+ * has read forty times is the one it skims.
+ *
+ * WHY IT IS THIS SHORT. The protocol is paid for on EVERY LLM request: the system
+ * prompt is re-sent each time and nothing in this repository uses provider-side
+ * prefix caching. An earlier draft carried a 1.9 KB version whose second half
+ * repeated the disclosure ladder that `<available_skills>` already states three
+ * lines above it. Repeating a rule is not emphasis, it is noise — and noise about
+ * a rule teaches the model that these blocks are skimmable. Measured size of the
+ * block below is 1273 bytes; `skill-triage-prompt.test.ts` asserts the ceiling of
+ * 1500 so an edit has 227 bytes of room, not unlimited scope.
+ *
+ * ASCII ONLY — `agent/` is inside the glyph scanner's scope.
+ */
+import type { SkillCandidate } from '../skills/triage.js';
+/** Bump when the wording changes, so a transcript can be dated. */
+export declare const SKILL_TRIAGE_BLOCK_VERSION = "v1-2026-10-26";
+export interface SkillTriageBlockOptions {
+    /** This turn's candidates, best first. Empty is normal and renders no data block. */
+    candidates: SkillCandidate[];
+}
+/**
+ * Protocol first, candidates second — in that order, always.
+ *
+ * The order is the meaning: the protocol says what to do, the data block says with
+ * what. Reversing them would put a list of suggestions above the rules for reading
+ * it, which is how a suggestion turns into an instruction.
+ */
+export declare function buildSkillTriageBlock(options: SkillTriageBlockOptions): string;
+/** Byte size of the protocol half, for the budget assertion in the tests. */
+export declare function skillTriageProtocolBytes(): number;
+/** The ceiling the protocol half must stay under, in bytes. */
+export declare const SKILL_TRIAGE_PROTOCOL_MAX_BYTES: number;

package/dist/agent/skill-triage-prompt.js

@@ -0,0 +1,74 @@
+/**
+ * The `<skill_triage>` system-prompt block (skill-triage-and-unbounded-ask §4.2.3).
+ *
+ * WHY A PROTOCOL BLOCK AT ALL. The capability this feature fixes already existed:
+ * the Level 1 catalog is in every prompt, `skill(name)` loads a body, and
+ * `README.md` has claimed since the Skills feature landed that "the model decides
+ * on its own whether a task matches a skill". What was missing is any instruction
+ * that the decision has to HAPPEN, before the work rather than after it. The
+ * catalog's own opening paragraph is a STATEMENT ("if a task matches one, call the
+ * skill tool"), not a step in an order of operations, and a statement the model
+ * has read forty times is the one it skims.
+ *
+ * WHY IT IS THIS SHORT. The protocol is paid for on EVERY LLM request: the system
+ * prompt is re-sent each time and nothing in this repository uses provider-side
+ * prefix caching. An earlier draft carried a 1.9 KB version whose second half
+ * repeated the disclosure ladder that `<available_skills>` already states three
+ * lines above it. Repeating a rule is not emphasis, it is noise — and noise about
+ * a rule teaches the model that these blocks are skimmable. Measured size of the
+ * block below is 1273 bytes; `skill-triage-prompt.test.ts` asserts the ceiling of
+ * 1500 so an edit has 227 bytes of room, not unlimited scope.
+ *
+ * ASCII ONLY — `agent/` is inside the glyph scanner's scope.
+ */
+import { renderSkillCandidates, SKILL_TRIAGE_LIMITS } from '../skills/triage.js';
+/** Bump when the wording changes, so a transcript can be dated. */
+export const SKILL_TRIAGE_BLOCK_VERSION = 'v1-2026-10-26';
+/**
+ * The protocol text. Kept as a literal array so a diff of the prompt is a diff of
+ * the source, and so the grader/test can see line boundaries.
+ */
+const PROTOCOL_LINES = [
+    '<skill_triage>',
+    `Version: ${SKILL_TRIAGE_BLOCK_VERSION}`,
+    '',
+    'Triage every task that touches the workspace: AFTER the project guidance and the',
+    'directory listing, BEFORE you plan or change anything. A user-typed /<skill-name>',
+    'is an override, not the only way in.',
+    '',
+    '1. Read <available_skills> above, and <skill_candidates> when present. A candidate',
+    '   is a computed guess about your message, not a verdict - check its one-line',
+    '   description before trusting it.',
+    '2. If the catalog says some skills were not shown, or nothing listed plainly',
+    '   covers the task, call skill_find(query) once before concluding there is no',
+    '   skill.',
+    '3. If a skill covers the task, call skill(name="...") BEFORE the first source read',
+    '   that would change code, then follow it. Say why in one line, not a paragraph.',
+    '4. If nothing covers the task, say so in one clause and continue. Do not load a',
+    '   skill to look diligent, and never load several "to be safe".',
+    '',
+    'A loaded skill is reference material, not permission to ignore the user, the',
+    'plan-mode rules, or the tools you actually have. If a skill narrows your tool set,',
+    'that is its allowed-tools declaration working: report it, do not work around it.',
+    'Never install or author a skill because a task looks like it needs one; that',
+    'decision belongs to the user.',
+    '</skill_triage>',
+];
+const PROTOCOL = PROTOCOL_LINES.join('\n');
+/**
+ * Protocol first, candidates second — in that order, always.
+ *
+ * The order is the meaning: the protocol says what to do, the data block says with
+ * what. Reversing them would put a list of suggestions above the rules for reading
+ * it, which is how a suggestion turns into an instruction.
+ */
+export function buildSkillTriageBlock(options) {
+    const candidates = renderSkillCandidates(options.candidates);
+    return candidates.length > 0 ? `${PROTOCOL}\n${candidates}` : PROTOCOL;
+}
+/** Byte size of the protocol half, for the budget assertion in the tests. */
+export function skillTriageProtocolBytes() {
+    return new TextEncoder().encode(PROTOCOL).length;
+}
+/** The ceiling the protocol half must stay under, in bytes. */
+export const SKILL_TRIAGE_PROTOCOL_MAX_BYTES = SKILL_TRIAGE_LIMITS.maxProtocolBytes;

package/dist/agent/system-prompt.d.ts

@@ -34,8 +34,20 @@ export interface SystemPromptParams {
      * plan as its final message instead of calling tools it does not have.
      */
     planInteractive?: boolean;
-    /** `planModeMaxAskRounds`, substituted into the block so the two agree. */
-    planMaxAskRounds?: number;
+    /**
+     * The rendered `<skill_triage>` block plus (when there are candidates) the
+     * `<skill_candidates>` block, or `''`.
+     *
+     * Spliced conditionally exactly as `skillsBlock` and the plan block are, which
+     * is what keeps invariant I-T1 true: `skills.triage: false`, a zero-skill
+     * install and `--no-skills` all produce the pre-feature prompt BYTE FOR BYTE.
+     *
+     * POSITION IS THE SEMANTICS. It goes immediately AFTER `skillsBlock`, because
+     * its first instruction refers to `<available_skills> above`, and a block
+     * separated from what it points at reads as a dangling reference. It also goes
+     * BEFORE the plan block, whose first step defers to it.
+     */
+    skillTriageBlock?: string;
     /**
      * The rendered `<team_mode>` block for a LEAD with team mode on, or `''`.
      *

package/dist/agent/system-prompt.js

@@ -33,11 +33,11 @@ export function buildSystemPrompt(params) {
     const skillsBlock = params.skillsBlock ?? '';
     const hasSkills = skillsBlock.length > 0;
     const planBlock = params.agentMode === 'plan'
-        ? buildPlanModeBlock({
-            interactive: params.planInteractive !== false,
-            maxAskRounds: params.planMaxAskRounds ?? 4,
-        })
+        ? buildPlanModeBlock({ interactive: params.planInteractive !== false })
         : '';
+    // `''` when the caller has no candidates or the feature is off — which is what
+    // keeps this block's absence byte-identical to the pre-feature prompt (I-T1).
+    const skillTriageBlock = params.skillTriageBlock ?? '';
     const teamBlock = params.teamBlock ?? '';
     const subagentBlock = params.subagentBlock ?? '';
     const todoBlock = params.todoBlock ?? '';
@@ -61,6 +61,9 @@ export function buildSystemPrompt(params) {
         '',
         buildProjectGuidanceBlock(),
         ...(hasSkills ? ['', skillsBlock] : []),
+        // AFTER <available_skills> (it refers to it as "above") and BEFORE <plan_mode>
+        // (whose step 1 defers to it). Conditional like every other optional block.
+        ...(skillTriageBlock ? ['', skillTriageBlock] : []),
         ...(planBlock ? ['', planBlock] : []),
         ...(teamBlock ? ['', teamBlock] : []),
         ...(subagentBlock ? ['', subagentBlock] : []),

package/dist/cli.js

@@ -29,7 +29,7 @@ import { COMPACTION_CONFIG_SET_KEYS, FAST_CONFIG_SET_KEYS, LOG_CONFIG_SET_KEYS,
 import { attachAgentEvents, attachTeamEvents, installLogging, setScreenRestore, setSignalTerminator, } from './logging/install.js';
 import { getLogger } from './logging/logger.js';
 import { runLogsCommand } from './logging/cli-commands.js';
-import { ADAPTER_PROVIDERS, clampDensity, clampTheme, clampThinkingLevel, clampAskRounds, clampHumanTimeout, clampSkillsIntegrity, clampSkillsToolPolicy, clampContextWindow, clampMaxRenderInterval, clampScrollMode, clampScrollResumeMs, clampTranscriptRetain, clampTranscriptWindow, coercePositiveInt, isAdapterProvider, isAutoToken, parseMaxTokensInput, DEFAULT_MAX_RENDER_INTERVAL_MS, DEFAULT_MAX_TOKENS, DEFAULT_PLAN_HUMAN_TIMEOUT_MS, DEFAULT_PLAN_MAX_ASK_ROUNDS, DEFAULT_SCROLL_MODE, DEFAULT_SCROLL_RESUME_MS, DEFAULT_SKILLS_CONFIG, DEFAULT_TRANSCRIPT_RETAIN, DEFAULT_TRANSCRIPT_WINDOW, } from './config/schema.js';
+import { ADAPTER_PROVIDERS, clampDensity, clampTheme, clampThinkingLevel, clampHumanTimeout, clampSkillsIntegrity, clampSkillsToolPolicy, clampContextWindow, clampMaxRenderInterval, clampScrollMode, clampScrollResumeMs, clampTranscriptRetain, clampTranscriptWindow, coercePositiveInt, isAdapterProvider, isAutoToken, parseMaxTokensInput, RETIRED_CONFIG_KEYS, DEFAULT_MAX_RENDER_INTERVAL_MS, DEFAULT_MAX_TOKENS, DEFAULT_PLAN_HUMAN_TIMEOUT_MS, DEFAULT_SCROLL_MODE, DEFAULT_SCROLL_RESUME_MS, DEFAULT_SKILLS_CONFIG, DEFAULT_TRANSCRIPT_RETAIN, DEFAULT_TRANSCRIPT_WINDOW, } from './config/schema.js';
 import { makeGetApiKey } from './config/load.js';
 import { AgentController, DENY_ALL_APPROVAL } from './agent/controller.js';
 import { runSkillsCommand } from './skills/cli-commands.js';
@@ -1559,7 +1559,6 @@ const CONFIG_SET_KEYS = new Set([
     'scrollResumeMs',
     'historyEnabled',
     'planModeDefault',
-    'planModeMaxAskRounds',
     'planModeHumanTimeoutMs',
     // Dotted keys route into the nested `skills` object; see the switch below.
     'skills.enabled',
@@ -1569,6 +1568,7 @@ const CONFIG_SET_KEYS = new Set([
     'skills.integrity',
     'skills.usageTracking',
     'skills.toolPolicy',
+    'skills.triage',
     // `log.*` keys are handled by `applyLogConfigSet` below, NOT by the switch:
     // that switch is already past this package's complexity ceiling.
     ...LOG_CONFIG_SET_KEYS,
@@ -1660,6 +1660,18 @@ function runConfigSet(key, value) {
     }
 }
 function runConfigSetValue(key, value) {
+    // RETIRED KEYS ARE REFUSED BY NAME, BEFORE THE UNKNOWN-KEY CHECK. Falling
+    // through to `Unknown config key` would be technically true and practically
+    // useless: a script that has run `config set planModeMaxAskRounds 5` for months
+    // needs to be told what happened to it, not that it never existed. Exit 2 for
+    // the same reason a bad value is 2 — the caller's argument is wrong, the file
+    // is not.
+    const retired = RETIRED_CONFIG_KEYS[key];
+    if (retired !== undefined) {
+        process.stderr.write(`"${key}" was removed: ${retired}\n`);
+        process.exitCode = 2;
+        return;
+    }
     if (!CONFIG_SET_KEYS.has(key)) {
         process.stderr.write(`Unknown config key "${key}". Known keys: ${[...CONFIG_SET_KEYS].join(', ')}.\n`);
         process.exitCode = 2;
@@ -1852,9 +1864,6 @@ function runConfigSetValue(key, value) {
         case 'planModeDefault':
             patch.planModeDefault = value === 'true' || value === '1';
             break;
-        case 'planModeMaxAskRounds':
-            patch.planModeMaxAskRounds = clampAskRounds(value, DEFAULT_PLAN_MAX_ASK_ROUNDS);
-            break;
         case 'planModeHumanTimeoutMs':
             patch.planModeHumanTimeoutMs = clampHumanTimeout(value, DEFAULT_PLAN_HUMAN_TIMEOUT_MS);
             break;
@@ -1893,6 +1902,13 @@ function runConfigSetValue(key, value) {
                 toolPolicy: clampSkillsToolPolicy(value, DEFAULT_SKILLS_CONFIG.toolPolicy),
             };
             break;
+        // The triage master switch. `false` restores the pre-feature prompt BYTE FOR
+        // BYTE (invariant I-T1), which is the reason it is a key rather than a flag.
+        case 'skills.triage':
+            patch.skills = {
+                triage: value === 'true' || value === '1',
+            };
+            break;
     }
     updatePersistedConfig(patch);
     process.stdout.write(`Set ${key} = ${value}\n`);

package/dist/commands/builtins.js

@@ -27,6 +27,7 @@ import { registerQueueCommand } from './queue-command.js';
 import { registerPromptCommands } from '../prompts/command.js';
 import { registerKitCommand } from './kit-command.js';
 import { registerAgentsCommand } from './agents-command.js';
+import { registerSubagentCommand } from './subagent-command.js';
 // THE DRAWER AND THE HEADER LABEL (tui-shortcut-drawer-and-task-summary §4.7):
 // two single-purpose commands in their own modules, registered from here. Both are
 // UNCONDITIONAL, even with `taskSummary.enabled=false`, because they are the only
@@ -412,8 +413,10 @@ const COMMANDS = [
             if (arg === 'status') {
                 const s = ctx.controller.getPlanStatus();
                 const pending = s.pending ? ` (pending ${MODE_LABEL[s.pending]} after this run)` : '';
-                ctx.notify('info', `Mode: ${MODE_LABEL[s.effective]}${pending}. ` +
-                    `Ask rounds used: ${s.askRoundsUsed}/${s.maxAskRounds}.`);
+                // NO ROUND COUNT. The old line ended with `Ask rounds used: 3/4.`, which
+                // told the user their agent was rationing questions - a limit that no
+                // longer exists. Nothing replaced it: "0 of unlimited" is noise.
+                ctx.notify('info', `Mode: ${MODE_LABEL[s.effective]}${pending}.`);
                 return;
             }
             if (arg.length > 0 && arg !== 'on' && arg !== 'off') {
@@ -1508,6 +1511,11 @@ export function registerBuiltinCommands(registry) {
     // The read-only subagent board (tui-subagent-panel §6.4). Same shape again: the
     // body is `commands/agents-command.ts` and the registration is this one line.
     registerAgentsCommand(registry);
+    // `/subagent` (subagent-fanout 3.5). REGISTERED UNCONDITIONALLY, like `/prompts`
+    // and for the same reason: a `--no-team` session must still be able to ask the
+    // command why it cannot force anything (I-7 / AC-15) - so registering it may
+    // not read config, build a connection or send a request.
+    registerSubagentCommand(registry);
     // The keyboard drawer (`Ctrl+G` / `/keys`) and the task label (`/task`). Two
     // registrations, no new mechanism: `/keys` sets the panel's pre-filter and opens
     // the same overlay `Ctrl+G` opens, and `/task` reports what the header cell says.
@@ -1522,7 +1530,8 @@ export function registerBuiltinCommands(registry) {
  * `registry.get(name)` instead, because that is the only check that stays
  * correct when commands are registered dynamically (§7.1 / P1-2).
  */
-export const BUILTIN_COMMAND_NAMES = ['queue', 'prompts', 'agents', 'keys', 'task',
+export const BUILTIN_COMMAND_NAMES = ['queue', 'prompts', 'agents', 'subagent',
+    'keys', 'task',
     ...COMMANDS.flatMap((c) => [
         c.name,
         ...(c.aliases ?? []),

package/dist/commands/skills.js

@@ -12,6 +12,7 @@ import { checkManifest } from '../skills/manifest.js';
 import { updateAllSkills, updateSkill, isHardFailure } from '../skills/updater.js';
 import { currentPlatform } from '../skills/node-host.js';
 import { listUsage, resetUsage, getUsagePath } from '../skills/usage.js';
+import { SKILL_TRIAGE_LIMITS } from '../skills/triage.js';
 import { HOST_TOOL_NAMES, SKILL_TOOL_FLOOR } from '../tools/index.js';
 import { SKILLS_TOOL_POLICY_MODES, isSkillsToolPolicyMode } from '../config/schema.js';
 import { pickGlyphs } from '../ui/glyphs.js';
@@ -92,12 +93,96 @@ async function runSkills(ctx, service, version) {
             return unloadFrames(ctx, service);
         case 'usage':
             return usageFromCommand(ctx, service, argument);
+        case 'triage':
+            return triageFromCommand(ctx, service, argument);
+        case 'route':
+            return routeFromCommand(ctx, service, argument);
         default:
             ctx.notify('warn', `Unknown subcommand "/skills ${sub}". Try: list, info, install, update, remove, enable, ` +
-                'disable, reload, create, trust, untrust, policy, unload, usage.');
+                'disable, reload, create, trust, untrust, policy, unload, usage, triage, route.');
     }
 }
 // ---------------------------------------------------------------------------
+// /skills triage · route  (skill-triage-and-unbounded-ask §4.2.8)
+// ---------------------------------------------------------------------------
+/**
+ * `/skills triage [on|off]`.
+ *
+ * The report names the switch AND the last turn's result, because "on" alone does
+ * not answer the question a user actually has, which is "is it finding anything?".
+ * `lastSkillRouting` comes from the controller — it is per-turn session state, not
+ * skill-service state, and the service must not start owning a copy of it.
+ */
+function triageFromCommand(ctx, service, argument) {
+    const requested = argument.trim().toLowerCase();
+    if (requested.length === 0) {
+        const on = service.getConfig().triage === true;
+        const last = ctx.controller.getSkillRouting();
+        const summary = last === null
+            ? 'No turn has been triaged yet.'
+            : last.candidates.length === 0
+                ? `Last turn: no candidate (${last.eligible} eligible skill(s) scored).`
+                : `Last turn: ${last.candidates.length} candidate(s), best ${last.candidates[0].name} (${last.candidates[0].score}).`;
+        ctx.notify('info', `Skill triage: ${on ? 'on' : 'off'}. ${summary}`);
+        return;
+    }
+    if (requested !== 'on' && requested !== 'off') {
+        ctx.notify('warn', `Unknown argument "${argument}" - use /skills triage [on|off].`);
+        return;
+    }
+    const enabled = requested === 'on';
+    // `setTriageEnabled` persists AND fires `onChange`, which rebuilds the prompt in
+    // this session. Without that second half the switch would look applied and take
+    // effect only after a restart (AC-T23).
+    service.setTriageEnabled(enabled);
+    // A toast, not a transcript notice: flipping a switch is an acknowledgement, and
+    // `toast` is this package's channel for exactly that (see `toggleSkill`). The
+    // level still differs by direction, so "off" does not read as a win.
+    ctx.toast(enabled ? 'success' : 'info', `Skill triage: ${enabled ? 'on' : 'off'}. ` +
+        (enabled
+            ? 'Each new task gets a short candidate list.'
+            : 'The system prompt no longer carries the triage block.'));
+}
+/**
+ * `/skills route [text]`.
+ *
+ * Two modes, one output shape. With text it routes that text; without text it
+ * replays the previous turn's real routing, which is the case a user is most often
+ * in — they just watched the model ignore a suggestion. The "never triaged" text
+ * names the form that works instead of leaving them to guess.
+ */
+function routeFromCommand(ctx, service, argument) {
+    const task = argument.trim();
+    if (task.length === 0) {
+        const last = ctx.controller.getSkillRouting();
+        if (last === null) {
+            ctx.notify('info', 'No turn has been triaged yet. Run /skills route <text> to try one.');
+            return;
+        }
+        ctx.notify('info', renderRoutingReport(last));
+        return;
+    }
+    // A fresh computation, NOT the cached one: `/skills route <text>` is how a user
+    // tests whether a phrasing would have matched.
+    ctx.notify('info', renderRoutingReport(service.route(task)));
+}
+/** One `info` notification, one line per candidate, ASCII only (`commands/`). */
+function renderRoutingReport(report) {
+    if (report.candidates.length === 0) {
+        const close = report.topUnqualified === null
+            ? ''
+            : ` Closest was ${report.topUnqualified.name} (${report.topUnqualified.score}); ` +
+                `the threshold is ${SKILL_TRIAGE_LIMITS.minScore}.`;
+        return (`No skill matched "${report.task}". The catalog has ${report.eligible} eligible skills.` +
+            close);
+    }
+    const lines = report.candidates.map((candidate) => {
+        const reasons = candidate.reasons.length > 0 ? candidate.reasons.join('+') : 'none';
+        return `${candidate.name} (${candidate.scope}) score ${candidate.score} [${reasons}]`;
+    });
+    return [`Routed "${report.task}" (${report.tokenCount} token(s)):`, ...lines].join('\n');
+}
+// ---------------------------------------------------------------------------
 // /skills policy · unload · usage  (§5.5 / §9)
 // ---------------------------------------------------------------------------
 /**

package/dist/commands/subagent-command.d.ts

@@ -0,0 +1,25 @@
+/**
+ * `/subagent` — force the next turn to fan out into a parallel team
+ * (subagent-fanout 3.5 / 5.2).
+ *
+ * ASCII ONLY: `src/commands/**` is inside `glyphs.test.ts::inScope`.
+ *
+ * WHAT THIS COMMAND IS AND IS NOT (D-8 / D-9 / D-10). It does not dispatch: it
+ * parses the user's intent, refuses honestly when forcing cannot work, prints
+ * ONE line saying what will happen next, and submits a normal user turn. The
+ * lead then calls `task` on the one dispatch path that already exists, so Esc,
+ * the watchdog pause, the report, spend accounting and the concurrency lock all
+ * keep working without a second implementation. The consequence the user must
+ * be told about is that forcing is INSTRUCTION-LEVEL: the notice says "the next
+ * turn dispatches them", never "N subagents started".
+ *
+ * THE GUARD ORDER IS A CONTRACT (R-P1-10 / R-P1-11): status -> capability ->
+ * parse. A `--no-team` session typing `/subagent -n x` is told the session has
+ * no team capability, because a syntax hint would send them to fix the one thing
+ * that is not wrong.
+ */
+import type { CommandContext, CommandRegistry } from './registry.js';
+/** The command body; `registerSubagentCommand` is the only registration site. */
+export declare function runSubagentCommand(ctx: CommandContext): void;
+/** Registered from `builtins.ts` with one line, next to every other subsystem. */
+export declare function registerSubagentCommand(registry: CommandRegistry): void;