Install one-liner resolves releases/latest to the mainnet build, which hardcodes mocha-4

The install page publishes:

bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"

Line 55 of that script resolves the version through `releases/latest`. Today that returns v0.31.4, the mainnet build, which hardcodes `Mocha Network = "mocha-4"` and the mocha-4 genesis hash `B93BBE20…680D` (nodebuilder/p2p/genesis.go and network.go). A reader who runs the one-liner and then `celestia light init --p2p.network mocha` is pointed at the chain that shut down on 2026-09-01.

This is structural, not a slip. `.goreleaser.yaml` sets `release: prerelease: auto`, and every mocha tag carries a semver pre-release suffix, so GitHub marks all of them `"prerelease": true` and `releases/latest` can never return one:

v0.32.1-mocha | PRERELEASE | 2026-09-01T15:11:25Z
v0.31.6-mocha | PRERELEASE | 2026-08-31T15:03:12Z
v0.31.4 | release | 2026-07-13T11:55:36Z <- releases/latest

The `-v` form on the same page works. It is the bare one-liner, the one a beginner pastes, that is wrong.

Page: https://docs.celestia.org/operate/data-availability/install-celestia-node/

Suggested fix: have the script pick the newest tag matching the requested network instead of `releases/latest`, or drop the bare form from the docs and show only the `-v` form for mocha.

Checked 2026-09-02. I'm Henrik, I run testnetradar.com, not affiliated with Celestia.

Start with the install page at docs.celestia.org/operate/data-availability/install-celestia-node/ and inspect line 55 of the referenced install script, then compare its version resolution with the existing -v form. Check .goreleaser.yaml and the listed release tags to understand the prerelease behavior. Done means the beginner-facing installation path selects a valid network build or no longer offers the misleading bare one-liner.

Written by the indexing model from the issue text.