docs: retain deployed artwork and corrected VM startup evidence

This commit is contained in:
archipelago
2026-10-07 20:24:41 -04:00
parent 3dacf217a0
commit d62769067d
2 changed files with 27 additions and 4 deletions
+5 -4
View File
@@ -12,8 +12,8 @@ the delivered Cloud PiP flow on2026-10-07. Audio and video use separate channels
Native background audio is operator-confirmed on companion 0.5.37/build57 for
the reported background playback and notification flow. The full physical
controls, queue, task-removal and recovery matrix remains open. Notification
artwork has a qualified dashboard correction awaiting guarded deployment and
physical confirmation; it does not require another APK. Browser and Robolectric
artwork has a qualified dashboard correction deployed on dev and Yaya; physical
confirmation remains open. It does not require another APK. Browser and Robolectric
results do not establish phone acceptance.
## Declare the audio integration
@@ -193,8 +193,9 @@ 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. The artwork origin correction passes 26 focused dashboard
tests, production browser checks at 390/1440px and two native JPEG tests on API
28/35. Guarded dashboard deployment and physical artwork confirmation remain
pending; these checks do not prove the cover from a particular live track.
28/35. Guarded dashboard deployment and deployed browser checks passed on dev
and Yaya (receipt d23da226). Physical artwork confirmation remains pending;
these checks do not prove the cover from a particular live track.
Apps continue using the existing version1 app audio protocol above. They do not