18 lines
3.2 KiB
Markdown
18 lines
3.2 KiB
Markdown
# Chat message timestamps
|
|
|
|
User messages and folded assistant replies show a small local date and time using recorded epoch-millisecond `created_at` values. Missing, invalid and out-of-range values stay absent. Folded replies use the first valid creation time, not render time. Native localization and secondary theme colors supply the presentation; full dates are exposed through tooltip and accessibility semantics. Material and Cupertino hosts are supported.
|
|
|
|
Timestamp metadata is inside `SelectionContainer.disabled`, so cross-message drag selection and the reply Copy action exclude it. Existing delivery/model/copy controls remain.
|
|
|
|
Manager recovered the incomplete Mobile v15 run 254 directly after detecting an ISO-string assumption that contradicted `protocol.ChatMessage.CreatedAt`. The run was canceled and awaited before editing; its worktree and changes were preserved. No workflow definitions changed.
|
|
|
|
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.
|
|
|
|
Date format follow-up: use day-first written months and 24-hour time (`5 November 2026 · 09:18`) on Material and Cupertino, including tooltip/semantics. Focused 25 tests pass and analysis is clean. Inspected narrow dark Material and light Cupertino screenshots at `/private/tmp/dayfirst-material/01-dates.png` and `/private/tmp/dayfirst-cupertino/01-dates.png`; no overflow.
|
|
|
|
Day-first release published from `5cb2da90`: Android build `29898613`; signing certificate unchanged. Authenticated served JS/feed/APK hashes match the build files. JS SHA256 `0dc30c7b967039378d44a4d9e766e4057f8988a8ee93d37f2cc2204e30a00513`; APK SHA256 `28435d3a00e079045b8e05c564704718a38f627fdb88cbca98fc91cef001964a`. Rollbacks under installed lib: `app-web.before-web-update-1793916900793104000` and `app-updates.before-client-update-1793916900883853000`. No backend restart or device installation.
|