fix(call-to-play): expire elapsed calls clearly

Deadline completion previously shared the green Ready presentation with a full
roster and remained visible forever. An abandoned call therefore looked ready
to launch and required its creator to return and cancel it.

Give elapsed calls a distinct Time's up state and a five-minute grace period in
which the creator can start or extend them. After that, both the reducer and
peer store remove the call as a unit. Filled calls remain ready until their
deadline, and active calls continue to retain complete history for late joiners.

Test Plan:
- `just fmt` -- passed
- `just clippy` -- passed
- `just test` -- passed, 147 peer tests
- `just frontend-test` -- passed, 22 tests
- `just build` -- passed
- `git diff --cached --check` -- passed

crates/lanspread-peer/ARCHITECTURE.md

@@ -56,7 +56,9 @@ or `Cancel` event replaces that terminal call with one small tombstone; this
 lets a peer that missed the live action heal on its next handshake without
 retaining the inactive call's full history. Active calls are never partially
 trimmed. If genuinely active history reaches the bound, local publishes return
-an error to the caller instead of appearing to succeed. A
+an error to the caller instead of appearing to succeed. A call whose deadline
+elapses remains available for five minutes so the creator can start or extend
+it, then its history is evicted as a unit. A
 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.