Record APK57 acceptance and combined UI qualification with rollback

2026-10-07 18:37:04 -04:00
parent 7383d47bad
commit b15f0dc9ea
4 changed files with 101 additions and 8 deletions
@@ -291,7 +291,7 @@ No percentage is inferred from test counts.
 | 17 HTTPS apps | In progress | Exact hostname/trust and companion acceptance |
 | 18 Firewall/tunnel | In progress | Read-only UI done; settings persistence/reboot/rollback qualification |
 | 19 Media guide/Cloud PiP | Nearly finished | PiP operator-accepted; finish reusable contract and remaining edge cases |
-| 20 Native background media | In progress — physical test failed | APK56 stops about five seconds after locking/switching apps; no playback notification. USB unavailable; investigate native bridge/service and retained page. |
+| 20 Native background media | In progress | Operator confirms APK57 background playback works; notification artwork missing. Full controls/queue/recovery matrix remains. |
 | 21 Public files/folders | Queued, before22 | Shared pricing interface with blue tints, unrelated-node discovery and tiny marker |
 | 22 Mesh file sharing | Queued, final task | Node/computer choice, tree/search picker, retained multi-selection, delivery design and usual paid-file flow |

@@ -486,3 +486,47 @@ Monitoring gate or deferred connection UX/removal work.
 - Wrong-window PWA request was inspection only and was withdrawn; no PWA change.
 - Heavy builds are serialized around the constrained host; no live wallet/app
  shutdown was used to free resources. No OTA/ISO/catalog publication occurred.
+
+
+## Latest resumed checkpoint — APK57 and combined qualification
+
+- Operator reports APK0.5.37 background playback now works; notification exists
+  but song artwork is missing. Do not keep asking for the failed-flow diagnostic
+  report or USB. Audio agent is correcting the admitted-app-origin artwork path;
+  earlier physical failure remains historical, with no definitive root cause.
+- Diagnostic APK source committed7383d47b. Download:
+  http://192.168.63.240/packages/archipelago-companion-0.5.37.apk
+  SHA2569b63bd928ab396278791ab3b514dbb53daaf4b7de9311e8e4f505acc02594a2c.
+  33 Android tests, canonical clean packaging and existing signer passed.
+- Combined UI:1,448 tests/176 files pass; production build and390/1440 Chromium
+  Fleet outage/recovery fixture pass. Frozen701-input artifact/evidence resides
+  in `~/.local/state/archipelago/release-qualification/combined-ui-20261007/`.
+  Source subsequently reopened for artwork changes; they are not in that artifact.
+- IndeeHub VM caught real manager-startup replacement of saved containers in
+  generic environment-drift repair. Early saved-recipe guards and outer sweep
+  exclusions are under combined isolated backend qualification. The seven-service
+  fixture was restored/rebaselined with failed evidence retained; this is not
+  rollback acceptance. Normal saved-unit Start/Stop/Restart also needs correction
+  before activation. Lifecycle patch prepared separately during source freeze.
+- Paid-file agent owns the one active Rust compile; it is progressing but page-I/O
+  bound. IndeeHub owns next source/build slot. No live wallet/app teardown is used
+  to free memory. Current guard tests do not qualify the pending lifecycle patch.
+- Public sharing read-only assessment checkpoint is `/tmp/archy-public-sharing-plan.md`.
+  Implementation remains queued. Public paid delivery still needs authenticated
+  identity/transport independent of federation; do not bypass payment journals.
+- No new OTA/ISO/catalog publication. Yaya UI/backend/IndeeHub remain unchanged
+  during this checkpoint. Dev-only combined UI deployment is being qualified.
+
+
+Dev combined UI attempt rolled back automatically when independent botfights
+replacement changed the post-deployment inventory. HTTP verified the old index
+hash matches the preflight baseline. The new artifact remains qualified but is
+not deployed. Existing health-monitor restarts were confirmed read-only; retain
+this new qualification issue rather than weakening the preservation gate.
+
+Five completed historical UI release archives were moved from RAM-backed `/tmp`
+to durable `release-qualification/retained-tmp-archives`, with exact SHA256 checks
+and original paths retained as symlinks. This released496,544,104 tmpfs bytes;
+no build inputs, running services or wallet files changed. Indee's owned VM is
+being shut down at its transaction-idle boundary to relieve compilation pressure;
+its disk/evidence are retained for a dedicated4GB qualification window later.
@@ -181,7 +181,16 @@ bearer token or second player crosses the channel. The entire dashboard must
 never be used as the PiP surface. This is currently a Cloud-host contract, not
 permission for arbitrary embedded apps to call native PiP directly.

-## Companion native audio: build56 candidate
+## Companion native audio: build57 background playback operator-confirmed
+
+On 7 October APK0.5.36 failed after locking or switching apps, without a native
+notification. Restarting did not resolve it. Build57 added local diagnostics;
+the operator subsequently reports that background playback now works and the
+notification is present, but song artwork is missing. This accepts the reported
+background flow only; the complete controls, queue and recovery matrix below
+remains open. No definitive cause of the earlier failure is established. USB
+access is unavailable. Artwork handling is under investigation/correction.
+

 Apps continue using the existing version1 app audio protocol above. They do not
 need a second Android stream or a separate queue implementation. The dashboard
@@ -44,6 +44,26 @@ result: `/tmp/archy-fleet-recovery-browser.log`. The owned server was stopped.
 This is local component/composable evidence, not a live-node outage test.
 No node service, peer relationship, wallet or payment was changed.

+Combined frontend regression suite subsequently passed **1,448 tests in 176 files**,
+zero failures, using one worker. Log:`/tmp/archy-combined-ui-20261007-full.log`.
+Input hashes:`/tmp/archy-combined-ui-20261007-inputs.json`.
+
+Production build passed from a separate frozen copy of all 701 qualified inputs;
+all hashes were verified again after build. Real Chromium loaded this production
+dist at 390px and1440px, with synthetic Fleet outage/recovery replies: retained
+reports, keyboard Retry, genuine zero, layout and error checks passed. Payment
+and signing were blocked. This is artifact qualification, not a real outage.
+
+Durable artifact and evidence:
+`~/.local/state/archipelago/release-qualification/combined-ui-20261007/`.
+Archive SHA256:`16523c80ecebbb4ba1f6d289ead81ab86d59daf67093ce1d8d68d5bce3ffaae5`.
+Index SHA256:`65e5a09eb736f73650ef5ac52bdebf66d1c877e69511edd7bd3095847f6734de`.
+
+The initial dev deployment preservation gate refused before any writes because
+three container start times changed independently after preflight. Failed log
+retained at `/tmp/archy-combined-ui-dev-deploy.log`; actual deployed-node
+acceptance remains separate until the retry and browser checks pass.
+
 ## Remaining acceptance matrix

 | Area | Established evidence | Remaining |
@@ -59,3 +79,22 @@ No node service, peer relationship, wallet or payment was changed.

 No current-node restart or deliberate network outage was performed. Live fault
 qualification must preserve wallets, installed applications and operator intent.
+
+
+## Dev deployment attempt and verified rollback
+
+The immediate retry passed preflight but failed the final container-preservation
+check because `botfights` was independently replaced during the deployment. The
+helper automatically restored the prior UI. A subsequent HTTP fetch verified
+index SHA256 `4d9424a4ad7548221a07e2c4f14019029ac5fc4e3f1d27ff5eca72b5ff0f6a56`,
+matching the preflight baseline. Do not claim the new UI is deployed.
+
+Read-only systemd and management journal checks show pre-existing health-monitor
+restarts of datum, gashboard and angor-relay, and later botfights recovery from a
+stuck stopping state. These checks explain the inventory change; they do not
+establish why the health checks failed. No live app was stopped by this UI task.
+Keep the preservation gate, leave the prior UI in place, and retry only after
+qualification conditions are stable. Yaya was not changed.
+
+Logs: `/tmp/archy-combined-ui-dev-deploy-retry.log` and the private preflight
+receipt `/tmp/archy-combined-ui-dev-preflight-retry.json`.
@@ -589,12 +589,13 @@ WebViewFullscreen handles fullscreen; this is not evidence of native PiP support

 ## 20. Companion background media for V4V and other apps

-**In progress — physical test failed (2026-10-07):** APK0.5.36 plays while
-open, but the operator reports stopping about five seconds after locking or
-switching apps, with no playback notification. Native background acceptance
-remains failed despite automated passes. USB access is unavailable. Investigate
-bridge/service startup and rule out a retained pre-deployment dashboard page;
-no root cause or replacement fix has been verified.
+**In progress — background playback operator-confirmed on APK0.5.37 (2026-10-07):**
+The earlier APK0.5.36 failed after locking/switching apps. After installing0.5.37,
+the operator reports playback now works and the notification is present; song
+artwork is missing. Record this as acceptance of the reported background flow,
+not proof of the complete controls/queue/reconnect matrix or a confirmed root
+cause. Artwork correction and remaining lifecycle checks are ongoing. USB access
+is unavailable.

 Later media-platform task requested by the operator. When a user closes an
 embedded V4V demo or another authorized media app on the companion, playback