spawn/test
A d0847986f8
fix: use shared install_claude_code across all clouds with fnm PATH fix (#1242)
All cloud claude.sh scripts had inline curl-only installs with no fallback.
When the curl installer failed (transient outage, rate limit), installation
failed with no recovery. Additionally, fnm-installed Node.js was invisible
to subsequent SSH sessions because each SSH command runs in a non-interactive
shell that doesn't source .bashrc/.zshrc.

Changes:
- Migrate 8 cloud scripts to use shared install_claude_code (curl → npm → bun)
- Move _ensure_node_runtime before npm/bun install attempts (not after)
- Add fnm paths to claude_path so node is discoverable across SSH sessions
- Prefix npm/bun install commands with claude_path for PATH visibility
- Update test assertion to match new install_claude_code behavior

Co-authored-by: lab <6723574+louisgv@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-02-15 23:16:23 -08:00
..
fixtures feat: trim to 9 curated launch clouds, upvote-driven discovery (#1184) 2026-02-15 00:19:39 -08:00
mock-curl-script.sh feat: trim to 9 curated launch clouds, upvote-driven discovery (#1184) 2026-02-15 00:19:39 -08:00
mock.sh feat: trim to 9 curated launch clouds, upvote-driven discovery (#1184) 2026-02-15 00:19:39 -08:00
qa-dry-run.sh feat: qa bot and emails (#565) 2026-02-11 20:19:45 -08:00
record.sh feat: trim to 9 curated launch clouds, upvote-driven discovery (#1184) 2026-02-15 00:19:39 -08:00
run.sh fix: use shared install_claude_code across all clouds with fnm PATH fix (#1242) 2026-02-15 23:16:23 -08:00
update-readme.py QA-Bot setup (#335) 2026-02-10 19:51:07 -08:00