docs: clarify cloud profile activation in java-cfenv docs

The `cloud` Spring profile is activated by CloudProfileApplicationListener,
which ships only in the java-cfenv-all module (not java-cfenv-boot or the
core module). Correct the framework doc and the migration guide's
troubleshooting entry, and show SPRING_PROFILES_INCLUDE (add alongside
existing profiles) vs SPRING_PROFILES_ACTIVE (replace) for explicit
activation.

Refs #1349.

Author: stokpop

docs/framework-java-cfenv.md

@@ -3,7 +3,7 @@ The Java CfEnv Framework provides the `java-cfenv` library for Spring Boot 3.x a
 
 This is the recommended replacement for Spring AutoReconfiguration library which is deprecated. See the `java-cfenv` <a href="https://github.com/pivotal-cf/java-cfenv">repository</a> for more details.
 
-The included `java-cfenv` library activates the `cloud` Spring profile at runtime when `VCAP_SERVICES` is present, as the Spring AutoReconfiguration framework did. The buildpack itself does not set any Spring profile.
+The `cloud` Spring profile is activated at runtime by java-cfenv's `CloudProfileApplicationListener`, which ships in the `java-cfenv-all` module. To ensure the profile is active — or to activate it independently of java-cfenv — set it explicitly. Use `SPRING_PROFILES_INCLUDE=cloud` to add `cloud` alongside any other active profiles, or `SPRING_PROFILES_ACTIVE=cloud` to set it as the sole active profile (this replaces any others). The buildpack itself does not set any Spring profile.
 
 The buildpack selects the appropriate `java-cfenv` version based on the detected Spring Boot major version:
 

docs/spring-auto-reconfiguration-migration.md

@@ -2,6 +2,24 @@
 
 This guide provides step-by-step instructions for migrating from the deprecated **Spring Auto-reconfiguration** framework to **java-cfenv**.
 
+> **Note — the `cloud` Spring profile**
+>
+> Spring Auto-reconfiguration activated a Spring profile named `cloud`. java-cfenv only
+> activates that profile if the `java-cfenv-all` module is on the classpath (it contains
+> `CloudProfileApplicationListener`); the `java-cfenv-boot` module does **not**. If your
+> application relies on the `cloud` profile — for example `application-cloud.yml` /
+> `application-cloud.properties` or `@Profile("cloud")` beans — either use `java-cfenv-all`,
+> or activate it explicitly. If the application already sets other active profiles, use
+> `SPRING_PROFILES_INCLUDE` to add `cloud` alongside them:
+>
+> ```bash
+> cf set-env <APP> SPRING_PROFILES_INCLUDE cloud   # adds 'cloud' to any existing profiles
+> cf restage <APP>
+> ```
+>
+> Use `SPRING_PROFILES_ACTIVE=cloud` only if `cloud` should be the sole active profile (it
+> replaces any others).
+
 ---
 
 ## Table of Contents
@@ -453,16 +471,23 @@ public class CustomConfig {
 
 ### Issue: "cloud" profile not active
 
-**Cause**: java-cfenv only activates "cloud" profile on Cloud Foundry
-
-**Solution**: This is expected. Locally, the "cloud" profile won't be active.
+**Cause**: The `cloud` profile is activated by `CloudProfileApplicationListener`, which ships
+only in the `java-cfenv-all` module. The `java-cfenv-boot` dependency shown above does **not**
+activate it. If you previously depended on the `cloud` profile under Spring Auto-reconfiguration,
+it will not be active after migrating to `java-cfenv-boot` alone.
 
-To test cloud profile locally:
+**Solution**: Either depend on `java-cfenv-all` instead of `java-cfenv-boot`, or activate the
+profile explicitly. If the application already sets other active profiles, add `cloud` alongside
+them with `SPRING_PROFILES_INCLUDE`:
 
 ```bash
-java -jar myapp.jar --spring.profiles.active=cloud
+cf set-env <APP> SPRING_PROFILES_INCLUDE cloud   # adds 'cloud' to any existing profiles
+cf restage <APP>
 ```
 
+Use `SPRING_PROFILES_ACTIVE=cloud` only if `cloud` should be the sole active profile (it replaces
+any others). To activate it locally: `java -jar myapp.jar --spring.profiles.active=cloud`.
+
 ---
 
 ## Rollback Plan