Streamline GitHub presentation and releases - #29

Summary

• redesign the repository README as a clear application landing page with status badges and a direct APK download path
• make all public project documentation and historical release notes English-only while retaining Russian runtime support
• add direct install links and file guidance to release notes
• reduce future GitHub Releases from 15 loose assets to the production APK, its checksum, and one verification bundle
• preserve exact source, SBOM, vulnerability, license, signer, digest, and immutable-release verification inside the bundle

Verification

• python -m unittest discover -s scripts/tests -p 'test_*.py' (32/32)
• python scripts/security_source_scan.py .
• python scripts/kotlin_style_check.py .
• workflow YAML parsing
• Bash and PowerShell release-script syntax checks
• :app:lintRelease :crypto-core:lintRelease :pairing:lintRelease :secure-storage:lintRelease
• :app:testDebugUnitTest :crypto-core:testDebugUnitTest :pairing:testDebugUnitTest :secure-storage:testDebugUnitTest
• public-prose Cyrillic scan

Release Asset Compatibility

Published releases remain immutable and keep their original evidence assets.
Their live notes now point users directly to the installable APK. The next
release produced from this branch will publish exactly three assets; the
published-release workflow safely extracts and verifies the bundled evidence.