fix: recurriing network issue

toju-app/src/app/domains/direct-message/README.md

@@ -1,6 +1,6 @@
 # Direct Message Domain
 
-Direct messages provide local, offline-safe one-to-one messaging over the existing WebRTC data channel.
+Direct messages provide local, offline-safe one-to-one messaging over the existing WebRTC data channel, with a signaling relay fallback when no peer data channel is available but a route to the recipient is known.
 
 ## Structure
 
@@ -16,9 +16,10 @@ direct-message/
 
 1. `DirectMessageService.sendMessage()` stores the message locally with `QUEUED`.
 2. `PeerDeliveryService` tries to send a `direct-message` P2P event to the recipient's current peer id.
-3. If the peer is connected, the sender advances to `SENT`; otherwise the message id remains in `OfflineMessageQueueService`.
-4. The recipient persists the message as `DELIVERED` and sends a `direct-message-status` event back.
-5. Opening the conversation marks incoming messages as `ACKNOWLEDGED` and emits a status event.
+3. If no data channel is connected, `PeerDeliveryService` tries the recipient's known signaling route before leaving the message queued.
+4. If either transport sends, the sender advances to `SENT`; otherwise the message id remains in `OfflineMessageQueueService`.
+5. The recipient persists the message as `DELIVERED` and sends a `direct-message-status` event back.
+6. Opening the conversation marks incoming messages as `ACKNOWLEDGED` and emits a status event.
 
 Status transitions are monotonic, so a stale `SENT` event cannot overwrite `DELIVERED` or `ACKNOWLEDGED`.