@kontextmind/kxm 0.7.85 → 0.7.87

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.85",
14
+ "version": "0.7.87",
15
15
  "category": "development",
16
16
  "tags": ["kxm", "multi-agent", "workflows", "mcp"]
17
17
  }
@@ -310,6 +310,8 @@ The gate group contains exactly the five implemented gates listed above. Names d
310
310
 
311
311
  Global flags: `--json`, `--dry-run`, `--workspace`. Project-root `kxm init` discovers from the current directory, rejects `--workspace`, and intentionally ignores legacy `KXM_*` workspace overrides; `--workspace` continues to scope current hub commands. Root init accepts repeated `--repository <id=absolute-path>` member bindings and uses the platform-local state root described above. `kxm workflow start <definitionId> --payload <JSON|@file>` creates a signed webhook delivery. With an active definition source, start, signal, and GitHub watch resolve that definition's `secretEnv` / `signalSecretEnv`; when no separate signal secret is declared, callbacks use the workflow-start secret, matching the hub. Generic credential variables are used only when no active definition source is configured. `--dry-run` never appends telemetry. Non-dry-run gate evidence and summaries are written to the protected telemetry JSONL after configured-value redaction; do not place unnecessary sensitive text in evidence. `kxm gate degrade` requires `KXM_AUTH_TOKEN` to contain the administrative token; use `--dry-run --json` first and never put a secret in its reason. `kxm agent worker --name <name> --project <project>` and `kxm hub start` honor the same workspace flag. `--no-continue` disables every session resume; `--fresh-start` skips only the initial resume. `--session-isolation workflow` enables isolated contexts and starts a fresh scoped default history on first use; `--session-isolation off` is the upgrade-compatible default and keeps the former shared Pi history. GitHub watch posts an exact signed `failed` signal on timeout and exits `4`, preserving the distinction from a successful gate.
312
312
 
313
+ **`--dry-run` changes nothing.** Every command either only reads, or stops at its plan: the envelope it prints when it runs, with `dryRun: true` and a `planned` list of `{ "action", "target" }` entries (`write`, `delete`, `move`, `request`, `ssh`). A dry run writes no file, sends no mutating hub request, starts no Runtime supervisor, persists no session token, and runs nothing on a remote host; its reads of local SQLite stores do not even leave `-wal`/`-shm` sidecars behind. `kxm backup --dry-run` lists the stores and target files without opening a source store (opening one checkpoints its WAL); `kxm restore --dry-run` verifies the manifest and every backup digest, checks each store's recorded schema version against this build's ceiling, and lists the stores it would overwrite — a real restore now runs the same checks for every store before it overwrites the first. A create that assigns an id when it runs (`goal create`, `task create`, `memory note`) plans with a preview id the real run will not reuse. A command that cannot say what it would do without doing part of it refuses with exit `2` and `dry_run_unsupported` instead of running: `kxm runs status|list|receipt` when no supervisor is running (answering would start one) and the interactive `kxm models` screen. That refusal is also the default: the CLI keeps one list of the commands that answer `--dry-run`, and any command missing from it is refused before its action runs.
314
+
313
315
  ## Webhook workflow settings
314
316
 
315
317
  Configure either `KXM_WEBHOOK_WORKFLOWS` or `KXM_WEBHOOK_WORKFLOWS_FILE`, never both. A definition selects a provider source, project, coordinator, event and payload filters, prompt template, and ordered stages. Use `secretEnv` to resolve the workflow-start HMAC secret from another environment variable. Use the optional `signalSecretEnv` for a separate callback secret; otherwise external signals use the workflow-start secret. Do not store either secret in JSON.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kontextmind/kxm",
3
- "version": "0.7.85",
3
+ "version": "0.7.87",
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.85",
5
+ "version": "0.7.87",
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",