chore: production values live in platform; drop the production compose

.graphite.yml

@@ -28,9 +28,7 @@ projects:
 
       # kind: compose
       # host: my-project.project-graphite.com # <label>.project-graphite.com
-      # source: { file: compose.production.yaml, service: web, port: 80 }
-      # secrets: [SECRET_KEY] # UPPER_SNAKE_CASE[]
 
       # kind: pages
       # host: my-project.project-graphite.com # <label>.project-graphite.com
-      # source: { directory: web, output: dist }
+      # source: { directory: web, output: dist, command: npm run build }

README.md

@@ -34,22 +34,24 @@ Delete this section once the checklist is done.
    `lint`, `test`, and `build` scripts. A folder with a `Makefile` must provide `install`, `lint`, and
    `test` targets.
 4. Update `compose.yaml` for local development, with its bind mounts, hot reload, and development
-   ports. Update `compose.production.yaml` to pull the prebuilt GHCR images,
-   define health checks and persistent volumes, avoid published host ports, and cap CPU and memory.
-5. Add a screenshot or short GIF, the eventual live link, the stack, and clear local instructions
+   ports.
+5. For a `compose` deploy, open a pull request in `platform` adding `deploy/<slug>/values.yaml`:
+   the production services, health checks, volumes, resource limits and the names of its secrets.
+   Ask an organisation owner to add the secret values. Merging the values deploys it.
+6. Add a screenshot or short GIF, the eventual live link, the stack, and clear local instructions
    to this README.
 
 Use named service folders even for a single-service project. Images are published as
-`ghcr.io/project-graphite/<repo>/<service>`, and each image name must match its service in the
-production Compose file.
+`ghcr.io/project-graphite/<repo>/<service>`, and each one is a service of the same name in the
+project's platform values.
 
 `.github/workflows/pipeline.yml` runs the shared `reusable-pipeline.yml`. Turn a stage off with its
 switch, e.g. `with: { changelog: false }`, or replace the file with calls to the individual shared
 workflows.
 
 Until the platform entry is merged, the `Deploy` job on `main` fails with a clear message. Builds
-and checks continue. Once the repository has the `COOLIFY_WEBHOOK` and `COOLIFY_TOKEN` secrets, the
-same job deploys to Coolify.
+and checks continue. After that, each `main` push records its image tag in `platform`, which
+deploys it.
 
 ## Conventions