Development record
2026-10-29 — Carry iss-2610240827243654 (the unreadable install one-liner) past the v0.15.1 anchor for this one cut: its fix documents a release asset that exists only once this release is published, so the install-docs change merges immediately after the tag, after the asset URL is confirmed, and resolves the record then.
decisiondcn-2610290939169539
2026-10-29 — Carry iss-2610240827243654 (the unreadable install one-liner) past the v0.15.1 anchor for this one cut: its fix documents a release asset that exists only once this release is published, so the install-docs change merges immediately after the tag, after the asset URL is confirmed, and resolves the record then.
Frontmatter
| id | dcn-2610290939169539 |
|---|---|
| type | decision |
| date | 2026-10-29 |
.abcd/work/decisions/dcn-2610290939169539-carry-iss-2610240827243654-the.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610240827243654The documented CLI install one-liner (README and docs/how-to/install.md) is far too complicated to be a one-liner: a single sh -c string of roughly 3,000 characters that unsets proxy variables, refuses a symlinked ~/.abcd.noindex, maps uname output to a release asset, downloads it and checksums.txt, verifies the checksum, probes gh attestation verify for four flags, resolves the latest tag and its commit through the GitHub API, verifies build provenance, prints a long fallback warning, installs to ~/.local/bin and writes ~/.abcd.noindex/path-entry. Nobody can read, audit or safely retype it, and a reader cannot tell what they are agreeing to run.