feat(ql3): publish complete release sets

deploy/kubernetes/ql3-cluster/README.md

@@ -161,10 +161,13 @@ pnpm audit:cluster-remote-manifest:ql3 \
 ```
 
 The existence of the workflow is not publication evidence. Before production
-rollout, record a successful release run for both image repositories,
-independently verify each signature and attestation set, and pin both resulting
-`sha256:` digests. Never treat the version tag or the control image's proof as
-authority for the admin Job.
+rollout, obtain the `cluster` or `all` deployment release set from a successful
+release run, verify its file provenance, and pin the four control, control-ai,
+worker and admin `sha256:` references recorded in that one source-bound set.
+Never treat the version tag, a partial matrix run or one image's proof as
+authority for another role. The exact operator procedure and non-atomic tag
+recovery boundary are documented in
+[`docs/operations/ql3-release-set-deployment.md`](../../../docs/operations/ql3-release-set-deployment.md).
 
 The committed CloudNativePG control, migration and Plugin Package recovery overlays use
 an all-zero SHA-256 digest as an intentionally unpullable fail-closed

deploy/kubernetes/ql3-worker/README.md

@@ -31,6 +31,12 @@ docker build \
   .
 ```
 
+Production rollout must take the Worker `@sha256:` reference from the same
+verified `cluster` or `all` release set as control, control-ai and admin. A
+version/source tag or a successful control image alone is not Worker release
+authority. See
+[`docs/operations/ql3-release-set-deployment.md`](../../../docs/operations/ql3-release-set-deployment.md).
+
 The builder and runtime dependency roots have separate npm v3 locks generated
 from the reviewed workspace `pnpm-lock.yaml`. The runtime image contains only
 `runtime-core`, `local-process`, `worker-runtime` and their 24 external runtime