@onlineapps/conn-orch-validator 10.0.0 → 11.0.0

package/templates/business-service/docker-compose.yml

@@ -80,6 +80,23 @@ services:
     mem_limit: 1g
     volumes:
       - .:/app
+      # The runner's OWN conn-runtime, and the reason it is a volume rather than
+      # a second bind mount. `conn-runtime/validation-proof.json` is an assertion
+      # about ONE running instance
+      # (docs/biz/50-lifecycle/validation-responsibilities.md § Data Flow), and
+      # with `.:/app` alone the runner writes it into the directory the SERVICE
+      # reads — measured in api_biz/converter on 2026-09-16, where a proof
+      # produced by a probe schema stood in the place of the service's own.
+      #
+      # ANONYMOUS on purpose: F-RUNNER holds this block and
+      # `oa-sync-template docker-compose.yml` writes this block and nothing else,
+      # so a named volume would reach every service without the top-level
+      # `volumes:` key that declares it and `docker compose config` would refuse
+      # the document. Docker seeds the volume from the IMAGE at that path, which
+      # is why the Dockerfile's development stage creates /app/conn-runtime and
+      # gives it to uid 1000 — without that, docker creates it root-owned and the
+      # runner cannot write it at all.
+      - /app/conn-runtime
     env_file:
       - ./config/env-active/shared.env
       - ./config/env-active/__SERVICE_NAME__.env