@kontextmind/kxm 0.7.111 → 0.7.112

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -11,7 +11,7 @@
11
11
  "name": "kxm",
12
12
  "source": "./plugins/kxm",
13
13
  "description": "Durable workflows, peer agents, and kxm tui",
14
- "version": "0.7.111",
14
+ "version": "0.7.112",
15
15
  "category": "development",
16
16
  "tags": ["kxm", "multi-agent", "workflows", "mcp"]
17
17
  }
package/CHANGELOG.md CHANGED
@@ -81,6 +81,12 @@ All notable user-facing changes are documented here. The project follows [Semant
81
81
 
82
82
  ### Changed
83
83
 
84
+ - **Windows Validate legs run again on GitHub-hosted `windows-latest`.** The PR gate
85
+ still requires only `Validate (linux, Node 22.19.0)` and `Validate (linux, Node 24)`
86
+ on ARC `kontextmind-doks`. Windows Node 22.19.0 and 24 report `validate:pr` but are
87
+ not protect-main required checks. Nightly complete coverage and release stay on
88
+ Linux. See [CI and release](docs/contributing/ci-and-release.md).
89
+
84
90
  - **The rotation surface drive uses is the one setup writes.** Guide setup appends only
85
91
  reviewed selectors to `.kxm/routes.yaml`. It skips Google guide candidates: Google's
86
92
  route is the Pi `antigravity` provider, which a Runtime drive cannot reach yet, so a
@@ -24,10 +24,11 @@ flowchart LR
24
24
  MAIN -->|"daily 04:00 UTC"| NIGHT[Nightly<br/>complete suite]
25
25
  ```
26
26
 
27
- All workflows live in `.github/workflows/`. Every job runs on the organization's
28
- ARC runner scale set, and `test/core/ci-contract.test.ts` pins the
29
- runner selector, job names, coverage floors and release triggers. Change a
30
- workflow and that test together.
27
+ All workflows live in `.github/workflows/`. Linux jobs run on the organization's
28
+ ARC runner scale set. Validate also runs two Windows legs on GitHub-hosted
29
+ `windows-latest`. `test/core/ci-contract.test.ts` pins the runner selectors, job
30
+ names, coverage floors and release triggers. Change a workflow and that test
31
+ together.
31
32
 
32
33
  ## What runs where
33
34
 
@@ -64,11 +65,14 @@ Three differences matter when a check fails on one side only:
64
65
 
65
66
  ### Validate matrix and required checks
66
67
 
67
- The Validate job runs on Node 22.19.0 and Node 24, on Linux, with a
68
- three-minute job timeout. The branch ruleset
69
- requires the job names `Validate (linux, Node 22.19.0)` and
70
- `Validate (linux, Node 24)`, so renaming the job or the matrix means updating
71
- the ruleset in the same change. A newer push cancels an older pull request run;
68
+ The Validate job runs on Node 22.19.0 and Node 24, on Linux and Windows. Linux
69
+ uses the ARC scale set `kontextmind-doks` with a three-minute job timeout.
70
+ Windows uses GitHub-hosted `windows-latest` with a fifteen-minute timeout so
71
+ `npm ci` can finish. The branch ruleset requires the job names
72
+ `Validate (linux, Node 22.19.0)` and `Validate (linux, Node 24)` only; the
73
+ Windows names are reported but not required, so a Windows-only failure does not
74
+ block merge. Renaming a required Linux job or the matrix means updating the
75
+ ruleset in the same change. A newer push cancels an older pull request run;
72
76
  runs on `main` are never cancelled.
73
77
 
74
78
  ### CI jobs stay queued while a runner is online
@@ -106,9 +110,11 @@ autoscaler. Do not relabel `km-gh-rn01` or push an empty commit as a routing
106
110
  workaround.
107
111
 
108
112
  > [!NOTE]
109
- > Windows legs are paused, not removed. Windows stays a supported target, and
110
- > Windows-specific fixtures (for example the `pi.cmd` worker launch in
111
- > `test/core/worker.test.ts`) run when you test on Windows locally.
113
+ > Windows Validate uses GitHub-hosted `windows-latest`, not a self-hosted
114
+ > homelab runner and not the ARC scale set. Do not add a `kontextmind-doks`
115
+ > label to a Windows runner. Nightly complete coverage and release stay on
116
+ > Linux. Windows-specific fixtures (for example the `pi.cmd` worker launch in
117
+ > `test/core/worker.test.ts`) also run in the hosted Windows Validate legs.
112
118
 
113
119
  ### The docs-only classifier
114
120
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kontextmind/kxm",
3
- "version": "0.7.111",
3
+ "version": "0.7.112",
4
4
  "description": "KXM local-first multi-agent orchestration and operator dashboard",
5
5
  "type": "module",
6
6
  "author": "KontextMind",
@@ -2,7 +2,7 @@
2
2
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
3
3
  "name": "kxm",
4
4
  "displayName": "KXM",
5
- "version": "0.7.111",
5
+ "version": "0.7.112",
6
6
  "description": "Headless multi-agent orchestration, durable workflows, and a live operator dashboard for Pi and Claude Code",
7
7
  "author": {
8
8
  "name": "KontextMind",
@@ -17313,7 +17313,7 @@ function sessionTokenFixHint(policy) {
17313
17313
  }
17314
17314
 
17315
17315
  // plugins/kxm/src/mcp-server.ts
17316
- var VERSION = "0.7.111";
17316
+ var VERSION = "0.7.112";
17317
17317
  var CONFIGURE_PLUGIN = "/plugin configure kxm@kxm";
17318
17318
  var inbox = /* @__PURE__ */ new Map();
17319
17319
  var notifiedInbox = /* @__PURE__ */ new Set();
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-plugin",
3
- "version": "0.7.111",
3
+ "version": "0.7.112",
4
4
  "private": true,
5
5
  "type": "module",
6
6
  "engines": {
@@ -11,7 +11,7 @@ import { deliverInboxNotification } from "./inbox.ts";
11
11
  import type { HubEvent, MessageRecord } from "./protocol.ts";
12
12
  import { sessionTokenFixHint } from "./session-token-hint.ts";
13
13
 
14
- const VERSION = "0.7.111";
14
+ const VERSION = "0.7.112";
15
15
  const CONFIGURE_PLUGIN = "/plugin configure kxm@kxm";
16
16
  const inbox = new Map<string, MessageRecord>();
17
17
  const notifiedInbox = new Set<string>();