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

feat: complete admin canonical tenant rollout #165

Merged
ahmido merged 2 commits from 136-admin-canonical-tenant into dev 2026-03-13 08:09:21 +00:00
Conversation 0 Commits 2 Files Changed 93 +3130 -316
ahmido commented 2026-03-12 22:26:58 +00:00
Owner
Copy Link

Summary

  • complete Spec 136 canonical admin tenant rollout across admin-visible and shared Filament surfaces
  • add the shared panel-aware tenant resolver helper, persisted filter-state synchronization, and admin navigation segregation for tenant-sensitive resources
  • expand regression, guard, and parity coverage for admin-path tenant resolution, stale filters, workspace-wide tenant-default surfaces, and panel split behavior

Validation

  • vendor/bin/sail artisan test --compact tests/Feature/Guards/AdminTenantResolverGuardTest.php
  • vendor/bin/sail artisan test --compact tests/Feature/Filament/TableStatePersistenceTest.php
  • vendor/bin/sail artisan test --compact --filter='CanonicalAdminTenantFilterState|PolicyResource|BackupSchedule|BackupSet|FindingResource|BaselineCompareLanding|RestoreRunResource|InventoryItemResource|PolicyVersionResource|ProviderConnectionResource|TenantDiagnostics|InventoryCoverage|InventoryKpiHeader|AuditLog|EntraGroup'
  • vendor/bin/sail bin pint --dirty --format agent

Notes

  • Livewire v4.0+ compliance is preserved with Filament v5.
  • Provider registration remains unchanged in bootstrap/providers.php.
  • PolicyResource and PolicyVersionResource have admin global search disabled explicitly; EntraGroupResource keeps admin-aware scoped search with a View page.
  • Destructive and governance-sensitive actions retain existing confirmation and authorization behavior while using canonical tenant parity.
  • No new assets were introduced, so deployment asset strategy is unchanged and does not add new filament:assets work.
## Summary - complete Spec 136 canonical admin tenant rollout across admin-visible and shared Filament surfaces - add the shared panel-aware tenant resolver helper, persisted filter-state synchronization, and admin navigation segregation for tenant-sensitive resources - expand regression, guard, and parity coverage for admin-path tenant resolution, stale filters, workspace-wide tenant-default surfaces, and panel split behavior ## Validation - `vendor/bin/sail artisan test --compact tests/Feature/Guards/AdminTenantResolverGuardTest.php` - `vendor/bin/sail artisan test --compact tests/Feature/Filament/TableStatePersistenceTest.php` - `vendor/bin/sail artisan test --compact --filter='CanonicalAdminTenantFilterState|PolicyResource|BackupSchedule|BackupSet|FindingResource|BaselineCompareLanding|RestoreRunResource|InventoryItemResource|PolicyVersionResource|ProviderConnectionResource|TenantDiagnostics|InventoryCoverage|InventoryKpiHeader|AuditLog|EntraGroup'` - `vendor/bin/sail bin pint --dirty --format agent` ## Notes - Livewire v4.0+ compliance is preserved with Filament v5. - Provider registration remains unchanged in `bootstrap/providers.php`. - `PolicyResource` and `PolicyVersionResource` have admin global search disabled explicitly; `EntraGroupResource` keeps admin-aware scoped search with a View page. - Destructive and governance-sensitive actions retain existing confirmation and authorization behavior while using canonical tenant parity. - No new assets were introduced, so deployment asset strategy is unchanged and does not add new `filament:assets` work.
ahmido added 1 commit 2026-03-12 22:26:59 +00:00
ahmido added 1 commit 2026-03-13 01:20:16 +00:00
ahmido merged commit 45a804970e into dev 2026-03-13 08:09:21 +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#165
No description provided.
Delete Branch "136-admin-canonical-tenant"

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?