docs(waitlist): record v0.4.13 = Play versionCode 149 (production) (#167)

The publish workflow overwrites versionCode with github.run_number + 100, so
the gradle number (40) is not what Play reports. Production dispatch run 49 ->
versionCode 149. Without this row, play-version-share.mjs reports the new
release as an unknown versionCode and the AGE-100 after-number cannot be split
by build.

Co-authored-by: engineer <engineer@macbookpro.lan>
Co-authored-by: Paperclip <noreply@paperclip.ing>

distribution/waitlist-signup-path-coverage.md

@@ -40,7 +40,7 @@ returns 0 results) and the app is not on IzzyOnDroid, so those channels contribu
 
 ## After-number: how it gets attributed (AGE-100)
 
-_Pending — v0.4.13 (the first build users can actually run the retry queue on) ships 2026-08-14._
+_Pending — v0.4.13 (the first build users can actually run the retry queue on) went to the Play **production** track on 2026-08-14 as **versionCode 149** ([run 31786473735](https://github.com/dzianisv/opencode-mobile/actions/runs/31786473735)). Re-read one week out._
 
 Baseline at release time, from the hourly reconciler's last run before the cut
 (`Waitlist Mailto Reconcile`, 2026-08-14 07:59 UTC): `scanned=34 synced=0 skipped=34 failed=0`

scripts/play-version-share.mjs

@@ -86,6 +86,8 @@ const VERSION_NAMES = {
   142: "0.4.10",
   143: "0.4.11",
   146: "0.4.12",
+  // v0.4.13 (retry queue + mailto version stamp) — production dispatch run 49.
+  149: "0.4.13",
 };
 
 const args = process.argv.slice(2);