Customizable install: pick-and-choose tools (flags vs prompt vs manifest)

[primetimetank21]

Make scripts/linux/setup.sh and its Windows peer support pick-and-choose tool installation -- some users want a subset, not the full set.

Why now

Two new tools are queued (delta, lazygit) and the existing scripts/linux/tools/ directory already implies a tools-as-modules pattern. Adding a flag/manifest framework first means new tools (#TBD-delta, #TBD-lazygit) slot in cleanly instead of being bolted on and refactored later.

Open design questions (go:needs-research)

The team should grill these before implementation. Three credible shapes:

Shape	Pros	Cons
Flags -- setup.sh --only=delta,lazygit / --skip=copilot-cli	Script-friendly, CI-friendly, terse	Discovery is poor; users must know tool names
Interactive prompt -- check-boxes via select / Out-GridView	Best UX for humans	Breaks CI/headless; needs a --non-interactive escape hatch
Manifest file -- tools.manifest opt-in/opt-out file in repo or ~/.config/	Reproducible, version-controllable	Indirection; harder to discover than flags
Hybrid (likely answer) -- flags for CI, prompt for humans, manifest for reproducibility	Covers all three audiences	Most surface area to design and test

Required outcomes (whatever shape wins)

• All existing tool installers in scripts/linux/tools/ and scripts/windows/tools/ remain individually invocable
• Default behavior (no flags) MUST match current behavior -- backward compatibility gate
• A --list / --help mode that enumerates available tools
• New tests (bash + pwsh parity) covering: default install, --only subset, --skip subset, unknown-tool error
• Documentation update in README and scripts/linux/setup.sh --help

Routing

• squad:goofy (cross-platform: bash + pwsh parity is the core constraint)
• squad:mickey (Lead -- architectural decision on flags vs interactive vs manifest)
• go:needs-research until the shape decision is grilled and recorded in decisions.md

[github-actions]

🏗️ Squad Triage — Mickey (Lead)

Issue: #468 — Customizable install: pick-and-choose tools (flags vs prompt vs manifest)
Assigned to: Chip (Tester)
Reason: Issue relates to testing/quality work

Team roster:

• Mickey (Lead) → label: squad:mickey
• Donald (Shell Dev) → label: squad:donald
• Goofy (Cross-Platform Dev) → label: squad:goofy
• Pluto (Config Engineer) → label: squad:pluto
• Chip (Tester) → label: squad:chip
• Jiminy (Squad Hygiene Auditor) → label: squad:jiminy
• Doc (Fact Checker) → label: squad:doc
• Ralph (Work Monitor) → label: squad:ralph

To reassign, remove the current squad:* label and add the correct one.

[github-actions]

📋 Assigned to Mickey (Lead)

Issue: #468 — Customizable install: pick-and-choose tools (flags vs prompt vs manifest)

Mickey will pick this up in the next Copilot session.

For Copilot coding agent: If enabled, this issue will be worked automatically.
Otherwise, start a Copilot session and say:
Mickey, work on issue #468

[github-actions]

📋 Assigned to Goofy (Cross-Platform Dev)

Issue: #468 — Customizable install: pick-and-choose tools (flags vs prompt vs manifest)

Goofy will pick this up in the next Copilot session.

For Copilot coding agent: If enabled, this issue will be worked automatically.
Otherwise, start a Copilot session and say:
Goofy, work on issue #468