@compilr-dev/cli 0.7.3 → 0.7.5

package/dist/tools.js

@@ -1,387 +1,32 @@
 /**
- * Tool Registry Setup
+ * Tool Registry Helpers (slim).
  *
- * Configures all available tools from @compilr-dev/sdk
- * (which re-exports from @compilr-dev/agents and @compilr-dev/agents-coding).
+ * Pre-SDK migration this file owned the full HOT_TOOLS / WARM_TOOLS /
+ * DIRECT_TOOLS / META_REGISTRY_TOOLS arrays and a token-saving registry
+ * (~15K → ~2K per turn). That optimisation moved to the SDK as the
+ * capability-manager direct/meta tier split (`TOOL_GROUPS.<id>.tier`),
+ * and `createCompilrAgent({ capabilities: ... })` now handles tool
+ * registration end-to-end. See `src/agent.ts` and
+ * `@compilr-dev/sdk/src/capabilities/packs.ts`.
  *
- * ARCHITECTURE (Meta-Tools):
- * - DIRECT TOOLS: Always available, called by name (most common operations)
- * - META-REGISTRY TOOLS: Available via use_tool() (specialized operations)
+ * What remains here is the small surface CLI code outside agent.ts still
+ * touches:
+ *   - `todoStore` — alias for the SDK's `getDefaultTodoStore()` singleton,
+ *     read by the footer renderer (see `repl-v2.ts`).
+ *   - `TOOL_NAMES` / `ToolName` / `getAllToolNames` — re-exported from
+ *     `./tool-names.js` for convenience.
  *
- * This reduces token overhead from ~15K to ~2K per request.
+ * Audit refs: TODO-4 (HOT/WARM cleanup), TODO-15 (deleted the parallel
+ * dead MetaToolsRegistry singleton + its setMetaToolFilter /
+ * getRegisteredMetaTools / isMetaToolSilent surface — the SDK's
+ * per-agent CapabilityManager already handles tool filtering at agent
+ * factory time, so the CLI re-exports here were always no-ops).
  *
- * SINGLE SOURCE OF TRUTH:
- * Tool names are defined in tool-names.ts (a dependency-free module).
- * This file re-exports them for convenience. Import from here or tool-names.ts.
- */
-// Re-export tool names from the dependency-free module
-// This breaks circular dependencies while maintaining a single source of truth
-export { TOOL_NAMES, DIRECT_TOOL_NAMES, HOT_TOOL_NAMES, WARM_TOOL_NAMES, META_TOOL_NAMES, META_REGISTRY_TOOL_NAMES, getAllToolNames, } from './tool-names.js';
-// =============================================================================
-// TOOL IMPORTS
-// =============================================================================
-import { readFileTool, writeFileTool, createBashTool, bashOutputTool, killShellTool, grepTool, globTool, editTool, createTodoTools, defineTool, } from '@compilr-dev/sdk';
-// Create todo tools with shared store (includes claim/handoff)
-const todoToolsResult = createTodoTools();
-const originalTodoWriteTool = todoToolsResult.todoWrite;
-const todoReadTool = todoToolsResult.todoRead;
-const todoClaimTool = todoToolsResult.todoClaim;
-const todoHandoffTool = todoToolsResult.todoHandoff;
-// Explicit type annotation avoids TS2742 when importing createTodoTools via @compilr-dev/sdk
-export const todoStore = todoToolsResult.store;
-const todoWriteTool = defineTool({
-    name: 'todo_write',
-    description: 'Update the SESSION todo list (shown in footer). These are ephemeral tasks for the current session only. ' +
-        'For persistent project backlog items, use workitem_* tools instead. ' +
-        'Provide the complete list of todos to replace the current list.',
-    inputSchema: {
-        type: 'object',
-        properties: {
-            todos: {
-                type: 'array',
-                description: 'The complete list of todos',
-                items: {
-                    type: 'object',
-                    properties: {
-                        content: {
-                            type: 'string',
-                            description: 'Task description (imperative form, e.g., "Fix bug in login")',
-                        },
-                        status: {
-                            type: 'string',
-                            enum: ['pending', 'in_progress', 'completed'],
-                            description: 'Task status',
-                        },
-                        activeForm: {
-                            type: 'string',
-                            description: 'Active form (present continuous, e.g., "Fixing bug in login")',
-                        },
-                        priority: {
-                            type: 'number',
-                            description: 'Priority (higher = more important)',
-                        },
-                        owner: {
-                            type: 'string',
-                            description: 'Owner agent ID (e.g., "dev", "pm", "arch"). Omit for unassigned.',
-                        },
-                        blockedBy: {
-                            type: 'array',
-                            items: { type: 'number' },
-                            description: 'Array of 1-based task numbers this task depends on (e.g., [3, 4] means blocked by task #3 and #4)',
-                        },
-                    },
-                    required: ['content', 'status'],
-                },
-            },
-        },
-        required: ['todos'],
-    },
-    execute: async (input) => {
-        // Normalize todos - accept alternative property names
-        const normalizedTodos = input.todos.map((todo) => ({
-            content: (todo.content || todo.title || todo.description || todo.task || todo.text || '').trim(),
-            status: todo.status,
-            activeForm: todo.activeForm,
-            priority: todo.priority,
-            owner: todo.owner,
-            blockedBy: todo.blockedBy,
-        }));
-        // Filter out empty todos and provide fallback
-        const validTodos = normalizedTodos.map((todo) => ({
-            ...todo,
-            content: todo.content || 'Untitled task',
-        }));
-        // Call the original tool with normalized input
-        const result = await originalTodoWriteTool.execute({ todos: validTodos });
-        return result;
-    },
-    silent: true,
-});
-// Create bash tool with longer timeout (2 minutes instead of 30 seconds)
-const bashTool = createBashTool({
-    timeout: 120000, // 2 minutes
-});
-import { 
-// Git tools (basic)
-gitStatusTool, gitDiffTool, gitLogTool, gitCommitTool, gitBranchTool, 
-// Git tools (advanced)
-gitStashTool, gitBlameTool, gitFileHistoryTool, 
-// Project detection
-detectProjectTool, findProjectRootTool, 
-// Smart runners
-runTestsTool, runLintTool, runBuildTool, runFormatTool, 
-// Code search
-findDefinitionTool, findReferencesTool, findTodosTool, 
-// Dependency analysis
-checkOutdatedTool, findVulnerabilitiesTool, 
-// Testing analysis
-analyzeTestCoverageTool, 
-// Unified analysis (auto-detect language)
-getFileStructureTool, getComplexityTool, } from '@compilr-dev/sdk';
-// Local tools
-import { askUserTool } from './tools/ask-user.js';
-import { askUserSimpleTool } from './tools/ask-user-simple.js';
-import { delegateTool } from './tools/delegate.js';
-import { delegateBackgroundTool } from './tools/delegate-background.js';
-import { delegationStatusTool } from './tools/delegation-status.js';
-import { handoffTool } from './tools/handoff.js';
-import { createGuideTool } from '@compilr-dev/sdk';
-import { CLI_GUIDE_ENTRIES } from './guide/cli-guide-entries.js';
-const guideTool = createGuideTool({
-    environment: 'cli',
-    additionalEntries: CLI_GUIDE_ENTRIES,
-});
-// DB tools for project, work item, document, plan, backlog, anchor, artifact, and episode management
-import { allDbTools, allFactoryTools } from './tools/db-tools.js';
-// Meta-tools for dynamic tool loading
-import { initializeMetaToolRegistry, generateToolIndex, generateFilteredToolIndex, getMetaToolCount, META_TOOLS_SYSTEM_PROMPT_PREFIX, setMetaToolFilter, getRegisteredMetaTools, createMetaToolFallback, getToolInfoTool, } from './tools/meta-tools.js';
-// Re-export for use in agent.ts
-export { setMetaToolFilter, getRegisteredMetaTools };
-/**
- * Check if a tool in the meta-registry is marked as silent.
- * Used by the repl to suppress output for warm tools like todo_write/todo_read.
- */
-export function isMetaToolSilent(name) {
-    const tools = getRegisteredMetaTools();
-    const tool = tools.find((t) => t.definition.name === name);
-    return tool?.silent === true;
-}
-// =============================================================================
-// DIRECT TOOLS - Always available, called by name
-// =============================================================================
-/**
- * Hot tools — used in >50% of turns. Always declared as direct schemas.
- * Estimated: ~2,100 tokens for definitions
- */
-const HOT_TOOLS = [
-    // File operations (most common)
-    readFileTool,
-    writeFileTool,
-    editTool,
-    // Shell (very common)
-    bashTool,
-    // Search (very common)
-    globTool,
-    grepTool,
-    // User interaction (always needed)
-    askUserTool,
-];
-/**
- * Warm tools — used occasionally. In hot-tools mode these move to meta-registry.
- * Estimated: ~3,300 tokens for definitions
- */
-const WARM_TOOLS = [
-    // Shell management
-    bashOutputTool,
-    killShellTool,
-    // Task tracking
-    todoWriteTool,
-    todoReadTool,
-    todoClaimTool,
-    todoHandoffTool,
-    // User interaction (simple variant)
-    askUserSimpleTool,
-    // Delegation (coordinator only)
-    delegateTool,
-    // Background delegation (coordinator mode)
-    delegateBackgroundTool,
-    // Handoff (specialist-to-specialist)
-    handoffTool,
-    // CLI documentation
-    guideTool,
-];
-/**
- * All direct tools combined (hot + warm).
- * Used in legacy mode (no meta-tools) and for backwards compatibility.
- */
-const DIRECT_TOOLS = [...HOT_TOOLS, ...WARM_TOOLS];
-// =============================================================================
-// META-REGISTRY TOOLS - Available via use_tool()
-// =============================================================================
-/**
- * Meta-registry tools are specialized tools available via use_tool().
- * Instead of declaring their full schemas (~12K tokens), we:
- * 1. Add them to a registry
- * 2. Generate a tool index for the system prompt (~800 tokens)
- * 3. Let the agent call them via use_tool("tool_name", {args})
- */
-const META_REGISTRY_TOOLS = [
-    // Git operations (basic)
-    gitStatusTool,
-    gitDiffTool,
-    gitLogTool,
-    gitCommitTool,
-    gitBranchTool,
-    // Git operations (advanced)
-    gitStashTool,
-    gitBlameTool,
-    gitFileHistoryTool,
-    // Project detection
-    detectProjectTool,
-    findProjectRootTool,
-    // Smart runners
-    runTestsTool,
-    runLintTool,
-    runBuildTool,
-    runFormatTool,
-    // Code search (language-agnostic)
-    findDefinitionTool,
-    findReferencesTool,
-    findTodosTool,
-    // Dependency analysis
-    checkOutdatedTool,
-    findVulnerabilitiesTool,
-    // Testing analysis
-    analyzeTestCoverageTool,
-    // Unified analysis (auto-detect language: TS/JS/Python/Go)
-    getFileStructureTool,
-    getComplexityTool,
-    // DB tools (project, workitem, document, plan, backlog, anchor, artifact, episode)
-    ...allDbTools,
-    // Factory tools (app_model_get, app_model_update, app_model_validate, factory_scaffold, factory_list_toolkits)
-    ...allFactoryTools,
-    // Delegation status (coordinator query)
-    delegationStatusTool,
-];
-// =============================================================================
-// LEGACY API (for backwards compatibility)
-// =============================================================================
-/**
- * Creates the tool registry with all available tools.
- * Returns tools as-is - the Agent.registerTools() method handles typing.
- *
- * @deprecated Use createDirectToolRegistry() + initializeMetaTools() instead
- */
-export function createToolRegistry() {
-    return [
-        ...DIRECT_TOOLS,
-        ...META_REGISTRY_TOOLS,
-    ];
-}
-/**
- * Returns a minimal set of tools for basic testing.
- */
-export function createMinimalToolRegistry() {
-    return [
-        readFileTool,
-        writeFileTool,
-        bashTool,
-        globTool,
-    ];
-}
-// =============================================================================
-// META-TOOLS API (new architecture)
-// =============================================================================
-/**
- * Get direct tools that are always available.
- * When hotOnly is true, returns only hot tools (7 tools, ~2.1K tokens).
- * When false/undefined, returns all direct tools (18 tools, ~5.4K tokens).
- */
-export function getDirectTools(hotOnly) {
-    if (hotOnly)
-        return HOT_TOOLS;
-    return DIRECT_TOOLS;
-}
-/**
- * Get meta-tools for agent registration.
- * Only get_tool_info is kept as a direct tool — use_tool and list_tools
- * are no longer needed since the fallback handler routes calls transparently.
- */
-export function getMetaTools() {
-    return [getToolInfoTool];
-}
-/**
- * Create a fallback handler for the tool registry.
- * When the agent calls a tool not in the direct registry, this handler
- * checks the meta-registry and executes it transparently.
- *
- * Auto-loading of capability packs for filtered tools is handled by the
- * shared onFilteredTool callback in meta-tools.ts (covers both use_tool
- * and direct fallback paths).
- */
-export function createToolFallback() {
-    return createMetaToolFallback();
-}
-/** Whether hot-tools mode is active (warm tools in meta-registry) */
-let hotToolsModeActive = false;
-/**
- * Check if hot-tools mode is active.
- * When true, only hot tools are declared as direct schemas; warm tools are in meta-registry.
- */
-export function isHotToolsMode() {
-    return hotToolsModeActive;
-}
-/**
- * Initialize the meta-tool registry with specialized tools.
- * When includeWarmTools is true, warm tools are also added to the meta-registry
- * (enabling hot-tools mode where only 7 core tools are declared directly).
- * Call this once at startup.
- */
-export function initializeMetaTools(includeWarmTools) {
-    const tools = includeWarmTools
-        ? [...WARM_TOOLS, ...META_REGISTRY_TOOLS]
-        : META_REGISTRY_TOOLS;
-    initializeMetaToolRegistry(tools);
-    if (includeWarmTools) {
-        hotToolsModeActive = true;
-    }
-}
-/**
- * Get the tool index for the system prompt.
- * This lists all meta-registry tools with their signatures.
- */
-export function getToolIndexForSystemPrompt() {
-    return META_TOOLS_SYSTEM_PROMPT_PREFIX + generateToolIndex();
-}
-/**
- * Get a filtered tool index for the system prompt.
- * Only includes tools whose names are in the given set.
- * Used by the capability-aware BeforeLLM hook.
- */
-export function getFilteredToolIndexForSystemPrompt(activeToolNames) {
-    return META_TOOLS_SYSTEM_PROMPT_PREFIX + generateFilteredToolIndex(activeToolNames);
-}
-/**
- * Get count of meta-registry tools.
- */
-export function getMetaToolsCount() {
-    return getMetaToolCount();
-}
-/**
- * Check if meta-tools mode is enabled.
- * Returns true if the meta-tool registry has been initialized.
- */
-export function isMetaToolsEnabled() {
-    return getMetaToolCount() > 0;
-}
-// =============================================================================
-// STATISTICS
-// =============================================================================
-/**
- * Get tool statistics for debugging/display.
- */
-export function getToolStats() {
-    const hotCount = HOT_TOOLS.length;
-    const warmCount = WARM_TOOLS.length;
-    const directCount = hotToolsModeActive ? hotCount : hotCount + warmCount;
-    const metaCount = hotToolsModeActive
-        ? META_REGISTRY_TOOLS.length + warmCount
-        : META_REGISTRY_TOOLS.length;
-    const totalCount = hotCount + warmCount + META_REGISTRY_TOOLS.length;
-    // Rough estimates: ~300 tokens per tool definition
-    const tokensPerTool = 300;
-    const estimatedDirectTokens = directCount * tokensPerTool;
-    const estimatedMetaTokens = 1000; // Tool index + meta-tool definitions
-    const estimatedLegacyTokens = totalCount * tokensPerTool;
-    return {
-        directTools: directCount,
-        hotTools: hotCount,
-        warmTools: warmCount,
-        metaRegistryTools: metaCount,
-        totalTools: totalCount,
-        estimatedDirectTokens,
-        estimatedMetaTokens,
-        estimatedLegacyTokens,
-        tokenSavings: estimatedLegacyTokens - estimatedDirectTokens - estimatedMetaTokens,
-    };
-}
+ * See `project-docs/00-requirements/compilr-dev-sdk/architecture-audit-cli-vs-desktop.md`.
+ */
+import { getDefaultTodoStore } from '@compilr-dev/sdk';
+// Tool-name constants — re-exported from the dependency-free module.
+export { TOOL_NAMES, getAllToolNames } from './tool-names.js';
+// Footer + UI reads this; the SDK preset's todo tools write through the
+// same singleton (audit TODO-9).
+export const todoStore = getDefaultTodoStore();

package/dist/ui/markdown-renderer.js

@@ -112,22 +112,40 @@ function reflowText(text, width, gfm) {
         const fragments = sec.split(/(\u001b\[(?:\d{1,3})(?:;\d{1,3})*m)/g);
         let column = 0;
         let currentLine = '';
-        let lastWasEscape = false;
+        // Carries through ANSI fragments so the space-before-word decision for
+        // the next text fragment knows whether boundary whitespace existed in
+        // the source. Fixes the bug where "the `consult` tool" rendered as
+        // "theconsulttool" — the trailing space of "the " and leading space of
+        // " tool" were both discarded by the split-on-whitespace, and the old
+        // `lastWasEscape` flag suppressed re-inserting them.
+        let prevTextEndedWithWs = false;
         for (const fragment of fragments) {
-            if (fragment === '') {
-                lastWasEscape = false;
+            if (fragment === '')
                 continue;
-            }
             if (!textLength(fragment)) {
+                // ANSI escape sequence — append untouched. We deliberately do NOT
+                // reset prevTextEndedWithWs here, so the next text fragment can
+                // still re-introduce a space across the ANSI boundary if needed.
                 currentLine += fragment;
-                lastWasEscape = true;
                 continue;
             }
+            // Plain text fragment.
+            const startsWithWs = /^[ \t\n]/.test(fragment);
+            const endsWithWs = /[ \t\n]$/.test(fragment);
             const words = fragment.split(/[ \t\n]+/);
+            let isFirstWordInFragment = true;
             for (const word of words) {
                 if (!word)
                     continue;
-                const addSpace = column !== 0 && !lastWasEscape;
+                // Insert a space before this word when column > 0 AND one of:
+                //   - it's NOT the first word in this fragment (intra-fragment
+                //     whitespace existed), OR
+                //   - this fragment had leading whitespace (e.g. " tool" after a
+                //     closing ANSI), OR
+                //   - the previous text fragment ended with whitespace (e.g.
+                //     "the " before an opening ANSI).
+                const addSpace = column !== 0 &&
+                    (!isFirstWordInFragment || startsWithWs || prevTextEndedWithWs);
                 const neededWidth = word.length + (addSpace ? 1 : 0);
                 if (column + neededWidth > width && word.length <= width) {
                     reflowed.push(currentLine);
@@ -160,8 +178,9 @@ function reflowText(text, width, gfm) {
                     currentLine += word;
                     column += word.length;
                 }
-                lastWasEscape = false;
+                isFirstWordInFragment = false;
             }
+            prevTextEndedWithWs = endsWithWs;
         }
         if (textLength(currentLine))
             reflowed.push(currentLine);

package/dist/ui/overlay/data/tutorial-registry.js

@@ -16,6 +16,7 @@ import { sessionManagementTutorial } from './tutorials/projects/session-manageme
 import { anchorsTutorial } from './tutorials/projects/anchors.js';
 import { importProjectTutorial } from './tutorials/projects/import-project.js';
 import { appModelTutorial } from './tutorials/projects/app-model.js';
+import { interactiveFlowsTutorial } from './tutorials/projects/interactive-flows.js';
 import { designTutorial } from './tutorials/planning/design.js';
 import { backlogTutorial } from './tutorials/planning/backlog.js';
 import { sketchTutorial } from './tutorials/planning/sketch.js';
@@ -69,6 +70,7 @@ export function buildTutorialRegistry(s) {
                 sessionManagementTutorial(s),
                 anchorsTutorial(s),
                 appModelTutorial(s),
+                interactiveFlowsTutorial(s),
             ],
         },
         // =========================================================================

package/dist/ui/overlay/data/tutorials/projects/interactive-flows.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Interactive Flows Tutorial
+ *
+ * Explains the `build_interactive_flow` agent tool — when an agent uses it,
+ * what to expect when the modal opens, and how it differs from `/ask_user`.
+ * Desktop-only feature in Phase 1 (CLI degradation lands in Phase 3).
+ */
+import type { TutorialBuilder } from '../../tutorial-types.js';
+export declare const interactiveFlowsTutorial: TutorialBuilder;

package/dist/ui/overlay/data/tutorials/projects/interactive-flows.js

@@ -0,0 +1,94 @@
+/**
+ * Interactive Flows Tutorial
+ *
+ * Explains the `build_interactive_flow` agent tool — when an agent uses it,
+ * what to expect when the modal opens, and how it differs from `/ask_user`.
+ * Desktop-only feature in Phase 1 (CLI degradation lands in Phase 3).
+ */
+export const interactiveFlowsTutorial = (s) => ({
+    id: 'interactive-flows',
+    title: 'Interactive Flows',
+    description: 'Agent-driven decision trees',
+    pages: [
+        // Page 1: What it is
+        {
+            title: 'What is an Interactive Flow?',
+            lines: [
+                '',
+                `  Sometimes an agent needs to walk you through a ${s.primaryBold('branching decision')}`,
+                `  — picking a database, choosing a stack, navigating a tradeoff.`,
+                '',
+                `  Instead of asking 5 questions in a row, the agent can build a`,
+                `  ${s.primary('navigable tree')} you step through with Back/Forward.`,
+                '',
+                `  ${s.secondary('Each step shows up as a modal on the desktop app:')}`,
+                '',
+                `    ${s.muted('•')} Single-choice questions ${s.muted('(pick one)')}`,
+                `    ${s.muted('•')} Multi-select questions ${s.muted('(pick several)')}`,
+                `    ${s.muted('•')} Free-text questions ${s.muted('(type your answer)')}`,
+                `    ${s.muted('•')} Info screens ${s.muted('(read context, click Next)')}`,
+                `    ${s.muted('•')} A summary at the end recapping your choices`,
+                '',
+                `  ${s.warning('Desktop-only for now.')} CLI rendering arrives later — when the`,
+                `  agent uses this tool from a CLI session, you'll see a degraded`,
+                `  text-prompt fallback.`,
+                '',
+            ],
+        },
+        // Page 2: When agents use it
+        {
+            title: 'When the Agent Uses This',
+            lines: [
+                '',
+                `  Agents pick ${s.primaryBold('build_interactive_flow')} over plain ${s.primary('ask_user')} when:`,
+                '',
+                `    ${s.primary('1.')} The decision has ${s.primaryBold('2+ branching considerations')} —`,
+                `       "if you pick A, the next question changes"`,
+                '',
+                `    ${s.primary('2.')} You'd benefit from ${s.primaryBold('exploring before committing')} —`,
+                `       Back/Forward lets you revisit prior steps`,
+                '',
+                `    ${s.primary('3.')} The reasoning ${s.primaryBold('matters as much as the answer')} —`,
+                `       the agent gets back your full path through the tree, not`,
+                `       just your final choice`,
+                '',
+                `  ${s.secondary('Typical patterns:')}`,
+                '',
+                `    ${s.muted('•')} Tech stack selection ${s.muted('(database type → vendor → details)')}`,
+                `    ${s.muted('•')} Architecture trade-offs ${s.muted('(monolith vs microservices)')}`,
+                `    ${s.muted('•')} Backlog item refinement ${s.muted('(complexity, dependencies, scope)')}`,
+                `    ${s.muted('•')} Project type selection during ${s.primary('/design')}`,
+                '',
+            ],
+        },
+        // Page 3: Navigation + result
+        {
+            title: 'What to Expect',
+            lines: [
+                '',
+                `  ${s.secondary('In the modal:')}`,
+                '',
+                `    ${s.primaryBold('Single-choice')}    Click an option → auto-advance to next step`,
+                `    ${s.primaryBold('Multi-select')}     Tick boxes → ${s.primary('Next')} button to advance`,
+                `    ${s.primaryBold('Free text')}        Type → ${s.muted('Enter')} (single-line) or`,
+                `                      ${s.muted('Cmd/Ctrl+Enter')} (multi-line) to submit`,
+                `    ${s.primaryBold('Summary')}          Confirm your path, or ${s.primary('Back')} to revise`,
+                '',
+                `  ${s.secondary('Cancel anytime:')}`,
+                '',
+                `    ${s.muted('•')} ${s.primary('Esc')} key`,
+                `    ${s.muted('•')} ${s.primary('X')} icon in the header`,
+                `    ${s.muted('•')} Click outside the modal`,
+                '',
+                `  Canceling sends the agent ${s.primaryBold('completed: false')} with your`,
+                `  partial answers. The agent can resume the same flow or ask`,
+                `  again with adjustments.`,
+                '',
+                `  ${s.warning('TIP:')} The agent gets your full path back — including any`,
+                `  nodes you backtracked through. That's intentional: the path is`,
+                `  ${s.primaryBold('reasoning data')}, not just answer data.`,
+                '',
+            ],
+        },
+    ],
+});