- **CI routing-only edits, selected cheap core-test fixture edits, and narrow plugin contract helper/test-routing edits** use a fast Node-only manifest path: `preflight`, security, and a single `checks-fast-core` task. That path skips build artifacts, Node 22 compatibility, channel contracts, full core shards, bundled-plugin shards, and additional guard matrices when the change is limited to the routing or helper surfaces the fast task exercises directly.

- **Windows Node checks** are scoped to Windows-specific process/path wrappers, npm/pnpm/UI runner helpers, package manager config, and the CI workflow surfaces that execute that lane; unrelated source, plugin, install-smoke, and test-only changes stay on the Linux Node lanes.

The slowest Node test families are split or balanced so each job stays small without over-reserving runners: plugin contracts and channel contracts each run as two weighted Blacksmith-backed shards with the standard GitHub runner fallback, core unit fast/support lanes run separately, core runtime infra is split between state, process/config, cron, and shared shards, auto-reply runs as balanced workers (with the reply subtree split into agent-runner, dispatch, and commands/state-routing shards), and agentic gateway/server configs are split across chat/auth/model/http-plugin/runtime/startup lanes instead of waiting on built artifacts. Broad browser, QA, media, and miscellaneous plugin tests use their dedicated Vitest configs instead of the shared plugin catch-all. Include-pattern shards record timing entries using the CI shard name, so `.artifacts/vitest-shard-timings.json` can distinguish a whole config from a filtered shard. `check-additional-*` keeps package-boundary compile/canary work together and separates runtime topology architecture from gateway watch coverage; the boundary guard list is striped into one prompt-heavy shard and one combined shard for the remaining guard stripes, each running selected independent guards concurrently and printing per-check timings. The expensive Codex happy-path prompt snapshot drift check runs as its own additional job for manual CI and for prompt-affecting changes only, so normal unrelated Node changes do not wait behind cold prompt snapshot generation and the boundary shards stay balanced while prompt drift is still pinned to the PR that caused it; the same flag skips prompt snapshot Vitest generation inside the built-artifact core support-boundary shard. Gateway watch, channel tests, and the core support-boundary shard run concurrently inside `build-artifacts` after `dist/` and `dist-runtime/` are already built.

The slowest Node test families are split or balanced so each job stays small without over-reserving runners: plugin contracts and channel contracts each run as two weighted Blacksmith-backed shards with the standard GitHub runner fallback, core unit fast/support lanes run separately, core runtime infra is split between state, process/config, shared, and three cron domain shards, auto-reply runs as balanced workers (with the reply subtree split into agent-runner, dispatch, and commands/state-routing shards), and agentic gateway/server configs are split across chat/auth/model/http-plugin/runtime/startup lanes instead of waiting on built artifacts. Broad browser, QA, media, and miscellaneous plugin tests use their dedicated Vitest configs instead of the shared plugin catch-all. Include-pattern shards record timing entries using the CI shard name, so `.artifacts/vitest-shard-timings.json` can distinguish a whole config from a filtered shard. `check-additional-*` keeps package-boundary compile/canary work together and separates runtime topology architecture from gateway watch coverage; the boundary guard list is striped into one prompt-heavy shard and one combined shard for the remaining guard stripes, each running selected independent guards concurrently and printing per-check timings. The expensive Codex happy-path prompt snapshot drift check runs as its own additional job for manual CI and for prompt-affecting changes only, so normal unrelated Node changes do not wait behind cold prompt snapshot generation and the boundary shards stay balanced while prompt drift is still pinned to the PR that caused it; the same flag skips prompt snapshot Vitest generation inside the built-artifact core support-boundary shard. Gateway watch, channel tests, and the core support-boundary shard run concurrently inside `build-artifacts` after `dist/` and `dist-runtime/` are already built.

Android CI runs both `testPlayDebugUnitTest` and `testThirdPartyDebugUnitTest` and then builds the Play debug APK. The third-party flavor has no separate source set or manifest; its unit-test lane still compiles the flavor with the SMS/call-log BuildConfig flags, while avoiding a duplicate debug APK packaging job on every Android-relevant push.

.filter((shard) => shard.includePatterns.length > 0);

}

function resolveCronShardName(file) {

const name = relative("src/cron", file).replaceAll("\\", "/");

if (name.startsWith("isolated-agent")) {

return "core-runtime-cron-isolated-agent";

}

if (name.startsWith("service")) {

return "core-runtime-cron-service";

}

return "core-runtime-cron-core";

}

function createCronSplitShards() {

const groups = new Map();

for (const file of listTestFiles("src/cron")) {

const shardName = resolveCronShardName(file);

groups.set(shardName, [...(groups.get(shardName) ?? []), file]);

}

return ["core-runtime-cron-core", "core-runtime-cron-isolated-agent", "core-runtime-cron-service"]

.map((shardName) => ({

configs: ["test/vitest/vitest.cron.config.ts"],

includePatterns: groups.get(shardName) ?? [],

requiresDist: false,

shardName,

}))

.filter((shard) => shard.includePatterns.length > 0);

}

const SPLIT_NODE_SHARDS = new Map([

[

"core-unit-fast",

shardName: "core-runtime-shared",

configs: [

"test/vitest/vitest.acp.config.ts",

"test/vitest/vitest.cron.config.ts",

"test/vitest/vitest.shared-core.config.ts",

"test/vitest/vitest.tasks.config.ts",

"test/vitest/vitest.utils.config.ts",

],

requiresDist: false,

},

...createCronSplitShards(),

],

],

[

{

configs: [

"test/vitest/vitest.acp.config.ts",

"test/vitest/vitest.cron.config.ts",

"test/vitest/vitest.shared-core.config.ts",

"test/vitest/vitest.tasks.config.ts",

"test/vitest/vitest.utils.config.ts",

runner: undefined,

shardName: "core-runtime-shared",

},

{

configs: ["test/vitest/vitest.cron.config.ts"],

requiresDist: false,

runner: undefined,

shardName: "core-runtime-cron-core",

},

{

configs: ["test/vitest/vitest.cron.config.ts"],

requiresDist: false,

runner: undefined,

shardName: "core-runtime-cron-isolated-agent",

},

{

configs: ["test/vitest/vitest.cron.config.ts"],

requiresDist: false,

runner: undefined,

shardName: "core-runtime-cron-service",

},

]);

});

it("covers every cron test exactly once across core runtime cron shards", () => {

const cronShards = createNodeTestShards().filter((shard) =>

shard.shardName.startsWith("core-runtime-cron-"),

);

const actual = cronShards

.flatMap((shard) => shard.includePatterns ?? [])

.toSorted((a, b) => a.localeCompare(b));

expect(cronShards.map((shard) => shard.shardName)).toEqual([

"core-runtime-cron-core",

"core-runtime-cron-isolated-agent",

"core-runtime-cron-service",

]);

expect(actual).toEqual(listTestFiles("src/cron"));

expect(new Set(actual).size).toBe(actual.length);

});

it("splits the agentic lane into control-plane, command, agent, gateway, SDK, and plugin shards", () => {