Group Mongo bootstrap secrets under infrastructure ownership

docs/local-development.md

@@ -41,10 +41,9 @@ kv/
 │   └── notifications/
 │       ├── callers/bff                 # token; read by BFF and notifications
 │       └── email/resend                # driver, api_key, sender_address, sender_name
-├── infrastructure/
-│   └── nats/auth                       # token; read by NATS and notifications
-└── bootstrap/
-    └── mongo                           # local administrator and replica-set bootstrap material
+└── infrastructure/
+    ├── nats/auth                       # token; read by NATS and notifications
+    └── mongo/bootstrap                 # local administrator and replica-set bootstrap material
 ```
 
 Every secret has an owning service or infrastructure component. Service policies
@@ -130,7 +129,8 @@ still interrupt work. Repository consumers use `source.Source` operation scopes;
 ## Migration and persistence
 
 Bootstrap migrates the old flat `bff`, `caller`, `email` and `nats` paths into the
-hierarchy above. It copies with CAS protection, compares values, and refuses to
+hierarchy above, and moves `bootstrap/mongo` to `infrastructure/mongo/bootstrap`.
+It copies with CAS protection, compares values, and refuses to
 overwrite conflicting destinations. After consumers use the new paths, it removes
 old KV metadata and obsolete `tls`, `frontend-tls`, `notifications-tls` entries.
 Readable old version history and metadata are archived privately in