@bradygaster/squad-cli 0.9.6-insider.2 → 0.9.6-insider.3

package/templates/skills/squad-commands/SKILL.md

@@ -0,0 +1,303 @@
+---
+name: squad-commands
+description: >
+  Categorized catalog of common Squad operations. Coordinator reads this
+  file and presents it as an interactive menu when the user asks for
+  available commands or help.
+domain: squad-operations
+confidence: high
+source: first-party
+triggers: ["squad commands", "what can squad do", "show me squad options", "slash commands"]
+---
+
+## Menu Presentation Rules
+
+When the user triggers this skill ("squad commands", "help", "what can squad do", etc.):
+
+1. **Category-level menu first.** Present category names as an `ask_user` choice list:
+   ```
+   📋 Squad Commands — pick a category:
+   1. Install & Upgrade
+   2. Team Management
+   3. Issues & PRs
+   4. Plugins & Skills
+   5. Model & Cost
+   6. Sessions & State
+   ```
+2. **Drill-down.** After selection, show operation titles in that category as a second `ask_user` list.
+3. **Direct match skips the menu.** If the user says "how do I upgrade with state backend," match to the specific entry and go straight to argument collection.
+4. **Compact fallback.** If `ask_user` is unavailable, render as a markdown table instead.
+5. **Back / Cancel.** Include "← Back to categories" in sub-menus. Include "Cancel" in confirmation prompts. Respect "never mind" / "cancel" at any point.
+
+**Argument collection:** For entries with `args`, iterate the list sequentially. Use `ask_user` with choices when `choices` is provided; free-text prompt otherwise. If the user says "just do it" or "defaults are fine," skip remaining args and use their defaults.
+
+**Confirmation template:**
+```
+⚠️ This will {action-description}.
+{what will change}
+Proceed? (yes / no)
+```
+
+---
+
+## Install & Upgrade
+
+### Upgrade Squad CLI
+
+- **intent:** upgrade squad, update squad, install latest version, get new version
+- **summary:** Upgrade Squad CLI to the latest version for your channel
+- **action:** shell
+- **command:** squad upgrade
+- **args:**
+  - `state-backend`: Which state backend? | choices: {worktree, git-notes, orphan, two-layer} | default: (keep current)
+- **confirm:** false
+- **platform_caveats:** Requires terminal. In VS Code, open the integrated terminal and run the command directly.
+
+### Initialize Squad
+
+- **intent:** set up squad, initialize squad, create team, start squad in this project
+- **summary:** Scaffold Squad in the current directory (idempotent)
+- **action:** shell
+- **command:** squad init
+- **args:** (none)
+- **confirm:** false
+- **platform_caveats:** Requires terminal. Recommend a standalone terminal for best results.
+
+### Switch State Backend
+
+- **intent:** switch state backend, change state storage, use git-notes, use orphan branch
+- **summary:** Change where Squad stores mutable state (config.json)
+- **action:** file-edit
+- **command:** .squad/config.json → stateBackend
+- **args:**
+  - `stateBackend`: Which state backend? | choices: {worktree, git-notes, orphan, two-layer} | default: (keep current)
+- **confirm:** true
+- **platform_caveats:** May require migration if switching away from worktree. Show current value and new value before confirming.
+
+---
+
+## Team Management
+
+### Add Team Member
+
+- **intent:** add team member, hire agent, add agent, add developer, recruit
+- **summary:** Add a new agent to the team roster
+- **action:** coordinator
+- **command:** Add Team Member flow (Init Mode / Team Mode)
+- **args:**
+  - `role`: What role should this agent fill? (e.g., Frontend Dev, Backend Dev, QA Engineer)
+  - `name`: Preferred name or casting universe? | default: (auto-cast from active universe)
+- **confirm:** false
+
+### Remove Team Member
+
+- **intent:** remove team member, fire agent, delete agent, remove developer
+- **summary:** Remove an agent and delete their charter and history files
+- **action:** coordinator
+- **command:** Remove Team Member flow
+- **args:**
+  - `member`: Which team member to remove? (name or role)
+- **confirm:** true
+
+### Reassign Roles
+
+- **intent:** reassign role, change role, swap roles, update team member role
+- **summary:** Update a team member's role in team.md and their charter
+- **action:** coordinator
+- **command:** Update team.md roster + charter.md
+- **args:**
+  - `member`: Which team member?
+  - `newRole`: New role?
+- **confirm:** false
+
+### Show Roster
+
+- **intent:** show roster, who is on the team, list team members, show team, capability profile
+- **summary:** Display the current team roster and capability profile
+- **action:** coordinator
+- **command:** Direct Mode — read team.md, answer
+- **args:** (none)
+- **confirm:** false
+
+---
+
+## Issues & PRs
+
+### Connect GitHub Repo
+
+- **intent:** connect github, enable issues, set up issues, link repository, github issues mode
+- **summary:** Connect this project to GitHub Issues via gh auth
+- **action:** coordinator
+- **command:** GitHub Issues Mode (connection flow)
+- **args:** (none)
+- **confirm:** false
+- **platform_caveats:** Requires `gh auth login` to have been run in the terminal.
+
+### Triage Issues
+
+- **intent:** triage issues, review issues, assign issues, label issues
+- **summary:** Run the Lead triage flow on open GitHub issues
+- **action:** coordinator
+- **command:** GitHub Issues Mode → Lead triage
+- **args:** (none)
+- **confirm:** false
+
+### Activate Ralph
+
+- **intent:** activate ralph, start ralph, ralph go, start work monitor, start auto-work
+- **summary:** Activate Ralph — Work Monitor — to pick up and run queued issues
+- **action:** coordinator
+- **command:** Ralph — Work Monitor triggers
+- **args:** (none)
+- **confirm:** false
+
+### Set Ralph Polling Interval
+
+- **intent:** set ralph interval, change ralph timing, how often does ralph check, ralph every N minutes
+- **summary:** Tell Ralph how frequently to poll for new work
+- **action:** coordinator
+- **command:** Ralph trigger: "Ralph, check every N minutes"
+- **args:**
+  - `interval`: How often should Ralph poll? (in minutes) | default: 10
+- **confirm:** false
+
+### Start Squad Watch
+
+- **intent:** start watch, squad watch, monitor issues, watch for issues, auto-triage
+- **summary:** Start squad watch to continuously poll and triage issues
+- **action:** shell
+- **command:** squad watch
+- **args:**
+  - `interval`: Poll interval in minutes | default: 10
+- **confirm:** false
+- **platform_caveats:** CLI-only — long-running foreground process. Not viable in VS Code without an integrated terminal. Run: `squad watch --interval {n}` in your terminal.
+
+---
+
+## Plugins & Skills
+
+### Browse Plugin Marketplace
+
+- **intent:** browse plugins, explore plugins, what plugins are available, plugin marketplace
+- **summary:** Browse available plugins in the Squad marketplace
+- **action:** shell
+- **command:** squad plugin marketplace browse
+- **args:**
+  - `name`: Plugin name to search for | default: (browse all)
+- **confirm:** false
+
+### Add Marketplace Plugin
+
+- **intent:** add plugin, install plugin, get plugin from marketplace
+- **summary:** Add a plugin from the marketplace to this Squad
+- **action:** shell
+- **command:** squad plugin marketplace add
+- **args:**
+  - `plugin`: Plugin owner/repo (e.g., owner/plugin-name)
+- **confirm:** false
+
+### Remove Marketplace Plugin
+
+- **intent:** remove plugin, uninstall plugin, delete plugin
+- **summary:** Remove an installed marketplace plugin
+- **action:** shell
+- **command:** squad plugin marketplace remove
+- **args:**
+  - `name`: Plugin name to remove
+- **confirm:** true
+
+### List Marketplace Plugins
+
+- **intent:** list plugins, show installed plugins, what plugins do I have
+- **summary:** List all plugins registered in this Squad
+- **action:** shell
+- **command:** squad plugin marketplace list
+- **args:** (none)
+- **confirm:** false
+
+### List Installed Skills
+
+- **intent:** list skills, show skills, what skills are installed, skill catalog
+- **summary:** List all skills installed in .squad/skills/ and .copilot/skills/
+- **action:** coordinator
+- **command:** Direct Mode — list .squad/skills/ and .copilot/skills/ directories
+- **args:** (none)
+- **confirm:** false
+
+---
+
+## Model & Cost
+
+### Set Default Model
+
+- **intent:** set default model, change model, use gpt-4, use claude, switch model
+- **summary:** Set the default model for all agents in config.json
+- **action:** file-edit
+- **command:** .squad/config.json → defaultModel
+- **args:**
+  - `model`: Model name (e.g., gpt-4o, claude-sonnet-4.5, o3)
+- **confirm:** false
+
+### Override Per-Agent Model
+
+- **intent:** set model for agent, agent model override, use different model for one agent
+- **summary:** Set a model override for a specific agent in config.json
+- **action:** file-edit
+- **command:** .squad/config.json → agentModelOverrides.{agentName}
+- **args:**
+  - `agent`: Agent name (must match name in team.md)
+  - `model`: Model name (e.g., gpt-4o, claude-sonnet-4.5)
+- **confirm:** false
+
+### Clear Model Preference
+
+- **intent:** clear model, reset model, remove model preference, use default model
+- **summary:** Remove a model override from config.json (reverts to system default)
+- **action:** file-edit
+- **command:** .squad/config.json → remove defaultModel or agentModelOverrides.{agentName}
+- **args:**
+  - `scope`: Clear default or a specific agent? | choices: {default model, specific agent} | default: default model
+  - `agent`: Agent name (only if scope = specific agent)
+- **confirm:** false
+
+---
+
+## Sessions & State
+
+### Catch-Up Summary
+
+- **intent:** catch me up, what happened, status, what did the team do, session summary
+- **summary:** Summarize recent agent activity and key decisions
+- **action:** coordinator
+- **command:** Session catch-up flow (lazy scan)
+- **args:** (none)
+- **confirm:** false
+
+### Show Recent Decisions
+
+- **intent:** show decisions, recent decisions, what decisions were made, decision log
+- **summary:** Display recent entries from .squad/decisions.md
+- **action:** coordinator
+- **command:** Direct Mode — read decisions.md, answer
+- **args:** (none)
+- **confirm:** false
+
+### Archive Old Decisions
+
+- **intent:** archive decisions, clean up decisions, move old decisions, compact decisions
+- **summary:** Move old decisions from decisions.md to decisions-archive.md
+- **action:** coordinator
+- **command:** Move entries older than threshold from .squad/decisions.md → .squad/decisions-archive.md
+- **args:**
+  - `olderThan`: Archive decisions older than how many days? | default: 30
+- **confirm:** true
+
+### Summarize Agent History
+
+- **intent:** summarize history, what did agent do, agent history, compress history
+- **summary:** Spawn an agent to summarize and compress a team member's history file
+- **action:** coordinator
+- **command:** Spawn agent with history.md summarization task
+- **args:**
+  - `member`: Which team member's history to summarize?
+- **confirm:** false

package/templates/skills/squad-version-check/SKILL.md

@@ -0,0 +1,160 @@
+# SKILL: Squad CLI Internals — Version Stamping & Upgrade Mechanics
+
+**Confidence:** medium
+**Discovered by:** Data
+**Date:** 2026-05-26
+**Validated in:** Issue #1173 recon (bradygaster/squad)
+
+---
+
+## What This Skill Covers
+
+Reusable knowledge about how `@bradygaster/squad-cli` stamps its version into `squad.agent.md`, how `squad upgrade` works, what it preserves vs. overwrites, and how to probe the npm registry for the latest version from a coordinator prompt.
+
+---
+
+## Package & Registry Facts
+
+- **Package name:** `@bradygaster/squad-cli`
+- **Registry:** npm (public)
+- **CLI binary:** `squad` (registered via `package.json#bin.squad`)
+- **Node version requirement:** Node ≥22.5.0 (ESM-only codebase)
+
+---
+
+## Version Stamping Mechanism
+
+**Source file:** `dist/cli/core/version.js`
+
+Three functions:
+
+### `getPackageVersion()`
+Walks up from the compiled JS file to find `package.json`. Returns `pkg.version`. Works from both `dist/cli/core/version.js` and a bundled root `cli.js`. Returns `'0.0.0'` as fallback if not found.
+
+### `stampVersion(filePath, version)`
+Mutates `squad.agent.md` in three places:
+1. HTML comment: `<!-- version: {version} -->` (must be on the line immediately after frontmatter `---`)
+2. Identity line: `- **Version:** {version}`
+3. Greeting instruction: backtick-quoted `` `Squad v{version}` ``
+
+**Called by:** both `init` and `upgrade` — after copying the template to the destination.
+
+### `readInstalledVersion(filePath)`
+Reads the stamped version back from `squad.agent.md`:
+1. First tries HTML comment format: `/<!-- version: ([0-9.]+(?:-[a-z]+(?:\.\d+)?)?) -->/`
+2. Falls back to old frontmatter format: `/^version:\s*"([^"]+)"/m`
+3. Returns `'0.0.0'` on any error
+
+---
+
+## `squad upgrade` Behavior
+
+**Source file:** `dist/cli/core/upgrade.js`
+
+### What gets overwritten:
+- `squad.agent.md` — full overwrite from template, then `stampVersion()`
+- Files with `overwriteOnUpgrade: true` in `TEMPLATE_MANIFEST`: casting JSON files, template .md files, `copilot-instructions.md` (if @copilot enabled)
+- GitHub Actions workflows — from `templates/workflows/`; non-npm projects get type-aware stubs
+- Runs `runMigrations()` after file copy
+
+### What is PRESERVED:
+- `team.md`, `routing.md`, `decisions.md`, `ceremonies.md` (user-owned)
+- `agents/*/history.md` (individual agent memory)
+- `.squad/config.json` — **never touched**; `stateBackend` survives intact
+- User-added files not in TEMPLATE_MANIFEST
+
+### Self-upgrade path (`selfUpgradeCli()`):
+Detects npm/pnpm/yarn via `npm_execpath` and `npm_config_user_agent`. Runs:
+- npm: `npm install -g @bradygaster/squad-cli@latest`
+- pnpm: `pnpm add -g @bradygaster/squad-cli@latest`
+- yarn: `yarn global add @bradygaster/squad-cli@latest`
+Use `@insider` tag for insider builds.
+
+### `compareSemver(a, b)` utility (in upgrade.js):
+Returns -1/0/1. Handles pre-release: strips pre-release for base comparison, then treats pre-release as less than release (e.g., `0.9.5-insider.1` < `0.9.5`). Can be ported directly if needed in prompt logic.
+
+---
+
+## `.squad/config.json` — What It Holds
+
+```json
+{
+  "version": 1,
+  "stateBackend": "worktree"
+}
+```
+
+Other optional fields added by the coordinator at runtime:
+- `defaultModel` — global model override for all agent spawns
+- `agentModelOverrides.{agentName}` — per-agent model override
+
+The file is read-only from the upgrade path's perspective. Only the coordinator writes to it (for model preferences).
+
+---
+
+## Version-Check Probe (npm Registry)
+
+Use this one-liner from inside a coordinator prompt to fetch dist-tags:
+
+```
+npm view @bradygaster/squad-cli dist-tags --json
+```
+
+- Timeout: **5 seconds.** If no response within 5 seconds, abandon and show normal greeting.
+- On success: extract `dist-tags[channel]` (e.g., `dist-tags["insider"]`).
+- On any error (network failure, registry unreachable, parse error): show normal greeting.
+
+---
+
+## Upstream OS-Specific Cache
+
+The CLI (`self-update.ts`) writes `latest` version info to an OS-specific path with a 24h TTL.
+
+**One-liner to read the upstream cache:**
+```
+node -e "const p=require('path'),o=require('os');const b=process.env.APPDATA||(process.platform==='darwin'?p.join(o.homedir(),'Library','Application Support'):p.join(o.homedir(),'.config'));const f=p.join(b,'squad-cli','update-check.json');try{const d=JSON.parse(require('fs').readFileSync(f,'utf8'));const age=Date.now()-d.checkedAt;if(age<86400000)console.log(JSON.stringify(d));else console.log('STALE')}catch{console.log('MISS')}"
+```
+
+Output semantics:
+- Valid JSON `{"latestVersion":"X.Y.Z","checkedAt":N}` → cache hit; use `latestVersion`
+- `STALE` → cache expired (older than 24h); treat as no data
+- `MISS` → cache missing or corrupt; treat as no data
+
+**OS-specific cache path:**
+- Windows: `%APPDATA%\squad-cli\update-check.json`
+- Linux: `~/.config/squad-cli/update-check.json`
+- macOS: `~/Library/Application Support/squad-cli/update-check.json`
+
+---
+
+## Repo-Local Cache Convention: `.squad/.cache/version-check.json`
+
+Used by coordinator for `insider`/`preview` channels (the upstream cache only stores `latest`).
+
+**Schema:**
+```json
+{
+  "checkedAt": "2026-05-26T14:13:28.492Z",
+  "currentVersion": "0.9.6-insider.2",
+  "channel": "insider",
+  "channelVersion": "0.9.7-insider.1"
+}
+```
+
+**TTL:** 24 hours from `checkedAt`.
+**Gitignore:** `.squad/.cache/` is listed in `.gitignore` — cache files are never committed.
+
+---
+
+## Key File Paths (installed CLI)
+
+| Purpose | Path |
+|---|---|
+| Version utilities | `dist/cli/core/version.js` |
+| Upgrade logic | `dist/cli/core/upgrade.js` |
+| Init logic | `dist/cli/core/init.js` |
+| Template manifest | `dist/cli/core/templates.js` |
+| Copilot install helper | `dist/cli/copilot-install.js` |
+| squad.agent.md template | `templates/squad.agent.md.template` |
+| Session init reference | `templates/session-init-reference.md` |
+| All templates | `templates/` |

package/templates/spawn-reference.md

@@ -0,0 +1,132 @@
+# Spawn Reference
+
+### How to Spawn an Agent
+
+**You MUST dispatch every agent spawn** via the platform's tool (`task` on CLI, `runSubagent` on VS Code):
+
+- **`agent_type`**: `"general-purpose"` (always — this gives agents full tool access)
+- **`mode`**: `"background"` (default) or `"sync"` — use `"background"` for all parallelizable work; use `"sync"` only when the result is needed before the next step can proceed
+- **`description`**: `"{Name}: {brief task summary}"` (e.g., `"Ripley: Design REST API endpoints"`, `"Dallas: Build login form"`) — this is what appears in the UI, so it MUST carry the agent's name and what they're doing
+- **`prompt`**: The full agent prompt (see below)
+
+**⚡ Inline the charter.** Before spawning, read the agent's `charter.md` (resolve from team root: `{team_root}/.squad/agents/{name}/charter.md`) and paste its contents directly into the spawn prompt. This eliminates a tool call from the agent's critical path. The agent still reads its own `history.md` and `decisions.md`.
+
+**Background spawn (the default):** Use the template below with `mode: "background"`.
+
+**Sync spawn (when required):** Use the template below and omit the `mode` parameter (sync is default).
+
+> **VS Code equivalent:** Use `runSubagent` with the prompt content below. Drop `agent_type`, `mode`, `model`, and `description` parameters. Multiple subagents in one turn run concurrently. Sync is the default on VS Code.
+
+**Template for any agent** (substitute `{Name}`, `{Role}`, `{name}`, and inline the charter):
+
+```
+agent_type: "general-purpose"
+model: "{resolved_model}"
+mode: "background"
+name: "{name}"
+description: "{emoji} {Name}: {brief task summary}"
+prompt: |
+  You are {Name}, the {Role} on this project.
+
+  YOUR CHARTER:
+  {paste contents of .squad/agents/{name}/charter.md here}
+
+  TEAM ROOT: {team_root}
+  CURRENT_DATETIME: <resolved CURRENT_DATETIME literal>
+  All `.squad/` paths are relative to this root.
+
+  Use the literal CURRENT_DATETIME value from your prompt for dated file content:
+  `<literal CURRENT_DATETIME value from your prompt>`. Substitute the actual CURRENT_DATETIME value; never write placeholder text.
+
+  PERSONAL_AGENT: {true|false}  # Whether this is a personal agent
+  GHOST_PROTOCOL: {true|false}  # Whether ghost protocol applies
+
+  {If PERSONAL_AGENT is true, append Ghost Protocol rules:}
+  ## Ghost Protocol
+  You are a personal agent operating in a project context. You MUST follow these rules:
+  - Read-only project state: Do NOT write to project's .squad/ directory
+  - No project ownership: You advise; project agents execute
+  - Transparent origin: Tag all logs with [personal:{name}]
+  - Consult mode: Provide recommendations, not direct changes
+  {end Ghost Protocol block}
+
+  WORKTREE_PATH: {worktree_path}
+  WORKTREE_MODE: {true|false}
+
+  {% if WORKTREE_MODE %}
+  **WORKTREE:** You are working in a dedicated worktree at `{WORKTREE_PATH}`.
+  - All file operations should be relative to this path
+  - Do NOT switch branches — the worktree IS your branch (`{branch_name}`)
+  - Build and test in the worktree, not the main repo
+  - Commit and push from the worktree
+  {% endif %}
+
+  STATE_BACKEND: {state_backend}
+
+  ## State Protocol — Runtime State Tools
+  Mutable squad state is owned by the runtime. You MUST use the `state.*` tools
+  whenever they are available:
+  - `squad_state_read` / `squad_state_list` for decisions, history, logs, and inbox entries
+  - `squad_state_write` / `squad_state_append` for durable updates
+  - `squad_state_delete` after Scribe merges inbox entries
+  - `squad_state_health` when diagnosing backend availability
+  - `squad_decide` for team-relevant decisions
+
+  The runtime routes those calls to the configured backend (`{state_backend}`), including
+  git-native backends. Do NOT run backend git commands, switch to a state branch, push
+  note refs, or write mutable `.squad/` state files by hand. Static config (charters,
+  team.md, routing.md, skills) remains on disk and may be read with normal file tools.
+
+  Read `agents/{name}/history.md` with `squad_state_read` when state tools are available; otherwise fall back to `.squad/agents/{name}/history.md`.
+  Read `decisions.md` with `squad_state_read` when state tools are available; otherwise fall back to `.squad/decisions.md`.
+  If .squad/identity/wisdom.md exists, read it before starting work.
+  If .squad/identity/now.md exists, read it at spawn time.
+  Check .copilot/skills/ for copilot-level skills (process, workflow, protocol).
+  Check .squad/skills/ for team-level skills (patterns discovered during work).
+  Read any relevant SKILL.md files before working.
+
+  ⚠️ WORK FRESHNESS: When determining what to work on:
+  - If an external tracker is configured (GitHub Issues, GitLab Issues, Azure DevOps),
+    ALWAYS query it for current open/active items. The tracker is the authoritative
+    source of truth — local plan files and checkboxes are advisory only.
+  - If .squad/identity/now.md has a `last_verified` timestamp older than your session
+    start, re-verify the current focus against the tracker before acting.
+  - NEVER work on items marked closed/done in the tracker, even if local files
+    suggest they are incomplete.
+
+  {only if MCP tools detected — omit entirely if none:}
+  MCP TOOLS: {service}: ✅ ({tools}) | ❌. Fall back to CLI when unavailable.
+  {end MCP block}
+
+  **Requested by:** {current user name}
+
+  INPUT ARTIFACTS: {list exact file paths to review/modify}
+
+  The user says: "{message}"
+
+  Do the work. Respond as {Name}.
+
+  ⚠️ OUTPUT: Report outcomes in human terms. Never expose tool internals or SQL.
+  ⚠️ DATES: When writing dates in any file (decisions, history, logs), use ONLY the CURRENT_DATETIME value above. Never infer or guess the date.
+
+  AFTER work (BEST-EFFORT — do NOT retry on failure):
+  ⚠️ POST-WORK BUDGET: Spend at most 20 tool calls on post-work steps below.
+  If you are running low on context or have used 60+ tool calls on primary work,
+  skip post-work entirely -- Scribe handles it independently.
+  1. APPEND learnings with `squad_state_append` to `agents/{name}/history.md`.
+     Include architecture decisions, patterns, user preferences, and key file paths.
+     Use `<literal CURRENT_DATETIME value from your prompt>` as the entry timestamp.
+     Substitute the actual CURRENT_DATETIME value; do not write placeholder text.
+  2. If you made a team-relevant decision, call `squad_decide`. If that tool is
+     unavailable, use `squad_state_write` to `decisions/inbox/{name}-{brief-slug}.md`.
+  3. If state tools are unavailable, skip post-work state persistence and report the
+     backend/tool availability problem in your final summary.
+  4. SKILL EXTRACTION is handled by Scribe — do NOT attempt it yourself.
+
+  ⚠️ STOP ON FAILURE: If ANY post-work step fails (git conflict, file not found,
+  permission error), SKIP it and move on. Do NOT retry. Scribe handles cleanup
+  independently. Your primary deliverable is already done — post-work is optional.
+
+  ⚠️ RESPONSE ORDER: After ALL tool calls, write a 2-3 sentence plain text
+  summary as your FINAL output. No tool calls after this summary.
+```