Notifications & Updates Intelligence

Count sessions, not events

"Conversations" becomes countSessions over today's feed message timestamps (new session after a >30min gap) plus discrete task_sessions — never a raw interactionCount of logged events.

Busyness from edge-countable signals, not chat volume

Mentions handled, digs run, and session counts feed the teaser as labelled facts; calendar meeting-hours is flagged as the strongest signal but deferred — parsing agenda prose is explicitly rejected as fragile.

Device-local push suppression, not global focus-tracking

Each device decides for itself whether to show a push based on its own foreground state (web SW clients.matchAll, Android ProcessLifecycleOwner) — so a focused desktop never silences the phone and vice versa.

Collapsing batch notifications

Batch pushes get a fixed tag/collapse_key so a new "awaiting you" replaces the prior one instead of stacking, and titles lead with the most urgent item/people instead of a bare count.

Resolve is purely subtractive

A manual per-item resolve marks an Updates item strikethrough-and-greyed in place; it never creates a tracked task, keeping Updates a triage surface rather than a to-do list.

Retention tightens and becomes resolve-aware

Resolved items are kept 24h then dropped; unresolved items are now kept only 3 days (a change from the prior indefinite retention) — implemented as a single pruneUpdates predicate in the EOD decay tick.