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.
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.
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.
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.
AI runtime coverage summaries now distinguish recent full patrol errors from scoped-only activity so Patrol assessment copy matches the verification evidence.
Move hosted verification and checkout service/configuration failures onto the owned unavailable outcome UX so non-user-fixable errors no longer fall back to inline form state.
Move invalid and expired hosted backup-link states onto the owned outcome UX so verification and verified-token checkout do not fall back to dead-end forms with missing Pulse context.
Move pre-checkout hosted trial conflicts onto the owned terminal outcome UX so users do not land back in an editable form for non-retryable duplicate-trial states.
Keep hosted trial request-verification and checkout pages aligned with the canonical issuance conflict type so duplicate recovery-email usage is surfaced distinctly from organization reuse.
Use explicit hosted trial completion failure kinds so retryable errors can keep restart links while terminal conflicts and service outages show the correct next-step guidance.
Keep Stripe return-path failures inside branded Pulse trial UX, preserve restart links only when the originating instance binding is still available, and update hosted trial proofs/contracts.
rcourtman