test: validate install.sh on Linux (Debian/Ubuntu/Arch) + report any package-manager quirks

[evemcgivern]

Context

install.sh was developed on macOS and exercised under WSL. CI now mechanizes the installer-centric checks on Ubuntu (see the install.sh smoke (ubuntu) job in .github/workflows/test.yml, added for this issue): it runs install.sh --help, a real install into a scratch target, the --target override (Codex layout), and python3 work_plan.py --help, asserting each lands. The Python suite already runs on ubuntu-latest across 3.9–3.12.

What CI cannot prove — and what this issue now tracks — is the package-manager one-liners and non-Ubuntu distros. CI installs the yq binary directly rather than going through the README's apt/pacman/dnf instructions, so those paths (and the mikefarah-vs-kislyuk yq distinction they produce) are still unverified by a human on real distros.

Remaining acceptance criteria (manual)

• On a fresh Debian/Ubuntu env, install the four prereqs (gh, git, yq, python3) using the README one-liners — confirm they work as written
• On a fresh Arch env, same via pacman — confirm the one-liner is correct
• (bonus) Fedora via dnf
• On each, confirm the yq the README one-liner installs is mikefarah/yq (Go binary), NOT kislyuk/yq (Python jq wrapper) — see CONTRIBUTING.md. This is the highest-risk item: distro repos sometimes ship the wrong yq.
• Comment here with any distro-specific quirks (especially yq packaging or Python version skew), and flag any README one-liner that's wrong/outdated

Already covered by CI (no manual action needed)

• Run ./install.sh → install.sh smoke (ubuntu) job
• Run ./install.sh --target=$HOME/.agents → smoke job (Codex-layout override)
• Run ./install.sh --help → smoke job
• Run python3 work_plan.py --help → smoke job
• Python suite on Linux → unittest matrix (ubuntu-latest, 3.9–3.12)

Pointers

• README "Requirements" section has the per-distro install one-liners — flag any that are wrong/outdated
• install.sh is POSIX-ish bash with set -euo pipefail

Effort

~15-30 minutes per distro (one-liner verification only — the installer mechanics are now CI-covered).

[snakefood3232]

I'll validate install.sh on multiple Linux distros, focusing on yq discrepancies as outlined. I'd handle this by using the README one-liners for gh, git, yq, and python3, testing on Debian, Ubuntu, and Arch, while checking if yq is the mikefarah Go version. I'll clone the toolkit, run the install script with various flags, and ensure help messages render correctly. Can have a PR up in 48 hours. I've built extensive automation scripts in cross-distro environments before, ensuring compatibility and identifying package manager issues.

[evemcgivern]

Still relevant after the plugin conversion — install.sh remains the fallback path and was substantially changed (PRs #83/#85). Add to the Linux validation:

• Installs the bin/work-plan launcher into <target>/bin/; work-plan --version resolves via the wrapper's ../ self-location.
• Copies the dispatcher from installer/work-plan.md (per-verb suite is plugin-only, not copied).
• Config self-seeds at ~/.claude/work-plan/config.yml (one config home, even with --target=$HOME/.agents).
• uninstall.sh removes the launcher + dispatcher.