copilotkit__copilotkit

mirror of https://github.com/CopilotKit/CopilotKit.git synced 2026-09-14 16:26:20 +08:00

Files

T

History

Jordan Ritter 0809c25dac chore(showcase): remove redundant harness-legacy service from SSOT and fixtures

The pool-fleet migration is complete: the control-plane harness plus the
prod workers (deployed 2026-06-19, HARNESS_ROLE=worker, pool count 2) now
cover every probe dimension the interim `harness-legacy` fleet-migration
bridge was holding live, so `harness-legacy` is dead config.

This is the code-side cleanup only:
- Remove the `harness-legacy` entry from the railway-envs SSOT and the
  now-dead `key === "harness-legacy"` special-case in computePromoteClosure.
- Regenerate railway-envs.generated.json (41 -> 40 services).
- Drop harness-legacy from the golden snapshot, the gateIgnore expectation
  sets, the promote-notify fixtures, and the redeploy-env doc comments;
  update the service-count assertions (41 -> 40).
- Fix the stale "STAGING-ONLY" harness-workers comment: prod workers are
  live on Railway, though this SSOT entry still models the staging
  instance only (no prod env backfilled here yet).

The live Railway `harness-legacy` service is torn down separately as a
follow-up infra step.

2026-06-23 17:05:26 -07:00

parity

feat(showcase/scripts): add validate-parity.ts demo/spec/qa parity validator

2026-04-17 22:34:40 -07:00

pin-drift

feat(showcase): replace starters/ with on-demand extract-starter

2026-04-28 07:50:39 -07:00

pins

feat(showcase/scripts): add validate-pins.ts pin-drift validator

2026-04-17 22:34:18 -07:00

invalid-genui-manifest.yaml

fix(showcase): complete open-gen-ui scrub — 5→4 count, schema enum, fixture, full regen