chore(compose): enable toolchain matching in the personal compose files

ROBOCO_TOOLCHAIN_MATCH_ENABLED on (default true, .env-overridable) in the
orchestrator env of docker-compose.yml + docker-compose.yaml only;
docker-compose.registry.yml is intentionally left off so the published default
stays conservative until live-verified.
This commit is contained in:
Renn F
2026-06-22 03:02:26 +02:00
parent 8b20afbc33
commit e4b6c8bdfd
2 changed files with 14 additions and 0 deletions
+7
View File
@@ -342,6 +342,13 @@ services:
ROBOCO_SELF_HEAL_ORIGINATE_ENABLED: ${ROBOCO_SELF_HEAL_ORIGINATE_ENABLED:-false}
ROBOCO_SELF_HEAL_PROJECT_SLUG: ${ROBOCO_SELF_HEAL_PROJECT_SLUG:-roboco-api}
ROBOCO_SELF_HEAL_CI_WORKFLOW: ${ROBOCO_SELF_HEAL_CI_WORKFLOW:-ci.yml}
# Agent runtime toolchain matching: provision each agent workspace with
# the TARGET project's Python (uv resolves requires-python) and block a
# delivery gate when the suite can't be executed instead of passing on a
# source read. Config default is OFF; enabled HERE (personal deploy) but
# deliberately left OFF in docker-compose.registry.yml so the published
# default stays conservative until it's verified on a live run.
ROBOCO_TOOLCHAIN_MATCH_ENABLED: ${ROBOCO_TOOLCHAIN_MATCH_ENABLED:-true}
volumes:
# Docker socket - allows spawning agent containers
- /var/run/docker.sock:/var/run/docker.sock