Stale generated custom-connection.test.ts for a type removed from the schema (4 TS failures)

[sethjuarez]

Summary

runtime/typescript/packages/core/tests/model/connection/custom-connection.test.ts is committed generated output for a CustomConnection type that no longer exists in the schema. It produces 4 vitest failures and survives regeneration untouched.

Failures

FAIL tests/model/connection/custom-connection.test.ts > CustomConnection > construction > should create a new instance with defaults FAIL tests/model/connection/custom-connection.test.ts > CustomConnection > construction > should create a new instance with partial initialization FAIL tests/model/connection/custom-connection.test.ts > CustomConnection > load and save > should load from dictionary FAIL tests/model/connection/custom-connection.test.ts > CustomConnection > load and save > should save to dictionary

all TypeError: CustomConnection is not a constructor.

Evidence it is stale

• CustomConnection appears nowhere in schema/.
• It appears nowhere in generated runtime/typescript/packages/core/src/.
• A full npm run generate (Compilation completed successfully.) does not modify or remove the test file.
• Its dictionary test still uses the pre-0.4.19 = {} shape, which dates it to before that release.

It was introduced by commit 92e23806.

Why it needs a manual delete

The emitter does not prune generated files whose source type has been removed — it writes the current type set and leaves everything else. I have filed that gap upstream as sethjuarez/typra#69, but even once it is addressed, this particular file is already committed here and needs deleting.

Suggested fix

git rm runtime/typescript/packages/core/tests/model/connection/custom-connection.test.ts

Worth flagging

These 4 failures sit in the same directory as connection-roundtrip-vectors.test.ts and surfaced alongside a genuine open-discriminator defect, so they read plausibly as the same root cause. They are not — that defect is fixed in @typra/emitter@0.4.21, and these 4 are unrelated.

Not verified

I checked only the TypeScript output directory. Other backends may carry similar orphans; I did not audit them.

[sethjuarez]

Fixed on wip/typra-0.4.20-regen in fecc12b2. Confirmed orphaned rather than current by mtime — 08/04 versus 08/05 for every sibling regenerated in the 0.4.21 run. Deleting it took TypeScript core from 4 failures to 0 (1518 passed).

I also swept the other four runtimes for the same class of orphan; the Go, C# and Python candidates are all legitimately handwritten (go vet clean), so this was the only instance.