1 files changed, 10 insertions, 4 deletions
diff --git a/docs/playlists.md b/docs/playlists.md
index badbc99..d8eda18 100644
--- a/docs/playlists.md
+++ b/docs/playlists.md
@@ -1197,7 +1197,9 @@ reads §15.1 as more than it is.
    framing for a payload of this size, which nothing here exercises.
 2. **Two browsers, one account, one node, converging** — and the same with the
    node stopped between the two edits. The merge is proved; the *plumbing*
-   around it is proved against a stub that always behaves.
+   around it is proved against a stub that always behaves. Confirmed working in
+   the field once (a desktop client and a phone, same account, same node), which
+   is evidence and not a test: nothing re-checks it on the next change.
 3. **A real cross-group playlist playing**, which is where §11.3 and §9.5 meet
    real latency rather than a stub that rejects instantly.
 4. **The 650 ms sign-in budget**, measured. Argon2 is proved to run once; the
@@ -1215,6 +1217,10 @@ reads §15.1 as more than it is.
 - `deleteUserBlob` reclaims a tombstoned body, but **tombstones themselves are
   never collected** (O6). At forty bytes each this is not a real problem yet,
   and a collector needs the per-node acknowledged `rev` that O6 describes.
-- **Nothing calls `syncWith` on the Search page.** It has a transport per group
-  and no single one to ride; the group page's mount is what reconciles today. A
-  reader who only ever uses Search converges only when they open a group.
+- ~~Nothing calls `syncWith` on the Search page.~~ **Closed.** Riding whichever
+  page happened to be open was the bug behind "the playlists are absent on my
+  phone": the Search page has a transport per group and no single one to ride,
+  so a reader who never opened a group never converged. Sync is no longer a
+  page's business — `app.js` owns it, resolving a transport by preferring the
+  open group and otherwise dialing up to three, and reconciling once per
+  sign-in. `playlists.js` pushes itself on every write.