Rebrand the hosted control-plane portal as Pulse Account and expose transitional self-hosted commercial services there so the account story stops reading as Cloud-only.
Define the canonical Pulse Account portal spec, wire cloud-paid to the hosted/account portal boundary, and surface the spec in the v6 governance README.
Sort pending Patrol approvals and approval-linked findings by urgency in the shared store contract so Patrol review surfaces consistently lead with the most urgent approval.
Move Patrol attention ordering into aiIntelligenceStore so dashboard hooks consume a canonical queue instead of adding their own ordering logic downstream.
Use a shared attention-queue sorter so dashboard action consumers surface Patrol runtime issues ahead of same-severity infrastructure findings instead of inheriting arbitrary store order.
Route dashboard overview Patrol runtime findings through the shared compact badge, title, and primary action/manual control helpers so the action-required panel does not expose rejected generic controls or raw Patrol-prefixed titles.
Route Patrol-owned runtime finding titles through the shared finding presentation helper so visible rows, assistant handoff prompts, and approval surfaces stop repeating the product prefix.
Use a shared runtime-qualified severity badge for Patrol-owned runtime findings, keep the findings row readable without duplicate classification chips, and record the rule in the Patrol contract.
Use the shared Patrol runtime classification for the findings workspace badge so runtime-only issues do not inherit the generic warning tone meant for infrastructure findings.
Sort active Patrol-owned runtime issues ahead of same-severity infrastructure findings so operators see Patrol trust impairments before ordinary warning noise.
Make the Patrol supporting metrics strip use the canonical runtime-versus-infrastructure classification so runtime failures no longer appear as generic infrastructure warnings.
Prevent Patrol-owned runtime findings from being hidden via generic lifecycle actions; reject those actions in the backend and remove the corresponding UI controls while preserving the direct AI settings remediation path.
Expanded Patrol runtime findings now offer the same direct Open AI Settings action as the summary card, with the action owned by the shared finding presentation helper.
Patrol summary cards now expose an Open AI Settings action when the primary issue is a Patrol-owned runtime/provider failure, so the fix path is available directly in the top assessment.
Patrol now renders investigation context beneath the findings and history workspace, keeping the primary summary card focused on assessment and verification while preserving the same context content and toggle behavior.
Patrol now labels the summary score chip as Assessment when coverage is incomplete or only Patrol-owned runtime findings are active, while keeping Health for verified healthy states.
Patrol assessment copy now names a single active Patrol runtime failure directly, instead of reducing it to a generic runtime-finding count, and updates the governed Patrol presentation contract and proofs.
The findings store now clears acknowledgement timestamps that predate a recorded regression when persisted findings are loaded, persists the normalized state, and keeps regression lifecycle metadata explicit.
The shared findings lifecycle now clears prior acknowledgement state when a resolved finding regresses, records that prior acknowledgement in regression metadata, and documents the contract in ai-runtime.
Patrol-owned ai-service findings now render as Patrol runtime in findings rows and assistant handoff prompts instead of exposing backend resource tokens.
The Patrol findings list and summary now use the same shared classification for Patrol-owned runtime findings, including an explicit Patrol runtime badge in the active finding row.
Patrol assessment now classifies synthetic Patrol runtime findings separately from infrastructure findings so the top summary can truthfully describe Patrol-owned service failures.
Synthetic Patrol runtime findings such as ai-service provider failures now stay active in seed/reconcile flows instead of being auto-resolved as deleted infrastructure resources.
Preserve last_seen_at in the shared finding model and use it for active Patrol finding recency text and sorting so recurring issues do not appear stale.
Hide the Patrol findings filter bar when there are no findings or special queues to navigate, keeping empty-state Patrol surfaces focused on the actual assessment rather than inert controls.
