Every page URL-syncs its search through `?q=...` (Infrastructure,
Workloads, Recovery, Storage all use the same convention via
`routeStateNavigation`), and `useSavedViews.saveCurrent` snapshots the
full URL search string. So saved views already capture both the active
filter chips and the search term, and applying a view later restores
both.
Adds a SharedPrimitives guardrail assertion that pins the
`window.location.search` snapshot in saveCurrent. A future refactor
that narrowed the snapshot to a curated subset of URL params would
silently strip search from saved views; this assertion catches that.
Operators that look at the same filtered slice repeatedly (stopped
containers on a specific cluster, stale backups in last 30 days,
TrueNAS pools needing attention) now save the current filter state as
a named view and recall it with one click.
The view is the page's URL query string at save time, so saved views
double as shareable URLs: copying the bar URL after applying a view
gives someone else the exact filtered state. Storage is per-browser
localStorage under `pulse:filterbar:saved-views:<key>`. Each catalog
opts in by passing `savedViewsKey` to FilterBar:
Infrastructure: 'infrastructure'
Workloads: 'workloads'
Storage: 'storage'
Recovery Protected items: 'recovery-protected'
Recovery events: 'recovery-events'
The menu lives next to "+ Filter" on the search row. Empty state
prompts the user to save the active filters; populated state lists
saved views with hover-to-reveal X buttons for delete. The save flow
is a small inline dialog (name input + Save / Cancel) so users never
leave the menu.
The hook (useSavedViews) owns localStorage IO, JSON parse hardening,
and URL navigation through @solidjs/router. The menu (SavedViewsMenu)
owns dropdown chrome and click-outside / Escape lifecycle. WorkloadsFilter
unit tests mock @solidjs/router so the menu can render outside a Router
context in test setup.
Implicit "remember last filters" is intentionally not added: defaulting
to yesterday's `Status: Failed` would hide real problems on a monitoring
page. Recently-used auto-tracking and pinned quick-buttons remain
deferred until we see whether named views is enough.
Subsystem contracts updated to reflect the new primitive and the
per-page opt-ins:
- frontend-primitives.md: adds SavedViewsMenu + useSavedViews to
Canonical Files; describes the shared saved-views primitive in
Extension Points.
- performance-and-scalability.md, storage-recovery.md,
unified-resources.md: note that Workloads / Storage / Recovery /
Infrastructure each opt into shared saved views by passing
savedViewsKey.
- Recovery.test.tsx: regression assertion that the events controls
group renders the Saved views menu trigger (verification artifact
for the storage-recovery contract change).
Deletes files that no runtime path imports after the migration to
chip-based FilterBar:
Storage's three-layer filter indirection:
- StorageFilter.tsx (legacy filter shell)
- StorageControls.tsx (subtab + filter pass-through wrapper)
- useStorageFilterToolbarModel.ts (legacy active-filter / reset hook)
- useStoragePageControlsModel.ts (sortDisabled + groupBy gating)
- useStorageControlsModel.ts (subtab + node-filter wiring)
- their tests
Workloads filter state hook:
- useWorkloadsFilterState.ts (replaced by inline FilterBar wiring;
countActiveWorkloadsFilters / hasActiveWorkloadsFilters stay in
workloadsFilterModel.ts)
- its test
The StorageStatusFilter and StorageGroupByFilter type aliases that
StorageFilter.tsx exported fold into the existing canonical types in
storagePageState.ts (StorageStatusFilterValue) and storageModelCore.ts
(StorageGroupKey), keeping useStorageFilterState.ts alive without the
deleted shell.
PageControls.tsx and its companion FilterToolbar primitives stay in
the tree because the alert-history filter card and the Kubernetes
deployments drawer still consume them. The canonical claim shifts:
FilterBar is the chip-based shell for catalog-driven page filters
(Infrastructure, Workloads, Storage, Recovery Protected items, Recovery
events). PageControls remains for non-migrated surfaces.
Subsystem contracts and registry updated:
- frontend-primitives.md: adds FilterBar files to Canonical Files;
describes FilterBar as the canonical page-level filter shell for
catalog-driven resource lists; PageControls described as the legacy
fallback for non-migrated surfaces.
- performance-and-scalability.md: drops useWorkloadsFilterState
references; describes Workloads' FilterBar / viewOptionsTrailing
composition.
- storage-recovery.md: replaces "PageControls toolbar rail" prose with
FilterBar / viewOptionsTrailing for both Storage and Recovery events;
notes the legacy three-layer indirection retired.
- registry.json: drops deleted file paths from owned_files,
verification.exact_files, and verification.path_policies entries.
- canonical_completion_guard_test.py + subsystem_lookup_test.py: drop
deleted file paths from hard-coded fixtures so the governance helper
tests track the registry.
- SharedPrimitives.guardrails.test.ts: adds regression assertions that
StoragePageControls no longer imports the deleted shells.
All four pages (Infrastructure, Workloads, Storage, Recovery) shared
PageControls as a layout container but each declared its own filter
row. The xl breakpoint silently swapped segmented buttons for selects,
Storage injected a bare unlabelled <select> for Node, and Recovery's
events sub-tab kept six advanced filters behind a separate popover.
This adds FilterBar as a shared primitive that takes a filter catalog
descriptor (label, options, value, defaultValue, group). Each page
declares its filters; the bar renders chips for active values and
reaches everything else through a "+ Filter" menu. Type-ahead in both
the menu and the chip popovers keeps power-user speed: one click plus
a few keystrokes replaces three clicks.
Infrastructure, Recovery (Protected items + Recovery events),
Workloads, and Storage migrate. Storage's three-layer
StoragePageControls -> StorageControls -> StorageFilter indirection
collapses into a single component; the bare unlabelled Node select
becomes a regular catalog chip; the xl segmented->select swap retires.
PageControls and its companion primitives (LabeledFilterSelect,
LabeledFilterToggleGroup, FilterSegmentedControl, FilterToolbarPanel,
filterControlsVariant, the Storage indirection) remain in the tree
but are no longer in any runtime path. The immediate follow-up commit
retires them and updates the frontend-primitives and unified-resources
subsystem contracts to name FilterBar as canonical.
Parse the /proc/mdstat operation keyword for mdadm arrays and propagate it through host reports, models, unified resources, monitoring views, alert metadata, and AI storage summaries.
Treat recovery and reshape as rebuild signals while silencing routine check and resync maintenance, with fallback rebuild detection only when no mdstat operation is available.
Tests cover mdstat operation parsing plus recovery, check, and resync alert behavior.
Fixes#1446
Pass keep_alive=30s on both Chat and ChatStream requests so Ollama unloads the model shortly after Patrol or one-shot analysis bursts instead of refreshing the default 5-minute residency window on every request.
Tests assert both streaming and non-streaming Ollama request bodies include the keep_alive field.
Fixes#1425
Remove local upgrade-metrics API registration, settings payload wiring, startup store migration, and backend conversion recorder hooks from the normal product runtime.
Delete the retired conversion/funnel and metering packages from compiled licensing code, and extend diagnostics boundary audits and governance contracts so maintainer commercial analytics cannot return through Settings or diagnostics.
rcourtman