Record timestamp web and Android release verification

This commit is contained in:
2026-11-05 22:01:29 +00:00
parent 9180e84109
commit 3c4a7ec710
+2
View File
@@ -9,3 +9,5 @@ Manager recovered the incomplete Mobile v15 run 254 directly after detecting an
Checks: bounded analysis clean; 586 transcript/conversation tests passed through the memory watchdog (peak 1955 MB, 43s). 63 domain tests also passed (peak 954 MB, 4s). After strengthening local-format assertions, 25 focused message/selection tests passed (peak 1028 MB, 5s). Tests cover actual protocol values, invalid/missing values, folded replies and streaming, local formatting, Cupertino 2x text, copy buttons and forward/backward selection exclusion.
Real Chrome full-app fixture screenshots inspected: `/private/tmp/timestamps-wide-final/01-timestamp.png` (1100x1000 light), `/private/tmp/timestamps-narrow-final/01-timestamp.png` (560x1000 dark), and `/private/tmp/timestamps-cupertino-final/01-timestamp.png` (560x1000 Cupertino light). Fixture uses opt-in `timestamps=1`; no production sessions touched. Capture tools exited normally. No physical device or Safari verification.
Published web and Android from source commit `9180e841`. APK build `29898600`, matching previous release signing certificate. Web JS SHA256 `49681884de1be41e59bc1c47d9f174bfc8f9e5b3a88d7545ee7dc11c5a2b374a`; APK SHA256 `b998322320394e506126dc409192ac51e35d160e2f6d751a1fcc70f44889906f`. Authenticated local HTTP downloads of JS/feed/APK matched; public HTTPS JS/feed verified. Web rollback: `app-web.before-web-update-1793916032086548000`; APK rollback: `app-updates.before-client-update-1793916075676166000`, both under the installation lib directory. No backend restart or device installation.