fix(call-to-play): resync after live delivery failure

A failed fire-and-forget event left one peer's active call state divergent until
some later discovery or reconnect happened. During a LAN party that could leave
different players looking at different rosters or chat.

Fall back to the existing bidirectional handshake whenever a live Call to Play
send fails. Its active-history exchange heals both sides immediately when the
failure was transient. Document the related wall-clock synchronization
assumption for deadline and countdown presentation.

Test Plan:
- `just fmt` -- passed
- `just clippy` -- passed
- `just test` -- passed, 147 peer tests
- `just peer-cli-tests S48` -- passed
- `git diff --cached --check` -- passed

crates/lanspread-peer/ARCHITECTURE.md

@@ -63,6 +63,11 @@ local action is applied to that history, sent to the UI, and broadcast to every
 currently known peer. An incoming live event is applied once and sent to the UI
 without being rebroadcast, which prevents forwarding loops.
 
+If a live Call to Play delivery fails, the sender immediately falls back to a
+normal `Hello` / `HelloAck` exchange with that peer. The handshake carries the
+full active history in both directions, so a transient request failure heals
+without waiting for mDNS rediscovery or a later reconnect.
+
 Actors are keyed by the peer's stable ID and carry a separate display name. The
 origin peer overwrites the actor ID on local actions, and live-event envelopes
 must match the known sending peer. This prevents duplicate default usernames
@@ -74,6 +79,10 @@ uses the project's trusted-LAN identity model.
 join after a call was created reconstruct the same nominations, responses,
 RSVPs, chat, and terminal actions. The launcher reducer sorts the event stream
 deterministically and derives deadlines and check-in phases from timestamps.
+Those phases compare creator-supplied wall-clock timestamps with each viewer's
+local wall clock, so LAN machines are assumed to be synchronized closely enough
+for human-scale minute countdowns; clock skew shifts the displayed boundary by
+the same amount.
 There is deliberately no compatibility path for older protocol versions.
 
 ### 4) Shutdown