From fa928a6226f2b00301c41c92746d7ad884f338f3 Mon Sep 17 00:00:00 2001 From: Alan Silva Date: Fri, 6 Nov 2026 15:12:29 +0000 Subject: [PATCH] Record richer background task client delivery and backend staging --- app/notes/background-task-list-metadata.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/app/notes/background-task-list-metadata.md b/app/notes/background-task-list-metadata.md index ef4c790a..323137d7 100644 --- a/app/notes/background-task-list-metadata.md +++ b/app/notes/background-task-list-metadata.md @@ -11,3 +11,11 @@ Focused watchdog checks: 36 existing shell/domain/background-controller/modal te 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.