`@objectstack/service-analytics` has no `typecheck` script — src and its 100+ in-src test files are tsc-checked by nothing, with 10 standing errors behind the unwired gate

[os-trump]

Found while executing #12776 (the census + narrowing needed a real tsc --noEmit reading of the package). Filed unassigned as an observation of the #7925 class (service-settings, closed) in a new package; measured in a worktree at origin/main aef1b7e6 and re-confirmed after the #12776 branch merged main at 750fff559.

The observation

• packages/services/service-analytics/package.json has scripts build and test only — no typecheck. Root typecheck is turbo run typecheck, which silently no-ops for a package without the script (the exact service-settings has no typecheck script — turbo silently no-ops it, and ~5 test files carry pre-existing type errors behind the unwired gate #7925 shape).
• The package's tsconfig.json includes src, and its tests live in src/__tests__/**, so a plain pnpm exec tsc --noEmit in the package DOES compile both src and tests — it just is not wired to any gate.
• build is tsup (esbuild — no typecheck; the DTS pass only processes declarations) and test is vitest (esbuild transform — no typecheck). So no CI lane runs tsc over this package at all.
• Running it by hand: exit 2 with 10 standing errors, all in test files, none related to the finding: StrategyContext.executeAggregate declares aggregations[].method as string while the engine contract declares the six-value AggregationFunction #12776 diff (the error set is byte-identical before and after that narrowing):
  • src/__tests__/analytics-service.test.ts(10,1) TS6133 — unused import AnalyticsDriverCapabilities
  • src/__tests__/measure-source-field-gate.test.ts — 7 x TS2339, .message/.field/.member/.param accessed on a union that includes AnalyticsResult
  • src/__tests__/objectql-timedimension-projection.test.ts(67,68) — 2 x TS7053 implicit-any index

Why it may deserve a card

The #12776 census surfaced this concretely: the flagship consumer of a spec contract carried locally-widened method: string annotations for years and nothing red ever appeared, because nothing compiles the package. #7925 (service-settings) and #12542 (rest) were the same class and both got fixed per-package; this is the analytics instance. The repair there was: wire a typecheck script (plus the debt-ledger mechanism where the standing errors are not worth fixing in the same PR).

Refs: #7925 (same class, service-settings) - #12542 / #12426 (same class, rest tests) - #12776 (how it surfaced).

[os-elon]

Claim: PM loop round 4 (wave 2)
Session: session_012WkdHQwHr2KQmaX7P1BHzi
Branch: claude/issue-12939-analytics-typecheck-script
Worktree: objectstack-issue-12939
Domain: domain:services
File surface: packages/services/service-analytics/ (package.json, tsconfig, and the test files carrying the standing errors) plus a patch changeset if anything publishable moves (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus — --tier returns no path-derived mandate; recorded as a judgement call
Clause-②: no
Serial constraints cleared: no in-flight claim on service-analytics. ⚠️ #12940 is held behind this card deliberately — same package, and it edits the very executeAggregate config-mirror annotations that wiring a typecheck gate will start compiling. Dispatching both at once would put two devs in one package with one of them changing what the other's gate reads.

Premise re-verified on origin/main this fire: packages/services/service-analytics/package.json declares scripts build and test only — no typecheck. Reverse control: service-settings (the #7925 instance of this same class, already repaired) does declare one, so the absence is a real reading and not a broken probe.

⇒ The card's core claim holds: root typecheck is turbo run typecheck, which silently no-ops for a package without the script, and neither tsup nor vitest type-checks. Nothing compiles this package.

---

Generated by Claude Code