fix(recovery): preserve route-owned platform filters

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

@@ -896,6 +896,14 @@ consume that shared `platform` filter surface directly. They must not keep
 recovery-local `provider` route/query vocabulary alive behind renamed labels,
 or the UI will drift back to backend-shaped navigation even when the copy says
 `Platform`.
+That same shared recovery filter owner must also preserve route-owned platform
+visibility while transport-backed options are still hydrating. If
+`frontend-modern/src/features/recovery/useRecoverySurfaceState.ts` restores a
+canonical `platform` selection such as `truenas` from the route before the
+rollups, points, or facets payloads arrive, it must keep that selected
+platform present in the option set so the shared `LabeledFilterSelect` shows
+the owned value immediately instead of flashing back to `All Platforms` until
+recovery data warms.
 `frontend-modern/src/utils/problemResourcePresentation.ts` now also belongs to
 that same dashboard overview boundary so the problem-resource severity contract
 stays shared with `ProblemResourcesTable.tsx` instead of floating as an

docs/release-control/v6/internal/subsystems/storage-recovery.md

@@ -100,6 +100,7 @@ querying, and the operator-facing storage health presentation layer.
 9. Letting whitespace-padded recovery timeline params fall off canonical route state; shared recovery URLs must trim and normalize `day`, `range`, `scope`, `status`, `verification`, `cluster`, `node`, `namespace`, `itemType`, and adjacent history filters before the page model validates them so pasted or hand-edited links resolve to the same canonical timeline and filter state as UI-authored routes
 10. Letting explicit recovery `all` sentinels survive in canonical route state; shared recovery URLs must collapse case- or whitespace-variant `all` values for `cluster`, `node`, `namespace`, and `itemType` back to the canonical unset route state so copied links do not preserve fake active filters
 11. Letting non-canonical recovery platform values survive in route or transport state; shared recovery URLs must collapse unsupported or fake `platform` values back to the canonical unset state, and only owned source-platform options or canonical legacy aliases may reach rollups, points, series, and facets transport filters
+11c. Letting route-owned recovery platform selections disappear while filter options are still hydrating; the recovery page state owner must keep the current canonical `platform` query value present in the platform option set until transport-backed facets and records arrive so shared filter selects keep the user-visible TrueNAS or other owned platform selection instead of flashing back to `All Platforms`
 11a. Letting adjacent workload-route changes in shared `frontend-modern/src/routing/resourceLinks.ts` perturb recovery parse/build semantics; expanding canonical `/workloads` platform scoping must not alter the owned `/recovery` `platform` and `itemType` vocabulary, legacy alias rewrites, or recovery drill-down workspace selection
 11b. Letting adjacent storage-link additions in shared `frontend-modern/src/routing/resourceLinks.ts` perturb recovery route semantics; expanding canonical `/storage` deep links for unified resources must not reuse recovery-owned query names or alter the owned `/recovery` parse/build contract while those surfaces continue sharing the same route-helper module
 12. Letting protected-item recovery outcome filtering fork from the canonical history status filter; the protected inventory status control must drive the same route-backed `status` field and the same rollups, points, series, and facets transport filters as the history surface instead of keeping a protected-only local outcome branch