chore(release): GitHub Release ct-cli.tgz asset is pinned at 0.1.0 while GitHub Packages carries the real version #84

Surfaced by the #24 GitHub Packages review (PR #83).

The build job packs release/ct-cli.tgz via npm pack before semantic-release runs, so it always carries the placeholder package.json version 0.1.0. Now that @semantic-release/npm publishes the real computed version (e.g. 1.2.2) to GitHub Packages, the two npm-install paths diverge:

• GitHub Packages: @eqrm/ct-cli@<real version> ✅
• GitHub Release ct-cli.tgz (per INSTALL.md): @eqrm/ct-cli@0.1.0 ❌ (stale; code is current, only the version metadata is wrong — pre-existing, made visible by ci(release): publish @eqrm/ct-cli to GitHub Packages — no-PAT cross-repo consumption (#24) #83)

Options:

1. @semantic-release/npm tarballDir (packs after the version bump) attached to the Release — but the version-stamped filename breaks the stable latest/download/ct-cli.tgz URL.
2. Drop the tarball-install path from INSTALL.md, point npm installs at GitHub Packages (now canonical), keep only the standalone binaries on the Release.

Low priority — does not affect the ct-structure consumer (it uses the Packages path). Binaries may also report 0.1.0 if they read package.json version.