docs: add prebuilt seid binary install option (node ops + CLI pages)

[monty-sei]

What

Adds the prebuilt release binary as the recommended seid install path on the two install surfaces, presented as tabs alongside the existing build-from-source and Docker options:

• node/index.mdx — the Install Sei step in the node setup flow
• evm/installing-seid-cli.mdx — the CLI installation guide

The instructions cover download, sha256 checksum verification, and install, with callouts for the two caveats: linux/amd64 only, and no hardware Ledger support (both routed to build-from-source/Docker).

Why

sei-chain releases attach a statically linked seid (built and boot-tested by CI via sei-protocol/sei-chain#3749's pipeline), which removes the Go-toolchain requirement for operators. The docs currently only describe building from source.

Notes for reviewers

• Asset filenames omit the leading v of the version tag (sei-chain_6.6.0_linux_x86_64.tar.gz under the v6.6.0 release); the examples handle this with ${VERSION#v} so copy-paste works.
• Merge timing: hold until the first release that actually carries binaries is out (the next sei-chain tag after Fix static seid SIGSEGV (pin pre-gcc-12 libgcc unwinder), add boot smoke gate, build binaries on manual tag pushes sei-chain#3749 reaches the release branch), so the download commands resolve on day one.
• mint broken-links passes.

[cursor]

PR Summary

Low Risk
Documentation-only changes to installation and upgrade instructions; no application or infrastructure code is modified.

Overview
Documents prebuilt GitHub release binaries as the recommended way to install seid, alongside existing build-from-source (and Docker on the node setup page).

evm/installing-seid-cli.mdx — Installation is now tabbed: download with ${VERSION#v} asset naming, sha256 checksum verification, install to /usr/local/bin. Go is called out as build-from-source only; GOPATH troubleshooting and uninstall cover both install paths. Notes cover linux/amd64, no Ledger, and PATH shadowing from old make install copies.

node/index.mdx — The Install Sei step uses the same prebuilt flow (plus RocksDB / Ledger caveats). Go install is scoped to source builds; Docker moves into its own tab; GOPATH guidance sits under the source tab.

node/node-operators.mdx — Update Procedures add a warning about not mixing install methods, and minor/major upgrade steps are split into prebuilt vs source tabs with the same download-and-verify commands.

^{Reviewed by Cursor Bugbot for commit cd76293. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
sei-docs	🟢 Ready	View Preview	Jul 13, 2026, 5:31 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[alexander-sei]

Pushed review follow-ups in 5e77cc2:

Bugbot fix — the verify → extract → install steps are now &&-chained, so tar/install only run if sha256sum -c exits 0. Both failure modes halt the block on Linux/GNU coreutils: a checksum mismatch (FAILED, exit 1), and nothing-verified-at-all — if the release asset 404s or the tarball isn't in the current dir, --ignore-missing reports "no file was verified" and exits non-zero. So even pasting the whole block before a release carries binaries can't install anything.

Coverage gaps — the install pages weren't the only seid install surfaces:

• node/node-operators.mdx "Update Procedures" only documented git checkout + make install. Both minor and major update flows now have a Prebuilt binary tab with the same download/verify/replace sequence, plus a callout to upgrade with the method you originally installed with — make install writes to $(go env GOPATH)/bin while the prebuilt flow writes to /usr/local/bin, and mixing them can leave the service unit running a stale binary (which -a seid shows every copy).
• The prebuilt caveat on the node page now also notes the binaries omit the optional RocksDB state-store backend (make install-rocksdb remains source-only).
• Smaller alignments: Go prerequisite and GOPATH troubleshooting scoped to source builds, "Uninstalling seid" covers both install locations, <version-tag> placeholders and the verify command made consistent across tabs.

Validated with mint broken-links (passes) and a local mint dev render check of all three pages.

The merge hold from the description still applies — v6.5.2 has no binary assets, so this lands with the first release that ships them.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit cd76293. Configure here.}