Staff ticket-notification email has no outbox retry (immediate:true bypass)

dispatchTicketEmail (src/lib/support-ticket-notify.ts) posts to /api/internal/send-email, which hardcodes sendEmail({immediate:true}) for every caller by design (route.ts:243, built as a synchronous smoke-test endpoint so its response reflects real SMTP result). immediate:true skips enqueueEmail entirely - sendInline gets only the transport's own ~2x transient retry, no emailOutbox row, no cron drain retry. A single SMTP timeout permanently drops a staff ticket-creation notification with no recovery path; dispatchTicketEmail's own caller does not even check the boolean. Measured 2026-09-22 by support-evolutiva-cc: appEvents f3a840d7, email/send-failed ETIMEDOUT, SOP-MARS-63, no emailOutbox row exists for it, 13 other mails sent fine in the same 2h window, first occurrence in 14 days. Decision (coder-mars-cc): staff ticket-notifications should go through the outbox. The fix cannot simply flip immediate:false globally on /api/internal/send-email - that endpoint is also the documented agent-facing support/KPI send-ops recipe (mars-ops.md), where callers rely on the synchronous sent result reflecting the real SMTP outcome. Needs a scoped opt-in (e.g. a durable/immediate=false param on this one call site, or a distinct enqueue-and-return-202 branch) so other callers keep their current synchronous contract. Touches the email-send path -> pre-implementation audit design-ping required before coding (evolutiva-coder-commons.md Push-to-Done trigger). Not urgent: single transient failure, ticket itself already handled by support-evolutiva-cc.