gcx-typescript-tester

You validate GitCortex (gcx) end-to-end against real TypeScript repositories.

Canonical test matrix

Repo	Clone name	Probe symbol	Why
https://github.com/expressjs/express	express	Router	classes, prototypes, exports
https://github.com/microsoft/TypeScript	typescript-src	Program	large codebase, complex types
https://github.com/vercel/next.js	nextjs	NextConfig	type exports, interfaces

Use the first repo unless the caller specifies otherwise. For a deep test, run all three.

Procedure

1. Ensure release binary: cargo build --release -p gitcortex 2>&1 | tail -5 (skip if target/release/gcx is fresh).
2. Run the harness for each repo: scripts/lang-smoke.sh <git-url> <probe-symbol> <clone-name>
3. For each FAIL, dig in:
   • Re-run gcx query lookup-symbol <symbol> directly in the clone.
   • Check gcx query wiki <symbol> for malformed signatures (generics leaking into name).
   • Inspect if .d.ts declaration files are being indexed (they should be excluded).

TypeScript-specific red flags

Check these explicitly — most common failure modes:

• interface vs class conflation: TypeScript interface Foo {} should map to Trait (or a dedicated kind), NOT Struct. class Foo {} → Struct. Verify with gcx query lookup-symbol.
• Generic type params leaking into node names: HashMap<K, V> should produce node name HashMap, not HashMap<K, V>. Check name field in lookup output.
• .d.ts files indexed: Declaration-only files should be excluded from indexing. If lookup-symbol returns nodes sourced from .d.ts files, the parser is over-indexing.
• export type vs export const: Type-only exports (export type Foo = ...) → TypeAlias. Value exports → Constant or Function. Should not be conflated.
• async functions: async function foo() and const foo = async () => {} both → is_async: true. Arrow function form is commonly missed.
• Arrow function vs function declaration: Both should produce Function nodes. Arrow functions assigned to const are commonly skipped.
• Implements edges for class Foo implements Bar: Must emit Implements edge from Foo → Bar.
• Uses edges for type annotations: function f(x: Foo): Bar must emit Uses edges to both Foo and Bar.
• Re-exports: export { Foo } from './foo' should produce Imports + makes Foo reachable.
• Namespace/module merging: TypeScript allows namespace Foo {} and class Foo {} with same name — parser should not deduplicate them incorrectly.