Add Go CI coverage and a cross-language proto drift check

[ShreeBohara]

PR #11 merged with no CI protection at all — ci.yml had Python 3.11 and Node 20 only, so nothing compiled the Go service, ran go vet, or checked that the two languages' generated stubs still agreed. Its automated review also never ran (the Codex bot hit its usage limit), so that code landed unguarded twice over.

indexer-go

gofmt (excluding gen/, which the drift job owns), go vet, go test -race, and a cgo build.

CGO_ENABLED=1 throughout, plus an explicit cc --version step — every tree-sitter grammar is a cgo package with its own generated parser.c, so if the runner ever loses its C toolchain the failure should name that rather than surface as a link error.

proto-codegen-drift

Regenerates both the Go and Python stubs from proto/indexer.proto and fails if either differs from what's committed. Without it, editing the proto and regenerating only one side produces a server and client that disagree, and nothing catches it until runtime.

Generators are pinned, not @latest:

protoc 29.3 · protoc-gen-go v1.36.12 · protoc-gen-go-grpc v1.6.2 · grpcio-tools 1.83.0

Generated files embed the generator version (protoc-gen-go v1.36.12, Protobuf Python Version: 7.35.1), so an unpinned plugin would eventually change the output and fail this check for a reason unrelated to the contract.

I verified the round-trip is byte-identical on both sides with these versions before relying on a strict whole-file diff — and corrected a comment I'd written that claimed the comparison was looser than it actually was.

Go tests, which did not exist before

These cover the properties I'd previously only verified by hand:

• .tsx parses under the tsx grammar with no parse error — the plain TypeScript grammar cannot parse JSX, the bug that shipped in the Python parser
• chunks after non-ASCII text still slice as 'class Café:' and 'def método(self):' rather than misaligned fragments, because tree-sitter offsets are byte offsets
• HadParseError is set on a syntax error rather than swallowed, since tree-sitter returns a partial tree instead of failing
• MaxFiles actually stops the walk and sets Truncated — the Python original's break left only the inner filename loop, so os.walk continued into the next directory
• extension mapping, unlinked extensions, and the module-chunk fallback

Two things caught locally

Validating the workflow YAML before pushing caught an unquoted colon in a step name (Verify C toolchain (required: grammars are cgo)) that YAML reads as a mapping — it would have failed the run. And gofmt flagged two of my own source files.

Verified

gofmt clean · go vet clean · go test ./... passes both packages · cgo build succeeds · proto round-trip byte-identical · workflow parses with 4 jobs

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
codebaseqa-web	Ready	Preview	Aug 13, 2026 3:58pm

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.