Jordan Ritter 3f62cd45e6 fix: validate aimock fixtures at load time to prevent runtime 500s ...

Follow-up to #3971. aimock supports fixture schema validation at startup via
--validate-on-load, but it's opt-in. The showcase Dockerfile did not pass
the flag, so fixtures with unrecognized response keys (e.g. "text" instead
of "content") loaded silently and only failed at request time with HTTP 500.
That's what crashed crewai-crews on startup.

Changes:
- showcase/aimock/Dockerfile: pass --validate-on-load so broken fixtures
  fail the container boot, not individual requests.
- showcase/scripts/__tests__/aimock-fixtures.test.ts: new vitest spec that
  loads feature-parity.json and smoke.json via @copilotkit/aimock's
  loadFixtureFile + validateFixtures and asserts zero errors. Runs as part
  of the existing showcase-validate CI workflow.
- showcase/scripts/package.json: add @copilotkit/aimock dependency for the
  validator import.

Verified red-green: with the pre-#3971 broken "text" fixtures, validateFixtures
flags 5 errors; post-#3971 it returns zero. Docker red-green: container with
an intentionally broken fixture fails to start with "Validation failed: 1
error(s)" and non-zero exit.

2026-04-16 12:32:24 -07:00

..

Dockerfile

fix: validate aimock fixtures at load time to prevent runtime 500s

2026-04-16 12:32:24 -07:00

feature-parity.json

fix(aimock): use valid response schema for broken fixtures, unblock crewai-crews

2026-04-16 12:06:41 -07:00

smoke.json

feat: add aimock proxy for showcase smoke checks

2026-04-09 13:53:58 -07:00