Skip to content

[finding] service-cluster tests compile under no tsc program — a TS2322 sits in memory.contract.test.ts, the package's contract witness (services-family instance of the #14062 class) #14181

Description

@claude

Found while implementing #13331 (first test file for MetadataClusterBridgePlugin — checking what would typecheck it). Same class as #14062 (plugins family), #13676 (objectql), #12542 (rest, closed); this instance is packages/services/**, starting with service-cluster. Observation, not a live-defect repro.

Measurement (worktree at 44a2e59)

src/memory/memory.contract.test.ts(26,46): error TS2322: Type 'number' is not assignable to type 'void or Promise-of-void'.

(the assignable-to type is spelled out in words here because the sanitizer eats angle-bracket tokens; the compiler prints it with generics.)

That file is the package's CONTRACT witness — type conformance is the point of its existence, and it does not compile. The new metadata-cluster-bridge-plugin.test.ts (#13331) was one-off checked clean, but lives in the same untyped zone.

What this card asks

Nothing separate from #14062's decision — it is filed so the services family is IN the population when that decision is taken (checked test zone vs deliberate exclusion with pins re-sited). ⛔ Not asking to grow test-typecheck-debt.json (shrink-only, maintainer-only per #5286).

Dedup: REST open-issues sweep (443 open issues, positive control hit): #14062 covers packages/plugins/** explicitly and says the family-per-card pattern is the shape; no card names packages/services/**.


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions