Converge platform alert severity filters

docs/release-control/v6/internal/subsystems/frontend-primitives.md

@@ -2425,6 +2425,12 @@ label formatting and severity-bucket-to-status-indicator mapping. Docker,
 Kubernetes, TrueNAS, vSphere, and future platform alert tables must compose
 `AlertSeverityBadge` and `AlertSeverityDot`; they must not recreate
 `severityVariant`, `severityTextClass`, or severity badge spans locally.
+Platform alert severity filters follow the same shared-template rule.
+`frontend-modern/src/features/platformPage/platformAlertSeverityFilterOptions.tsx`
+owns the canonical All/Critical/Warning/Info option labels, tones, and leading
+dots for platform alert table toolbars. Platform alert tables must call
+`getPlatformAlertSeverityFilterOptions` instead of declaring local severity
+filter arrays or calling `filterChipStatusDot` directly for those filters.
 Read-only metadata badges follow the same primitive-owned shell rule.
 `frontend-modern/src/components/shared/MetadataBadge.tsx` owns filled and
 outlined appearances, compact sizing, shape, typed tone vocabulary, fit

docs/release-control/v6/internal/subsystems/unified-resources.md

@@ -1784,7 +1784,9 @@ severity dots, badges, and severity label formatting must compose
 `AlertSeverityDot`, `AlertSeverityBadge`, and
 `formatAlertSeverityLabel` from the frontend-primitives-owned shared path
 instead of restoring table-local `severityVariant`, `severityTextClass`, or
-severity-label helpers,
+severity-label helpers, and their severity toolbar filters must use
+`getPlatformAlertSeverityFilterOptions` instead of restoring local
+All/Critical/Warning/Info option arrays,
 and local operator identity labels now split from governed detail summaries:
 infrastructure tables, selectors, links, and drawer headings must preserve the
 canonical local instance identity (`displayName`, canonical display name,