mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Jordan Ritter
da03e1626a
The pool-fleet worker's Railway service is named `harness-workers` (PLURAL), but the SSOT keyed it `showcase-harness-worker` (singular). The image-ref gate matches SSOT keys to Railway service names verbatim, so the gate reported `harness-workers` as an untracked Railway service AND the stale singular key matched nothing. Rename the SSOT key (and every test/fixture reference) to the exact Railway name `harness-workers`. It stays the staging-only, domainless, probe-disabled worker that runs the shared `showcase-harness` image: serviceId c2aa8a0b-…, staging instance 362c1e37-…, ciBuilt:false, gateIgnore:true, no build slot (so no dispatchName), single `staging` env with no domain. Add a focused test pinning that shape. Counts are unchanged (29 services / 26 CI_BUILT) — this is a rename, not an addition; both harness workers already existed on main. Verified LOCALLY against Railway: verify-railway-image-refs reports `54 env-scoped instances verified (2 skipped)` — 0 violations, 0 missing, 0 untracked (harness-workers reconciled, harness-workers + harness-legacy the 2 gateIgnore'd skips). emit --check zero drift, Ruby parity green (borrowed .up.railway.app host is parity-excluded), full scripts suite + typecheck green.