ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects 1 Releases Wiki Activity

feat: implement spec 192 record page header discipline #226

Merged
ahmido merged 1 commits from 192-record-header-discipline into dev 2026-04-11 21:20:42 +00:00
Conversation 0 Commits 1 Files Changed 44 +3839 -365
ahmido commented 2026-04-11 21:10:20 +00:00
Owner
Copy Link

Summary

  • implement Spec 192 across the targeted Filament record, detail, and edit pages with explicit action-surface inventory and guard coverage
  • add the focused Spec 192 browser smoke, feature tests, and spec artifacts under specs/192-record-header-discipline
  • improve unhandled promise rejection diagnostics by correlating 419s to the underlying Livewire request URL
  • disable panel-wide database notification polling on the admin, tenant, and system panels and cover the mitigation with focused tests

Validation

  • cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Filament/DatabaseNotificationsPollingTest.php
  • cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Filament/DatabaseNotificationsPollingTest.php tests/Feature/Filament/UnhandledRejectionLoggerAssetTest.php tests/Feature/Filament/FilamentNotificationsAssetsTest.php tests/Feature/Workspaces/ManagedTenantsLivewireUpdateTest.php tests/Feature/Filament/AdminSmokeTest.php
  • cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent
  • manual integrated-browser verification of the Spec 192 surfaces and the notification-polling mitigation

Notes

  • Livewire v4 / Filament v5 compliance remains unchanged.
  • Provider registration stays in bootstrap/providers.php.
  • No Global Search behavior was expanded.
  • No destructive action confirmation semantics were relaxed.
  • The full test suite was not run in this PR.
## Summary - implement Spec 192 across the targeted Filament record, detail, and edit pages with explicit action-surface inventory and guard coverage - add the focused Spec 192 browser smoke, feature tests, and spec artifacts under `specs/192-record-header-discipline` - improve unhandled promise rejection diagnostics by correlating 419s to the underlying Livewire request URL - disable panel-wide database notification polling on the admin, tenant, and system panels and cover the mitigation with focused tests ## Validation - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Filament/DatabaseNotificationsPollingTest.php` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Filament/DatabaseNotificationsPollingTest.php tests/Feature/Filament/UnhandledRejectionLoggerAssetTest.php tests/Feature/Filament/FilamentNotificationsAssetsTest.php tests/Feature/Workspaces/ManagedTenantsLivewireUpdateTest.php tests/Feature/Filament/AdminSmokeTest.php` - `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent` - manual integrated-browser verification of the Spec 192 surfaces and the notification-polling mitigation ## Notes - Livewire v4 / Filament v5 compliance remains unchanged. - Provider registration stays in `bootstrap/providers.php`. - No Global Search behavior was expanded. - No destructive action confirmation semantics were relaxed. - The full test suite was not run in this PR.
ahmido added 1 commit 2026-04-11 21:10:21 +00:00 
- land the spec 192 resource, guard, browser smoke, and documentation changes
- add unhandled rejection request correlation for 419 diagnostics
- disable panel-wide database notification polling and cover it with focused tests
ahmido merged commit 9f6985291e into dev 2026-04-11 21:20:42 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ahmido/TenantAtlas#226
No description provided.
Delete Branch "192-record-header-discipline"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?