fix: address the fifth review round

- The Ollama upgrade commands ran unprofiled, so Compose would have skipped the
  profile-scoped `ollama` service and left `OLLAMA_URL` pointing at nothing.
  Both commands now carry the install's `--profile`.
- `start` / `stop` / `restart` are only whole-install operations on Compose.
  On a source checkout they manage just the Postgres and Redis containers, and
  on Kubernetes they print kubectl commands rather than acting.

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/docker.mdx

@@ -169,7 +169,7 @@ docker compose -f "$COMPOSE_FILE" up -d --force-recreate simstudio
 | `sim-setup` | The setup wizard. `--quick` skips the prompts, `--dir <path>` picks the directory, `--mode compose\|dev\|k8s` picks the target (`dev` and `k8s` need a source checkout) |
 | `sim-setup status` | Show what is installed and healthy |
 | `sim-setup logs` | Follow logs. On a source checkout it prints where the logs are — the dev server streams in its own terminal — rather than following a stream |
-| `sim-setup start` / `stop` / `restart` | Bring the install up, down, or cycle it |
+| `sim-setup start` / `stop` / `restart` | Bring the install up, down, or cycle it. On a source checkout this covers only the managed Postgres and Redis containers — the dev server is yours to start and stop. On Kubernetes it prints the equivalent `kubectl` commands instead of acting |
 | `sim-setup update` | Pull or rebuild images and apply them. Compose installs only — it refuses on source checkouts and Kubernetes, which update through git and `helm upgrade` |
 | `sim-setup down` | Remove containers, keep the data |
 | `sim-setup reset` | Archive `.env` and wipe managed data |

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

@@ -196,8 +196,10 @@ Inspect the result with `npx sim-setup logs`, which targets whichever Compose fi
 The CLI detects only those two files. An install started from `docker-compose.ollama.yml` is invisible to it — `update`, `logs`, and `status` all report no install — so upgrade that stack directly:
 
 ```bash
-docker compose -f docker-compose.ollama.yml pull
-docker compose -f docker-compose.ollama.yml up -d
+# Same --profile you installed with: gpu or cpu. The Ollama service is
+# profile-scoped, so an unprofiled command silently skips it.
+docker compose -f docker-compose.ollama.yml --profile gpu pull
+docker compose -f docker-compose.ollama.yml --profile gpu up -d
 ```
 
 <Callout type="warn">