Embed refund and privacy-data request flows into the Pulse Account shell so the existing public utility pages become compatibility paths rather than the primary commercial account UX.
Move subscription management and license retrieval into the Pulse Account shell using the canonical commercial APIs, while keeping refund and privacy flows as explicit external fallbacks during the rollout.
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.
rcourtman