fix(metadata): repair the 89 hidden test-type errors and wire a typecheck script

[os-musk]

Fixes #14342

packages/metadata/tsconfig.json declared a program over src/**/* — every test file included — while package.json declared no typecheck script, so turbo run typecheck never selected the package and nothing ever ran that program. Run it and it did not compile: 89 errors across 12 test files, all pre-existing, checked by nothing.

Route ruled by precedent on the card, not by fresh judgement: PR #13978 took exactly this for the sibling @objectstack/metadata-protocol and it landed. Option 2 (excluding **/*.test.ts) was refused there and is refused here — it buys an honest config by giving up the coverage, against this repo's declared = enforced direction. The 89 are repaired, never ledgered (test-typecheck-debt.json is shrink-only and maintainer-only, per #5286).

Head sha: ef901e559. Every number below was measured on b195676a7, the implementation commit, after the last commit of that round; ef901e559 is the patch round at the bottom of this body and touches only two comments, with the readings it re-took listed there.

Re-measured composition, and where the card's summary was wrong

Baseline on this branch's base (7085f9053), dependency closure built first (pnpm --filter '@objectstack/metadata^...' build, exit 0), then tsc --noEmit -p packages/metadata/tsconfig.json:

     33 error TS7006
     30 error TS2345
     25 error TS2835
      1 error TS6133

89 exactly, across the same 12 files the card tabulates, per-file counts identical. The card calls these "the two mundane kinds"; there are four codes and the ledger's own note already knew of a third family (TS2345 x30).

The interesting part is what happened after the config tier was repaired. Fixing only the 25 TS2835 took the pile from 89 to 52:

     30 error TS2345
     20 error TS2322      (NEW, absent from the 89)
      1 error TS6133
      1 error TS18048     (NEW, absent from the 89)

All 33 TS7006 dissolved — they were the cascade off the unresolved imports, not noise this package owed — while 21 errors the 89 had never contained appeared. So the true code tier was 51, not the 30 the ledger recorded. This is the ledger's own standing lesson ("a config-tier count is an upper bound on nothing: fix the config first, then read the residue"), measured a second time; @objectstack/rest is the first, and its TS18048 x13 is the same class of exposure.

The three repair families

1. TS2835 x25 — the codemod (12 files). Relative imports wanting an explicit .js extension under node16 resolution. Applied from tsc's own diagnostics, and each rewrite was cross-checked against tsc's suggested specifier before being written; the script threw rather than writing on any mismatch. Verified from the diff that every one of the 25 changed lines is a relative specifier — no @objectstack/*, no vitest, no node:* import was touched.

2. TS2345 x30 — one shared fixture, fixed once. All 30 are the same mock PluginContext literal in metadata.test.ts (571 through 908), and tsc names the whole defect: is missing the following properties from type 'PluginContext': registerServiceFactory, getServiceScoped. Both are required members of PluginContext in @objectstack/core; both were added as inert vi.fn() stubs to the single createMockPluginContext factory, closing all 30 call sites at one site. The stubs are provably inert here — neither member is referenced anywhere in this package's sources. No assertion moved, no as any, no widening of the parameter type.

3. TS2322 x20 + TS18048 x1 + TS6133 x1 — the residue the config repair exposed. The 20 TS2322 are one shape twenty times over: (evt) => arr.push(evt) passed to subscribe, whose callback return type is the union of void and a void-resolving Promise (spelled without angle brackets here so the body sanitizer cannot eat the type argument). Array.prototype.push returns number, and TypeScript's void-return assignability rule does not forgive that here because the target is that union rather than bare void. Brace-wrapping the concise body ((evt) => { arr.push(evt); }) is behaviour-identical — subscribe discards the return value either way — and it is the smallest edit that stops the value escaping into the slot. Plus one possibly-undefined read (diffResult.patch!.length, a non-null assertion, which is this package's existing convention in tests and which no rule in eslint.config.mjs forbids) and one unused type import removed.

⛔ No non-test source file under src/ was touched, in any family.

The deliverable's proof

$ pnpm --filter @objectstack/metadata typecheck
> @objectstack/metadata@17.2.0 typecheck /home/user/objectstack-issue-14342/packages/metadata
> tsc --noEmit
TYPECHECK_EXIT=0

The script name is echoed, so this is not a zero-match --filter run exiting 0 having run nothing.

The program really holds the tests. tsc --noEmit --listFiles over the package: 43 of 43 *.test.ts files on disk are in the program, none missing — including src/loaders/filesystem-loader-keyed-items.test.ts, the pin file that landed after the card was written, which is clean. A typecheck that excludes the files it advertises is the exact failure mode this gate family exists for, so it is measured rather than assumed.

The gate now bites (reverse verification, not an ablation). Reverting exactly one .js extension this PR added:

HEAD blob:      53c521a78e0b2eb32d9795144ebbaabbc4b73ce7
anchor with .js : 1 then 0   (injected extensionless: 1)
post-mutation:  cef0663218dc1198f97732b593a993a3dd74889b
MUTATED_TYPECHECK_EXIT=2
src/utils/lru-cache.test.ts(4,26): error TS2835: Relative import paths need explicit file extensions ...
post-restore:   53c521a78e0b2eb32d9795144ebbaabbc4b73ce7
git diff HEAD -- target: EMPTY

The mutation was proved on disk before the run (anchor counts both directions, plus a blob hash differing from HEAD), and the restore is proved by reproducing the HEAD blob hash exactly, not by an exit code. No rebuild leg is owed or claimed: tsc reads this package's own src/ directly, so no dist/ sits between the mutation and the measurement — only the dependency closure is dist-resolved, and it was neither mutated nor restored.

Turbo selection

turbo run typecheck --filter @objectstack/metadata --dry-run=json now emits the task:

"taskId": "@objectstack/metadata#typecheck", "command": "tsc --noEmit"

And the root pnpm typecheck (turbo run typecheck) has 79 #typecheck tasks, @objectstack/metadata#typecheck among them. Both readings taken on b195676a7.

Ledger update, by the gate's own path

check:type-check-coverage names the remedy itself, and it was followed rather than invented. With the script added but the row still present:

• @objectstack/metadata: declares `typecheck` but still has a DEBT entry -- it graduated;
  delete its entry from DEBT in scripts/check-type-check-coverage.mjs.

The DEBT preamble prescribes the same thing in prose ("fix (or config-fix) its errors, add a typecheck script, and delete its entry here in the same PR"). So the row was deleted, not hand-lowered to 0 — --lower writes a measured number back for an entry that still stands, and this one graduated. A graduation note recording the 89 to 52 measurement was added to the DEBT preamble, matching the convention the rest / plugin-security / trigger-record-change notes established.

After:

check-type-check-coverage: OK — 70/79 workspace packages type-checked (plus the root),
9 in the DEBT ledger (216 frozen raw errors), 1 exempt.

Was 69/79 covered, 10 entries, 305 frozen raw errors. ⛔ No test-typecheck-debt.json entry was added: this package's tsconfig hides no tests, so it was never in TEST_DEBT's hole, and that ledger is shrink-only and maintainer-only anyway.

skip-changeset — measured, not assumed

The label is applied, on the rule the workflow states for itself ("this PR declares no release of its own"). Measurement rather than reasoning:

• packages/metadata/tsup.config.ts declares four entries (src/index.ts, src/node.ts, src/migrations/index.ts, src/errors.ts) — no test file among them.
• Reading the built artefact rather than the config: across all six sourcemaps in dist/, 95 source inputs in total, zero are *.test.ts. Grep of every shipped .js / .cjs / .d.ts / .d.cts for createMockPluginContext, vitest and describe(: 0 hits. (The .test. strings that do appear in dist are prose inside docblocks of src/metadata-manager.ts, a file this PR does not touch, carried through sourcesContent.)
• Every one of the 12 files this PR edits under packages/metadata/src is a *.test.ts and therefore an input to nothing published. The only other change inside the package is a scripts.typecheck entry in package.json — dev tooling metadata, no runtime behaviour, the identical change PR [finding] @objectstack/metadata-protocol has no typecheck script: its only type coverage is the tsup dts build, which reports one file per run and never reaches the 138 test files #13978 made for the sibling package.

So dist/ is invariant under this diff and no user-visible behaviour moves.

Clause-② self-reading: no

Read off this diff, not off the dispatch note. 12 test files (mechanical typing repairs, no assertion moved, no accept/reject behaviour touched), one scripts entry in a package.json, and one gate ledger row deleted with its graduation recorded. No public type changes, no parse or validation behaviour changes, and no gate is weakened — a gate is ADDED (this package's typecheck now runs under turbo run typecheck) and the DEBT ledger shrinks by one entry and 89 frozen errors.

Verification

Union re-derived on the final tree with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands (no path list) after the last commit — 14 paths vs merge base 7085f9053, 44 gates — and run. Exit codes captured after a redirect, never through a pipe.

Green (exit 0): pnpm lint (whole repo, eslint . --no-inline-config, exit 0 — not narrowed) · pnpm check:nul-bytes (plus a control-byte self-scan over the diff, 0 hits) · pnpm check:error-status-conformance · pnpm --filter @objectstack/metadata typecheck · pnpm --filter @objectstack/metadata exec vitest run (43 test files, 677 tests, all passed — assertions untouched) · pnpm --filter @objectstack/metadata build (8/8 declaration files present) · check:type-check-coverage · check:type-source-resolution · check:turbo-task-graph · check:published-files · check:pnpm-filter-targets · check:workspace-manifest-cycles · check:test-source-alias · check:ratchet-remedy-authority · check:service-providers · check:query-options-erasure · check:slot-lookup · check:watch-hint-literal · check:where-matcher · check:engine-double-contract · check:entry-guard · check:parse-guard · check:doc-authoring · check:override-consistency · check:page-declaration-shape · check:durability-log-level · check:logger-receiver-detach · check:objectql-double-limit · check:cli-command-ids · check:agent-test-spelling · check:bash32-floor · check:cross-package-test-inputs · check:llms-txt · check-changeset-fixed · check-ci-filter-parity · check-comment-mask-adoption · check-cross-package-test-inputs · check-keyed-text-bounds · check-osv-exemptions · check-plugin-teardown-shape · check-shard-attestation · check-system-context-census · check-undeclared-dep-imports · docs-audit/check-affected-docs · docs-audit/check-drift-comment · pm/bare-root-worklist --self-test.

Edited gate script — its own suite. This PR edits scripts/check-type-check-coverage.mjs, so its own tests are owed on top of the derived family. Repo-wide grep finds no vitest file that executes it (all 12 *.test.ts matches are prose citations in comments), so its suite is its built-in --self-test, which both check:type-check-coverage and check:type-check-debt chain and which passed: 48 semantic + 68 observation + 43 re-measure + 28 built-closure + 19 auto-lowering + 18 exit-code cases.

NOT MEASURED locally — declared, with the reason (four gates). None is a red, and each is CI-owned:

• check:type-check-debt — exit 3, the gate's own PREREQUISITE-NOT-MET code, in its own words "NOT a pass and NOT a finding: nothing was measured". It names 42 unbuilt workspace dependencies and the remedy (turbo run build --filter='./packages/*' --filter='./packages/*/*' — a whole-workspace build; 60 packages here have no dist), which is a step lint.yml runs immediately before it and which does not fit this container's ~10-minute foreground cap from cold. The substitute measurement for the entry this PR removes is the one that gate would have made: tsc --noEmit over the package with its dependency closure built, which is the run above at 0 errors. No other ledger entry's package is touched by this diff.
• check:test-completeness — exit 3, same class: it grades a saved turbo run test log and none was supplied. Its own message prescribes the disposition — "running the family locally, record this gate as NOT MEASURED".
• check:dual-build-cjs-loads — exit 3: it reads built output and 52 packages have no dist in a fresh worktree. "Run pnpm build first. This is NOT a pass: nothing was measured."
• check:pm-dispatch-gates — killed by the container's foreground cap on three attempts (540s, 540s, 575s), each getting further, with 0 failing assertions in all three. It is a thin wrapper around one long dispatch-gates.mjs --self-test. The assertion in it that actually reads the file this PR edits — "the type-check ledger gate declares the root-program script whose errors it ratchets" — ran and passed before the kill.

CI runs the whole farm exactly once on a built tree, which is where these four land.

Out of scope, filed not fixed

• [finding] every assertion in packages/metadata/src/metadata-history.test.ts sits behind an if (manager.X) guard over a method that is unconditionally declared — 8 sites that go green asserting nothing #14623 — every assertion in packages/metadata/src/metadata-history.test.ts sits behind an if (manager.X) guard (8 sites) over methods that are unconditionally declared on MetadataManager, so the file goes green asserting nothing the moment one of them moves. Noticed while repairing the TS18048 on line 150 of that file; repairing it is an assertion move, which this card's ruling excludes.

Related family, named so it is not re-filed: PR #13978 (first member, @objectstack/metadata-protocol) and the newly filed #14613 (@objectstack/core, same shape, 98 errors). ⛔ Neither is addressed here and this PR does not widen to cover them. The general shape is worth a census question for triage: a package whose tsconfig declares a program over src/**/* but whose package.json declares no typecheck script is never selected by turbo run typecheck, so the config reads as coverage and delivers none — three instances are now known, and check:type-check-coverage's COVERED invariant catches only the packages that carry a ledger row, not the ones whose absence of a row was never noticed.

Patch round — ef901e559

Review found that the codemod falsified a comment in one of its own files, and it did. packages/metadata/src/register-notifies-watchers.test.ts carried a block explaining why its loader-interface import spells .js, and two of its sentences were true when written and false at the head of the round before this one:

• "unlike the three extensionless imports above it" — after the codemod the relative imports above it carry .js, so the contrast had nothing left to contrast with. (It was already loose: only two relative imports sat above it, the third being a package specifier the sentence's own reasoning is not about.)
• "this package's pre-existing type-check debt ([P2] framework: 66 个包用 tsup 构建、无人做类型检查 —— 实测 18 个包共 380 处 code-tier 错误(#4118 的 framework 侧对应) #4311) ... left for whoever pays that ledger down" — this branch IS that payment, so the comment told the next reader to leave alone the thing the same change repaired.

The block is kept, because the reason in it is exactly what this branch proves: under moduleResolution: nodenext an extensionless relative import does not resolve and every symbol it names silently becomes any, which is what makes implements MetadataLoader on the fixture below a check rather than decoration. What replaces the two false sentences is the fact that now holds — the package declares a typecheck script, so turbo run typecheck compiles this file and a regression here is a red gate rather than a silent any.

Swept the rest of the diff for the same shape, and the result is none. Two greps over the changed set (git diff --name-only MERGE_BASE HEAD, 14 paths):

grep -nEi "extensionless|extension-less|without (an?|its|the) \.js|no \.js|missing (an?|the) \.js|nodenext|node16|moduleResolution" FILES
grep -nEi "\b89\b|type-check debt|typecheck debt|4311|DEBT ledger|no typecheck script|not type-?checked|nothing reads|never selected|hidden from" FILES

Across the 12 touched test files the only hits are the rewritten block itself and one unrelated line in database-loader.test.ts ("rowToRecord reaches createdAt / updatedAt through an unchecked cast ... which is why tsc reported nothing") — that sentence is about an as cast defeating tsc on one field, it is untouched by this diff, and a cast still defeats tsc after the script lands, so it is not falsified. In scripts/check-type-check-coverage.mjs every hit is either the generic top-of-ledger NodeNext lesson or another package's entry (rest, cli), plus three sha-anchored past-tense worked examples that cite this package's old numbers as history ("were repaired by hand", "on the trees that carried them: at 699132f", "the fixtures are the real instances, transplanted") — none claims a live row. The decisive check for that: after the deletion the ONLY surviving occurrence of @objectstack/metadata in that file is the graduation note itself.

Graduation note quotation made exact. It paraphrased the deleted row's split; it now quotes the row's opening itemisation verbatim — code-tier 30 (TS2345 x30); config-tier 25 (TS2835 x25); noise 34 (TS7006 x33, TS6133) — which also makes the "ALL 33 TS7006 dissolved" line beside it land against the exact figure it overturns.

Both edits are comments. Re-verified on ef901e559: dependency closure rebuilt, pnpm --filter @objectstack/metadata typecheck 0 errors, vitest run 43 files / 677 tests passed, pnpm lint (whole repo) exit 0, pnpm check:nul-bytes exit 0 plus a control-byte self-scan over the two changed files with 0 hits, and the comment-sensitive and ratchet gates re-run green: check:type-check-coverage (still "OK — 70/79 ... 9 in the DEBT ledger (216 frozen raw errors)"), check-comment-mask-adoption, check:entry-guard, check:parse-guard, check-keyed-text-bounds, check:ratchet-remedy-authority, check:test-source-alias, check:agent-test-spelling. The gate family re-derived on ef901e559 is byte-identical to the one derived on b195676a7, so nothing new was owed.

One reading worth passing on rather than acting on: dispatch-gates.mjs now prints a STALE TREE warning on this branch — at least 21 commits behind origin/main, with 9 files the derivation reads changed across that range. The family is unchanged, and CI derives against the merge result, so this is a note for the landing seat, not a finding.

🤖 Generated with Claude Code

https://claude.ai/code/session_0112hMx9hjJ9BgB28X97DS68

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.

Coarse fallback — 0 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 7251bad7d8c3a96725b85104b4c7ff73023bdd5b → packageMentionDocs.

[os-musk]

Not flipped, and the reason is not this PR — engine execution seat, session session_0112hMx9hjJ9BgB28X97DS68.

This PR is ACCEPTed (comment 5512521458 on #14342) and its enqueue bar is otherwise met, but one check on ef901e559 is red and it is not yours:

Validate Package Dependencies — OSV-Scanner against pnpm-lock.yaml, exit 1 on four medium advisories: @xmldom/xmldom 0.8.13 and 0.9.11 (GHSA-6gmq-8vp8-gcm6) and qs 6.15.3 (GHSA-4mjr-xmp4-gh2g, GHSA-x5fp-wj9c-mxmx). All four have fixed versions.

Established as not this PR's, by measurement rather than by assumption:

• This diff touches no dependency and no lockfile. Its only manifest change is one line — "typecheck": "tsc --noEmit" — in packages/metadata/package.json.
• All three flagged versions are present in origin/main's pnpm-lock.yaml (:5359, :5364, :8252), byte-identical to this branch's.
• The workflow triggers on **/package.json, so the one added script line is the entire reason the job ran here at all. Any PR touching any manifest gets the same red today.
• The lockfile last moved at 7085f9053; the advisories are newer than that bump.

⛔ The fix is not ported into this PR. A lockfile bump or a pnpm.overrides entry is a shared single-writer change and would widen a test-typecheck card into a dependency change; osv-scanner.toml's own header forbids an exemption while a fix exists. Filed instead as #14639, with the measurement and the lineage — this is the sixth occurrence of a known class (#4945, #5032, #5039, #6407, #6506, all closed by taking the available fix).

Standing state of this PR: draft, ACCEPTed, not enqueued. It flips the moment the lockfile carries the fix and this check goes green; no change is owed from its author. The other three checks that were still running at 16:1xZ (Lint & Repo Gates, Test Core (1/6), the Test Core aggregate) are unrelated and were green or in progress, not red.

One note for whoever lands it afterwards, carried from the review: this branch is ~21 commits behind origin/main and deliberately unmerged, and it touches scripts/check-type-check-coverage.mjs, a file other lanes also graduate rows in. If the merge queue reports a conflict there, merge origin/main and re-run the ledger gate — ⛔ never rebase.

---

Generated by Claude Code