THROTTLED tracker — the nightly-integration workflow is installed + active here, but the first-wave autonomous build is intentionally paced (no @claude mention yet) to avoid a fleet-wide build storm. Tonight's nightly will find this issue and no-op.
When scheduled (deliberately, a few repos at a time), this becomes the build contract:
- devops-engineer — vendor FuzeInfra submodule +
docker-compose.consumer-test.yml + versions.env + the mock matrix; no prod egress.
- test-engineer — integration/contract suite (
test:integration or pytest -m integration).
- local-env-verifier — verify the boundary.
The orchestrator will add the @claude mention to kick the build when its turn comes.
THROTTLED tracker — the nightly-integration workflow is installed + active here, but the first-wave autonomous build is intentionally paced (no
@claudemention yet) to avoid a fleet-wide build storm. Tonight's nightly will find this issue and no-op.When scheduled (deliberately, a few repos at a time), this becomes the build contract:
docker-compose.consumer-test.yml+versions.env+ the mock matrix; no prod egress.test:integrationorpytest -m integration).The orchestrator will add the
@claudemention to kick the build when its turn comes.