fix(cloudcp): make Pulse Account health states explicit

docs/release-control/v6/internal/PULSE_ACCOUNT_PORTAL_SPEC.md

@@ -154,6 +154,14 @@ It adds:
 3. per-workspace health summary
 4. account roles suitable for owner/admin/tech/read-only workflows
 
+Workspace health in Pulse Account must distinguish three states explicitly:
+
+1. `healthy`
+2. `checking` when no completed health check exists yet
+3. `unhealthy` when the latest health check failed
+
+The portal must not label a failed health check as `checking`.
+
 ### Pulse Relay and Pulse Mobile
 
 Pulse Relay does not get a standalone portal. Relay is a capability inside

docs/release-control/v6/internal/subsystems/api-contracts.md

@@ -215,6 +215,9 @@ account identity context, signed-out versus signed-in shell state, workspace
 summaries, and renderer-owned public, commercial, and control-plane route
 configuration, including the canonical bootstrap route path, magic-link request
 path, signup path, and stable workspace summary fields such as `created_at`.
+That workspace summary contract must expose explicit health semantics: `healthy`
+for passing health checks, `checking` only when no completed health check
+exists yet, and `unhealthy` for a failed latest health check.
 `/portal` is now one bootstrap-driven shell for both anonymous and
 authenticated users, so new account frontend work must extend that shared
 contract rather than inventing a second local payload shape, reviving separate