RUST-FEAT-054 - Prioritize nightly eMuleBB Rust public presence #183

Summary

Make eMuleBB Rust nightlies the public front-door download and testing path. Treat Beta 2 as stale, immutable release history rather than a current call to action. State that Beta 3 is expected after a few more weeks of implementation and stabilization.

Product language

• Display name: eMuleBB Rust; retain emulebb-rust for repository and technical identifiers.
• Status: Active beta.
• Exact evidence claim: Repeatedly tested on live eD2K/Kad networks.
• Primary download path: the GitHub Releases page, where users select the newest dated nightly prerelease.
• Beta 2 may remain in release history, compatibility notes, immutable technical records, and nightly version derivation only.
• Beta 3 is expected after a few more weeks of implementation and stabilization.
• eMuleBB Rust and its product/docs surfaces remain English-only.
• Localized home and FAQ pages are frozen to minimal evergreen copy and must not carry version numbers, beta targets, ETAs, or time-sensitive release status.

Scope

• Keep archival Beta 2 fields in the public-presence contract, but stop rendering them on current-facing surfaces.
• Add the approved Beta 3 directional ETA to the public-presence contract.
• Update the generated organization profile, canonical documentation, repository README, and root site to lead with nightlies.
• Remove Beta 2 from current CTAs, navigation, summaries, FAQ answers, SEO metadata, and Rust structured release data.
• Preserve the existing website layout and professional dark theme.
• Add regression validation for current-facing Beta 2 promotion and dynamic release language in localized pages.

Acceptance criteria

• Nightlies are the first and only current Rust download/testing CTA on public-facing surfaces.
• Current-facing copy tells users to choose the newest dated nightly from GitHub Releases.
• Beta 2 is presented only as archival or technical history, never as the current baseline or secondary CTA.
• Current English Rust surfaces include the approved Beta 3 directional ETA.
• The exact live-network testing claim remains on principal Rust surfaces.
• The Rust product page remains English-only and removes Beta 2 softwareVersion and release-note structured data.
• Localized home and FAQ pages contain no semantic versions, Beta 2/Beta 3 targets, or ETA language.
• Existing site layout and professional dark theme remain unchanged.
• Contract, profile, site rendering/static checks, documentation checks, and focused Rust validation pass.
• Changes are delivered through reviewed pull requests and merged to each affected default branch.

Identifier correction

Earlier public-presence commits used RUST-FEAT-052, but that identifier already belongs to issue #146. Issue #148 owns RUST-FEAT-053. Historical commit messages are not rewritten; this follow-up work and its durable tracking use RUST-FEAT-054.

Delivery

• emulebb-tooling PR RUST-BUG-122 - Make completed-download delivery isolated and transactional #125 — 6e855f7n- emulebb-rust PR #185 — c23bb263n- organization profile PR RUST-FEAT-002 - Indexer — autonomous Kad/eD2K observation index #2 — 486b86en- GitHub Pages PR #2 — �93e322n
  All required PR and post-merge workflows passed. The deployed site was verified at the canonical English, Rust, German home, and Japanese FAQ URLs.