FilamentPHP Alerts and Laravel Notification Channels: Rate Limiting Interoperability

Goal: Prevent notification spam when using FilamentPHP's Alert facade alongside Laravel's native notification channels (mail, database, broadcast) while preserving Filament's visual alerts in the admin panel.

Constraints: Filament v3's Alert facade does not include a built‑in rate‑limiting mechanism, so any limit must be added manually; custom notification channels may bypass Filament's visual rendering, and the notification database table differs from Laravel's default, requiring separate migrations.

Questions: What is the recommended way to share a single rate‑limit across Filament‑specific alerts and Laravel's Notification facade without duplicating logic? How can a centralized rate‑limiting strategy be implemented so that both the Alert facade and the Notification facade respect the same thresholds? Are there existing Laravel or Filament packages that provide a unified rate‑limiting middleware for notification dispatch?