A bcb59eb925 fix: stop sourcing rc files in launch command — fnm env destroys PATH (#1261) ... Root cause: the launch command did `source ~/.bashrc; source ~/.zshrc; claude`. The .zshrc contains `eval "$(fnm env)"` which outputs PATH with literal "$PATH" in quotes instead of expanding it, destroying the entire PATH. Confirmed via debugging: - `ssh -t ... 'export PATH=...; which claude'` → works (/root/.bun/bin/claude) - `ssh -t ... 'export PATH=...; source ~/.zshrc; which claude'` → "command not found" - `source ~/.zshrc; echo $PATH` → `"/run/user/0/fnm_multishells/...":"$PATH"` (broken) Fix: - Remove `source ~/.bashrc` and `source ~/.zshrc` from ALL launch commands - ssh -t creates a pseudo-terminal, so bash auto-sources .bashrc for env vars - Explicit PATH export is all we need for finding the claude binary - Remove fnm eval snippet from _finalize_claude_install (it poisoned rc files) - Also: clean up stale ~/.bash_profile, fix cloud-init PATH, move node install after bun attempt Co-authored-by: lab <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-02-16 01:06:55 -08:00
..
common.sh	fix: stop sourcing rc files in launch command — fnm env destroys PATH (#1261)	2026-02-16 01:06:55 -08:00
github-auth.sh	refactor: decompose ensure_jq and ensure_gh_cli into focused helpers (#994)	2026-02-13 12:14:56 -08:00
key-request.sh	fix: HIGH severity security issues (command injection + weak VNC password) (#1150)	2026-02-14 20:39:48 -05:00