4.2 KiB
Rich background task list
Task rows now use the recorded description as their title (retaining the full command in selected detail). Native Material and Cupertino rows show task type/status and elapsed runtime, a day-first written local start date with 24-hour time, one bounded progress/description preview, and available tool/token counts. Selecting a task exposes the full command and identity, full progress/description, last tool, last update, counters and the existing lazy bounded output page.
Only recorded started_at drives elapsed time. Missing or invalid starts say “Start time unavailable”; an upstream duration_ms is labelled “Reported runtime” and never presented as a clock-derived uptime. Future starts report clock skew instead of a negative runtime. Zero counters remain distinguishable from absent counters.
One timer belongs to the mounted modal panel and captures one clock value per rebuild for all rows/detail. Closing/disposal cancels it. Ticks neither poll the server nor load output. Streaming partial frames and snapshots preserve metadata already learned without retaining tasks the current server snapshot no longer lists.
Focused watchdog checks: 36 existing shell/domain/background-controller/modal tests passed (peak 1296 MB, 12s); 6 new metadata/clock/layout/selection tests passed (peak 794 MB, 4s). Tests cover both native hosts at 390px and 2x text, duration/clock-skew/malformed values, partial metadata, no new requests on timer ticks, timer disposal, and lazy output only when selected. Bounded analysis was clean before the final opt-in fixture polish; final analysis and integration results follow below.
Rendered evidence uses the real full-app scratch fixture with opt-in chats=1&tasks=rich. Inspected wide Material light list/detail at /private/tmp/background-task-ui-wide-final/01-list.png and 02-detail.png, narrow Material dark list/detail at /private/tmp/background-task-ui-narrow-final/01-list.png and 02-detail.png, and Cupertino light list at /private/tmp/background-task-ui-cupertino-final/01-list.png. The native dialogs scroll selected detail and keep output bounded. Capture-owned servers and browsers exited normally. No production chats, devices or services were modified. Metadata availability depends on the backend update and provider support; the frontend never invents missing facts.
Final integration: tool/memwatch/full.sh 'test/features/chat/conversation test/features/chat/domain --no-pub' passed all 522 tests (peak 1966 MB, 44s), log /tmp/memwatch/out.YASMW0. Final bounded analysis of every changed Dart path is clean. Fresh fixture web build (including Wasm dry run) passed. Screenshot list/detail interactions succeeded and all five final PNGs were inspected. No physical-device or Safari acceptance is claimed.
Integrated delivery
Backend commit 6421554b, UI commit 6dfb5d7a, merged at c405cdfe; follow-up 7ce754f6 removes a pre-existing unused timestamp-test import. Full app analysis is clean. All 846 chat tests passed through the watchdog (peak 1738 MB, 86s); full Go build/vet/test passed. Parent inspected representative final wide list, narrow detail and Cupertino list PNGs.
Published web and APK build 29899630. Authenticated HTTP served JS/feed/APK matched built bytes, and public HTTPS JS/feed were verified. JS SHA256 c5867c55373a5c025fcfd5eaf80f22a163506f4f776dc3fea6674ba934838279; APK SHA256 c7d3b340681b1432464011a91af79d564fe499aef88da1d1da16dd51b3bf89c7. APK signing certificate matches the previous release. Rollbacks under installed lib: app-web.before-web-update-1793977894792784000, app-updates.before-client-update-1793977925224782000. No physical device installation/verification.
Backend binaries are staged from clean commit c405cdfe2488ad0ef619790c529add3457d8d209; backend has NOT been restarted. New timing/progress values require that backend delivery; the compatible new client displays unknown values accurately meanwhile. The earlier deferred deployment job expired blocked and is no longer running. Current audit still shows this Codex chat active plus Claude session b73a1bae-991e-44ef-ac05-fe8a30abede5 with two background tasks. No active work was stopped. Deferred desktop files and the user session export remain intact.