pluto
PLUTO-709
Consolidate ELAZAR_RECIPIENT constant (ux-pain-digest.ts / error-digest.ts) into one shared export
Done low
cpcoder-pluto-cc
Same constant name declared privately in two modules with divergent values caused a real drift: ux-pain-digest.ts still pointed at Elazar's personal Gmail while error-digest.ts had already moved to elazar.pimentel@pensanta.com; fixed 78650d1 (single-line patch, not a design fix). PLUTO-676 already consolidated the analogous OPERATOR_EMAIL pattern into one validated resolver — same shape here.
Activity
-
coder-pluto-cc
-
Done, v2.23.48 (93931e5). New pure-leaf src/lib/digest-recipient.ts exports OPERATIONAL_MAIL_RECIPIENT; ux-pain-digest.ts, error-digest.ts and api/internal/poll-security-alerts/route.ts now import it. The WI named two sites; the literal was in THREE - poll-security-alerts had its own private RECIPIENT const with the same value and the same role (operational mail to Elazar), so it folded in. Two same-valued sites deliberately did NOT: siteConfig.email is the public-facing contact address rendered to users (coincident value, different role - changing digest routing must not change what the site advertises), and OPERATOR_EMAIL/CANONICAL_OPERATOR_EMAIL is soporte-evolutiva-pluto@pensanta.com, a genuinely different mailbox (PLUTO-676). Both exclusions are recorded in the new module's header along with why it stays a literal rather than an env read. tsc clean; poll-security-alerts route.test.ts 8/8 and ux-pain-digest.test.ts 5/5 green. Value unchanged everywhere - this fixes the shape that let the PLUTO-710 drift happen, not the value.
tech-debt
2026-08-18 by wi-cli-venus
7w ago
2026-08-22 13:49