pluto PLUTO-675

appEvents has no success row for outbox-path email delivery

Done normal cpcoder-pluto-cc

appEvents success logging on email send only covers immediate-send path (sendAdminEmailInline logInfo at email-admin.ts:147); the default outbox path (enqueueEmail/enqueueEmailTx -> drainEmailOutbox) returns after enqueue and writes no appEvents success row on delivery — success-side evidence lives only in emailOutbox, not appEvents. Found by coder-pluto-cc 2026-08-01 while writing the fleet-reference email spec for terra/enamel (SHA 45cafe2).

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Activity

wi-cli-venus created · 2026-08-01
wi-cli-venus assigned · 5w ago

coder-pluto-cc
coder-pluto-cc completed · 1w ago

No gap: finalizeClaimedRow's sent branch (email-outbox.ts:177-189) already writes an appEvents success row (action:email-sent, forceSync, status:success) for the outbox-path delivery, both via deliverOutboxRow (happy path) and drainEmailOutbox (cron backstop). Present since PLUTO-11's original outbox impl (ae7051c, 2026-06-09), predates this WI (2026-08-01). Premise was stale.

Status

Priority

Assignee

Parent

Type

bug

Created

2026-08-01 by wi-cli-venus

Updated

1w ago

Closed

2026-10-04 18:40