chore(repo): clear dead files from the repo root

.gitignore

@@ -11,8 +11,22 @@ node_modules
 
 .env
 
-.vscode/
-.idea/
+.vscode
+.idea
+
+# Empty files once committed at the root. No trailing slash, so a FILE of
+# the name is ignored too.
+/.bashrc
+/.bash_profile
+/.zshrc
+/.zprofile
+/.profile
+/.gitconfig
+/.ripgreprc
+/config
+/hooks
+/objects
+/refs
 
 build/
 dist/

docs/deployment/DEPLOYMENT.md

@@ -113,11 +113,7 @@ Notes:
 - The repository also ships `.env.example` with these local defaults; `./dev.sh up` will create `.env` from it automatically if missing.
 - AI keys are optional for boot. If `GEMINI_API_KEY`, `OPENAI_API_KEY`, and `OPENROUTER_API_KEY` are all unset, the app still starts but AI-backed features will stay limited until you add a key and restart.
 
-2. Download the CA certificate only if you are using external PostgreSQL:
-
-```bash
-node download-ca.js
-```
+2. Only if you are using external PostgreSQL with SSL: put your provider's CA certificate at `./ca.pem` and set `PG_SSL_ENABLED=true`. `docker-compose.yml` mounts that file at `/app/ca.pem`, the path it sets as `PG_SSL_CA_PATH`.
 
 ### Step 3: Build and Start the Containers
 
@@ -168,10 +164,7 @@ Note: In development, the backend container will install dependencies on first b
 
 2. Place the `.env` file in the project root directory.
 
-3. Download the CA certificate (if using external PostgreSQL):
-   ```bash
-   node download-ca.js
-   ```
+3. If you use external PostgreSQL with SSL, put your provider's CA certificate at `./ca.pem` and set `PG_SSL_ENABLED=true`. `docker-compose.yml` mounts that file at `/app/ca.pem`, the path it sets as `PG_SSL_CA_PATH`.
 
 ### Step 3: Configure HTTPS (Optional but Recommended)
 

docs/runbooks/domain-migration-commonly-me.md

@@ -38,8 +38,10 @@ Move the dev cluster's public surface from `app-dev` / `api-dev` to the apex
   `backendUrl`, ingress `hosts.{frontend,backend,litellm}.host`, and
   `cloudflared.hostnames` (also deduped a repeated `api-dev` entry and dropped a
   stray `app.commonly.me`).
-- `.github/workflows/deploy-dev.yml` + `cloudbuild.frontend.yaml` —
-  `REACT_APP_API_URL=https://api.commonly.me` (frontend build arg).
+- `.github/workflows/deploy-dev.yml` —
+  `REACT_APP_API_URL=https://api.commonly.me` (frontend build arg). At the
+  time `cloudbuild.frontend.yaml` carried the same arg; that file was removed
+  in #2861, since Deploy Dev builds every image.
 - `backend/server.ts` — CORS fallback default + a doc comment.
 - `frontend/src/v2/components/V2AgentBYO.tsx` — BYO snippet API-URL fallback.
   (The hostname-derivation regex correctly falls through to this fallback for
@@ -92,6 +94,6 @@ Move the dev cluster's public surface from `app-dev` / `api-dev` to the apex
   add the old hosts back as ingress `aliases` on each service and keep them in
   `cloudflared.hostnames` until step 5 — say the word and I'll prepare that shape.
 - **Pre-existing (not from this branch):** `cloudbuild.frontend.yaml` line 19
-  hard-codes a GCP project id + AR path in the public repo. Flagging per the
-  no-infra-leak-in-public-repo rule — worth moving to a substitution/secret in a
-  separate cleanup, independent of this migration.
+  hard-coded a GCP project id + AR path in the public repo, against the
+  no-infra-leak-in-public-repo rule. Resolved: the file now uses
+  substitutions, and was then removed in #2861.