| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| gbrain-darwin-arm64 | < 9 hours ago | 188.3 MB | |
| gbrain-linux-x64 | < 9 hours ago | 207.5 MB | |
| README.md | < 9 hours ago | 1.2 kB | |
| v0.60.520.0 source code.tar.gz | < 9 hours ago | 50.8 MB | |
| v0.60.520.0 source code.zip | < 9 hours ago | 60.0 MB | |
| Totals: 5 Items | 506.6 MB | 0 | |
The Heavy nightly's Codex plugin door test checks the plugin's MCP surface against PLUGIN_SURFACE, the surface the plugin's mcp.json actually serves, instead of REGISTRATION_SURFACE. A unit-shard listing that dies on a signal now names the signal instead of an empty error.
The plugin ships serve --surface PLUGIN_SURFACE --source-guard, so the door test's launcher-args check and its tools/list oracle compared against the wrong surface and failed every Heavy nightly (#6049).
unitShards() in scripts/sharding.ts threw scripts/test-shard.sh --dry-run-list 26 28 failed: with nothing after it when a plain bun test test/scripts/unit-shard-budget.test.ts hit Bun's 5 s default test timeout. Bun ignores bunfig's timeout, the 28 listings take about 5.5 s, and the timeout kills the child, so the status is null and stderr is empty. The error now reads killed by SIGTERM. CI was never affected: scripts/test-shard.sh passes --timeout=60000.
Itemized changes
test/e2e/codex-plugin-install-real.serial.test.ts: assertPLUGIN_SURFACE.scripts/sharding.ts:unitShards()names the signal that killed a listing.test/scripts/sharding.test.ts: a listing killed by SIGTERM reports it.
