Rejection reasons emailed to submitter with resubmission instructions

A rejected submission that generates no notification leaves the submitter with no recourse: they do not know the listing was rejected, why it failed, or how to fix it. This silently degrades the directory's submission funnel — legitimate businesses give up and post elsewhere. It also creates GDPR Art. 17 exposure if a user later requests deletion of data that was never communicated to them as rejected. The submitter's time and data were consumed with zero return.

Trigger a rejection email with reason and next steps as part of the moderation action. Tie it to the same API route that logs the action:

// app/api/admin/listings/[id]/moderate/route.ts
if (action === 'reject') {
  await sendEmail({
    to: listing.contact_email,
    subject: `Your listing "${listing.title}" was not approved`,
    html: `
      <p><strong>Reason:</strong> ${reason}</p>
      <p>To resubmit with corrections, visit:
         <a href="${BASE_URL}/listings/resubmit?id=${listing.id}">Resubmit listing</a>.
      </p>
      <p>Questions? Reply to this email or contact support@yourdomain.com.</p>
    `
  })
}

Require reason to be non-empty when action is reject — enforce this at the API route level so moderators cannot submit a rejection without providing text.