rbe-west's pool workers run gascity main's tools/rbe/worker-env and
advertise its pin; the schedulers match //platforms:rbe_worker's pin
exactly. When gascity re-pins and beads' copy falls behind, every remote
action queues until the lanes time out, and the only check ran nightly
with no notification (review finding S1).
- bazel.yml's rbe job: after decide, only when the lanes execute remotely
(enabled: modes remote, fork-ro, fork-rw; merge groups are remote), a
sparse checkout of tools/rbe and platforms and tools/rbe/worker-env-sync
main. Out of step fails the job, so every lane skips and pr.yml's gate is
red within a minute, with the diff and the pin to commit in the summary.
No fallback to mode cache: pr.yml's ci-gate requires a remote run
(BAZEL_REMOTE), so it would be just as red, only slower. gascity
unreachable warns and proceeds. The steps set no output; the job's
outputs stay decide's.
- worker-env-sync: exit 1 only for out of step, exit 2 (warning) when it
cannot compare (ERR trap; curl timeouts), WORKER_ENV_SYNC_REPORT copies
the markdown report.
- nightly.yml: top-level permissions contents: read; rbe-worker-env-sync
gets issues: write and, on exit 1, tools/rbe/worker-env-sync-issue opens
a ci/infra issue with the report or updates the open one (body + comment
linking the run). GITHUB_TOKEN is in that one step.
- Policy tests: TestBazelRBEWorkerEnvPreflight (shape + the step's script
run in step / out of step / unreachable), TestNightlyWorkerEnvSyncOpensIssue
(permissions, token scope, rc output, issue create/update via a stub gh),
TestRBEWorkerEnvSync (exit codes, report); rbe job step and checkout
counts updated.
Agent-Signature: claude-code-claude-opus-5-5-medium on behalf of Julian Knutsen
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>