fix(cloud): align planner configuration and records

openspec/changes/cloud-console-governance/design.md

@@ -40,8 +40,9 @@ or `tools`.
   control layer.
 - General remote Host control, inbound connections, or allowing one Host to
   enqueue work for another Host.
-- Charging, invoice generation, provider price catalogues, prompt/screenshot
-  retention, or an attempt to hard-limit direct-to-provider planner calls.
+- Charging, invoice generation, provider price catalogues, defining planner
+  prompt/screenshot retention (owned by `task-execution-progress-visibility`),
+  or an attempt to hard-limit direct-to-provider planner calls.
 - Cloud workflow-definition distribution.  Host-self submission is goal-only
   because a workflow definition is still stored locally on each Host.
 
@@ -162,9 +163,10 @@ when `tasks:submit` is present.  Policy and usage administration render only
 for `governance:admin`; backend scope and policy checks are authoritative.
 
 Every policy change records a safe audit event with actor, target, old/new
-revision, and non-secret values.  The Console clears any password inputs from
-the existing Users flow and never displays provider credentials, prompts,
-screenshots, cookies, or lease secrets.
+revision, and non-secret values. The governance views clear password inputs and
+never display provider credentials, screenshots, cookies, or lease secrets;
+the separate task-detail planner-history view is governed by
+`task-execution-progress-visibility`.
 
 ## Risks / Trade-offs