๐ŸŒ‹ VGI Manager

CI & release monitor ยท Query-farm
VGI engine โ€” shared vgi test/sql reference
โš ๏ธ Implementations are NOT all tested against the same vgi ref. "All green" does not currently prove mutual consistency โ€” see drift below.
ImplementationRuns vgi suitePinned vgi refRef ageHaybarn runnerStatus
vgi-pythonโ€”โ€”โ€”โ€”does not run the vgi test/sql suite
vgi-rustโœ“mainโ€”latest (dynamic)unpinned
vgi-javaโœ“mainโ€”latest (dynamic)unpinned
vgi-typescriptโœ“mainโ€”latest (dynamic)unpinned
vgi-goโœ“mainโ€”latest (dynamic)unpinned
vgi-kotlinโ€”โ€”โ€”โ€”no CI workflows

The engines pin the haybarn-unittest runner, but the published vgi extension is built at haybarn-v1.5.5-rc1 โ€” a runner/extension version skew is its own source of inconsistency.

vgi-rpc โ€” wire-protocol reference (separate axis)

These test against vgi-rpc-python, not the engine. >= floors resolve to different actual versions over time.

Implementationvgi-rpc reference pin
vgi-rpc-rustvgi-rpc[http,cli,external,conformance]>=0.42.0
vgi-rpc-gobuilt from a checked-out vgi-rpc-python ref
vgi-rpc-javabuilt from a checked-out vgi-rpc-python ref
vgi-rpc-typescriptvgi-rpc[http,cli,external,conformance]>=0.42.0
vgi-rpc-cppnot found

Checked 5h ago ยท reads each repo's integration workflow from GitHub.