9.2 — Notification channels

[tessak22]

Summary

Deliver via SMS (sent.dm) and email (Resend) behind Laravel's notification-channel abstraction, respecting consent, preferences, and staff overrides.

Spec references

• §5.7, §9, §10b (Notification recipients)

Requirements

• Custom sent.dm SMS channel + Resend mail, both behind Laravel notifications (swappable via config).
• Resolve channel per message from consent (consent_sms), channel_prefs, and staff_channel_override.

Acceptance criteria

• SMS (sent.dm) and email (Resend) sit behind Laravel's notification-channel abstraction, swappable via config (§5.7, §7).
• Sending respects per-category consent_sms, channel_prefs, and staff_channel_override (override wins) (§5.7, 3.4).
• Owner receives all client notifications by default; invited members receive nothing until they opt in themselves (§10b, 3.3).
• Vets never receive automated client notifications (§10b).
• Promotional (cat.4) requires explicit opt-in (TCPA-safe) (§5.7).

Config over code

Provider + channels config-driven.

Tests

• Channel resolution: prefs vs staff override.
• SMS suppressed without category consent.
• Member without opt-in receives nothing; vet excluded.

Definition of done

sent.dm + Resend channels; consent/preference/override resolution; recipient rules.