A successfully filed access request notifies nobody: COORDINATION_GROUP is null, so the success-path promise has no transport

MEASURED by coder-terra-cc 2026-08-16 while scoping TERRA-41: src/lib/email/recipients.ts:66 holds 'const COORDINATION_GROUP: string | null = null', so resolveCoordinationRecipients returns sourceUndecided UNCONDITIONALLY and no mail is ever sent - including on the SUCCESS path. A user who successfully files an access request is told 'la coordinacion la va a responder' and nobody is notified. The supportTickets row is the entire channel, and whether anyone reads it is a separate unmeasured question. WHY ITS OWN ROW AND NOT PART OF TERRA-41: coder-terra-cc's call and I agree with the reason. TERRA-41 is about a FAILURE-path toast that does not tell the user their request was not filed. This is a SUCCESS-path promise with no transport behind it. Folding them means one closes and the other is quietly still open, which is the shape terra keeps rediscovering. Two defects, two rows. BLOCKED, and on a question already open rather than a new one: terra cannot pick a recipient because 'who is la coordinacion' has been on Elazar since the TERRA-13 mail work. Nothing here is buildable until that answers - this row exists so the consequence is visible and filed rather than living as a comment acknowledging its own gap. DO NOT FIX BY SOFTENING THE COPY ALONE. Changing the success message to stop promising a response would make the app honest and would ALSO silently retire a commitment to the user that nobody decided to drop. The promise or the transport is a product decision, not a wording cleanup.