peach-browser / f17d073716b4

diag: mesh-propagation round 2 — five tagged lines at every silent rejection path in applyVerifiedPeerManifest (v4.7.7) Live verification failed: after v4.7.4+v4.7.5, Firefox still does not appear in Chrome's paired-devices list after a sync. Manifest exchange is proven to run on every sync (incl. no-change), so the drop is inside applyVerifiedPeerManifest — every rejection path there has been silent since the v4.7.4 diag strip. Prime suspect from reading: deriveManifestMeshRoute returns null when the manifest entry lacks relayUrl (Android omits null fields in its canonical map), and a new device with no route is silently skipped. Five [Peach diag] lines cover: issuer-gate reason, signature rejection on both keys, issuerDeviceId mismatch, verified-manifest contents (device ids + relayUrls — answers whether the phone's manifest contains Firefox at all), and per-entry decision inputs. Also deletes the dead empty if/else block the v4.7.4 strip left behind. Temporary; strip once root cause is confirmed. Gates: tsc RC=0, sync-vault-adapter 31/31, build clean, dist/ at 4.7.7.

dev · 3 weeks ago · 2026-08-01 · 5.7 MB

parent: ec56ceb632a1