scripts/ holds the cutover and rollback tooling and its own test suite at scripts/__tests__/cutover.test.ts, but it is not a workspace package: pnpm-workspace.yaml lists only apps/* and packages/*. Three consequences follow, and all of them are invisible.
Nothing in CI runs those tests. pnpm test is turbo run test, which runs per-package tasks only. The root vitest.config.ts is the sole config whose include covers scripts/__tests__/**, and it is wired to no turbo task. .github/workflows/ci.yml runs pnpm test. So that suite is green-by-absence and breaks only for someone who happens to run vitest at the repo root.
That is not hypothetical — it already happened. Routing execute-cutover.ts through isShadowMode() in #233 made all 15 tests in that file fail to collect, and CI stayed green throughout. It was found by running the root config by hand.
Nothing typechecks them either. scripts/tsconfig.json is detached from pnpm typecheck the same way.
Resolution needs a workaround. Because pnpm does not hoist and scripts/ has no manifest of its own, there is no node_modules/@copilotkit for it to resolve through. #233 works around it by adding @copilotkit/outpost to the ROOT manifest and aliasing the specifier to source in the root vitest.config.ts. That is a workaround for the missing package boundary rather than a fix.
Worth knowing: npx tsx scripts/cutover/execute-cutover.ts — the invocation documented at the top of that file — already fails on @prisma/client for the same reason, so the script's runtime path is broken independently of its tests.
Shape of a fix
Give scripts/ a package.json with its own test and typecheck scripts, add it to pnpm-workspace.yaml, and declare its real dependencies (@copilotkit/outpost, @prisma/client) there instead of on the root. turbo run test then picks the suite up like any other package, the root-manifest dependency and the vitest alias added in #233 can both come back out, and the documented tsx invocation starts working.
The cutover scripts are the tooling that turns shadow mode off in production, so they are a poor choice for the one corner of the repo CI does not look at. Related: #261 covers those scripts reporting success while the flag is still engaged — the missing coverage here is why that went unnoticed.
scripts/holds the cutover and rollback tooling and its own test suite atscripts/__tests__/cutover.test.ts, but it is not a workspace package:pnpm-workspace.yamllists onlyapps/*andpackages/*. Three consequences follow, and all of them are invisible.Nothing in CI runs those tests.
pnpm testisturbo run test, which runs per-package tasks only. The rootvitest.config.tsis the sole config whoseincludecoversscripts/__tests__/**, and it is wired to no turbo task..github/workflows/ci.ymlrunspnpm test. So that suite is green-by-absence and breaks only for someone who happens to run vitest at the repo root.That is not hypothetical — it already happened. Routing
execute-cutover.tsthroughisShadowMode()in #233 made all 15 tests in that file fail to collect, and CI stayed green throughout. It was found by running the root config by hand.Nothing typechecks them either.
scripts/tsconfig.jsonis detached frompnpm typecheckthe same way.Resolution needs a workaround. Because pnpm does not hoist and
scripts/has no manifest of its own, there is nonode_modules/@copilotkitfor it to resolve through. #233 works around it by adding@copilotkit/outpostto the ROOT manifest and aliasing the specifier to source in the rootvitest.config.ts. That is a workaround for the missing package boundary rather than a fix.Worth knowing:
npx tsx scripts/cutover/execute-cutover.ts— the invocation documented at the top of that file — already fails on@prisma/clientfor the same reason, so the script's runtime path is broken independently of its tests.Shape of a fix
Give
scripts/apackage.jsonwith its owntestandtypecheckscripts, add it topnpm-workspace.yaml, and declare its real dependencies (@copilotkit/outpost,@prisma/client) there instead of on the root.turbo run testthen picks the suite up like any other package, the root-manifest dependency and the vitest alias added in #233 can both come back out, and the documentedtsxinvocation starts working.The cutover scripts are the tooling that turns shadow mode off in production, so they are a poor choice for the one corner of the repo CI does not look at. Related: #261 covers those scripts reporting success while the flag is still engaged — the missing coverage here is why that went unnoticed.