feat: implement findings notifications escalation #261

ahmido · 2026-04-22T00:52:31Z

ahmido commented

2026-04-22 00:52:31 +00:00

Summary

implement Spec 224 findings notifications and escalation v1 on top of the existing alerts and Filament database notification infrastructure
add finding assignment, reopen, due soon, and overdue event handling with direct recipient routing, dedupe, and optional external alert fan-out
extend alert rule and alert delivery surfaces plus add the Spec 224 planning bundle and candidate-list promotion cleanup

Validation

cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent
cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Findings/FindingsNotificationEventTest.php tests/Feature/Findings/FindingsNotificationRoutingTest.php
cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Alerts/FindingsAlertRuleIntegrationTest.php tests/Feature/Alerts/SlaDueAlertTest.php tests/Feature/Notifications/FindingNotificationLinkTest.php

Filament / Platform Notes

Livewire v4.0+ compliance is preserved
provider registration remains unchanged in apps/platform/bootstrap/providers.php
no globally searchable resource behavior changed in this feature
no new destructive action was introduced
asset strategy is unchanged and the existing cd apps/platform && php artisan filament:assets deploy step remains sufficient

Manual Smoke Note

integrated-browser smoke testing confirmed the new alert rule event options, notification drawer entries, alert delivery history row, and tenant finding detail route on the active Sail host
local notification deep links currently resolve from APP_URL, so a local localhost vs 127.0.0.1:8081 host mismatch can break the browser session if the app is opened on a different host/port combination

## Summary - implement Spec 224 findings notifications and escalation v1 on top of the existing alerts and Filament database notification infrastructure - add finding assignment, reopen, due soon, and overdue event handling with direct recipient routing, dedupe, and optional external alert fan-out - extend alert rule and alert delivery surfaces plus add the Spec 224 planning bundle and candidate-list promotion cleanup ## Validation - `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Findings/FindingsNotificationEventTest.php tests/Feature/Findings/FindingsNotificationRoutingTest.php` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Alerts/FindingsAlertRuleIntegrationTest.php tests/Feature/Alerts/SlaDueAlertTest.php tests/Feature/Notifications/FindingNotificationLinkTest.php` ## Filament / Platform Notes - Livewire v4.0+ compliance is preserved - provider registration remains unchanged in `apps/platform/bootstrap/providers.php` - no globally searchable resource behavior changed in this feature - no new destructive action was introduced - asset strategy is unchanged and the existing `cd apps/platform && php artisan filament:assets` deploy step remains sufficient ## Manual Smoke Note - integrated-browser smoke testing confirmed the new alert rule event options, notification drawer entries, alert delivery history row, and tenant finding detail route on the active Sail host - local notification deep links currently resolve from `APP_URL`, so a local `localhost` vs `127.0.0.1:8081` host mismatch can break the browser session if the app is opened on a different host/port combination

ahmido added 2 commits 2026-04-22 00:52:31 +00:00

feat: implement findings notifications escalation 99ebfa837e

merge: agent session work

PR Fast Feedback / fast-feedback (pull_request) Failing after 4m4s

Details

c007f42d1f

ahmido merged commit e15d80cca5 into dev

2026-04-22 00:54:39 +00:00

ahmido referenced this issue from a commit

2026-04-22 00:54:40 +00:00

feat: implement findings notifications escalation (#261)

Sign in to join this conversation.