{
  // Typechecking for the TEST tree, which the per-package builds exclude because they emit and
  // tests are not shipped. Excluding them from emit is right; excluding them from CHECKING was not,
  // and it hid real drift: tests calling an API with the shape it had two refactors ago still
  // passed, because JavaScript does not care and the assertions happened to survive.
  //
  // `noEmit`, so this is a check and never a build. It runs from `pnpm typecheck` and in CI.
  //
  // WHAT THIS DOES NOT COVER, because "the test tree is typechecked" reads stronger than it is.
  // Around 110 `as never` and 95 `as unknown as` casts predate this config, and `as never` is
  // assignable to every parameter, so `handler(args as never, ctx)` accepts any argument object at
  // all. At those call sites the checking is off. That matters more here than it would elsewhere:
  // the defect this gate found (`InferShape` requiring optional arguments) was found precisely
  // because some tests pass the arguments a real caller passes, and a cast turns that property off.
  //
  // They are not cleaned up here; some are legitimate and the rest are their own change. The
  // enforcement is a ratchet instead, in `packages/core/test/review-typecheck-tests.test.ts`: the
  // count may fall and may not rise.
  "extends": "./tsconfig.base.json",
  "compilerOptions": {
    "noEmit": true,
    "composite": false,
    "declaration": false,
    "declarationMap": false,
    "incremental": false,
    // ES2024 for the tests only. They run on the same Node 22 floor the server does, and a test may
    // reach for a newer built-in to make an assertion precise; `src` stays on ES2023 so nothing
    // ships against a library the runtime floor does not guarantee.
    "lib": ["ES2024"],
    "types": ["node"]
  },
  "include": ["packages/*/src/**/*.ts", "packages/*/test/**/*.ts"]
}