A bare `lc_macos_aarch64` download from the Releases page gets you `lc` and nothing else - no `lcreate`/`lcls`/`lclose`/`lcomment`/`lproj`. Only `install.sh` and the container image ever pulled the wrapper scripts, and both do it straight from a repo checkout, never from a release asset. Anyone following the Readme's own "Download a release binary" flow ends up with an incomplete install.
Fix: package each Burrito target into a per-platform tarball (`lc_macos_aarch64.tar.gz`, etc.) containing the binary (renamed to `lc`/`lc.exe`) plus all 5 wrapper scripts, replacing the loose binary uploads. Update the Readme's download instructions to match.
A bare `lc_macos_aarch64` download from the Releases page gets you `lc` and nothing else - no `lcreate`/`lcls`/`lclose`/`lcomment`/`lproj`. Only `install.sh` and the container image ever pulled the wrapper scripts, and both do it straight from a repo checkout, never from a release asset. Anyone following the Readme's own "Download a release binary" flow ends up with an incomplete install.
Fix: package each Burrito target into a per-platform tarball (`lc_macos_aarch64.tar.gz`, etc.) containing the binary (renamed to `lc`/`lc.exe`) plus all 5 wrapper scripts, replacing the loose binary uploads. Update the Readme's download instructions to match.