fix: clarify durable Postgres blocker diagnostics

Host commander merge after PR workflow closeout. Reviewed PR #230 against current main; D601 closeout task codex_1779506316145_1 recommended MERGE. Verification recorded: GitHub CLEAN/MERGEABLE; merge-tree clean over current main; focused PR tests node --check plus node --test internal/db/runtime-store.test.mjs internal/cloud/server.test.mjs scripts/src/dev-runtime-migration.test.mjs passed 33/33; synthetic merge including scripts/artifact-runtime-readiness-guard.test.mjs passed 40/40. This merge does not claim live DEV deployment or M3/M4/M5 acceptance; runtime durability remains blocked until deployed and separately verified.

docs/cloud-api-runtime.md

@@ -59,10 +59,10 @@ checks:
 - read readiness against the runtime tables used by audit and evidence
   queries.
 
-If DB auth, schema, migration, or read readiness is missing, `/health/live`
+If DB SSL negotiation, auth, schema, migration, or read readiness is missing, `/health/live`
 stays degraded with `runtime.durable: false`, `runtime.durableRequested: true`,
-and a runtime blocker such as `runtime_durable_adapter_auth_blocked`,
-`runtime_durable_adapter_schema_blocked`, or
+and a runtime blocker such as `runtime_durable_adapter_ssl_blocked`,
+`runtime_durable_adapter_auth_blocked`, `runtime_durable_adapter_schema_blocked`, or
 `runtime_durable_adapter_migration_blocked`. Fixture data and env presence are
 never promoted to `runtime.liveRuntimeEvidence`.
 

docs/reference/dev-runtime-boundary.md

@@ -180,7 +180,7 @@ proven through the configured adapter.
 `dbLiveEvidenceObserved=true` with
 `dbLiveEvidenceIsDurabilityEvidence=false` means the DB TCP/live layer is
 separate from runtime persistence. If runtime durability is blocked,
-`blockedLayer` names the current adapter/auth/schema/migration/durability query
+`blockedLayer` names the current adapter/ssl/auth/schema/migration/durability query
 layer, and `requiredEvidence` remains the durable adapter schema, migration,
 and read query contract.