Max age at which flushOutbox will still auto-replay an AMBIGUOUS queued send
(one that may already have run server-side — see QueuedSend.unsent). Kept
comfortably BELOW the server's completed-turn dedup window
(RECENT_TURN_TTL_MS, 60min) so any ambiguous item replayed within this
bound is still deduped and cannot double-run; older ambiguous items are
dropped (a lost uncertain message is the lesser evil vs a double bill /
duplicate side effect). Provably-unsent items ignore this age bound — they
never ran, so replaying one is always safe — and are instead bounded by
OUTBOX_MAX_REPLAY_ATTEMPTS below.
Max age at which flushOutbox will still auto-replay an AMBIGUOUS queued send (one that may already have run server-side — see
QueuedSend.unsent). Kept comfortably BELOW the server's completed-turn dedup window (RECENT_TURN_TTL_MS, 60min) so any ambiguous item replayed within this bound is still deduped and cannot double-run; older ambiguous items are dropped (a lost uncertain message is the lesser evil vs a double bill / duplicate side effect). Provably-unsent items ignore this age bound — they never ran, so replaying one is always safe — and are instead bounded byOUTBOX_MAX_REPLAY_ATTEMPTSbelow.