docs: update CHEATSHEET and README for new build/deploy commands

Replace AE_APP_BUILD_MODE=staging references and old docker compose
build-ui instructions with current build-docker-* and deploy-remote-*
Makefile targets.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

CHEATSHEET.md

@@ -4,7 +4,8 @@
 - **Full Rebuild:** `docker compose up -d --build`
 - **Rebuild SvelteKit only:** `docker compose up -d --build ae_app`
 - **Restart API (pick up Python changes):** `docker compose restart ae_api`
-- **Switch Build Mode:** Edit `.env` → `AE_APP_BUILD_MODE=prod` → `docker compose up -d --build ae_app`
+- **Rebuild SvelteKit (local):** `make build-docker-dev` / `build-docker-test` / `build-docker-prod`
+- **Deploy to remote:** `make deploy-remote-test` / `deploy-remote-prod` (SSH → linode.oneskyit.com)
 - **Shut everything down:** `npm run compose:down` (from `aether_app_sveltekit/`)
 
 ## 🛠️ Management Links

README.md

@@ -78,13 +78,24 @@ docker compose restart ae_api  # Restart the FastAPI Backend
 ```
 
 ### Deployment Workflow
-The SvelteKit application is built **inside** the container. You can control the build mode (which bakes in the correct `PUBLIC_` variables) via the `.env` file:
-- Set `AE_APP_BUILD_MODE=staging` for development/testing.
-- Set `AE_APP_BUILD_MODE=prod` for production.
+The SvelteKit application is built **inside** the container using `vite build --mode <env>`, which reads the corresponding `.env.<env>` file for `PUBLIC_` variables.
 
-Then run:
+From `aether_app_sveltekit/`:
 ```bash
-docker compose up -d --build ae_app
+# Build Docker image locally
+npm run build:docker:dev    # uses .env.dev
+npm run build:docker:test   # uses .env.test
+npm run build:docker:prod   # uses .env.prod
+
+# Deploy to remote server (linode.oneskyit.com)
+npm run deploy:remote:test
+npm run deploy:remote:prod
+```
+
+Or via Makefile targets in this directory:
+```bash
+make build-docker-dev
+make deploy-remote-prod
 ```
 
 ---