archetech / archon / 24314580013

95%

main: 89%

push

github

Select gatekeeper flavor via include: in docker-compose.yml

Make the active gatekeeper implementation explicit at the top of
docker-compose.yml instead of hardcoded deep in the service block.

- Move the gatekeeper service definition entirely out of docker-compose.yml
  and into two self-contained flavor files. Compose's include: directive
  treats same-named services across included files as a conflict, so
  each flavor file carries the full service body (env, ports, healthcheck,
  volumes, depends_on). The two files stay in sync via a comment header.
- docker-compose.yml now has
    include:
      - ${GATEKEEPER_COMPOSE_FILE:-docker-compose.gatekeeper-ts.yml}
  which defaults to the TypeScript gatekeeper and accepts an override to
  run the Rust port.
- start-node-ci exports GATEKEEPER_COMPOSE_FILE based on its second arg
  (rust | typescript), so the CLI test matrix in docker-build-test.yml
  can flip flavors without touching COMPOSE_FILE layering.
- Rename Dockerfile.gatekeeper -> Dockerfile.gatekeeper-ts and the two
  flavor compose files to docker-compose.gatekeeper-{ts,rust}.yml so all
  four gatekeeper artefacts share the same naming pattern.
- Update docker-build.yml, docker-publish.yml, release-publish.yml, and
  SECURITY_AUDIT.md for the renamed Dockerfile.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

1990 of 2192 branches covered (90.78%)

Branch coverage included in aggregate %.

4231 of 4345 relevant lines covered (97.38%)

1167.44 hits per line