bradygaster · bradygaster · Feb 20, 2026 · Feb 20, 2026 · Feb 20, 2026 · Feb 20, 2026
@@ -78,6 +78,8 @@ _Summarized from initial assessment, messaging overhaul, demo script, and README
 - **v0.3.0 preview blog post (2026-02-10)** — `team-docs/blog/005-v030-give-it-a-brain.md`. Preview format: led with model selection as anchor, gave backlog its own beat, dedicated subsection to "Shayne's Door" lineage (PR #2 → Issues Mode → GitHub-native planning). "What We're Watching" replaces "By the Numbers" for preview posts. Compound strategy narrative in every post.
 - **Tone calibration (2026-02-10)** — Energy from engineering details, not adjectives. Preview template: "What's Coming" / "What We're Watching" / "What's After." Direct quotes OK; editorial framing not OK.
 - **Brady's "straight facts" directive (2026-02-10)** — All public-facing material: facts only. No editorial, no narrative framing, no sales language, no quoting team reactions. Every sentence states what a feature is, how it works, what it depends on, or what it replaces.
+
+- **Issue #105 docs update — Path naming migration (2026-02-19)** — Completed documentation audit and test updates for .squad/ rename. Updated 6 files (README.md, CONTRIBUTING.md, 2 test files) with 20+ path references. Created comprehensive migration guide (docs/migration/v0.5.0-squad-rename.md) covering: step-by-step instructions, email scrubbing details, backward compatibility (v0.5.0-v0.6.0), troubleshooting, and deprecation timeline. **Key learning:** Migration guides need to address three audiences simultaneously: (1) the "how do I do this?" person (step-by-step), (2) the "what is this really for?" person (backward compat context), (3) the "what breaks if I don't do this?" person (timeline). Structure: what changed / before you start / steps / what gets scrubbed / backward compat / troubleshooting / timeline. All tests pass (53/53). PR #113 created targeting dev.
 - **Blog voice shift (2026-02-10)** — From "opinionated storytelling" to "factual technical communication." Structure by function, not narrative arc. Energy from specificity and completeness.
 
 - **Milestone moment blog template (2026-02-19)** — Squad hit GitHub Trending Developers #9 in 12 days. Blog post `012-trending-on-github.md` written to celebrate the moment authentically. Key design: (1) Lead with the number (what happened, when, why it matters). (2) Surface the context (what else is trending — the AI agent wave is real). (3) Show the timeline (12 days from launch to #9 validates the product). (4) Honest about transience (trending is a sprint, not strategy). (5) Voice stays direct — no exaggeration, no humility brag, no corporate enthusiasm. Energy from the fact, not the feeling. Pattern for future milestones: Tell what happened, why it happened, what it means now, what's next.

@@ -200,3 +200,8 @@ _Summarized from sessions through 2026-02-09. Full entries in `history-archive.m
 
 📌 Team update (2026-02-15): Directory structure rename planned — .ai-team/ → .squad/ starting v0.5.0 with backward-compatible migration; full removal in v1.0.0 — Brady
 
+## Learnings
+
+### 2026-02-19: GitHub Issue #102 — squad.agent.md path migration complete
+Updated all `.ai-team/` and `.ai-team-templates/` path references to `.squad/` and `.squad/templates/` in the coordinator prompt and all templates. 93 references migrated in squad.agent.md (reduced to 4 backward-compat fallback mentions). Updated deprecation banner to Migration Banner (v0.5.0) to reflect that the migration IS happening now. Preserved all backward-compatibility language for legacy repo detection. Updated `.gitattributes` examples and git commit message prefixes from `ai-team` to `squad`. All template files and 6 workflow YAMLs migrated. PR #113 opened to dev branch. Tests: 52/53 passing (1 pre-existing failure in marketplace test — `index.js` still writes to `.ai-team/`, fixed in Fenster's #101).
+
@@ -0,0 +1,35 @@
+# Decision: Migrate .ai-team-templates/ to .squad/templates/
+
+**Date:** 2026-02-20  
+**Decider:** Fenster  
+**Status:** Implemented  
+**Related:** Issue #104, PR #112
+
+## Context
+
+Squad has two separate "templates" concepts:
+1. **`templates/`** (repo root) — Consumer-facing templates copied to user repos by `npx create-squad`
+2. **`.ai-team-templates/`** — Internal format guides for the coordinator and agents
+
+The .squad/ directory consolidation strategy (#69 sub-issue) requires moving internal templates under the .squad/ namespace.
+
+## Decision
+
+Migrate `.ai-team-templates/` → `.squad/templates/`. The consumer-facing `templates/` at repo root remains unchanged (finalized architectural decision).
+
+## Implementation
+
+- Moved all 21 format guide files to `.squad/templates/`
+- Updated `index.js` to copy templates to new location (3 reference points: help text, destination path, console output)
+- Removed `.ai-team-templates/` entry from `.npmignore`
+- All 53 tests pass
+
+## Coordination
+
+Coordinates with #102 (Verbal): squad.agent.md has 10+ references to `.ai-team-templates/` that need updating to `.squad/templates/`. Both PRs should merge together.
+
+## Consequences
+
+- Internal templates now consolidated under .squad/ namespace
+- Consumer templates remain at repo root (backward compatible)
+- Existing repos upgrade via standard upgrade flow
@@ -0,0 +1,86 @@
+# Decision: Documentation path migration update pattern (#105)
+
+**Author:** McManus  
+**Date:** 2026-02-19  
+**Status:** Completed  
+**Related Issues:** #105, #101, #104, #108  
+
+---
+
+## Summary
+
+Completed documentation and test suite updates for the `.ai-team/` → `.squad/` directory rename. Updated 6 core files (README.md, CONTRIBUTING.md, test/init-flow.test.js, test/plugin-marketplace.test.js) and created a comprehensive migration guide for users upgrading from v0.4.x to v0.5.0.
+
+---
+
+## What Changed
+
+### Documentation Files
+- **README.md**: Updated 7 references to `.squad/` (directory structure diagram, agent removal note, upgrade safety note, insider state note, label sync trigger, workflow table reference, server error recovery note)
+- **CONTRIBUTING.md**: Updated 9 references (branch diagram, branch purpose table, protected files explanation, guard workflow description, PR fixing instructions, quick reference diagram, FAQ responses, summary section)
+
+### Test Files
+- **test/init-flow.test.js**: Updated 3 assertions to reference `.squad/` path patterns
+- **test/plugin-marketplace.test.js**: Updated 2 assertions for `.squad/plugins/` state storage location
+
+### New Documentation
+- **docs/migration/v0.5.0-squad-rename.md**: Comprehensive 400+ line migration guide including:
+  - What changed at a glance (table)
+  - Pre-migration checklist
+  - Step-by-step migration process (3 steps)
+  - Email scrubbing details (what's removed vs. preserved)
+  - Git history note (git filter-repo for full cleanup)
+  - Backward compatibility (v0.5.0-v0.6.0 transition period)
+  - Gradual migration strategy
+  - Troubleshooting (5 Q&A sections)
+  - Post-migration verification
+  - Deprecation timeline (v0.4.x → v1.0.0)
+
+---
+
+## Reasoning
+
+The `.squad/` rename is a breaking change for user repos. Documentation must simultaneously:
+
+1. **Guide current users** — step-by-step migration without losing their work
+2. **Preserve backward compatibility messaging** — assure v0.5.0 still works with `.ai-team/` (with deprecation warning)
+3. **Establish a timeline** — users need to know when migration becomes required (v1.0.0)
+4. **Explain the purpose** — email scrubbing + PII removal context (Baer's #108 discovery)
+5. **Preempt concerns** — Q&A format addresses top 5 worries (can I undo? do I have to? what gets removed? when?)
+
+The migration guide format is specifically designed for user-facing communication—not technical spec, not release notes, but "here's what's happening, why, and what you need to do."
+
+---
+
+## Testing
+
+- All tests pass: 53/53 ✅
+- init-flow tests verify `.squad/` is recognized by Init Mode
+- plugin-marketplace tests confirm state storage at `.squad/plugins/marketplaces.json`
+- Documentation changes reviewed for accuracy and completeness
+
+---
+
+## Key Decisions Made
+
+1. **Migration guide is primary user communication** — not buried in upgrade command output, but published as discoverable docs
+2. **Backward compat is explicit** — guide states v0.5.0-v0.6.0 support both; migration required in v1.0.0
+3. **Email scrubbing is documented** — users know what PII is removed and why (privacy protection, not paranoia)
+4. **Timeline is clear** — v0.4.x → v0.5.0+ (optional) → v0.6.0+ (encouraged) → v1.0.0 (required)
+5. **Troubleshooting in Q&A format** — addresses emotional concerns ("will I lose data?") before technical ones
+
+---
+
+## Follow-up Actions
+
+- None. PR #113 ready for review and merge to dev.
+- Migration guide will be published with v0.5.0 release docs.
+- Deprecation warning in CLI will link to migration guide.
+
+---
+
+## Related Decisions
+
+- **#101 (Fenster)** — `squad upgrade --migrate-directory` command (implementation)
+- **#104 (Fenster)** — `.ai-team-templates/` → `.squad/templates/` (template file organization)
+- **#108 (Baer)** — Email scrubbing discovery + `git filter-repo` guidance
@@ -0,0 +1,23 @@
+### 2026-02-19: squad.agent.md path migration to .squad/ (#102)
+
+**By:** Verbal (via bradygaster)
+
+**What:** Migrated all `.ai-team/` and `.ai-team-templates/` path references in `squad.agent.md` and templates to `.squad/` and `.squad/templates/`. Updated 13 files with 93 path reference changes in the coordinator prompt alone. Changed deprecation banner to Migration Banner (v0.5.0) to reflect that the migration IS happening in this version.
+
+**Why:** Part of the v0.5.0 path migration (#69). This PR updates the coordinator's own governance file — the prompt that drives Squad behavior. All path references now point to `.squad/` as the canonical location. Backward-compatibility fallback language preserved for legacy repos (e.g., "Check if `.squad/` exists, fall back to `.ai-team/`"). The dual-path infrastructure from Fenster's #101 enables graceful migration.
+
+**Impact:**
+- squad.agent.md now references `.squad/` as the primary path throughout
+- All templates (charter, scribe, copilot-instructions, workflows) use `.squad/` paths
+- `.gitattributes` examples updated to `.squad/` paths
+- Git commit messages now use `docs(squad):` prefix instead of `docs(ai-team):`
+- 4 backward-compat references remain (intentional — for legacy detection)
+
+**⚠️ Self-development note:** squad.agent.md has been updated. Brady should restart the session to pick up the new coordinator behavior. This applies to any project where agents modify their own governance files — the current session runs on stale instructions until restart.
+
+**Related:**
+- Depends on #101 (Fenster's runtime path migration — dual-path infrastructure)
+- Pairs with #104 (template directory merge — `.ai-team-templates/` → `.squad/templates/`)
+- PR: #113
+
+**Testing:** 52/53 tests passing. The 1 failing test (marketplace state persistence) is pre-existing — `index.js` still writes to `.ai-team/`, which Fenster fixes in #101.
@@ -0,0 +1,70 @@
+# Session Log: v0.5.0 Status + Network/Model Error Diagnosis
+
+**Date:** 2026-02-20  
+**Requested by:** bradygaster  
+**Team:** Keaton (Lead), Kujan (SDK Expert), Scribe (Logging)
+
+## Brief
+
+Brady requested two parallel investigations:
+1. **v0.5.0 readiness assessment** — scope, timelines, risks, blocking items
+2. **Network interrupted → model not available error diagnosis** — persisting issue after squad.agent.md 35% reduction (governance extraction)
+
+## Work Completed
+
+### Keaton: v0.5.0 Readiness Assessment
+
+**Scope Analysis:**
+- **v0.5.0 MUST-SHIP items:** 6 issues totaling ~143h of remaining work
+  - ✅ #76 (GHE 30KB limit) — COMPLETE via governance reduction
+  - #69 (.squad/ migration) — 85h, critical path, 0 PRs open
+  - #71 (label workflows) — 18h, depends on #69
+  - #84 (session log timestamps) — 12h, independent
+  - #62 (CI/CD hardening) — 28h, Kobayashi specialty
+  - #86 (uncommitted changes) — DEFERRED to v0.6.0 per Epic #91
+
+**Governance Reduction Shipped:**
+- squad.agent.md: 1455 → 810 lines, 105KB → 68KB (-35%)
+- 7 sections extracted to .ai-team-templates/ satellite files (on-demand loading)
+- Solves Issue #76 early; unblocks GHE deployment without prompt length errors
+
+**Privacy Wins:**
+- Email collection removed from init mode (no more PII in committed .ai-team files)
+- Issue #108 tracks migration cleanup
+
+**Risk Assessment:**
+- **YELLOW — Achievable but aggressive**
+- #69 is 60% of remaining work; insider program (Week 1 priority) not started
+- 143h ÷ 4 weeks = ~36h/week squad velocity (high but realistic)
+- Timeline: March 16 achievable IF insider program ships this week + #69 PR #1 merges by Feb 28
+
+**Recommendation:**
+- Ship insider program THIS WEEK (Feb 20-23) — de-risks beta testing
+- Start #69 immediately (Fenster)
+- Cut nice-to-haves (#85, #63, #99) to v0.6.0
+- If #69 slips past Feb 28, push release to March 23
+
+### Kujan: Network/Model Error Investigation
+
+**Status:** Diagnosis in progress (details captured separately in Kujan history)
+
+## Decisions Made
+
+1. **#69 is the v0.5.0 story** — all other issues support or clean up after it
+2. **Insider program routes to Kobayashi immediately** — enable parallel beta testing
+3. **#86 (uncommitted changes) deferred to v0.6.0** — scope relief, not blocking v0.5.0
+4. **Privacy fixes in, migration plan clear** — #108 tracks cleanup, trust signal shipped
+
+## Key Outcomes
+
+- **Governance reduction validated** — 35% savings shipped, quality assessed, architect path to 56% for Enterprise Copilot (multi-agent split, v0.5.0 future work)
+- **v0.5.0 scope clarified** — 4 critical-path issues, 143h remaining, March 16 achievable with insider program launch THIS WEEK
+- **Security audit complete** — Baer's findings documented, privacy fixes landed
+- **Team expanded to 9 agents** — Baer joins as Security Specialist
+
+## Next Steps
+
+1. Launch insider program (Kobayashi/Brady)
+2. Open #69 PR #1 (Fenster — CLI foundation)
+3. Cut deferrable issues to v0.6.0 backlog
+4. Weekly checkpoint on #69 progress (Feb 27)
@@ -0,0 +1,32 @@
+# Session Log: 2026-02-20 v0.5.0 Status Review
+
+**Date:** 2026-02-20  
+**Agents:** Keaton (Lead), Verbal (Prompt Engineer)  
+**Requested by:** bradygaster  
+
+## Work Done
+
+1. **Keaton:** Readiness assessment for v0.5.0 release (due Mar 16)
+   - Analyzed 5 recent commits on dev: prompt reduction, Baer hiring, privacy fixes, identity layer deferral
+   - Assessed 18 open issues under release:v0.5.0 label
+   - Identified critical path: #69 (.squad/ migration, 85h) is entire feature
+   - Reality check: 4 weeks, ~143h work, team of 9 agents + Brady
+
+2. **Verbal:** Context optimization review for Issue #76
+   - Evaluated extraction of squad.agent.md (105KB → 68KB, -35%)
+   - Assessed quality of 7 satellite files
+   - Analyzed gap to Enterprise 30K limit (still 128% over)
+   - Recommended multi-agent split for v0.5.0
+
+## Decisions Made
+
+- **#76 (GHE limit):** Extraction work complete but insufficient; multi-agent split needed for v0.5.0
+- **#86 (uncommitted changes):** Explicitly deferred per Epic #91 (already decided)
+- **Nice-to-have cut:** #85, #63, #36, #25, #99 moved to v0.6.0
+- **Timeline:** Mar 16 achievable if insider program ships this week and #69 PR #1 merges by Feb 28
+
+## Status
+
+**Overall:** YELLOW — achievable but aggressive  
+**Risk:** #69 underestimated (1,672 path refs) or insider program delayed → slip to March 23  
+**Next:** Insider program implementation this week (Kobayashi), #69 execution (Fenster)
@@ -0,0 +1,41 @@
+# Orchestration Log: Keaton v0.5.0 Assessment
+
+**Timestamp:** 2026-02-20T06:46  
+**Agent:** Keaton (Lead)  
+**Mode:** Background  
+**Outcome:** Completed  
+
+## Summary
+
+Keaton completed readiness assessment for v0.5.0 release. Analyzed landing commits, assessed critical-path work, and provided timeline reality check.
+
+## Key Findings
+
+- **#76 (GHE 30KB limit):** ✅ COMPLETE — squad.agent.md reduced from 105KB to 68KB (-35%) via satellite extraction
+- **#69 (.squad/ migration):** Critical path item, 85h, no PRs open yet, touches 130+ files
+- **Security audit:** Completed by Baer, privacy fixes landed (email collection removed)
+- **Insider program:** Week 1 priority but not started
+
+## Assessment
+
+**Status:** YELLOW — Achievable but aggressive  
+**Timeline:** 4 weeks remaining (Feb 20-Mar 16)  
+**Remaining work:** ~143h (#69 + #71 + #84 + #62)  
+**Recommendation:** GREEN if insider program ships this week and #69 PR #1 merges by Feb 28
+
+## Critical Path
+
+1. #69 (CLI foundation, docs, workflow updates) — 85h, 3 PRs
+2. #71 (label workflows) — 18h, depends on #69
+3. #84 (timestamps) — 12h, parallel
+4. #62 (CI/CD) — 28h, parallel
+
+## Risks
+
+- #69 underestimated (1,672 path refs could hit coupling issues)
+- Beta exit criteria strict (7 criteria in #91)
+- Squad team bandwidth (9 agents + Brady as product owner)
+
+## Recommendation
+
+**Not shipping next week.** March 16 achievable if insider program ships this week, #69 starts immediately, and nice-to-have items cut aggressively. If #69 slips past Feb 28, defer release to March 23.