chore(type-check): retire the narrow typetests projects in graduated packages (#4291) (#4345)

`tsconfig.typetests.json` is the objectui#3181 rescue hatch: a package whose
test tree was still in `check-type-check-coverage.mjs`'s TEST_DEBT could
compile the one file whose whole value is compile-time assertions, instead of
waiting for its whole backlog. As #4040's tranches landed full
`tsconfig.test.json` projects, the hatch went redundant wherever the package
graduated — the full project already compiles the same file, so the repo
carried two spellings of what gets compiled plus one extra tsc per run.

Retired in auth, plugin-chatbot, plugin-detail, plugin-form, plugin-grid and
plugin-list, each with its `type-check` chain entry. Per package, the full
project's `--listFiles` was checked to contain the exact file the narrow
project named, and a provably-false `Assert` appended to that file turned the
FULL project red (TS2344, exit 2) — the coverage moved rather than vanished.
app-shell, components, core and react are still in TEST_DEBT and keep theirs.

The gate now makes this a ratchet rather than a one-time sweep: a narrow
project on a package whose full test project already compiles everything is
reported as redundant, so the seventh cannot reappear. Section 5½ had no test
coverage at all — the gate keeping the rescue hatch honest was itself
unchecked — so it gains a fixture suite plus a real-repository pin.

Refs #4040, #3032, objectstack-ai/objectstack#4118


Claude-Session: https://claude.ai/code/session_017Qqyix2QcnpUC9XeYVDzx3

Co-authored-by: Claude <noreply@anthropic.com>

Author: yinlianghui

.changeset/retire-narrow-typetests-projects-4291.md

@@ -0,0 +1,12 @@
+---
+---
+
+Retire the narrow `tsconfig.typetests.json` projects in the six packages that have graduated out of `TEST_DEBT`
+
+`tsconfig.typetests.json` is a rescue hatch (objectui#3181): a package whose test tree was still in `scripts/check-type-check-coverage.mjs`'s `TEST_DEBT` could compile the one file whose whole value is compile-time assertions — `Assert< Equal< Local, Spec > >` is a `tsc` error or it is nothing — instead of waiting for its whole backlog to compile. As objectui#4040's tranches landed full `tsconfig.test.json` projects, that hatch became redundant in the packages that graduated: the full project already compiles the same file, so the repo carried two spellings of what gets checked plus one extra `tsc` per `type-check` run.
+
+Retired in `@object-ui/auth`, `@object-ui/plugin-chatbot`, `@object-ui/plugin-detail`, `@object-ui/plugin-form`, `@object-ui/plugin-grid` and `@object-ui/plugin-list`, each with its `type-check` chain entry. For every one, `tsc -p tsconfig.test.json --listFiles` was checked to contain the exact file the narrow project named, and a provably-false `Assert` appended to that file turned the FULL project red (TS2344, exit 2) — so the coverage moved rather than vanished. The four packages still in `TEST_DEBT` that have a narrow project (`app-shell`, `components`, `core`, `react`) keep theirs untouched.
+
+`scripts/check-type-check-coverage.mjs` now makes this a ratchet rather than a one-time sweep: a `tsconfig.typetests.json` on a package whose full test project already compiles everything is reported as redundant, so the seventh cannot reappear. Section 5½ had no test coverage at all before this change — the gate keeping the rescue hatch honest was itself unchecked — so it gains a fixture suite plus a real-repository pin on the six retirements.
+
+No published behaviour changes: only `type-check` scripts, checking-only tsconfig projects, test-file comments and a CI gate.

packages/auth/package.json

@@ -30,7 +30,7 @@
     "build": "tsc",
     "clean": "rm -rf dist",
     "test": "vitest run",
-    "type-check": "tsc --noEmit && tsc -p tsconfig.typetests.json && tsc -p tsconfig.test.json",
+    "type-check": "tsc --noEmit && tsc -p tsconfig.test.json",
     "lint": "eslint ."
   },
   "peerDependencies": {

packages/auth/tsconfig.test.json

@@ -4,12 +4,15 @@
   // the build correctly keeps tests out of `dist`, but nothing else compiled
   // them, so a test could assert a contract the compiler never checked.
   //
-  // `tsconfig.typetests.json` next door is the narrow rescue this supersedes for
-  // this package: it compiles `auth-spec-parity.test.ts` alone, because that one
-  // file's whole value is compile-time assertions and it could not wait for the
-  // rest of the tree to compile (objectui#3181). It stays chained — the file is
-  // now read by both projects, which costs one extra compile and keeps the
-  // narrow project's reasoning where it was written.
+  // This project is now the ONLY one that compiles `auth-spec-parity.test.ts`,
+  // whose whole value is compile-time assertions (objectui#3181). It used to be
+  // rescued by a narrow `tsconfig.typetests.json` next door, which named that one
+  // file while the rest of the tree was still in TEST_DEBT; the package graduated
+  // in objectui#4040 and the narrow project was retired in objectui#4291, after
+  // `--listFiles` showed this project reads the same file and a provably-false
+  // `Assert` appended to it turned this project red. Keep the file compiling
+  // here: those assertions are erased at runtime, so vitest proves nothing
+  // about them and `tsc` is the only thing that can.
   "extends": "../../tsconfig.json",
   "compilerOptions": {
     "noEmit": true,

packages/auth/tsconfig.typetests.json

@@ -27,7 +27,7 @@
     "build": "vite build",
     "test": "vitest run",
     "test:watch": "vitest",
-    "type-check": "tsc --noEmit && tsc -p tsconfig.typetests.json && tsc -p tsconfig.test.json",
+    "type-check": "tsc --noEmit && tsc -p tsconfig.test.json",
     "lint": "eslint ."
   },
   "dependencies": {

packages/plugin-chatbot/package.json

@@ -205,7 +205,8 @@ describe('the vendored directory stays vendored', () => {
 
 /* -------------------------------------------------------------------------- */
 /* Compile-time pins. A violation is a `tsc` error, not a runtime failure.      */
-/* Compiled by this package's `tsconfig.typetests.json` (objectui#3181).       */
+/* Compiled by this package's `tsconfig.test.json` (objectui#3181; the narrow  */
+/* project that named this file alone was retired in objectui#4291).           */
 /* -------------------------------------------------------------------------- */
 
 type Assert<T extends true> = T;

packages/plugin-chatbot/src/__tests__/spec-symbol-batch6.test.ts

@@ -4,12 +4,15 @@
   // the build correctly keeps tests out of `dist`, but nothing else compiled
   // them, so a test could assert a contract the compiler never checked.
   //
-  // `tsconfig.typetests.json` next door is the narrow rescue this supersedes for
-  // this package: it compiles `spec-symbol-batch6.test.ts` alone, because that
-  // one file's whole value is compile-time assertions and it could not wait for
-  // the rest of the tree to compile (objectui#3181). It stays chained — the file
-  // is now read by both projects, which costs one extra compile and keeps the
-  // narrow project's reasoning where it was written.
+  // This project is now the ONLY one that compiles `spec-symbol-batch6.test.ts`,
+  // whose whole value is compile-time assertions (objectui#3181). It used to be
+  // rescued by a narrow `tsconfig.typetests.json` next door, which named that one
+  // file while the rest of the tree was still in TEST_DEBT; the package graduated
+  // in objectui#4040 and the narrow project was retired in objectui#4291, after
+  // `--listFiles` showed this project reads the same file and a provably-false
+  // `Assert` appended to it turned this project red. Keep the file compiling
+  // here: those assertions are erased at runtime, so vitest proves nothing
+  // about them and `tsc` is the only thing that can.
   "extends": "../../tsconfig.json",
   "compilerOptions": {
     "noEmit": true,

packages/plugin-chatbot/tsconfig.test.json

@@ -27,7 +27,7 @@
     "build": "vite build",
     "test": "vitest run",
     "test:watch": "vitest",
-    "type-check": "tsc --noEmit && tsc -p tsconfig.typetests.json && tsc -p tsconfig.test.json",
+    "type-check": "tsc --noEmit && tsc -p tsconfig.test.json",
     "lint": "eslint ."
   },
   "dependencies": {

packages/plugin-chatbot/tsconfig.typetests.json

@@ -46,8 +46,9 @@ describe('FeedFilterMode is the spec enum, at runtime as well as in types', () =
 });
 
 /* -------------------------------------------------------------------------- */
-/* Compile-time pins — compiled by tsconfig.typetests.json, chained off        */
-/* "type-check" (this package's test tree is still in TEST_DEBT).              */
+/* Compile-time pins — compiled by tsconfig.test.json, chained off             */
+/* "type-check" (objectui#4291 retired the narrow project that named this      */
+/* file alone, once the package left TEST_DEBT in objectui#4040).              */
 /* -------------------------------------------------------------------------- */
 
 type Assert<T extends true> = T;