docs: explain the P2P diagnostic workflow

Guide users through Diagnostic summary, Diag logging, transfer progress,
symptom checks, and evidence collection from both devices. Link the guide
from the P2P, troubleshooting, reporting, and documentation entry points.
Keep transport compatibility and observation limits explicit.

Validated with the troubleshooting documentation Inspector, 145 local
references, 34 heading anchors, and current English UI labels. Runtime
source and translations are unchanged.
This commit is contained in:
vorotamoroz committed 2026-11-06 15:53:55 +00:00
1 parent eea78e44db
commit 966b6384f4
6 files changed
+137 -4

No files matched your search

+1 -1
View File
@@ -270,7 +270,7 @@ Use Safari on a Mac and follow Apple's [Inspecting iOS and iPadOS](https://devel
## P2P does not connect or transfer changes
Use [Peer-to-Peer Synchronisation Tips](tips/p2p-sync-tips.md). Check signalling discovery separately from the WebRTC data path, and confirm which devices announce and follow changes. P2P is not a repair step for another transport.
Start with [P2P diagnostic observations, logs, and transfer progress](tips/p2p-diagnostics.md). Use [Peer-to-Peer Synchronisation Tips](tips/p2p-sync-tips.md) for network and configuration checks. Check signalling discovery separately from the WebRTC data path, and confirm which devices announce and follow changes. P2P is not a repair step for another transport.
## Obsidian or LiveSync remains suspended