@@ -257,14 +257,26 @@
 - **Known issue:** #591 (aspire-integration.test.ts docker pull timeout — environmental, not code)
 - **Architecture insight:** Aspire is NOT a deprecated feature. It's a foundational observability integration that compounds with the OTel instrumentation work (#257–#260). File watcher + dashboard create closed-loop observability loop: runtime traces (internal) + file changes (external) = complete visibility.
 
+### 2026-03-05T[NOW]: PR #131 Close — Remote Squad Mode Ported to Main
+- **Task:** Brady's request to identify and close PR #131 from Shayne Boyer (@spboyer) as superseded. PR proposed elegant remote squad mode with dual-root resolver, repo mode, and hub mode. Brady suspected these features already existed in main via separate PRs.
+- **Investigation:** Reviewed CHANGELOG.md and found explicit credits: "ported from @spboyer's bradygaster/squad#131". All core features mapped to specific implementation PRs:
+  - `resolveSquadPaths()` dual-root resolver (projectDir vs teamDir) → #311
+  - `squad doctor` command (9-check setup validation) → #312
+  - `squad link <path>` + `squad init --mode remote` → #313
+  - `ensureSquadPathDual()` / `ensureSquadPathResolved()` write guards → #314
+- **Resolution:** Posted warm thank-you comment crediting Shayne's design as foundational, mapped each feature, noted that repo mode and hub mode were specializations of his core insight (team identity separation). Closed PR with appreciation note.
+- **Pattern learned:** **Superseded features often deserve explicit appreciation comments.** Closing PRs silently creates contributor alienation; acknowledging which ideas were ported + how they evolved creates goodwill. Shayne's file-ownership-split architecture (team-scoped vs project-scoped) became the backbone of remote squad mode in production.
+- **Next time:** When closing design PRs that were superseded, research the implementation history, map features to issues/PRs, and thank the original author. This is especially important for architectural contributions that influenced later decisions.
+
 ### From Beta (carried forward)
 - Architecture patterns that compound — decisions that make future features easier
-- Silent success mitigation lessons: ~7-10% of background spawns return no text, mitigated by RESPONSE ORDER block + filesystem checks
-- Reviewer rejection lockout enforcement: if Keaton/Hockney/Baer rejects, original author is locked out
-- Proposal-first workflow: docs/proposals/ before execution for meaningful changes
-- 13 modules: adapter, agents, build, casting, cli, client, config, coordinator, hooks, marketplace, ralph, runtime, sharing, skills, tools
-- Distribution: GitHub-native (npx github:bradygaster/squad), never npmjs.com
-- v1 docs are internal only — no published docs site
+- Silent success mitigation lessons: ~7-10% of background spawns return no text, mitigated by RESPONSE ORDER block + filesystem checks
+- Reviewer rejection lockout enforcement: if Keaton/Hockney/Baer rejects, original author is locked out
+- Proposal-first workflow: docs/proposals/ before execution for meaningful changes
+- 13 modules: adapter, agents, build, casting, cli, client, config, coordinator, hooks, marketplace, ralph, runtime, sharing, skills, tools
+- Distribution: GitHub-native (npx github:bradygaster/squad), never npmjs.com
+- v1 docs are internal only — no published docs site
+- **Remote Squad Mode Architecture:** File ownership split (team-scoped: team.md, agents/, casting/, skills/; project-scoped: decisions.md, decisions/inbox/, log/, orchestration-log/) drives dual-root resolution. Config pointer (no symlinks, JSON-based) is Windows-safe and portable. Design is backward-compatible (local mode when no config.json). Inspired by Shayne Boyer's PR #131 design.
 
 ### 2026-02-21: Interactive Shell Proposal
 - **Problem:** Copilot CLI dependency creates unreliable handoffs, zero agent visibility, and external UX control
 
@@ -7,6 +7,35 @@
 
 ## Learnings
 
+### 2026-03-07: Closed Public Repo Issues #175 & PR #182 — Documented Superseding Implementations (COMPLETE)
+**Status:** CLOSED. Both issues closed with appreciation for community work; implementations verified in current codebase.
+
+#### Context
+- **Issue #175:** Bug report from @uvirk — `squad copilot` subcommand hardcoded to `.ai-team/` instead of using `detectSquadDir()`
+- **PR #182:** Fix from @KalebCole — Added `squad doctor` diagnostic (9 checks) + fixed copilot path bug
+
+#### Verification
+1. ✅ `squad doctor` command located at `packages/squad-cli/src/cli/commands/doctor.ts` — implements 9 checks, emoji output, diagnostic-only exit
+2. ✅ `squad copilot` command located at `packages/squad-cli/src/cli/commands/copilot.ts` — properly uses `detectSquadDir()`, no hardcoded `.ai-team/` path
+3. ✅ CHANGELOG.md confirms both features shipped in v0.8.18+ as part of TypeScript replatform (#312, #313, #314)
+4. ✅ Full `.ai-team/` → `.squad/` migration completed in v1 codebase
+
+#### Action Taken
+1. ✅ Posted detailed comments on both PR #182 and issue #175, explaining:
+   - Both features are now implemented in the canonical v1 codebase
+   - Cited specific version (0.8.18+), issue/PR references (#312, #188, #313), and file paths
+   - Thanked @KalebCole for the thorough design and @uvirk for the clear bug report
+   - Explained that public repo had code duplication; v1 is the consolidated implementation
+2. ✅ Closed PR #182 with explicit reference to superseding v1 implementation
+3. ✅ Closed issue #175 with fix version (0.8.18+) and implementation details
+
+#### Key Learning
+When community work duplicates an internal refactor:
+1. Verify that the new implementation is indeed complete and correct
+2. Credit the community contribution for validating the design
+3. Use closure as a teaching moment about architecture consolidation
+4. Be genuine and specific in citations — it builds trust and respect
+
 ### 2026-03-07: Release v0.8.19 — Nap & Doctor Commands, Template Path Fix (COMPLETE)
 **Status:** RELEASED. v0.8.19 published to npm registry, GitHub release created, post-release bump committed.