ahmido d32b2115a8 Spec 103: IA semantics (scope vs filter vs targeting) + UI polish (#126) ... Implements Spec 103 (IA semantics: Scope vs Filter vs Targeting) across Monitoring + Manage. Changes - Monitoring tenant indicator copy: “All tenants” / “Filtered by tenant: …” - Alerts KPI header resolves tenant via OperateHubShell::activeEntitledTenant() for consistency - Manage list pages (Alert Rules / Destinations) no longer show tenant indicator - AlertRule form uses targeting semantics + sections (Rule / Applies to / Delivery) - Additional UI polish: resource sections, tenant view widgets layout, RBAC progressive disclosure (“Not configured” when empty) Notes - US6 (“Add current tenant” convenience button) intentionally skipped (optional P3). Testing - CI=1 vendor/bin/sail artisan test tests/Feature/TenantRBAC/ tests/Feature/Onboarding/OnboardingIdentifyTenantTest.php - vendor/bin/sail bin pint --dirty --format agent Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #126		2026-02-21 00:28:15 +00:00
..
filament	Spec 103: IA semantics (scope vs filter vs targeting) + UI polish (#126)	2026-02-21 00:28:15 +00:00
livewire	Spec 078: Operations tenantless canonical detail (#95)	2026-02-07 09:07:26 +00:00
admin-consent-callback.blade.php	fix(onboarding): preserve workspace scope and consent flow (#117)	2026-02-15 22:27:55 +00:00
welcome.blade.php	Initial commit from Specify template	2025-12-10 22:27:21 +01:00