mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Jordan Ritter
e88d01a99f
The prod `harness-workers` fleet worker (serviceId c2aa8a0b-350e-4b76-8541-3012dfac41d0, instance 7c48ee43-6df4-457b-b977-10f1f1ac1680) runs the shared `showcase-harness` image (`imageOf: "harness"`) but had NO `prod` env entry in the railway-envs SSOT. `expandImageConsumers` is env-aware — a consumer only joins an env's redeploy scope if it declares that env — so a rebuilt `showcase-harness:latest` bounced the prod control-plane but SILENTLY SKIPPED the prod worker, leaving it pinned to a stale 2026-06-19 image. That stale worker image carries a 1-demo `registry.json` for `ms-agent-harness-dotnet` (only `beautiful-chat`), so the hourly `e2e_demos` driver running on it produced only 1 of 39 `e2e:` rows in prod PocketBase. The other 38 feature rows were absent → `resolveD3` exists=false → `UI` badge omitted → broken D3 rung → D0. Backfill the live prod worker as a `prod` env entry (real serviceInstance ID), flip `gateIgnore` off, and set `gateValidated: true` so the env-aware `imageOf` expansion now pulls the prod worker into the prod redeploy scope on every `showcase-harness` rebuild. Regenerate the emitted JSON + golden fixture and update the two gate-count assertions accordingly.