Finish architecture-cleanup RAILIANCE-WP-0016 T05

Item 13 is the restore RESOURCE-WP-0002 already proved. Item 14 retires
the dead Bitnami postgresql-ha deploy path and gates Valkey until a
consumer exists. Item 17 publishes the versioned S3 consumer-interface
index.

SCOPE.md

@@ -21,11 +21,10 @@ Stack dimension: the platform services that multiple applications share. Five
 repos cover S1–S5; other `railiance-*` repos sit on other OAS dimensions rather
 than on the stack. See `ArchitectureBlueprint.md` for the full backbone.
 
-The active migration is from Bitnami postgresql-ha (repmgr + pgpool, deployed
-historically as part of the Gitea subchart in S2 — the forge itself is now
-Forgejo) to CloudNative PG (cnpg operator, already deployed in the cnpg-system
-namespace) as the canonical database operator. Valkey cluster is also in scope
-for S3 extraction from S2.
+The database operator is CloudNative PG. Bitnami postgresql-ha is retired
+(no live release; `make pg-deploy` fail-closed, `RAILIANCE-WP-0016` item 14).
+Valkey is a declared capability with no live instance and nothing left in S2
+to extract; `make valkey-deploy` is gated until a consumer rapp exists.
 
 OpenBao is a platform capability in this repo, but not every OpenBao-related
 file belongs in the long-term S3 ownership home. The deployable package surface
@@ -78,18 +77,18 @@ policy, and lane governance.
 ## Current State
 
 - Status: maintained / emerging
-- Implementation: CloudNative PG operator (cnpg) deployed; `databases` namespace active; OpenBao is live as the S3 secrets service; Valkey + legacy postgresql-ha extraction from S2 remain in progress
-- Stability: emerging — cnpg deployed but database cluster definitions not yet migrated from S2
-- Usage: shared database, cache, and secrets layer; cnpg-system, databases, and openbao namespaces are live
+- Implementation: CloudNative PG operator live; `databases` namespace holds the platform clusters; OpenBao is the S3 secrets service. Bitnami postgresql-ha is retired. Valkey is undeployed.
+- Stability: emerging — CNPG clusters are live; cache and in-cluster object storage are not
+- Usage: shared database and secrets layer; cnpg-system, databases, and openbao namespaces are live
 - Deploys via ArgoCD: four Applications (`external-secrets`, `issue-core`,
   `openbao-secretstore`, `target-revenue`) plus AppProjects under
   `argocd/bootstrap/`; see `docs/argocd-gitops.md`
 - Emits to `railiance-telemetry` (Q2 Observability) once the evidence plane
   exists — seeded 2026-08-11, not yet implemented
-- Open work: Valkey and legacy postgresql-ha extraction remain active; the
-  OpenBao package boundary and PAT consumer cutover are now documented and
-  closed; `rapp-openbao`/`rapp-postgres` declaration conformance
-  (`RAILIANCE-WP-0015-T02`) is held pending the `railiance-master` schema
+- Open work: Valkey remains a declared-but-unbuilt cache; MinIO is likewise
+  declared, not deployed. OpenBao package boundary and PAT cutover are
+  closed. Platform rapp declarations conform (`RAILIANCE-WP-0015`).
+  Versioned consumer interfaces: `docs/s3-consumer-interfaces.md`.
 - Known drift: State Hub attributes ~11 capabilities to this repo, including
   S1/S2/S4/S5 concerns it does not own. The four `capability` blocks in this
   file are authoritative; the hub carries stale pre-split attributions
@@ -138,7 +137,7 @@ keywords: [postgresql, postgres, cnpg, cloudnative-pg, operator, database, kuber
 ```capability
 type: infrastructure
 title: Valkey / Redis-compatible cache
-description: Shared Redis-compatible cache service (Valkey) for all applications in the Railiance stack.
+description: Declared shared Redis-compatible cache. Not deployed on railiance01 as of 2026-08-15; no S2 instance remains to extract.
 keywords: [valkey, redis, cache, shared, session, queue]
 ```