Skip to content

Correct README, npm README and install.sh where they describe a CLI that does not exist - #12

Merged
LopezAdan merged 1 commit into
mainfrom
docs-truth
Aug 31, 2026
Merged

LopezAdan merged 1 commit into
mainfrom
docs-truth

Conversation

@LopezAdan

@LopezAdan LopezAdan commented Aug 31, 2026 •

Copy link
Copy Markdown
Collaborator

A truth pass over the repo-local documentation in this snapshot. Nothing in the synced Rust source changed: reachpad/ and crates/ at 0.4.5 are already clean of the memory claims (upstream cli.rs says "Save disk, then stop the meter", and attach is a visible verb now), so every fix here is in a file the release sync preserves rather than overwrites.

Memory resume

ADR-0104 (accepted 2026-08-20) removed VM memory snapshotting entirely. A pause saves the disk, every start is a cold boot, files survive and running processes do not. The README opened by promising the opposite. npm/cli/README.md's pause line loses "and memory" for the same reason. (npm/README.md turned out to make no memory claim; checked, unchanged.)

Commands that do not work

  • "Get started" taught the v0.1.0 grammar. reachpad ws list and reachpad ws create --name scratch are hide = true in the shipped binary and are in no generated shell completion, so a reader who followed the README and then ran reachpad --help saw an unrelated command tree. Replaced with the current verbs.
  • npx @reachpad/cli run scratch -- cargo test addressed a workspace by its label. There is no name resolution in the CLI, so this fails with "There is no workspace scratch on this account". The example now captures the id.
  • The provenance section named a third crate, runtime. The snapshot ships proto and authz only; v1 dropped runtime from the CLI's dependencies and the assemble script deliberately does not copy it.

Intel Mac install

install.sh had no Darwin/x86_64 case, so curl -fsSL https://reachpad.dev/install | sh on an Intel Mac hit "reachpad: no prebuilt binary for Darwin/x86_64", while README.md claimed the platform and npm shipped @reachpad/cli-darwin-x64 for it.

Verified before choosing the fix: release.yml builds x86_64-apple-darwin in its matrix, and cli-v0.4.5 publishes reachpad-x86_64-apple-darwin.tar.gz, whose hash is in that release's SHA256SUMS (the file the installer verifies against before anything executes). The artifact exists, so the case is added rather than the claim removed. After the change every platform the table maps resolves to an asset the release publishes, and all four published assets are reachable from some case.

sh -n install.sh passes; the platform table was exercised for all six plausible uname -s/uname -m pairs against the live SHA256SUMS.

ADR-0104 removed VM memory snapshots on 2026-08-20: a pause saves the disk
only and every start is a cold boot, so "resumes mid-session" describes a
mechanism that is gone. Say what is true and still the reason to use this:
the disk survives, a paused workspace costs nothing and picks up from its
last save.

Three more things these files claimed that the shipped 0.4.5 binary does not
do. "Get started" taught the retired v0.1.0 grammar (`ws list`, `ws create
--name`), all of it hidden in the binary and absent from every generated
completion, so a reader who followed it and then ran `--help` saw a different
CLI. `npx @reachpad/cli run scratch -- cargo test` addressed a workspace by
its label, and there is no name resolution in the CLI, so it fails with "There
is no workspace scratch on this account". And the source description named a
`runtime` crate; the snapshot has carried only `proto` and `authz` since v1
dropped runtime from the CLI's dependencies.

install.sh had no Darwin/x86_64 case, so the advertised one-liner failed on an
Intel Mac with "no prebuilt binary" while the release has shipped
reachpad-x86_64-apple-darwin.tar.gz all along, listed in the SHA256SUMS the
installer verifies. Add the case: every platform the table maps now resolves
to an asset the release publishes, and every published asset is reachable.
@LopezAdan
LopezAdan merged commit d757b71 into main Aug 31, 2026
2 checks passed
@LopezAdan
LopezAdan deleted the docs-truth branch August 31, 2026 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant