@@ -0,0 +1,5 @@
+---
+"@bradygaster/squad-sdk": patch
+---
+
+deps: bump @opentelemetry/sdk-metrics and @opentelemetry/sdk-trace-node from 1.x to 2.8.0
@@ -0,0 +1,12 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Fix CLI and upgrade bugs:
+- `squad externalize` and `squad internalize` now appear in `squad --help` output (#1050)
+- `squad build` writes files to the externalized state directory when applicable (#1048)
+- `squad new agent` correctly adds agent definitions to `squad.config.ts` (#1047)
+- `squad upgrade` backs up customized `squad.agent.md` before overwriting; supports `--dry-run` (#1052)
+- Explicit `@agent` mentions bypass direct-response handler and route to named agent (#1029)
+- `state-mcp` server uses lazy initialization to avoid blocking multi-MCP startup (#1353)
@@ -0,0 +1,6 @@
+---
+"@bradygaster/squad-sdk": patch
+"@bradygaster/squad-cli": patch
+---
+
+Fix platform-specific path examples in personal squad docs, JSDoc, and bundled skill templates.
@@ -0,0 +1,60 @@
+---
+"@bradygaster/squad-cli": minor
+"@bradygaster/squad-sdk": minor
+---
+
+feat: add `squad preset install <source>` for sharing presets via repo URL or local path (#1224)
+
+Closes #1224. Adds a new subcommand that installs a single preset from a GitHub URL or local path into `$SQUAD_HOME/presets/<name>/` — the peer-to-peer preset sharing flow that was missing in v0.10.0.
+
+### CLI
+
+```bash
+# From a GitHub repo (preset at <repo-root>/preset.json or <repo-root>/presets/<name>/)
+squad preset install https://github.com/tamir/my-presets#my-awesome-team
+
+# From a sub-path
+squad preset install https://github.com/tamir/my-presets/tree/main/presets/my-awesome-team
+
+# From SSH URL
+squad preset install git@github.com:tamir/my-presets.git#my-awesome-team
+
+# From a local path
+squad preset install ./my-awesome-team
+
+# Override the installed name
+squad preset install https://github.com/tamir/my-presets#my-awesome-team --name corp-team
+
+# Overwrite an existing preset
+squad preset install <source> --force
+```
+
+After install, the preset is a normal entry in `$SQUAD_HOME/presets/` — `squad preset list`, `squad preset apply <name>`, and `squad init --preset <name>` all work as today.
+
+### Why
+
+The existing `squad preset init --remote` flow is for syncing your *whole* `$SQUAD_HOME` repo across machines (single-user, multi-machine use case). There was no built-in way to install just *one* preset from someone else's repo. Users had to:
+1. Manually clone the repo to a temp dir
+2. `cp -r <clone>/presets/<name> $SQUAD_HOME/presets/`
+3. Then `squad preset apply <name>`
+
+…or hijack `SQUAD_HOME` (which collides with their own personal squad config).
+
+### What it does
+
+1. Resolves source — GitHub URL → shallow `git clone --depth 1` to a temp dir; local path → use as-is
+2. Locates the preset within the source via 3 patterns:
+   - Source dir contains `preset.json` → single-preset source
+   - Source dir contains a `presets/` collection → require `--name` (or `#name` fragment) to pick
+   - Source dir IS the `presets/` dir → require `--name`, or auto-pick if only one preset
+3. Validates the preset's `preset.json` manifest (name, agents[]) before any destructive action
+4. Verifies `agents/` directory exists
+5. Copies `preset.json` (with optional rename) + `agents/` into `$SQUAD_HOME/presets/<name>/`
+6. Fail-stops if destination exists, unless `--force` is passed
+7. Cleans up the temp clone whether install succeeds or fails
+
+### What's NOT in scope (deferred to follow-ups)
+
+- `squad preset uninstall` — `rm -rf $SQUAD_HOME/presets/<name>` works for now
+- `squad preset update <name>` to pull a fresh version from origin
+- Public preset registry / discovery catalog
@@ -0,0 +1,5 @@
+---
+"@bradygaster/squad-cli": patch
+---
+
+Force the CLI's squad-sdk dependency through the repo workspace by using a root file dependency plus an npm override for the CLI package. This keeps fresh installs linked to the local SDK prerelease instead of pulling the stale published SDK. Closes #1405.
@@ -0,0 +1,24 @@
+---
+"@bradygaster/squad-cli": patch
+"@bradygaster/squad-sdk": patch
+---
+
+Fix coordinator inline-dispatch regression: restore always-on dispatch gate in the Squad coordinator template
+
+**Problem**
+
+In v0.10.0 the Squad coordinator started doing domain work itself instead of dispatching to roster agents (it worked in v0.9.4). Root cause: commit `afe78188` (#1035, "context overflow sentinel + coordinator size reduction") relocated the concrete inline-dispatch gate and the dispatch mechanics out of the always-on coordinator prompt (`.squad-templates/squad.agent.md`) into lazy-loaded reference files (`client-compatibility-reference.md`, `spawn-reference.md`). The remaining inline one-liner ("inline work is last-resort fallback only") was too soft, and the concrete "when may I work inline?" rule + the VS Code `runSubagent` how-to were no longer in-context, so the coordinator defaulted to executing work itself.
+
+**Fix**
+
+Three minimal edits to the canonical coordinator template (`.squad-templates/squad.agent.md`), synced to all mirrors via `npm run sync-templates`:
+
+1. **Client Compatibility** — replaced the soft one-liner with an explicit **Inline-dispatch gate**: doing domain work inline is permitted ONLY in Direct Mode, or when NEITHER `task` NOR `runSubagent` is available; otherwise the coordinator MUST dispatch.
+2. **How to Spawn an Agent** — added a one-line **STOP gate**: about to produce a domain artifact with no `task` / `runSubagent` call this turn → STOP and dispatch (exceptions: Direct Mode, or no spawn tool exists).
+3. Re-inlined a ~5-line **VS Code `runSubagent` micro-playbook** so the how-to-dispatch mechanics are always-on instead of lazy-loaded.
+
+The legitimate Direct/Lightweight response modes are preserved (Lightweight still spawns one agent; Direct still answers from context without spawning).
+
+**Validation**
+
+New deterministic, subprocess-free regression test `test/coordinator-inline-dispatch-gate.test.ts` asserts the gate/STOP-gate/micro-playbook exist in canonical and that the gate is present in all 5 synced copies (parity). Red before the fix (8/8 failing), green after. Existing requires a `squad upgrade` for existing installs to pick up the new template.
@@ -0,0 +1,12 @@
+---
+"@bradygaster/squad-sdk": patch
+---
+
+fix: update adapter/client.ts for @github/copilot-sdk 1.0.4 API changes
+
+Fixes 5 TypeScript errors caused by breaking changes in `@github/copilot-sdk@1.0.4`:
+
+- Replace removed `cliPath`/`cliArgs`/`useStdio`/`port`/`cliUrl` options with the new `RuntimeConnection` pattern
+- Update `ping()` return type from `timestamp: number` to `timestamp: string`
+- Make `SquadModelBilling.multiplier` optional to match upstream `ModelBilling`
+- Replace `client.on()` with `client.onLifecycle()` for session lifecycle events
@@ -0,0 +1,11 @@
+---
+"@bradygaster/squad-cli": patch
+---
+
+Fix Windows shell spawn issues and gh auth false-negative
+
+- **DEP0190 fix:** Added `escapeForCmd()`/`escapeArgs()` to properly quote args when `shell: true` is used on Windows. Changed `shell: true` → `shell: IS_WINDOWS`.
+- **Capability migration:** Moved monitor-email, monitor-teams, retro, decision-hygiene from inline `buildAgentCommand`/`spawnWithTimeout` to shared `agent-spawn.ts` module.
+- **gh auth fix:** Use `gh auth token` instead of `gh auth status` — the latter returns non-zero when any keyring entry is stale, even if the active account works fine.
+- **Copilot flag fix:** Use `-p` (correct) instead of `--message` (non-existent) for copilot CLI prompt flag.
+- **Default --yolo:** When `--execute` is active and no `copilotFlags`/`agentCmd` are set, default to `--yolo` so copilot doesn't hang waiting for permission prompts.
@@ -0,0 +1,5 @@
+---
+"@bradygaster/squad-sdk": patch
+---
+
+Fix local test-suite failures by aligning personal squad path expectations, stabilizing observer file classification, and skipping environment-dependent docs/Aspire checks when required local dependencies are unavailable.
@@ -0,0 +1,9 @@
+---
+"@bradygaster/squad-sdk": patch
+---
+
+Fix: strip surrounding quotes from routing.md example phrases in `parseRoutingMarkdown`
+
+`parseRoutingMarkdown` split the Examples cell on commas but never stripped the surrounding quotes, so a quoted example like `"unit tests"` was stored verbatim (quotes included). When `compileRoutingRules` / `matchRoute` later tokenized it, the quote characters glued onto the boundary words (`"unit`, `tests"`), producing regex patterns that could never match — so routing tables that used quoted examples silently routed every message to the fallback agent.
+
+Leading/trailing quotes (`"`, `'`, `` ` ``) are now stripped from each example, so quoted and unquoted examples behave identically. Adds regression tests covering both the parse step and end-to-end `matchRoute`.
-Original file line number
+Diff line change
@@ @@ -0,0 +1,5 @@ @@
 +---
 +"@bradygaster/squad-sdk": patch
 +---
++
 +deps: bump @opentelemetry/sdk-metrics and @opentelemetry/sdk-trace-node from 1.x to 2.8.0