merge: origin/dev into 058-tenant-ui-polish

specs/057-filament-v5-upgrade/checklists/requirements.md

@@ -1,4 +1,4 @@
-# Specification Quality Checklist: Admin UI Stack Upgrade (Panel + Suite)
+# Specification Quality Checklist: Admin UI Framework Upgrade (Panel + Suite)
 
 **Purpose**: Validate specification completeness and quality before proceeding to planning
 **Created**: 2026-01-20
@@ -30,6 +30,5 @@ ## Feature Readiness
 - [x] No implementation details leak into specification
 
 ## Notes
-
 - This is a technical upgrade, but the spec describes outcomes and guardrails rather than implementation steps.
 - Planning can capture concrete versions, dependency changes, and migration steps.

specs/057-filament-v5-upgrade/spec.md

@@ -1,4 +1,4 @@
-# Feature Specification: Admin UI Stack Upgrade (Panel + Suite)
+# Feature Specification: Admin UI Framework Upgrade (Panel + Suite)
 
 **Feature Branch**: `057-filament-v5-upgrade`  
 **Created**: 2026-01-20  
@@ -10,9 +10,9 @@ ## Clarifications
 ### Session 2026-01-20
 
 - Q: What exactly counts as a “remote call” that is forbidden during Monitoring/Operations page render? → A: Any outbound HTTP request.
-- Q: Are background/automatic Livewire requests (polling, auto-refresh, hydration) allowed to make outbound HTTP calls on Monitoring/Operations pages? → A: No; Monitoring/Operations must remain DB-only even for polling/auto-refresh/hydration. Remote work is only allowed via explicit user actions that enqueue tracked operations.
+- Q: Are background/automatic UI requests (polling, auto-refresh, hydration) allowed to make outbound HTTP calls on Monitoring/Operations pages? → A: No; Monitoring/Operations must remain DB-only even for polling/auto-refresh/hydration. Remote work is only allowed via explicit user actions that enqueue tracked operations.
 - Q: Which pages count as “Monitoring/Operations” for the DB-only rule? → A: Everything rendered under the Monitoring → Operations navigation section, including all widgets/partials/tabs rendered within that section.
-- Q: If a third-party package is incompatible with the upgraded stack, what remediation is allowed? → A: Upgrade/replace the package to preserve functionality. Mixed-version pinning is not allowed. If something is not realistically replaceable, treat it as an explicit scope/decision change.
+- Q: If a third-party admin UI extension is incompatible with the upgraded stack, what remediation is allowed? → A: Upgrade/replace the dependency to preserve functionality. Mixed-version pinning is not allowed. If something is not realistically replaceable, treat it as an explicit scope/decision change.
 - Q: Do we expect this upgrade to require any database schema/data changes? → A: Allowed only if strictly required by dependencies; must be reversible, non-destructive, backward compatible, and called out in release notes.
 
 ## User Scenarios & Testing *(mandatory)*
@@ -62,19 +62,18 @@ ### User Story 3 - Deployment remains reliable (Priority: P3)
 
 ### Edge Cases
 
-- A third-party admin/Live UI package is incompatible with the upgraded stack.
+- A third-party admin UI extension is incompatible with the upgraded stack.
 - Users have stale browser assets after deploy and experience partial UI breakage.
-- SPA navigation and global widgets fail to mount or miss events after navigation.
+- In-app navigation and global widgets fail to mount or miss events after navigation.
 - Tenant switching occurs mid-session and cached UI state risks showing stale cross-tenant data.
 - Monitoring pages accidentally perform remote calls during render (must be prevented/detected).
 
 ## Requirements *(mandatory)*
 
 **Constitution alignment (required):** This feature is an upgrade. It MUST NOT introduce new Microsoft Graph calls or new Graph write behavior.
-All content rendered under the Monitoring → Operations navigation section remains “DB-only” and must not perform any outbound HTTP requests during render or during background/automatic Livewire requests (polling/auto-refresh/hydration). Tenant isolation remains mandatory.
+All content rendered under the Monitoring → Operations navigation section remains “DB-only” and must not perform any outbound HTTP requests during render or during background/automatic UI requests (polling/auto-refresh/hydration). Tenant isolation remains mandatory.
 
 ### Functional Requirements
-
 - **FR-001**: The system MUST upgrade the admin UI stack to the next supported major release and remain fully functional for all in-scope admin workflows.
 - **FR-002**: The system MUST continue to support the existing styling and asset pipeline without build failures.
 - **FR-003**: All existing admin pages MUST load successfully for authorized users and preserve core interactions (navigation, lists, forms, actions, notifications, and global UI elements).
@@ -90,8 +89,8 @@ ### Functional Requirements
 
 ### Assumptions & Dependencies
 
-- The current platform runtime versions already meet (or exceed) the minimum requirements for the next major admin UI stack release.
-- Third-party UI packages used in the admin panel may need upgrades or replacements to remain compatible.
+- The current platform runtime versions already meet (or exceed) the minimum requirements for the next major admin UI framework release.
+- Third-party dependencies used in the admin panel may need upgrades or replacements to remain compatible.
 - Existing tenant isolation and “DB-only render time” guard tests (or equivalent checks) exist and remain authoritative for this upgrade.
 
 ### Key Entities *(include if feature involves data)*
@@ -107,4 +106,4 @@ ### Measurable Outcomes
 - **SC-001**: An administrator can sign in and reach a usable dashboard within 60 seconds on a fresh deployment.
 - **SC-002**: In regression testing, Monitoring/Operations pages render without any remote calls during render in 100% of runs.
 - **SC-003**: 0 critical UI-blocking errors occur in the primary admin journeys (P1 + P2 scenarios) during manual QA.
-- **SC-004**: Automated regression checks pass (100% green) for the project’s standard test run.
+- **SC-004**: Automated regression checks complete successfully (100% passing) for the project’s standard validation run.