Summary
packages/fathom-ts/ has vitest suites (test/client.test.ts, test/errors.test.ts, 19 tests) that pass locally only — no workflow runs them. The Go suite got its own lane (go-ci.yml, unit + integration); TypeScript has nothing, so a regression in @fathom-rules/sdk ships silently.
Required work
Add a TS CI lane mirroring go-ci.yml: pnpm install with --frozen-lockfile, run vitest, run tsc --noEmit (or the package's build) on PRs touching packages/fathom-ts/ plus the same no-path-filter treatment if it becomes a required check.
Priority
P1 — untested published-intent SDK surface.
Source: docs/reference/planned-integrations.md ("No CI for the TS suite"); roadmap sweep 2026-06-05
Summary
packages/fathom-ts/has vitest suites (test/client.test.ts,test/errors.test.ts, 19 tests) that pass locally only — no workflow runs them. The Go suite got its own lane (go-ci.yml, unit + integration); TypeScript has nothing, so a regression in@fathom-rules/sdkships silently.Required work
Add a TS CI lane mirroring
go-ci.yml: pnpm install with--frozen-lockfile, run vitest, runtsc --noEmit(or the package's build) on PRs touchingpackages/fathom-ts/plus the same no-path-filter treatment if it becomes a required check.Priority
P1 — untested published-intent SDK surface.
Source: docs/reference/planned-integrations.md ("No CI for the TS suite"); roadmap sweep 2026-06-05