cert-routing-custodians

Notes

• 2026-09-08 Dustin ruling: cert custodians for the unstaffed JES branches — Richmond → Lauren Chenault (Office Manager), Roanoke → Summer Sowash (Production Admin Assistant), West Virginia → Dustin explicitly (no contact named). Wired into config.CERT_ROUTES and CERT_SUCCESSOR_SCHEDULERS (so triage-routed legacy/PPDR certs originating in Richmond/Roanoke follow the same custodians). Side finding: Roanoke and WV routes previously had empty TO lists and resolve_route never fell through to a default, so a cert there would have gone to nobody; a test now forbids empty TO lists on any cert route. Not changed: pier-log SMS table (no phones), escalation routing, needs-digest recipients (Richmond/Roanoke/WV still digest to Dustin).
• 2026-09-08 follow-up (Dustin: “treat them as staffed by the same individuals for now”): Lauren Chenault (Richmond) and Summer Sowash (Roanoke) now also staff every tier of ESCALATION_ROUTING, receive the Mon/Thu needs digest for their branch, and are the pier-log RFI email contacts. West Virginia = Dustin explicitly on escalation, default recipient on digests, no pier-log RFI contact. SMS tables (pier-log 7:15 escalation, 6 PM follow-up, 6:45 request, 6:30 branch schedule snapshot) still fall back to Dustin because no phone numbers are on file for either. Tracker upload rights not granted.