ci(play): production track input + launch kit + F-Droid metadata fix (#19)

* ci(play): add track/status inputs to publish workflow

Lets the Play publish run target a public track (production/beta) and
choose draft vs completed, instead of being hard-wired to internal.
Defaults stay internal/completed so tag-push and release triggers are
unchanged. Enables promoting the app to a publicly-downloadable track —
the prerequisite for any real download growth.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* docs(play): record user authorization for production go-live

* docs(fdroid): correct metadata to cc.agentlabs.opencode + agentlabs.cc, flag post-rename tag gate

The fdroiddata submission still referenced the old package ai.opencode.mobile
and v0.3.1. Update package id, website, and document the real blocker: F-Droid
mainline needs a release tag built AFTER the package rename (v0.4.1 APK is the
old id) plus Play production live and a reproducible build. Signing fingerprint
is unchanged across the rename.

* docs(launch): ready-to-fire distribution kit (Show HN, Reddit, PH, X, dev.to)

Copy-paste launch posts + ordered fire checklist so distribution starts the
moment the public listing is live. Store URLs left as {{PLAY_URL}}/{{FDROID_URL}}
placeholders; web hub agentlabs.cc/opencode is live now.

---------

Co-authored-by: engineer <engineer@opencode.ai>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

distribution/fdroid-submission/metadata.yml

@@ -1,17 +1,18 @@
-# F-Droid metadata for ai.opencode.mobile
-# Target file path in fdroiddata: metadata/ai.opencode.mobile.yml
+# F-Droid metadata for cc.agentlabs.opencode
+# Target file path in fdroiddata: metadata/cc.agentlabs.opencode.yml
 #
-# BEFORE FILING THE MR:
-#   1. Replace <SIGNING_KEY_SHA256_FINGERPRINT> with the actual colon-separated hex fingerprint
-#      (found in distribution/SIGNING-KEY-FINGERPRINTS.md)
-#   2. Replace <FIRST_GITHUB_RELEASE_TAG> with the first tag that has a signed APK attached
-#      (e.g. v0.2.4)
-#   3. Verify the build steps produce a matching APK against AllowedAPKSigningKeys
+# BLOCKER (do NOT file the fdroiddata MR until all true):
+#   1. A release tag built AFTER the ai.opencode.mobile -> cc.agentlabs.opencode
+#      rename exists, with a cc.agentlabs.opencode APK attached, signed by the
+#      release key. v0.4.1 and earlier APKs are the OLD package id and cannot be
+#      used. Cut a new tag (e.g. v0.4.2+) post-rename, then set the Builds entry
+#      below (versionName / versionCode / commit) to that tag.
+#   2. First Google Play production release is live (required by F-Droid policy).
+#   3. Reproducible build verified locally (see REPRODUCIBLE-BUILD-NOTES.md). Expo
+#      RN builds are not reproducible by default; expect reviewer back-and-forth.
 #
-# Do NOT file this MR until:
-#   - First Google Play release is live (establishes signing key in production use)
-#   - Sentry opt-in gate is merged to main (anti-feature Tracking avoided)
-#   - You have the exact colon-separated SHA-256 key fingerprint confirmed
+# Signing key SHA-256 (AllowedAPKSigningKeys, lowercase no colons) is confirmed in
+# distribution/SIGNING-KEY-FINGERPRINTS.md and is unchanged across the rename.
 
 Categories:
   - Development