chore: remove Render configs, point docs at VPS domains

README.md

@@ -86,7 +86,6 @@ CI runs these checks on every push. CI also runs coverage gates. `npm run worker
 ## Production notes
 
 - The demo accounts are public and shown on the login page. Change the admin password before you use the app in public.
-- Render's free tier sleeps after about 15 minutes without traffic. The first request then takes 30 to 60 seconds to start. Use a paid plan or a warm-up ping for production.
 - Password reset emails use Resend. Set `RESEND_API_KEY` and verify a sender domain before real users sign up.
 - Work-order search uses a case-insensitive regex. It is correct but does a full scan. It is fine at starter scale.
 - The triage worker must be deployed alongside the API (both compose files ship a `worker` service). Run exactly one API instance: approvals are held in the in-process approval registry, so scaling the API horizontally would split pending approvals across processes.

render.yaml

@@ -1,28 +0,0 @@
-services:
-  - type: web
-    name: workorders-api
-    runtime: node
-    plan: free
-    buildCommand: NODE_ENV=development npm ci && npm run build -w @workorders/shared && npm run build -w backend
-    startCommand: node backend/dist/server.js
-    healthCheckPath: /ready
-    envVars:
-      - key: NODE_ENV
-        value: production
-      - key: TRUST_PROXY_HOPS
-        value: "2"
-      - key: CORS_ORIGIN
-        value: https://workorder.lverma.com
-      - key: APP_URL
-        value: https://workorder.lverma.com
-      # sync: false → values are entered in the Render dashboard at create time
-      - key: MONGODB_URI
-        sync: false
-      - key: JWT_SECRET
-        sync: false
-      - key: COOKIE_SECRET
-        sync: false
-      - key: RESEND_API_KEY
-        sync: false
-      - key: RESEND_FROM
-        value: Work Order Desk <no-reply@mail.lverma.com>