@dzhechkov/harness-cli 0.8.26 → 0.8.27

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.
package/.dz-manifest.json CHANGED
@@ -9,7 +9,7 @@
9
9
  },
10
10
  {
11
11
  "path": "README.md",
12
- "sha256": "61e9c0cf5c85f1a9841af35346e6ff6351b8cdb95d11aa3b5b7c0bd82d0a6a5e"
12
+ "sha256": "04f79f962ddeb8712933c36d691eb3bb54c7a41f7e59d298ac3ad1862bc2d9ef"
13
13
  },
14
14
  {
15
15
  "path": "dist/bin.d.ts",
@@ -149,7 +149,7 @@
149
149
  },
150
150
  {
151
151
  "path": "package.json",
152
- "sha256": "15747dd6aec74f1ea5202fb43ecc81ded2f8f1a7e7471fd26561c863b4ee3ac8"
152
+ "sha256": "88f5df48323c83afd1153dc13dbd1452a2a635aea855dbd2b4ad06820e179f5c"
153
153
  },
154
154
  {
155
155
  "path": "src/bin.ts",
@@ -185,5 +185,5 @@
185
185
  }
186
186
  ]
187
187
  },
188
- "signature": "eCd/+2pUENEEaUOCGFqCLA0FRD18kvDSmNY4YNaJTSmFeT+QI+UO54LdRm7FlUvzAvUkigu+hZDx0pfdC2h1AQ=="
188
+ "signature": "OP/y34/i1OigqorzDUD4re9FZNcB48J6joi+Uz1H9AMBpIfH2fxONGL59n3xh5aR1zaEOar2BnrVucP2udw3CQ=="
189
189
  }
package/README.md CHANGED
@@ -3391,7 +3391,7 @@ dz publish: BLOCKED harness-cli — sibling drift: @dzhechkov/memory@0.2.20 on t
3391
3391
  dz publish: refusing to publish (1 sibling-drift violation(s))
3392
3392
 
3393
3393
  $ dz publish --filter harness-cli --yes
3394
- dz publish: tarball @dzhechkov/harness-cli@0.8.26 sha256:9f2c…e10a
3394
+ dz publish: tarball @dzhechkov/harness-cli@0.8.27 sha256:9f2c…e10a
3395
3395
  dz publish: ✓ packed install smoke
3396
3396
  ✓ @dzhechkov/harness-cli 1.0.0 → 1.0.1 published (confirmed by registry after 1 probes)
3397
3397
  sha256:9f2c…e10a
@@ -3716,7 +3716,7 @@ Self-learning is a three-leg loop: **collect** (session hooks write into the sto
3716
3716
  Before this feature `dz setup` shipped the first two legs only — the apply leg's files existed
3717
3717
  solely in this repo's own `.claude/helpers/`, so every OTHER project that ran `dz setup --memory
3718
3718
  agentdb` got collection and ranking, but never automatic recall (MEASURED: a clean install wrote no
3719
- `UserPromptSubmit` entry at all, on 0.8.10 and 0.8.26 alike, with or without `--memory agentdb`).
3719
+ `UserPromptSubmit` entry at all, on 0.8.10 and 0.8.25 alike, with or without `--memory agentdb`).
3720
3720
 
3721
3721
  `dz setup --target claude-code --memory agentdb` now installs all three, additively (a repeat run
3722
3722
  changes nothing; a foreign hook you wrote yourself is left exactly where it is):
@@ -3740,7 +3740,7 @@ from `CLAUDE_PROJECT_DIR || cwd()` — the SESSION's project. A user-level insta
3740
3740
  (`dz setup --target claude-code --memory agentdb --project $HOME`, expecting the leg everywhere)
3741
3741
  silently looked up a DIFFERENT project's `.dz/` from every other session, and the `UserPromptSubmit`
3742
3742
  command itself broke down to `Cannot find module` (swallowed silently) whenever `project === $HOME`
3743
- and a session's own `CLAUDE_PROJECT_DIR` pointed elsewhere (issue #2, MEASURED on 0.8.26). Fixed: the
3743
+ and a session's own `CLAUDE_PROJECT_DIR` pointed elsewhere (issue #2, MEASURED on 0.8.25). Fixed: the
3744
3744
  hook and daemon now resolve their own INSTALL location first (`path.resolve(__dirname, '..', '..')`
3745
3745
  for the hook — the precedent already used by the destructive-guard hook), and `dz setup` writes the
3746
3746
  `UserPromptSubmit`/`SessionStart` commands as an ABSOLUTE path to that install root instead of the
@@ -5390,7 +5390,7 @@ refusal as the honest answer.
5390
5390
 
5391
5391
  ## Status
5392
5392
 
5393
- `harness-core v0.8.35` · `harness-cli v0.8.26` · `memory v0.2.22` — **this release (night 14→15.09, 8 features, each
5393
+ `harness-core v0.8.35` · `harness-cli v0.8.27` · `memory v0.2.22` — **this release (night 14→15.09, 8 features, each
5394
5394
  cross-family reviewed by Codex): the recall hook resolves its store from the INSTALL root, never from the session's cwd,
5395
5395
  and is never silent; the skill walker follows symlinks, drops build junk and names everything it skipped; one-character
5396
5396
  recall terms are searchable; and the mutation gate stays honest under load.**
@@ -5411,7 +5411,7 @@ for Latin script only (one combining mark — exactly FTS5 `unicode61 remove_dia
5411
5411
  gates only its own entries. (e) `store-generation-counter`: the daemon's engine cache invalidates on a generation bump
5412
5412
  written under a named lock. (f) `sandbox-copy-remaining-sites` + `full-suite-flake-fixes-2`: measured budgets
5413
5413
  (≥ 2× p95 under load), spawn timeouts strictly below the test budget, `waitForSocketReady` for daemon tests.
5414
- Previous release (v0.8.34 / v0.8.26): the recall hook and `dz recall` share ONE hybrid
5414
+ Previous release (v0.8.34 / v0.8.25): the recall hook and `dz recall` share ONE hybrid
5415
5415
  engine, the embedder is cached per process, and every publish-gate verdict is a durable per-package audit record.
5416
5416
  (0) Hook/CLI recall parity (`hook-recall-hybrid-parity`): the embed daemon answers `op: recall` through core's
5417
5417
  `recallHybrid` under a 500 ms budget (measured p95 100–190 ms on the real 743-pattern store, 99–100 of 100
@@ -5420,7 +5420,7 @@ and an engine cache used ONLY by the hook (`dz recall` itself resolves fresh); `
5420
5420
  The agentdb embedder is cached per process (`agentdb-embedder-cache`: cold 2117 ms → warm 1 ms). Sibling-drift
5421
5421
  inventories come from `pnpm pack` — the live transport — so the LICENSE pnpm synthesises from the workspace root
5422
5422
  no longer reads as drift; every gate verdict is one fsync'd audit record per package with `sha256:<hex|n/a>`.
5423
- Previous release (v0.8.33 / v0.8.26): `dz publish` refuses a broken pair, `dz setup`
5423
+ Previous release (v0.8.33 / v0.8.24): `dz publish` refuses a broken pair, `dz setup`
5424
5424
  reads the memory backend from config, and the embed daemon says "ready" only with a socket that exists.
5425
5425
  (1) Sibling-drift gate + packed install smoke: before any live `npm publish`, every `workspace:*` sibling on
5426
5426
  the registry is compared with the workspace (dist/files/bin + the shipping fields of package.json); a
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dzhechkov/harness-cli",
3
- "version": "0.8.26",
3
+ "version": "0.8.27",
4
4
  "description": "The dz CLI — install AI skills for Claude Code, Codex, OpenCode, Hermes, OpenClaude, GitHub Copilot. 87 commands, 14 presets, 10 platform targets.",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/sbom.json CHANGED
@@ -25,7 +25,7 @@
25
25
  "hashes": [
26
26
  {
27
27
  "alg": "SHA-256",
28
- "content": "61e9c0cf5c85f1a9841af35346e6ff6351b8cdb95d11aa3b5b7c0bd82d0a6a5e"
28
+ "content": "04f79f962ddeb8712933c36d691eb3bb54c7a41f7e59d298ac3ad1862bc2d9ef"
29
29
  }
30
30
  ]
31
31
  },
@@ -379,7 +379,7 @@
379
379
  },
380
380
  {
381
381
  "name": "dz:canonical-json-sha256-v2",
382
- "value": "15747dd6aec74f1ea5202fb43ecc81ded2f8f1a7e7471fd26561c863b4ee3ac8"
382
+ "value": "88f5df48323c83afd1153dc13dbd1452a2a635aea855dbd2b4ad06820e179f5c"
383
383
  }
384
384
  ]
385
385
  },