@kontextmind/kxm 0.7.153 → 0.7.154

package/.claude-plugin/marketplace.json

@@ -11,7 +11,7 @@
       "name": "kxm",
       "source": "./plugins/kxm",
       "description": "Durable workflows, peer agents, and kxm tui",
-      "version": "0.7.153",
+      "version": "0.7.154",
       "category": "development",
       "tags": ["kxm", "multi-agent", "workflows", "mcp"]
     }

package/CHANGELOG.md

@@ -156,6 +156,15 @@ All notable user-facing changes are documented here. The project follows [Semant
 
 ### Changed
 
+- **Windows pull-request unit lanes finish inside the job limit.** The light
+  lane on `windows-latest` was cancelled at 20 minutes on #361, #362, and
+  #363 after it stopped reporting tests. `package-install.test.ts` (171s on
+  that lane, 67s on Linux) now runs with the serial files. The other light
+  files are split into `light-1` and `light-2`. POSIX `#!/bin/sh` shims in
+  the land tests are skipped on Windows. `CI / required` still fails when a
+  lane fails or is cancelled. See
+  [CI and release](docs/contributing/ci-and-release.md).
+
 - **Workforce ids use one convention, and old ids still resolve.**
   Role ids stay `planner`, `writer`, `reviewer-arch`, and `reviewer-cli`.
   Agent ids and agent-step ids use those same names. Route ids are
@@ -494,8 +503,9 @@ All notable user-facing changes are documented here. The project follows [Semant
 
 - **Pull-request CI runs the unit suite on Linux Node 24, and `CI / required` is the aggregate check.**
   Docs and plan markdown skip the code jobs. `engine.test.ts` is split by
-  test name. `permission.test.ts` and `runtime.test.ts` run one file at a
-  time, and every other unit file runs in one light lane. Pushes to `main`
+  test name. `permission.test.ts`, `runtime.test.ts`, and
+  `package-install.test.ts` run one file at a time, and every other unit file
+  runs in two light shards. Pushes to `main`
   still run `validate:pr` on Linux and Windows for Node 22.19.0 and Node 24.
   A pull request that touches path, process, shell, spawn, package, lockfile,
   or workflow files also runs the unit lanes on Windows. Playwright stays on

package/docs/contributing/ci-and-release.md

@@ -39,8 +39,8 @@ together.
 | Before you push | Local | `npm run verify` |
 | Pull request, push to `main`, or manual | `ci.yml` (`required`) | Aggregates the lanes below into one pass/fail check named `CI / required` |
 | Pull request and push | `ci.yml` (Docs lint) | `lint:docs` and `check:versions`, always |
-| Code pull request and code push | `ci.yml` (Unit engine and Unit, Linux Node 24) | `engine.test.ts` split by test name; `permission.test.ts` and `runtime.test.ts` one file at a time; every other unit file together. Typecheck and `check-generated` run on the light lane |
-| Platform-sensitive pull request | `ci.yml` (Unit, Windows Node 24) | The same four unit lanes on `windows-latest` |
+| Code pull request and code push | `ci.yml` (Unit engine and Unit, Linux Node 24) | `engine.test.ts` split by test name; `permission.test.ts`, `runtime.test.ts`, and `package-install.test.ts` one file at a time; every other unit file in two light shards. Typecheck and `check-generated` run on `light-1` |
+| Platform-sensitive pull request | `ci.yml` (Unit, Windows Node 24) | The same unit lanes on `windows-latest` |
 | Push to `main`, or manual | `ci.yml` (Validate matrix) | `validate:pr` on Linux and Windows for Node 22.19.0 and Node 24; not on a pull request |
 | Code pull request and code push | `ci.yml` (Plugin validation) | `claude plugin validate --strict` on the marketplace and the plugin |
 | Daily at 04:00 UTC, or manual | `nightly.yml` | `test:coverage:complete`, `check`, `check:generated`, `npm pack --dry-run` |
@@ -54,7 +54,7 @@ The npm scripts behind those rows:
 | Script | Composition |
 |---|---|
 | `verify` | `npm test` (core and package unit tests), `check`, `check:generated` |
-| `test:ci-shard` | One unit lane: build, then `engine <index> <total>`, `serial`, or `light` over `test/core/*.test.ts` and `packages/core/*/tests/unit/*.test.ts` |
+| `test:ci-shard` | One unit lane: build, then `engine <index> <total>`, `serial`, `light`, or `light-<index>` over `test/core/*.test.ts` and `packages/core/*/tests/unit/*.test.ts` |
 | `validate:pr` | `build`, `typecheck`, a compact contract and smoke set of nine `test/core` files, `check:versions`, and the generated-`dist` check |
 | `validate:ci` | `test:coverage` (core and package tests, 91/80/92 floors), `check`, `npm pack --dry-run`; the Release workflow runs it, and it stays available locally |
 | `test:coverage:complete` | Core, simulation and package tests with 93/80/93 floors |
@@ -81,15 +81,20 @@ blocker: it is the only place the simulation suite and coverage floors run.
 ### Lanes and the required check
 
 Code pull requests run Docs lint, two Linux Node 24 engine shards, a serial
-lane (`permission.test.ts` then `runtime.test.ts`), a light lane for every
-other unit file, and Plugin validation. The light lane typechecks and checks
-generated bundles. `engine.test.ts` is split by test name because that file
-alone was 174 seconds; the serial lane keeps the next two longest files off
-the light pool, which was 268 seconds when every non-engine file shared one
-job. Linux jobs use the npm cache from
-`actions/setup-node`. Restoring a `node_modules` tarball was slower than
-`npm ci` on the Linux runners (about 24s versus 17s on 2026-09-24), so that
-cache stays on the Windows jobs, where `npm ci` is the slow step.
+lane (`permission.test.ts`, then `runtime.test.ts`, then
+`package-install.test.ts`), two light shards for every other unit file, and
+Plugin validation. `light-1` typechecks and checks generated bundles.
+`engine.test.ts` is split by test name because that file alone was 174
+seconds; the serial lane keeps the next longest files off the light pool,
+which was 268 seconds when every non-engine file shared one job.
+`package-install.test.ts` is serial because on Windows it took 171 seconds
+and the light job stopped reporting tests after that file finished (cancelled
+at 20 minutes on pull requests #361, #362, and #363). The other light files
+are round-robin split so each Windows job is about half of that pool. Linux
+jobs use the npm cache from `actions/setup-node`. Restoring a
+`node_modules` tarball was slower than `npm ci` on the Linux runners (about
+24s versus 17s on 2026-09-24), so that cache stays on the Windows jobs,
+where `npm ci` is the slow step.
 
 The job `required` always runs. Its check name is `CI / required`. It fails
 when a lane fails or is cancelled, and it passes when a lane was skipped

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kontextmind/kxm",
-  "version": "0.7.153",
+  "version": "0.7.154",
   "description": "KXM local-first multi-agent orchestration and operator dashboard",
   "type": "module",
   "author": "KontextMind",

package/plugins/kxm/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "kxm",
   "displayName": "KXM",
-  "version": "0.7.153",
+  "version": "0.7.154",
   "description": "Headless multi-agent orchestration, durable workflows, and a live operator dashboard for Pi and Claude Code",
   "author": {
     "name": "KontextMind",

package/plugins/kxm/dist/mcp-server.js

@@ -17313,7 +17313,7 @@ function sessionTokenFixHint(policy) {
 }
 
 // plugins/kxm/src/mcp-server.ts
-var VERSION = "0.7.153";
+var VERSION = "0.7.154";
 var CONFIGURE_PLUGIN = "/plugin configure kxm@kxm";
 var inbox = /* @__PURE__ */ new Map();
 var notifiedInbox = /* @__PURE__ */ new Set();

package/plugins/kxm/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-plugin",
-  "version": "0.7.153",
+  "version": "0.7.154",
   "private": true,
   "type": "module",
   "engines": {

package/plugins/kxm/src/mcp-server.ts

@@ -11,7 +11,7 @@ import { deliverInboxNotification } from "./inbox.ts";
 import type { HubEvent, MessageRecord } from "./protocol.ts";
 import { sessionTokenFixHint } from "./session-token-hint.ts";
 
-const VERSION = "0.7.153";
+const VERSION = "0.7.154";
 const CONFIGURE_PLUGIN = "/plugin configure kxm@kxm";
 const inbox = new Map<string, MessageRecord>();
 const notifiedInbox = new Set<string>();

package/scripts/ci-unit-shard.mjs

@@ -7,24 +7,33 @@
 // sequentially, and running them in one process pool stretched the rest of
 // the suite to 268s. engine.test.ts is split by test name across two jobs.
 // permission and runtime run one file at a time in a serial job so they do
-// not steal cores from each other. Every other unit file runs in a light
-// job at concurrency 4.
+// not steal cores from each other.
+//
+// package-install.test.ts is serial as well. On the Windows light lane for
+// PRs #361, #362, and #363 it took 171s (67s on Linux) and was the file that
+// finished immediately before that lane stopped reporting tests. The job
+// then sat until the 20-minute cancel. npm pack/install stays off the light
+// pool. The other light files are round-robin split into two shards so a
+// Windows job is not one 120-file process.
 //
 // Dynamic `test(\`...\${...}\`)` names stay together as one pattern so a
 // loop is not dropped. Run via `npm run test:ci-shard` so npm_execpath is
-// set for the packed-install test: `engine <index> <total>`, `serial`, or
-// `light`.
+// set for the packed-install test: `engine <index> <total>`, `serial`,
+// `light`, or `light-<index>` (two shards).
 
 import { spawn, spawnSync } from "node:child_process";
 import { globSync, readFileSync } from "node:fs";
 import { join } from "node:path";
 
 export const SHARD_TOTAL = 2;
+export const LIGHT_SHARD_TOTAL = 2;
 export const ENGINE_FILE = "test/core/engine.test.ts";
-// Solo Node 24 timings: permission 74s, runtime 53s. One file at a time.
+// Solo Node 24 timings: permission 74s, runtime 53s. package-install is 171s
+// on Windows CI and 67s on Linux. One file at a time.
 export const SERIAL_FILES = [
   "test/core/permission.test.ts",
   "test/core/runtime.test.ts",
+  "test/core/package-install.test.ts",
 ];
 const LIGHT_CONCURRENCY = 4;
 
@@ -125,6 +134,15 @@ export function planLight(root) {
   return light;
 }
 
+export function planLightShard(root, index, total = LIGHT_SHARD_TOTAL) {
+  if (!Number.isInteger(index) || !Number.isInteger(total) || index < 1 || index > total) {
+    throw new Error(`light shard ${index}/${total} is outside 1..${total}`);
+  }
+  const shard = planLight(root).filter((_, fileIndex) => fileIndex % total === index - 1);
+  if (shard.length === 0) throw new Error(`light shard ${index}/${total} assigned no unit files`);
+  return shard;
+}
+
 export function coverageOfShards(root, total = SHARD_TOTAL) {
   const heavy = new Map();
   for (let index = 1; index <= total; index += 1) {
@@ -138,7 +156,15 @@ export function coverageOfShards(root, total = SHARD_TOTAL) {
 
 function runNode(args, label, children) {
   return new Promise((resolve) => {
-    const child = spawn(process.execPath, args, { env: process.env });
+    const child = spawn(process.execPath, args, {
+      env: {
+        ...process.env,
+        // Git Credential Manager on windows-latest can wait on a prompt
+        // until the job is cancelled. Refuse that wait for every lane.
+        GIT_TERMINAL_PROMPT: process.env.GIT_TERMINAL_PROMPT || "0",
+        GCM_INTERACTIVE: process.env.GCM_INTERACTIVE || "Never",
+      },
+    });
     children.add(child);
     let stdout = "";
     let stderr = "";
@@ -220,10 +246,14 @@ async function main() {
       (children) => runNode(testArgs(1, files), "serial", children),
     ], 1));
   }
-  if (mode === "light") {
-    const files = planLight(root);
+  const lightShard = /^light-(\d+)$/.exec(mode);
+  if (mode === "light" || lightShard) {
+    const files = lightShard
+      ? planLightShard(root, Number(lightShard[1]), LIGHT_SHARD_TOTAL)
+      : planLight(root);
+    const label = lightShard ? mode : "light";
     process.exit(await runPool([
-      (children) => runNode(testArgs(LIGHT_CONCURRENCY, files), "light", children),
+      (children) => runNode(testArgs(LIGHT_CONCURRENCY, files), label, children),
     ], 1));
   }
   if (mode === "engine") {
@@ -234,7 +264,7 @@ async function main() {
       (children) => runNode(testArgs(1, [plan.file], plan.patterns), "engine", children),
     ], 1));
   }
-  process.stderr.write("usage: ci-unit-shard.mjs <serial|light|engine> [index total]\n");
+  process.stderr.write("usage: ci-unit-shard.mjs <serial|light|light-<index>|engine> [index total]\n");
   process.exit(2);
 }