Clarify fresh CloudNativePG bootstrap sequence

chart/README.md

@@ -32,6 +32,10 @@ Choose exactly one database arrangement:
   manage that Cluster independently (useful for database-first migrations).
   The operator's generated `<name>-app` Secret contains the application
   username and password. Put the same credentials in the private Quay config.
+  For a fresh operator-managed installation, first install with
+  `quay.enabled=false`, `repomirror.enabled=false`, and `ingress.enabled=false`;
+  wait for the Cluster and generated app Secret, create the private Quay config
+  Secret, then enable Quay and its Ingress in a second upgrade.
 - **External/shared PostgreSQL:** leave both switches false and point the
   `DB_URI` at your own server. The chart does not manage its data or users.
 

chart/quay/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v2
 name: quay
-description: Project Quay registry with optional PostgreSQL and Valkey
+description: Project Quay registry with embedded, CloudNativePG, or external PostgreSQL and optional Valkey
 type: application
 version: 0.0.0
 appVersion: 3.18.0