mirror of
https://github.com/DeusData/codebase-memory-mcp.git
synced 2026-10-27 06:53:11 +08:00
Ilya Brykau
a874b6bc95
The only CI venue that drives a repository through the shipped binary (MCP stdio -> supervisor -> pipeline -> SQLite) is the Windows guards harness, and every fixture it indexed was TypeScript-only. The Go/cgo extraction defect family (#1932: build-tag twins #1911, struct fields #1935, cgo #1929, channels #1930, cross-language bleed #1928) was invisible to that venue by construction. Add a dummy Go package to the test_non_ascii_path fixture covering those shapes: a struct with fields and a method, a //go:build linux/windows twin pair sharing one function name, a cgo file (C preamble, C. call, //export directive), and a channel producer/consumer pair. Count Go-file definitions per variant (Function/Method where file_path CONTAINS '.go'), require at least one in the ASCII baseline, and include the count in the cross-variant equality check - Go qualified names embed the containing directory, so non-ASCII paths reach the Go passes on their own route. Measured with the harness functions against a current binary: baseline nodes=28 edges=46 definitions=12 go=7, identical for the Latin-1 and Cyrillic variants. The go=7 includes exactly one FlushDisk - the twin collision on main is deterministic, and this guard will observe the second twin appear when the build-tag fix lands. Signed-off-by: Ilya Brykau <ilya.brykau@orca.security>