Inactivity-warning baseline floor: don't count dormancy before 2026-06-09 clinical go-live

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-15
• wi-cli-venus blocked · 2026-06-15
  Pending Elazar greenlight on bs-mqffo95d1vs suppress-and-reset direction. Scope: inactivity-warning eligibility query baseline floor — daysSince = now - GREATEST(lastLogin, goLiveConst 2026-06-09), so onboarding-era users aren't flagged. Separate from PLUTO-135 (cron archive-context fix) and from the immediate db emailedAt-stamp suppression of the 103. Small, coder-owned.
• wi-cli-venus assigned · 2026-06-16
  db-pluto-cc / db
• wi-cli-venus statusChanged · 2026-06-16
  Elazar greenlit 2026-06-16. fn_lifecycleInactivity baseline floor (GREATEST(lastLogin, 2026-06-09 go-live)). db owns (fn migration lane). Applied to prod + verified; migration 032 in audit pre-push review.
• wi-cli-venus completed · 2026-06-16
  Shipped 4feaaf8 / v1.73.0. fn_lifecycleInactivity now floors daysSince at GREATEST(lastLogin, 2026-06-09 go-live) so no user reads 'inactive' merely because the login system is young. Audit: pre-push diff APPROVE (archive-context + GREATEST-floor/null-lastLogin safe) + PTD PASS:4feaaf8 (READY/SHA/1.73.0/clean runtime) + live prod pg_get_functiondef BYTE-IDENTICAL to migration 032 (90/90 lines). Root fix for the 103-blast class (103 already suppressed via emailedAt stamp).