chore: scrub residual squad/cast-name references (#481)

.copilot/skills/changelog-fold-completeness/SKILL.md

@@ -168,29 +168,13 @@ never failed to find missing entries when applied.
 ## Placement decision
 
 This skill lives in `.copilot/skills/` (process automation level) rather than project-specific
-workflow. Rationale: the fold step is performed during a release cut -- it is release-process
-governance, not day-to-day workflow. The release automation is responsible for ensuring the
-fold is gated on completeness.
+workflow. The release automation is responsible for ensuring the fold is gated on completeness.
 
 Compare with other append-based hygiene checks which govern individual contributions.
 
-## Related Skills
-
-- `.squad/skills/gh-pr-base-develop/SKILL.md` -- every PR must pass
-  `--base develop`; if any PR was misrouted (base=main), the gh queries in Steps 4-5
-  will miss it; verify develop ancestry with `git log $LAST_TAG..develop --merges`
-  as the authoritative source.
-- `.copilot/skills/release-process/SKILL.md` -- the full release runbook; this skill
-  is a pre-step for the fold phase of that runbook.
-- `.squad/skills/history-md-pre-size-check/SKILL.md` -- companion hygiene check
-  (contributor-level); ensures history files are within gate before the sprint
-  closes and before the release audit.
-
 ## References
 
 - Issue #399 -- formalization request (Sprint 18)
-- Sprint 17 retro (`.squad/retros/2026-05-18-sprint-17-retro.md`) -- "Key learnings:
-  RECURRING: Pre-append history.md size check missing" and release completeness notes
 - PR #393 (commit 71d2ffe) -- Sprint 17 release (0.9.7); completeness check applied,
   5 missing entries added
 - PR #372 (commit 7172ae7) -- Sprint 16 release (0.9.6); completeness check applied

.copilot/skills/docs-standards/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: "docs-standards"
-description: "Microsoft Style Guide + Squad-specific documentation patterns"
+description: "Microsoft Style Guide + documentation patterns"
 domain: "documentation"
 confidence: "high"
 source: "earned (PAO charter, multiple doc PR reviews)"
 ---
 
 ## Context
 
-Squad documentation follows the Microsoft Style Guide with Squad-specific conventions. Consistency across docs builds trust and improves discoverability.
+Documentation follows the Microsoft Style Guide with project-specific conventions. Consistency across docs builds trust and improves discoverability.
 
 ## Patterns
 
@@ -19,7 +19,7 @@ Squad documentation follows the Microsoft Style Guide with Squad-specific conven
 - **Present tense:** "The system routes..." not "The system will route..."
 - **No ampersands in prose:** "and" not "&" (except in code, brand names, or UI elements)
 
-### Squad Formatting Patterns
+### Documentation Formatting Patterns
 - **Scannability first:** Paragraphs for narrative (3-4 sentences max), bullets for scannable lists, tables for structured data
 - **"Try this" prompts at top:** Start feature/scenario pages with practical prompts users can copy
 - **Experimental warnings:** Features in preview get callout at top
@@ -35,31 +35,31 @@ Squad documentation follows the Microsoft Style Guide with Squad-specific conven
 
 ? **Correct:**
 ```markdown
-# Getting started with Squad
+# Getting started with the project
 
 > ! **Experimental:** This feature is in preview.
 
 Try this:
 \`\`\`bash
-squad init
+init
 \`\`\`
 
-Squad helps you build AI teams...
+This project helps you build...
 
 ---
 
-## Install Squad
+## Install the tool
 
 Run the following command...
 ```
 
 ? **Incorrect:**
 ```markdown
-# Getting Started With Squad  // Title case
+# Getting Started With the Project  // Title case
 
-Squad is a tool which will help users... // Third person, future tense
+The tool is designed to help users... // Third person, future tense
 
-You can install Squad with npm & configure it... // Ampersand in prose
+You can install it with npm & configure it... // Ampersand in prose
 ```
 
 ## Anti-Patterns

.copilot/skills/git-workflow/SKILL.md

@@ -114,12 +114,12 @@ gh pr create --base develop --title "fix: stamp bug" --body "Closes #195" --draf
 
 All PRs target `develop` independently. Multiple worktrees don't interfere with each other's filesystem.
 
-### .squad/ State in Worktrees
+### Project State Files in Worktrees
 
-The `.squad/` directory (if present) exists in each worktree as a copy. This is safe because:
-- `.gitattributes` declares `merge=union` on append-only files (history.md, decisions.md, logs)
-- Each process appends to its own section; union merge reconciles on PR merge to develop
-- **Rule:** Never rewrite or reorder `.squad/` files in a worktree -- append only
+Project-specific state files (if present) exist in each worktree as a copy. To avoid conflicts on merge:
+- Configure `.gitattributes` to use `merge=union` for append-only files
+- Each process appends its own section; union merge reconciles sections on PR merge
+- **Rule:** Never rewrite or reorder state files in a worktree -- append only
 
 ### Cleanup After Merge
 

.copilot/skills/github-multi-account/SKILL.md

@@ -2,7 +2,7 @@
 name: github-multi-account
 description: Detect and set up account-locked gh aliases for multi-account GitHub. The AI reads this skill, detects accounts, asks the user which is personal/work, and runs the setup automatically.
 confidence: high
-source: https://github.com/tamirdresher/squad-skills/tree/main/plugins/github-multi-account
+source: earned (multi-account patterns from GitHub CLI documentation)
 author: tamirdresher
 ---
 
@@ -45,7 +45,7 @@ Set-Alias ghw gh-work
 }
 
 # 3. Create CMD wrappers
-$binDir = Join-Path $env:USERPROFILE ".squad\bin"
+$binDir = Join-Path $env:USERPROFILE ".local\bin"
 if (!(Test-Path $binDir)) { New-Item -ItemType Directory -Path $binDir -Force | Out-Null }
 "@echo off`ngh auth switch --user $personal >nul 2>&1`ngh %*" | Out-File "$binDir\ghp.cmd" -Encoding ascii
 "@echo off`ngh auth switch --user $work >nul 2>&1`ngh %*" | Out-File "$binDir\ghw.cmd" -Encoding ascii
@@ -84,12 +84,15 @@ ghw api user --jq '.login'   # should show work username
 
 ## Repo-Specific Account Binding
 
-This repo (`bradygaster/squad`) is bound to the **bradygaster** (personal) account.
-All `gh` operations in this repo MUST use `ghp` / `gh-personal`.
+Each repository is bound to a specific account based on ownership.
+All `gh` operations in that repo MUST use the appropriate alias (personal or work).
+
+Example: if `owner/repo` is your personal project, use `ghp` / `gh-personal`.
+
+## For Automation Agents
 
-## For Squad Agents
 At the TOP of any script touching GitHub, define:
 ```powershell
-function gh-personal { gh auth switch --user bradygaster 2>$null | Out-Null; gh @args }
-function gh-work { gh auth switch --user bradyg_microsoft 2>$null | Out-Null; gh @args }
+function gh-personal { gh auth switch --user $personal 2>$null | Out-Null; gh @args }
+function gh-work { gh auth switch --user $work 2>$null | Out-Null; gh @args }
 ```