Restore squad-cli as a default-installed tool (reverse part of #475)
Decision (Earl, 2026-06-19): squad-cli should be installed by default as part of dev-setup. It is a developer tool (the engine behind the gosquad launcher alias, gosquad='copilot --agent squad --yolo'), NOT squad coordination infrastructure. PR #475 (de-squad) removed its installer along with the embedded squad -- the same over-scrub class as the earlier gosquad removal that had to be reverted. This issue restores it.
Background
PR #475 (baee5d9; squad-cli removal in commit a3f257a) deleted the squad-cli installer and all call sites. The original files are recoverable from git at a3f257a^:
scripts/linux/tools/squad-cli.shscripts/windows/tools/squad-cli.ps1
Scope (whatever the final design)
Constraints
- Dependency ordering is positional in setup -- squad-cli MUST come after the node/npm chain.
develop is PR-protected; land via PR + admin-merge.- Confirm the exact install method (
npm install -g @bradygaster/squad-cli vs other) against the recovered installer + current upstream package name.
Relationship to #468
#468 (customizable install, flags-first) keeps squad-cli in its tool registry. This restore makes squad-cli a real installable tool; once #468 lands, it becomes one of the selectable/default tools. Restore can proceed independently of / in parallel with #468.
Out of scope
- Does NOT re-introduce the embedded
.squad/ coordination tree, squad workflows, squad.agent.md, or spawn scripts -- those stay removed (HQ coordinates the squad externally). This is ONLY the squad-cli tool installer.
Restore squad-cli as a default-installed tool (reverse part of #475)
Decision (Earl, 2026-06-19):
squad-clishould be installed by default as part of dev-setup. It is a developer tool (the engine behind thegosquadlauncher alias,gosquad='copilot --agent squad --yolo'), NOT squad coordination infrastructure. PR #475 (de-squad) removed its installer along with the embedded squad -- the same over-scrub class as the earliergosquadremoval that had to be reverted. This issue restores it.Background
PR #475 (
baee5d9; squad-cli removal in commita3f257a) deleted the squad-cli installer and all call sites. The original files are recoverable from git ata3f257a^:scripts/linux/tools/squad-cli.shscripts/windows/tools/squad-cli.ps1Scope (whatever the final design)
scripts/linux/tools/squad-cli.shandscripts/windows/tools/squad-cli.ps1(recover froma3f257a^, modernize to current tool/script conventions).scripts/linux/setup.sh(run_tool) andscripts/windows/setup.ps1(dot-source +Install-SquadCli), positioned after node/npm -- dependency chain is nvm -> node -> npm -> squad-cli (squad-cli installs via npm)..tool-versionspin if that pattern is still used (verify -- chore: remove embedded squad (infra + config) #475 removed it).tests/test_nvm_bootstrap.sh(squad-cli cases) +tests/test_windows_setup.ps1(Windows cases) + anye2e-install.ymlinstall check -- following current test conventions, not blindly reverting deleted blocks.Constraints
developis PR-protected; land via PR + admin-merge.npm install -g @bradygaster/squad-clivs other) against the recovered installer + current upstream package name.Relationship to #468
#468 (customizable install, flags-first) keeps squad-cli in its tool registry. This restore makes squad-cli a real installable tool; once #468 lands, it becomes one of the selectable/default tools. Restore can proceed independently of / in parallel with #468.
Out of scope
.squad/coordination tree, squad workflows, squad.agent.md, or spawn scripts -- those stay removed (HQ coordinates the squad externally). This is ONLY the squad-cli tool installer.