[Tracking] App distribution — Releases, signing, download page, iOS, policy

[chtnnh]

Summary

Umbrella for getting protestchat into users’ hands without requiring every person to build from source. Docs content and trust copy already live in website/ (#11 / #64). Docs hosting remains #61.

This issue tracks packaging and delivery only.

Already done / elsewhere

Piece	Where
Plain-language guide + “only trust a build you compiled or from a source you trust”	website/ (#64); trust copy on splash + responsibility pages
Docs public URL / Cloudflare Pages	#61 (ops)
Opt-in Android preview APK (SHA-256, provenance, 7-day Actions artifact, non-production signing)	CI via #12 / #37 — workflow_dispatch or v* tag
“Reproducible builds” called out as missing	README “What is not built yet”

Child issues

• [Distribution] Publish Android builds to GitHub Releases on v* tags #80 — GitHub Releases for Android (durable APK + checksums)
• [Distribution] Production Android signing (replace Expo template key) #81 — Production Android signing
• [Distribution] Website download page (link Releases + verify steps) #82 — Website download page (depends on [Docs] Host and publish the user guide (Cloudflare Pages / domain) #61 + Releases)
• [Distribution] Decide and document an iOS distribution path #83 — iOS distribution path
• [Distribution] Reproducible builds #84 — Reproducible builds
• [Distribution] Policy: stores, sideload, and mirrors #85 — Distribution policy (stores / sideload / mirrors)
• [Discussion] Keep INTERNET permission for automatic updates? #86 — Discussion: keep INTERNET for automatic updates vs strip for “no sockets”

Out of scope here

Mesh/crypto readiness (#8, #20, #21), feature work, docs content / trust copy (already shipped in #64).

Done when

Non-technical users can install from a stable, documented channel (at least Android), with signing and checksums explained on the public site once #61 is live.