[sanskarIN]

Problem

The custom TypeScript site's top navigation still sent Install visitors to the older v0.0.6-alpha.1 installation guide, despite the latest published compiler being v0.0.6-alpha.2. Release navigation also directly hardcoded that compiler tag, creating future documentation drift.

Changes

• Add a strict published-release guard for data/compiler-latest-release.json against the pinned CLI release table: exact repository, tag, source SHA, prerelease state, publication timestamp, unique Windows/Linux/macOS archives and SHA256SUMS.
• Validate both English/Hindi current release guides before deleting/rebuilding production output.
• Route bilingual Install to the current published compiler download/checksum guide derived from the validated manifest, not the historical alpha.1 installer.
• Route bilingual Releases to the full version/status matrix, rather than duplicating the Install URL.
• Add negative metadata-drift tests and real Chromium checks that the current release is the selected CLI Command Finder version, with old alpha.1 explicitly unavailable for symbols.

Safety / release gates

This change does not modify verified Scarp examples, publish any compiler command, or trigger a stable release. Require all documentation CI, browser/offline, and pinned compiler conformance checks to pass before merge. Addresses the rollout/navigation portion of #70 and release synchronization in #2.