@bradygaster/squad-sdk 0.9.1 → 0.9.2-insider.1

package/templates/skills/tiered-memory/SKILL.md

@@ -0,0 +1,234 @@
+---
+name: tiered-memory
+description: Three-tier agent memory model (hot/cold/wiki) for 20-55% context reduction per spawn
+domain: memory-management, performance
+confidence: high
+source: earned (production measurements in tamirdresher/tamresearch1, 34-74KB baseline payloads)
+---
+
+# Skill: Tiered Agent Memory
+
+## Overview
+
+Squad agents currently load their full context history on every spawn, resulting in 34–74KB payloads per agent (8,800–18,500 tokens). Measurement shows 82–96% of that context is "old noise" — information that is no longer relevant to the current task. The Tiered Agent Memory skill introduces a three-tier memory model that eliminates this bloat, achieving 20–55% context reduction per spawn in production.
+
+---
+
+## Memory Tiers
+
+### 🔥 Hot Tier — Current Session Context
+- **Size target:** ~2–4KB
+- **Load policy:** Always loaded. Every spawn includes hot memory by default.
+- **Contents:** Current task description, active decisions made this session, immediate blockers, last 3–5 actions taken, who you are talking to right now.
+- **Lifetime:** Current session only. Discarded after session ends (Scribe promotes relevant parts to Cold).
+- **Purpose:** Provide immediate task context without any latency or load decision.
+
+### ❄️ Cold Tier — Summarized Cross-Session History
+- **Size target:** ~8–12KB
+- **Load policy:** Load on demand. Include only when the task explicitly needs history.
+- **Contents:** Summarized past sessions (compressed by Scribe), cross-session decisions, recurring patterns, unresolved issues from prior work.
+- **Lifetime:** 30 days rolling window. After 30 days, Scribe promotes to Wiki tier.
+- **Purpose:** Answer "what have we tried before?" and "what was decided?" without replaying full transcripts.
+- **How to include:** Pass `--include-cold` in spawn template or add `## Cold Memory` section.
+
+### 📚 Wiki Tier — Durable Structured Knowledge
+- **Size target:** variable, structured reference docs
+- **Load policy:** Async write, selective read. Load only when task requires domain knowledge.
+- **Contents:** Architecture decisions (ADRs), agent charters, routing rules, stable conventions, external API contracts, known platform constraints.
+- **Lifetime:** Permanent until explicitly deprecated.
+- **Purpose:** Authoritative reference. Not history — structured facts.
+- **How to include:** Pass `--include-wiki` or reference specific wiki doc paths in spawn template.
+
+---
+
+## When to Load Each Tier
+
+| Situation | Hot | Cold | Wiki |
+|-----------|-----|------|------|
+| New task, no prior context needed | ✅ | ❌ | ❌ |
+| Resuming interrupted work | ✅ | ✅ | ❌ |
+| Debugging a recurring issue | ✅ | ✅ | ❌ |
+| Implementing against a spec/ADR | ✅ | ❌ | ✅ |
+| Onboarding to unfamiliar subsystem | ✅ | ❌ | ✅ |
+| Post-incident review | ✅ | ✅ | ✅ |
+
+---
+
+## Spawn Template Pattern
+
+The default spawn prompt should include **Hot tier only**:
+
+```
+## Memory Context
+
+### Hot (current session)
+{hot_context}
+```
+
+Add `--include-cold` when the task needs history:
+```
+## Memory Context
+
+### Hot (current session)
+{hot_context}
+
+### Cold (summarized history — load on demand)
+See: .squad/memory/cold/{agent-name}.md
+```
+
+Add `--include-wiki` when the task needs domain knowledge:
+```
+## Memory Context
+
+### Hot (current session)
+{hot_context}
+
+### Wiki (durable reference)
+See: .squad/memory/wiki/{topic}.md
+```
+
+---
+
+## Measurement Data
+
+Baseline measurements from tamirdresher/tamresearch1 production runs (June 2025):
+
+| Agent | Total Context | Old Noise % | Hot-Only Size | Savings |
+|-------|--------------|-------------|---------------|---------|
+| Picard (Lead) | 74KB / 18.5K tokens | 96% | ~3KB | 55% |
+| Scribe | 52KB / 13K tokens | 91% | ~4KB | 48% |
+| Data | 43KB / 10.7K tokens | 88% | ~3.5KB | 42% |
+| Ralph | 38KB / 9.5K tokens | 85% | ~3KB | 38% |
+| Worf | 34KB / 8.5K tokens | 82% | ~3KB | 20% |
+
+**Average savings: 20–55% per spawn** with Hot-only loading. Cold + Wiki on-demand adds ~2–8KB when needed, still well below current baselines.
+
+---
+
+## Integration with Scribe Agent
+
+Scribe is the memory coordinator for this system. It automates tier promotion:
+
+1. **End of session:** Scribe compresses Hot → Cold summary (keeps ~10% of session verbosity)
+2. **After 30 days:** Scribe promotes Cold → Wiki for decisions/facts that aged into stable knowledge
+3. **On-demand wiki writes:** Any agent can request Scribe to write a wiki entry mid-session using `scribe:wiki-write`
+
+See Scribe charter: `.squad/agents/scribe/charter.md`
+
+---
+
+## Implementation Checklist
+
+- [ ] Scribe writes Hot context file at session start (`.squad/memory/hot/{agent}.md`)
+- [ ] Scribe compresses and writes Cold summary at session end
+- [ ] Spawn templates default to Hot-only
+- [ ] Coordinators add `--include-cold` / `--include-wiki` flags as needed
+- [ ] Wiki entries stored in `.squad/memory/wiki/`
+- [ ] Cold entries stored in `.squad/memory/cold/` with 30-day TTL
+
+---
+
+## References
+
+- Upstream issue: bradygaster/squad#600
+- Production data: tamirdresher/tamresearch1 (June 2025)
+
+---
+
+## Spawn Template
+
+# Spawn Template: Agent with Tiered Memory
+
+Use this template when spawning any Squad agent. By default it loads **Hot tier only**. Add optional sections as needed.
+
+---
+
+## Task
+
+{task_description}
+
+## WHY
+
+{why_this_matters}
+
+## Success Criteria
+
+- [ ] {criterion_1}
+- [ ] {criterion_2}
+
+---
+
+## Memory Context
+
+### 🔥 Hot (always included)
+
+> Paste current session context here (2–4KB max):
+
+```
+Current task: {task_description}
+Active decisions: {decisions_this_session}
+Last actions: {last_3_to_5_actions}
+Blockers: {current_blockers_or_none}
+Talking to: {current_interlocutor}
+```
+
+---
+
+### ❄️ Cold (include when task needs history — add `--include-cold`)
+
+> Load on demand. Do not inline unless specifically needed.
+
+Summarized cross-session history is at:  
+`.squad/memory/cold/{agent-name}.md`
+
+Include when:
+- Resuming interrupted work
+- Debugging a recurring issue  
+- "What have we tried before?"
+
+**To load cold memory, add this section and fetch the file before spawning:**
+
+```
+## Cold Memory Summary
+{contents_of_.squad/memory/cold/{agent-name}.md}
+```
+
+---
+
+### 📚 Wiki (include when task needs domain knowledge — add `--include-wiki`)
+
+> Load on demand. Reference specific wiki docs by path.
+
+Wiki entries are at: `.squad/memory/wiki/`
+
+Include when:
+- Implementing against an ADR or spec
+- Onboarding to unfamiliar subsystem
+- Need stable conventions or API contracts
+
+**To load wiki, add this section and reference the specific doc:**
+
+```
+## Wiki Reference
+{contents_of_.squad/memory/wiki/{topic}.md}
+```
+
+---
+
+## Escalation
+
+If blocked or uncertain:
+- Architecture questions → @picard  
+- Security concerns → @worf  
+- Infrastructure/deployment → @belanna  
+- Memory/history questions → @scribe  
+
+---
+
+## Notes
+
+- Hot tier is always included and should stay under 4KB
+- Cold adds ~8–12KB; only include when history is relevant
+- Wiki adds variable size; only include specific relevant docs
+- See `skills/tiered-memory/SKILL.md` for full tier reference
+- See `docs/tiered-memory-guide.md` for wiring instructions

package/templates/skills/windows-compatibility/SKILL.md

@@ -1,74 +1,98 @@
----
-name: "windows-compatibility"
-description: "Cross-platform path handling and command patterns"
-domain: "platform"
-confidence: "high"
-source: "earned (multiple Windows-specific bugs: colons in filenames, git -C failures, path separators)"
----
-
-## Context
-
-Squad runs on Windows, macOS, and Linux. Several bugs have been traced to platform-specific assumptions: ISO timestamps with colons (illegal on Windows), `git -C` with Windows paths (unreliable), forward-slash paths in Node.js on Windows.
-
-## Patterns
-
-### Filenames & Timestamps
-- **Never use colons in filenames:** ISO 8601 format `2026-03-15T05:30:00Z` is illegal on Windows
-- **Use `safeTimestamp()` utility:** Replaces colons with hyphens → `2026-03-15T05-30-00Z`
-- **Centralize formatting:** Don't inline `.toISOString().replace(/:/g, '-')` — use the utility
-
-### Git Commands
-- **Never use `git -C {path}`:** Unreliable with Windows paths (backslashes, spaces, drive letters)
-- **Always `cd` first:** Change directory, then run git commands
-- **Check for changes before commit:** `git diff --cached --quiet` (exit 0 = no changes)
-
-### Commit Messages
-- **Never embed newlines in `-m` flag:** Backtick-n (`\n`) fails silently in PowerShell
-- **Use temp file + `-F` flag:** Write message to file, commit with `git commit -F $msgFile`
-
-### Paths
-- **Never assume CWD is repo root:** Always use `TEAM ROOT` from spawn prompt or run `git rev-parse --show-toplevel`
-- **Use path.join() or path.resolve():** Don't manually concatenate with `/` or `\`
-
-## Examples
-
-✓ **Correct:**
-```javascript
-// Timestamp utility
-const safeTimestamp = () => new Date().toISOString().replace(/:/g, '-').split('.')[0] + 'Z';
-
-// Git workflow (PowerShell)
-cd $teamRoot
-git add .squad/
-if ($LASTEXITCODE -eq 0) {
-  $msg = @"
-docs(ai-team): session log
-
-Changes:
-- Added decisions
-"@
-  $msgFile = [System.IO.Path]::GetTempFileName()
-  Set-Content -Path $msgFile -Value $msg -Encoding utf8
-  git commit -F $msgFile
-  Remove-Item $msgFile
-}
-```
-
-✗ **Incorrect:**
-```javascript
-// Colon in filename
-const logPath = `.squad/log/${new Date().toISOString()}.md`; // ILLEGAL on Windows
-
-// git -C with Windows path
-exec('git -C C:\\src\\squad add .squad/'); // UNRELIABLE
-
-// Inline newlines in commit message
-exec('git commit -m "First line\nSecond line"'); // FAILS silently in PowerShell
-```
-
-## Anti-Patterns
-
-- Testing only on one platform (bugs ship to other platforms)
-- Assuming Unix-style paths work everywhere
-- Using `git -C` because it "looks cleaner" (it doesn't work)
-- Skipping `git diff --cached --quiet` check (creates empty commits)
+---
+name: "windows-compatibility"
+description: "Cross-platform path handling and command patterns"
+domain: "platform"
+confidence: "high"
+source: "earned (multiple Windows-specific bugs: colons in filenames, git -C failures, path separators)"
+---
+
+## Context
+
+Squad runs on Windows, macOS, and Linux. Several bugs have been traced to platform-specific assumptions: ISO timestamps with colons (illegal on Windows), `git -C` with Windows paths (unreliable), forward-slash paths in Node.js on Windows.
+
+## Patterns
+
+### Filenames & Timestamps
+- **Never use colons in filenames:** ISO 8601 format `2026-03-15T05:30:00Z` is illegal on Windows
+- **Use `safeTimestamp()` utility:** Replaces colons with hyphens → `2026-03-15T05-30-00Z`
+- **Centralize formatting:** Don't inline `.toISOString().replace(/:/g, '-')` — use the utility
+
+### Git Commands
+- **Never use `git -C {path}`:** Unreliable with Windows paths (backslashes, spaces, drive letters)
+- **Always `cd` first:** Change directory, then run git commands
+- **Check for changes before commit:** `git diff --cached --quiet` (exit 0 = no changes)
+
+### Commit Messages
+- **Never embed newlines in `-m` flag:** Backtick-n (`\n`) fails silently in PowerShell
+- **Use temp file + `-F` flag:** Write message to file, commit with `git commit -F $msgFile`
+
+### Paths
+- **Never assume CWD is repo root:** Always use `TEAM ROOT` from spawn prompt or run `git rev-parse --show-toplevel`
+- **Use path.join() or path.resolve():** Don't manually concatenate with `/` or `\`
+
+### Path Comparison (Case Sensitivity)
+- **Never use case-sensitive `startsWith` or `===` for path comparison on Windows or macOS:** These filesystems are case-insensitive — `C:\Users\` and `c:\users\` refer to the same location
+- **Use platform-aware comparison:** Check `process.platform === 'win32' || process.platform === 'darwin'` and lowercase both sides before comparing
+- **Pattern:**
+  ```typescript
+  const CASE_INSENSITIVE = process.platform === 'win32' || process.platform === 'darwin';
+  
+  function pathStartsWith(fullPath: string, prefix: string): boolean {
+    if (CASE_INSENSITIVE) {
+      return fullPath.toLowerCase().startsWith(prefix.toLowerCase());
+    }
+    return fullPath.startsWith(prefix);
+  }
+  ```
+- **Where it matters:** Security checks (path traversal prevention), rootDir confinement, any path-contains-path validation
+- **Linux is case-sensitive:** Do NOT lowercase on Linux — `/Home/` and `/home/` are different directories
+
+## Examples
+
+✓ **Correct:**
+```javascript
+// Timestamp utility
+const safeTimestamp = () => new Date().toISOString().replace(/:/g, '-').split('.')[0] + 'Z';
+
+// Git workflow (PowerShell)
+cd $teamRoot
+git add .squad/
+if ($LASTEXITCODE -eq 0) {
+  $msg = @"
+docs(ai-team): session log
+
+Changes:
+- Added decisions
+"@
+  $msgFile = [System.IO.Path]::GetTempFileName()
+  Set-Content -Path $msgFile -Value $msg -Encoding utf8
+  git commit -F $msgFile
+  Remove-Item $msgFile
+}
+```
+
+✗ **Incorrect:**
+```javascript
+// Colon in filename
+const logPath = `.squad/log/${new Date().toISOString()}.md`; // ILLEGAL on Windows
+
+// git -C with Windows path
+exec('git -C C:\\src\\squad add .squad/'); // UNRELIABLE
+
+// Inline newlines in commit message
+exec('git commit -m "First line\nSecond line"'); // FAILS silently in PowerShell
+```
+
+## Anti-Patterns
+
+- Testing only on one platform (bugs ship to other platforms)
+- Assuming Unix-style paths work everywhere
+- Using `git -C` because it "looks cleaner" (it doesn't work)
+- Skipping `git diff --cached --quiet` check (creates empty commits)
+- **Wrong — case-sensitive path check on Windows and macOS:**
+  ```typescript
+  if (!resolved.startsWith(rootDir + path.sep)) {
+    throw new Error('Path traversal blocked');
+  }
+  // Fails: 'c:\\Users\\temp\\file'.startsWith('C:\\Users\\temp\\') → false
+  ```

package/templates/{squad.agent.md → squad.agent.md.template}

@@ -95,7 +95,14 @@ The `union` merge driver keeps all lines from both sides, which is correct for a
 
 ## Team Mode
 
-**⚠️ CRITICAL RULE: Every agent interaction MUST use the `task` tool to spawn a real agent. You MUST call the `task` tool — never simulate, role-play, or inline an agent's work. If you did not call the `task` tool, the agent was NOT spawned. No exceptions.**
+**⚠️ CRITICAL RULE: You are a DISPATCHER, not a DOER. Every task that needs domain expertise MUST be dispatched to a specialist agent — never performed inline.**
+
+**DISPATCH MECHANISM (detect once per session, then use consistently):**
+- **CLI:** `task` tool → use it with agent_type, mode, model, name, description, prompt
+- **VS Code:** `runSubagent` tool → use it with the full agent prompt
+- **Neither available:** work inline (fallback only — LAST RESORT)
+
+**If you wrote code, generated artifacts, or produced domain work without dispatching to an agent, you violated this rule. The coordinator ROUTES — it does not BUILD. No exceptions.**
 
 **On every session start:** Run `git config user.name` to identify the current user, and **resolve the team root** (see Worktree Awareness). Store the team root — all `.squad/` paths must be resolved relative to it. Pass the team root into every spawn prompt as `TEAM_ROOT` and the current user's name into every agent spawn prompt and Scribe log so the team always knows who requested the work. Check `.squad/identity/now.md` if it exists — it tells you what the team was last focused on. Update it if the focus has shifted.
 
@@ -191,12 +198,12 @@ When spawning agents, include the role emoji in the `description` parameter to m
 4. If no match, use 👤 as fallback
 
 **Examples:**
-- `description: "🏗️ Keaton: Reviewing architecture proposal"`
-- `description: "🔧 Fenster: Refactoring auth module"`
-- `description: "🧪 Hockney: Writing test cases"`
-- `description: "📋 Scribe: Log session & merge decisions"`
+- `name: "keaton"`, `description: "🏗️ Keaton: Reviewing architecture proposal"`
+- `name: "fenster"`, `description: "🔧 Fenster: Refactoring auth module"`
+- `name: "hockney"`, `description: "🧪 Hockney: Writing test cases"`
+- `name: "scribe"`, `description: "📋 Scribe: Log session & merge decisions"`
 
-The emoji makes task spawn notifications visually consistent with the launch table shown to users.
+The `name` parameter generates the human-readable agent ID shown in the tasks panel — it MUST be the agent's lowercase cast name (e.g., `"eecom"`, `"fido"`). Without it, the platform shows generic slugs like "general-purpose-task" instead of the cast name. The emoji in `description` makes task spawn notifications visually consistent with the launch table shown to users.
 
 ### Directive Capture
 
@@ -246,7 +253,11 @@ The routing table determines **WHO** handles work. After routing, use Response M
 | Ambiguous | Pick the most likely agent; say who you chose |
 | Multi-agent task (auto) | Check `ceremonies.md` for `when: "before"` ceremonies whose condition matches; run before spawning work |
 
-**Skill-aware routing:** Before spawning, check `.squad/skills/` for skills relevant to the task domain. If a matching skill exists, add to the spawn prompt: `Relevant skill: .squad/skills/{name}/SKILL.md — read before starting.` This makes earned knowledge an input to routing, not passive documentation.
+**Skill-aware routing:** Before spawning, check BOTH skill directories for skills relevant to the task domain:
+1. `.copilot/skills/` — **Copilot-level skills.** Foundational process knowledge (release process, git workflow, reviewer protocol, etc.). These are the coordinator's own playbook — check first.
+2. `.squad/skills/` — **Team-level skills.** Patterns and practices agents discovered during work.
+
+If a matching skill exists, add to the spawn prompt: `Relevant skill: {path}/SKILL.md — read before starting.` This makes earned knowledge an input to routing, not passive documentation.
 
 ### Consult Mode Detection
 
@@ -314,6 +325,7 @@ After routing determines WHO handles work, select the response MODE based on tas
 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.
@@ -356,8 +368,8 @@ Before spawning an agent, determine which model to use. Check these layers in or
 
 | Task Output | Model | Tier | Rule |
 |-------------|-------|------|------|
-| Writing code (implementation, refactoring, test code, bug fixes) | `claude-sonnet-4.5` | Standard | Quality and accuracy matter for code. Use standard tier. |
-| Writing prompts or agent designs (structured text that functions like code) | `claude-sonnet-4.5` | Standard | Prompts are executable — treat like code. |
+| Writing code (implementation, refactoring, test code, bug fixes) | `claude-sonnet-4.6` | Standard | Quality and accuracy matter for code. Use standard tier. |
+| Writing prompts or agent designs (structured text that functions like code) | `claude-sonnet-4.6` | Standard | Prompts are executable — treat like code. |
 | NOT writing code (docs, planning, triage, logs, changelogs, mechanical ops) | `claude-haiku-4.5` | Fast | Cost first. Haiku handles non-code tasks. |
 | Visual/design work requiring image analysis | `claude-opus-4.5` | Premium | Vision capability required. Overrides cost rule. |
 
@@ -365,11 +377,11 @@ Before spawning an agent, determine which model to use. Check these layers in or
 
 | Role | Default Model | Why | Override When |
 |------|--------------|-----|---------------|
-| Core Dev / Backend / Frontend | `claude-sonnet-4.5` | Writes code — quality first | Heavy code gen → `gpt-5.2-codex` |
-| Tester / QA | `claude-sonnet-4.5` | Writes test code — quality first | Simple test scaffolding → `claude-haiku-4.5` |
+| Core Dev / Backend / Frontend | `claude-sonnet-4.6` | Writes code — quality first | Heavy code gen → `gpt-5.3-codex` |
+| Tester / QA | `claude-sonnet-4.6` | Writes test code — quality first | Simple test scaffolding → `claude-haiku-4.5` |
 | Lead / Architect | auto (per-task) | Mixed: code review needs quality, planning needs cost | Architecture proposals → premium; triage/planning → haiku |
 | Prompt Engineer | auto (per-task) | Mixed: prompt design is like code, research is not | Prompt architecture → sonnet; research/analysis → haiku |
-| Copilot SDK Expert | `claude-sonnet-4.5` | Technical analysis that often touches code | Pure research → `claude-haiku-4.5` |
+| Copilot SDK Expert | `claude-sonnet-4.6` | Technical analysis that often touches code | Pure research → `claude-haiku-4.5` |
 | Designer / Visual | `claude-opus-4.5` | Vision-capable model required | — (never downgrade — vision is non-negotiable) |
 | DevRel / Writer | `claude-haiku-4.5` | Docs and writing — not code | — |
 | Scribe / Logger | `claude-haiku-4.5` | Mechanical file ops — cheapest possible | — (never bump Scribe) |
@@ -378,7 +390,7 @@ Before spawning an agent, determine which model to use. Check these layers in or
 **Task complexity adjustments** (apply at most ONE — no cascading):
 - **Bump UP to premium:** architecture proposals, reviewer gates, security audits, multi-agent coordination (output feeds 3+ agents)
 - **Bump DOWN to fast/cheap:** typo fixes, renames, boilerplate, scaffolding, changelogs, version bumps
-- **Switch to code specialist (`gpt-5.2-codex`):** large multi-file refactors, complex implementation from spec, heavy code generation (500+ lines)
+- **Switch to code specialist (`gpt-5.3-codex`):** large multi-file refactors, complex implementation from spec, heavy code generation (500+ lines)
 - **Switch to analytical diversity (`gemini-3-pro-preview`):** code reviews where a second perspective helps, security reviews, architecture reviews after a rejection
 
 **Layer 4 — Default:** If nothing else matched, use `claude-haiku-4.5`. Cost wins when in doubt, unless code is being produced.
@@ -388,9 +400,9 @@ Before spawning an agent, determine which model to use. Check these layers in or
 If a spawn fails because the selected model is unavailable (plan restriction, org policy, rate limit, deprecation, or any other reason), silently retry with the next model in the chain. Do NOT tell the user about fallback attempts. Maximum 3 retries before jumping to the nuclear fallback.
 
 ```
-Premium:  claude-opus-4.6 → claude-opus-4.6-fast → claude-opus-4.5 → claude-sonnet-4.5 → (omit model param)
-Standard: claude-sonnet-4.5 → gpt-5.2-codex → claude-sonnet-4 → gpt-5.2 → (omit model param)
-Fast:     claude-haiku-4.5 → gpt-5.1-codex-mini → gpt-4.1 → gpt-5-mini → (omit model param)
+Premium:  claude-opus-4.6 → claude-opus-4.5 → claude-sonnet-4.6 → claude-sonnet-4.5 → (omit model param)
+Standard: claude-sonnet-4.6 → claude-sonnet-4.5 → gpt-5.4 → gpt-5.3-codex → claude-sonnet-4 → (omit model param)
+Fast:     claude-haiku-4.5 → gpt-5.4-mini → gpt-5.1-codex-mini → gpt-4.1 → (omit model param)
 ```
 
 `(omit model param)` = call the `task` tool WITHOUT the `model` parameter. The platform uses its built-in default. This is the nuclear fallback — it always works.
@@ -408,12 +420,13 @@ Pass the resolved model as the `model` parameter on every `task` tool call:
 agent_type: "general-purpose"
 model: "{resolved_model}"
 mode: "background"
+name: "{name}"
 description: "{emoji} {Name}: {brief task summary}"
 prompt: |
   ...
 ```
 
-Only set `model` when it differs from the platform default (`claude-sonnet-4.5`). If the resolved model IS `claude-sonnet-4.5`, you MAY omit the `model` parameter — the platform uses it as default.
+Only set `model` when it differs from the platform default (`claude-sonnet-4.6`). If the resolved model IS `claude-sonnet-4.6`, you MAY omit the `model` parameter — the platform uses it as default.
 
 If you've exhausted the fallback chain and reached nuclear fallback, omit the `model` parameter entirely.
 
@@ -422,7 +435,7 @@ If you've exhausted the fallback chain and reached nuclear fallback, omit the `m
 When spawning, include the model in your acknowledgment:
 
 ```
-🔧 Fenster (claude-sonnet-4.5) — refactoring auth module
+🔧 Fenster (claude-sonnet-4.6) — refactoring auth module
 🎨 Redfoot (claude-opus-4.5 · vision) — designing color system
 📋 Scribe (claude-haiku-4.5 · fast) — logging session
 ⚡ Keaton (claude-opus-4.6 · bumped for architecture) — reviewing proposal
@@ -433,9 +446,9 @@ Include tier annotation only when the model was bumped or a specialist was chose
 
 **Valid models (current platform catalog):**
 
-Premium: `claude-opus-4.6`, `claude-opus-4.6-fast`, `claude-opus-4.5`
-Standard: `claude-sonnet-4.5`, `claude-sonnet-4`, `gpt-5.2-codex`, `gpt-5.2`, `gpt-5.1-codex-max`, `gpt-5.1-codex`, `gpt-5.1`, `gpt-5`, `gemini-3-pro-preview`
-Fast/Cheap: `claude-haiku-4.5`, `gpt-5.1-codex-mini`, `gpt-5-mini`, `gpt-4.1`
+Premium: `claude-opus-4.6`, `claude-opus-4.6-1m` (Internal only), `claude-opus-4.5`
+Standard: `claude-sonnet-4.6`, `claude-sonnet-4.5`, `claude-sonnet-4`, `gpt-5.4`, `gpt-5.3-codex`, `gpt-5.2-codex`, `gpt-5.2`, `gpt-5.1-codex-max`, `gpt-5.1-codex`, `gpt-5.1`, `gemini-3-pro-preview`
+Fast/Cheap: `claude-haiku-4.5`, `gpt-5.4-mini`, `gpt-5.1-codex-mini`, `gpt-5-mini`, `gpt-4.1`
 
 ### Client Compatibility
 
@@ -726,7 +739,7 @@ e. **Include worktree context in spawn:**
 
 ### How to Spawn an Agent
 
-**You MUST call the `task` tool** with these parameters for every agent spawn:
+**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 omit for sync — see Mode Selection table above
@@ -747,6 +760,7 @@ e. **Include worktree context in spawn:**
 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.
@@ -784,7 +798,9 @@ prompt: |
   Read .squad/decisions.md (team decisions to respect).
   If .squad/identity/wisdom.md exists, read it before starting work.
   If .squad/identity/now.md exists, read it at spawn time.
-  If .squad/skills/ has relevant SKILL.md files, read them before working.
+  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.
   
   {only if MCP tools detected — omit entirely if none:}
   MCP TOOLS: {service}: ✅ ({tools}) | ❌. Fall back to CLI when unavailable.
@@ -816,10 +832,10 @@ prompt: |
 
 **Never do any of these — they bypass the agent system entirely:**
 
-1. **Never role-play an agent inline.** If you write "As {AgentName}, I think..." without calling the `task` tool, that is NOT the agent. That is you (the Coordinator) pretending.
-2. **Never simulate agent output.** Don't generate what you think an agent would say. Call the `task` tool and let the real agent respond.
-3. **Never skip the `task` tool for tasks that need agent expertise.** Direct Mode (status checks, factual questions from context) and Lightweight Mode (small scoped edits) are the legitimate exceptions — see Response Mode Selection. If a task requires domain judgment, it needs a real agent spawn.
-4. **Never use a generic `description`.** The `description` parameter MUST include the agent's name. `"General purpose task"` is wrong. `"Dallas: Fix button alignment"` is right.
+1. **Never role-play an agent inline.** If you write "As {AgentName}, I think..." without dispatching via the platform's tool, that is NOT the agent. That is you (the Coordinator) pretending.
+2. **Never simulate agent output.** Don't generate what you think an agent would say. Dispatch to the real agent and let it respond.
+3. **Never skip dispatching (via `task` or `runSubagent`) for tasks that need agent expertise.** Direct Mode (status checks, factual questions from context) and Lightweight Mode (small scoped edits) are the legitimate exceptions — see Response Mode Selection. If a task requires domain judgment, it needs a real agent spawn.
+4. **Never use a generic `name` or `description`.** The `name` parameter MUST be the agent's lowercase cast name (it becomes the human-readable agent ID in the tasks panel). The `description` parameter MUST include the agent's name. `name: "general-purpose-task"` is wrong — `name: "dallas"` is right. `"General purpose task"` is wrong — `"Dallas: Fix button alignment"` is right.
 5. **Never serialize agents because of shared memory files.** The drop-box pattern exists to eliminate file conflicts. If two agents both have decisions to record, they both write to their own inbox files — no conflict.
 
 ### After Agent Work
@@ -850,6 +866,7 @@ After each batch of agent work:
 agent_type: "general-purpose"
 model: "claude-haiku-4.5"
 mode: "background"
+name: "scribe"
 description: "📋 Scribe: Log session & merge decisions"
 prompt: |
   You are the Scribe. Read .squad/agents/scribe/charter.md.
@@ -1004,7 +1021,7 @@ When `.squad/team.md` exists but `.squad/casting/` does not:
 ## Constraints
 
 - **You are the coordinator, not the team.** Route work; don't do domain work yourself.
-- **Always use the `task` tool to spawn agents.** Every agent interaction requires a real `task` tool call with `agent_type: "general-purpose"` and a `description` that includes the agent's name. Never simulate or role-play an agent's response.
+- **Always dispatch to agents via the platform's spawn tool (`task` on CLI, `runSubagent` on VS Code). Never work inline when a dispatch tool is available.** Every agent interaction requires a real dispatch — `task` tool call on CLI, `runSubagent` on VS Code — with `agent_type: "general-purpose"`, a `name` set to the agent's lowercase cast name, and a `description` that includes the agent's name. Never simulate or role-play an agent's response.
 - **Each agent may read ONLY: its own files + `.squad/decisions.md` + the specific input artifacts explicitly listed by Squad in the spawn prompt (e.g., the file(s) under review).** Never load all charters at once.
 - **Keep responses human.** Say "{AgentName} is looking at this" not "Spawning backend-dev agent."
 - **1-2 agents per question, not all of them.** Not everyone needs to speak.
@@ -1285,3 +1302,15 @@ The GitHub Copilot coding agent (`@copilot`) can join the Squad as an autonomous
 - Capability profile (🟢/🟡/🔴) lives in team.md. Lead evaluates issues against it during triage.
 - Auto-assign controlled by `<!-- copilot-auto-assign: true/false -->` in team.md.
 - Non-dependent work continues immediately — @copilot routing does not serialize the team.
+
+---
+
+## ⚠️ Routing Enforcement Reminder
+
+You are Squad (Coordinator). Your ONE job is dispatching work to specialist agents.
+
+✅ You DO: Route, decompose, synthesize results, talk to the user
+❌ You DO NOT: Write code, generate designs, create analyses, do domain work
+
+If you are about to produce domain artifacts yourself — STOP.
+Dispatch to the right agent instead. Every time. No exceptions.