fix: parameterize the Ollama rollback profile

The rollback hard-coded `--profile gpu` while the upgrade example above it uses
a variable, so a CPU install would have started the GPU service.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015BwsJTEQRzWJaY4BRCkPZt

Author: waleedlatif1

apps/docs/content/docs/platform/self-hosting/upgrades.mdx

@@ -284,8 +284,9 @@ git checkout <previous-release-tag>
 # Local stack
 docker compose -f docker-compose.local.yml up -d --build
 
-# Ollama stack — same profile you installed with
-docker compose -f docker-compose.ollama.yml --profile gpu up -d --build
+# Ollama stack — the profile you installed with
+PROFILE=gpu  # or cpu
+docker compose -f docker-compose.ollama.yml --profile "$PROFILE" up -d --build
 ```
 
 **Rollback after a schema change** requires restoring the database to the pre-upgrade backup, because migrations are forward-only: