docs: fix transition steps — compose-based, not docker run

docs/release-notes/v3.5.0.md

@@ -15,27 +15,28 @@ docker run -d --name corescope \
   ghcr.io/kpa-clawbot/corescope:latest
 ```
 
-**Transitioning from a source build?**
+**Transitioning from a source build (docker-compose)?**
 
 ```bash
-# 1. Stop your old container (your data volume is safe)
-docker stop corescope && docker rm corescope
+# 1. Stop and remove the old compose stack
+docker compose down
 
 # 2. Pull the pre-built image
 docker pull ghcr.io/kpa-clawbot/corescope:latest
 
-# 3. Start with your existing data directory
-#    Replace /path/to/your/data with wherever your meshcore.db + config.json live
-docker run -d --name corescope \
-  -p 80:80 -p 1883:1883 \
-  -v /path/to/your/data:/app/data \
-  ghcr.io/kpa-clawbot/corescope:latest
+# 3. Update your docker-compose.yml to use the pre-built image instead of building:
+#    Change:  build: .
+#    To:      image: ghcr.io/kpa-clawbot/corescope:latest
+#    Keep your existing volume mounts and port mappings.
 
-# 4. Verify
+# 4. Start with the pre-built image
+docker compose up -d
+
+# 5. Verify
 curl http://localhost/api/stats
 ```
 
-If you were using a named volume (e.g. `corescope-data`), use `-v corescope-data:/app/data` instead. Your DB, config, and theme are all in `/app/data` — nothing else to migrate.
+Your DB, config, and theme files live in the data volume — nothing to migrate. Just swap the image reference.
 
 Tags: `latest` (stable), `vX.Y.Z` (pinned), `edge` (master tip).