The cross-platform audit of #10416 found different freshness clocks: APNs emits a stale-date relative to delivery time, while Android derives activity expiry from the activity state timestamp. Queue delays and replays can therefore leave the two cards stale at different times.
Decide which parts are shared product policy and which are native presentation constraints. Put the shared deadline calculation in the relay policy and add adapter-level cases for delayed delivery, foreground replay, stale running work, and the 15-minute completed-card window.
Keep this policy decision outside the Android feature PR. A stale marker and card removal are different native behaviors; the follow-up should make that distinction explicit rather than force identical UI.
The cross-platform audit of #10416 found different freshness clocks: APNs emits a stale-date relative to delivery time, while Android derives activity expiry from the activity state timestamp. Queue delays and replays can therefore leave the two cards stale at different times.
Decide which parts are shared product policy and which are native presentation constraints. Put the shared deadline calculation in the relay policy and add adapter-level cases for delayed delivery, foreground replay, stale running work, and the 15-minute completed-card window.
Keep this policy decision outside the Android feature PR. A stale marker and card removal are different native behaviors; the follow-up should make that distinction explicit rather than force identical UI.