Freegle / Iznik / 24117

72%

Build Type

push

circleci

Committed by invalid-email-address

Commit Message

fix(rippling-stats): anchor KPIs on appearance date, time-bound is_rippled, add 90d filter

The sysadmin rippling KPIs (reply-rate, mean-replies, taken-rate) keyed on
messages.arrival — the ORIGINAL first-ever post date, which auto-repost never
updates (only messages_groups.arrival does, and rippling acts on that appearance).
So a post originally from early June, reposted and rippled after go-live (06-22),
was plotted on its stale early-June arrival day and flagged rippled-out — showing
phantom "rippled-out" data on days before rippling was even live (Discourse #9808).

Re-anchor those three KPIs on the origin group's messages_groups.arrival (the
appearance date the reach engine itself gates on, matching RippleTuneService and
the routing simulator). Also tighten is_rippled to be time-aware — a post counts
as rippled only if a rippled_in copy appeared within 36h of the appearance (or,
for the reply-distance chart which is keyed on reply date, by the reply time) —
so a pre-ripple reply/post isn't slotted into the ripple cohort. reply-source is
membership-based and unaffected. No arg changes; SQL text only.

Also add a "Last 90 days" option to the shared ModEmailDateFilter period dropdown.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014aXkxBPEiPSJBaRMjz7opk

Coverage Stats

11885 of 15794 branches covered (75.25%)

Branch coverage included in aggregate %.

27 of 27 new or added lines in 2 files covered. (100.0%)

7 existing lines in 2 files now uncovered.

128119 of 179745 relevant lines covered (71.28%)

36.97 hits per line