eust-w ee2fbe9f6a fix: match the Kubernetes baseline to the provisioner and drop stale settings
The base manifests described a design the code does not have: a Role that only
allowed Jobs, an unused sandbox account, a tool gateway that does not exist and
a deployer bound into the sandbox namespace. They now grant exactly what the
provisioner applies and deletes for runs and IDE workspaces, let sandbox pods
reach the API, Temporal and Git through the control namespace's default deny,
and let the IDE gateway reach workspace pods.

- The API reads the runtime image from WF_RUN_WORKER_IMAGE only, the same name
  the provisioner uses; the WF_RUN_IMAGE alias is gone.
- The provisioner takes the public gateway origin from WF_IDE_PUBLIC_URL, which
  is what the gateway and API call it, and refuses to start without an explicit
  WF_DEPLOYMENT_MODE.
- Environments no longer accept a runnerId that was always rejected.
- The Compose acceptance script uses the current Docker context unless
  WF_DOCKER_CONTEXT names one, instead of a hardcoded colima.
- Tests cover waiting reasons and their exits, and the production rejection of
  unsandboxed or unstated verification isolation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 18:01:28 +08:00
..