#187 fix(install): cargo build fails on fresh Mac when rustup was just installed in same session

[Anonymous]

Originally created by: adityaharishch

Problem

In install.sh, when rustup is installed fresh (line ~419), the script sources ~/.cargo/env to put cargo on PATH. But --no-modify-path is passed to the rustup installer so .profile is not modified. The source is conditional on DRY_RUN -eq 0.

If the source fails or is skipped, cargo build --release (line ~635) runs against the original PATH which has no cargo, failing with "command not found" on a completely fresh Mac.

Fix

After installing rustup, unconditionally verify cargo is on PATH before proceeding. Emit a clear error with instructions if not found (e.g. "open a new terminal and re-run install.sh").