docs(plans): strip stale squad-cli content from #468 plan (WI-0)#486
Closed
primetimetank21 wants to merge 1 commit into
Closed
docs(plans): strip stale squad-cli content from #468 plan (WI-0)#486primetimetank21 wants to merge 1 commit into
primetimetank21 wants to merge 1 commit into
Conversation
…dropped in #475) Resolve D4 decision: remove all 11 squad-cli references from the customizable-install plan document, including: - R5 NOTE banner (line 126) - squad-cli entries in Linux DEFAULT_TOOLS array (line 137) - squad-cli entries in Windows \\\ array (line 156) - squad-cli entry in Windows \\\ (line 213) - squad-cli entries in current order listings (lines 495, 513) - squad-cli rows in graceful-degradation table (lines 646-654, 661-662) Updated prose count: "seven run_tool calls" -> "six run_tool calls" (Linux). Updated front-matter 'updated' field to 2026-06-19. This is the first WI in the FLAGS-FIRST #468 implementation path (WI-0, doc-only). Backward-compat neutral: no functional changes, only documentation cleanup. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Owner
Author
|
Closing: superseded by user decision (2026-06-19). squad-cli is a dev tool Earl wants installed by default (it is the engine behind the gosquad launcher), not squad-infra to remove. Stripping it from the #468 plan was the wrong call. Tracking the squad-cli installer restore in a new issue instead. See HQ coordination. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WI-0: Strip stale squad-cli content from #468 plan
Issue: #468 (Customizable install)
What
Resolved D4 decision: stripped all 11 squad-cli references from the #468 customizable-install plan document. This work item is the first (WI-0) in the FLAGS-FIRST implementation series.
Why
The dev-setup repository fully de-squadded squad-cli in PR #475 (2026-06-11). The #468 plan document, created before that de-squad, still contained squad-cli as a live tool in multiple places. These stale references would dangerously seed squad-cli into the default-run tool registry with NO installer, violating the plan's own coherence invariants.
This doc-only PR strips the moot content before WI-1 (the framework implementation) ships, ensuring the plan reflects the current post-#475 reality.
Changes
Removed 11 squad-cli references:
Also:
updatedfield to 2026-06-19Backward-Compat Impact
None. This is a pure documentation cleanup. No functional code, no tool behavior changes. The file is now coherent with the post-#475 toolset.
Testing
git grep -i squad-clireturns emptyDeployment
Doc-only. No build, no deployment steps. This PR can merge anytime after review.
Next: WI-1 (Flags-first framework) will build the core engine for
--list,--only=,--skip=,--helpand the backward-compat gate. Part of FLAGS-FIRST #468 implementation phase.