@dzhechkov/harness-cli 0.4.6 → 0.5.0

package/.dz-manifest.json

@@ -9,43 +9,63 @@
       },
       {
         "path": "README.md",
-        "sha256": "2f053f11ea49780919d0557877302e70adb8f33949299b0b0637ece2809c1b67"
+        "sha256": "27e2ddfd256e5c89a1c51a2520b52cc4b947dd7295f5730bde0a2c735186fb8f"
       },
       {
         "path": "coverage/coverage-final.json",
-        "sha256": "e539390d6899ede6cdd0acb76cae6c58e90d4fb3d4389c00dce8604a014aeea7"
+        "sha256": "d2eef62228d4f2b31f5c7fca703f0f6844cf517d41be9dee516f3489f5babfec"
+      },
+      {
+        "path": "coverage/coverage-summary.json",
+        "sha256": "981eef381eb1e9a040a31eaa561ea078c6f6711d9908990e796d5213d6ffe89f"
       },
       {
         "path": "dist/bin.d.ts",
-        "sha256": "58be9f04d2fe63cca2efe3957b9933068e443a0e57f9838ff9ef800cc191e03f"
+        "sha256": "1d651fdfe05fc306c857bbbee44c395b63b39c1e0c53a8166eb7ca43c6cfa157"
       },
       {
         "path": "dist/bin.d.ts.map",
-        "sha256": "b1e41c8c19fa56ae9dec2267740eb4389bc785431478861a8843867f99c1b25b"
+        "sha256": "74105b3edb4c4a7d75393a7cb2dda06a0f545b1cce75e9a772a30b18b3609374"
       },
       {
         "path": "dist/bin.js",
-        "sha256": "c4a6b64f875db72a2897df0e3b0c7cd279308dba2471ae29a57775dad7a7d8f8"
+        "sha256": "e215d5ebb9d87106c3bdfda29c8cb1af59bc9bdbd62c11b2b6a313a2bd3ecd7c"
       },
       {
         "path": "dist/bin.js.map",
-        "sha256": "9661e4d167ea1c13c3f40de510f311024da3c44bcb452d3781fb89f46373eadc"
+        "sha256": "31849f2576f6e57a8a71f49cbb1a6e6c692f98dd8303217ec836933420d08dac"
       },
       {
         "path": "dist/cli.d.ts",
-        "sha256": "9afd7c4a02708d7d425214c5d3b76a2ad7bd5ea3ba6c725e4880a91d76062f34"
+        "sha256": "56db11f99b505b2ffbc314aa70b4bcd17ec741e14ca99a3662d0ca9f4afcc1cc"
       },
       {
         "path": "dist/cli.d.ts.map",
-        "sha256": "5bdc153e789ac180543e9b4955ea36666dc27b7238637b05875e048fc49ae30f"
+        "sha256": "19170be889713fffd051dfde1044074125f66bb4623e415c355f812a47721436"
       },
       {
         "path": "dist/cli.js",
-        "sha256": "0183c01a98e232554a7460be48ee5fdf59dd3a7d09c719a31b08acc9c6b3528c"
+        "sha256": "c80fe1740887b68a3521ee6d22e09303785238c6e27dd0c80fb76289927e73a4"
       },
       {
         "path": "dist/cli.js.map",
-        "sha256": "c5bd1b0b852dd21de328494d7a99db336afbde4397b7c687d416f1a6f3c297b2"
+        "sha256": "1ef2072181086e6b14c30005417f3edba91db5c3f2ae82201236ea493385d6a8"
+      },
+      {
+        "path": "dist/core-compat.d.ts",
+        "sha256": "dedfc859e163f229af0445d6439172a4b66c150c0942bce3ae1bf0304dbb3290"
+      },
+      {
+        "path": "dist/core-compat.d.ts.map",
+        "sha256": "bce1ded9ffac15080908af1a9571b67141c141374ec4ba90b987fd6fd8883aab"
+      },
+      {
+        "path": "dist/core-compat.js",
+        "sha256": "57930e6918c2a5d90826c74924a62de9a1ffab53d8196ff8f98a59c89baf23be"
+      },
+      {
+        "path": "dist/core-compat.js.map",
+        "sha256": "e95005978fdd733f78208d6d916f62f970123530241739c9da7d3a74154b7a13"
       },
       {
         "path": "dist/index.d.ts",
@@ -69,28 +89,64 @@
       },
       {
         "path": "package.json",
-        "sha256": "00a53276d145112e3c2ae5ca2950ac74877ea4b069b2b81040d49c5903eb6482"
+        "sha256": "be73e142cc0dcd05cf774c73827572b1e55e503c8ab84f4a396fa785b271980b"
       },
       {
         "path": "src/bin.ts",
-        "sha256": "f799d9771166fe95eb40463d1ebbeb0dd3acdd78fa9c692e086a6a673f54752a"
+        "sha256": "42a1f67e1f39c4cda2df0887c16fbb6f54eb108ba0cb18612bb83ee153092463"
       },
       {
         "path": "src/cli.ts",
-        "sha256": "0a1097fc3a2294f934fc50f5871b287cfbc5ec85becdab914b7caeca42cb7d1a"
+        "sha256": "c875709ccafe3493342776b28c8aa7b34e1fb800e2fccedcb499e6490e6ad1c0"
+      },
+      {
+        "path": "src/core-compat.ts",
+        "sha256": "3638272a91166a047c3edc14626c0011e91b2de862a197d1b8e424470e7a0575"
       },
       {
         "path": "src/index.ts",
         "sha256": "395b27b317e575b94a1049cdb284db185e0ec382fbae1e588c78ff2398b2563f"
       },
+      {
+        "path": "test/agents-sync.test.ts",
+        "sha256": "32606890dc57d58257e6b4a38246acb343eea88b6e4b2f643f061325a34d066a"
+      },
       {
         "path": "test/cli.test.ts",
-        "sha256": "c66bdd2fbbe2e0b622e3bc4e0e4521e865cc8088e581bd4b4862c1c550307900"
+        "sha256": "83d8c6a9d7e8d46b57bb2e5da47c0345e8a512bdcc2e7cc8c59e163ade41de10"
+      },
+      {
+        "path": "test/command-count.test.ts",
+        "sha256": "9958e10a8adb80ee64baad0d91fb4c9a3b6e8801c6379f7ba5f8f5ab6c1f1716"
+      },
+      {
+        "path": "test/core-compat-guard.test.ts",
+        "sha256": "98086d0b6bd7ce32cc844e0cbbc710c4dbf009389c1d020aed48ced2de8acd57"
+      },
+      {
+        "path": "test/core-compat.test.ts",
+        "sha256": "c54d5aa80a2455a396b396ff9fc398c141c3be4ec9c830e0941f830658758866"
+      },
+      {
+        "path": "test/core-import-floor.test.ts",
+        "sha256": "84e16e0f31608570f72575038ae246d9ff002671ade0e9f9fa6009dd862dfc03"
+      },
+      {
+        "path": "test/discrimination-check-cli.test.ts",
+        "sha256": "cd7507c8ec1f621fea6f05596541235d09efbd215540b56b012cf465e06b6ba0"
       },
       {
         "path": "test/epoch-replay-cli.test.ts",
         "sha256": "a5a48585b565288ca1ea96030b02b2ccb37a621ef7b3cfe54cd7aaa7164d6904"
       },
+      {
+        "path": "test/fixtures/discrimination-check/fake-runner.sh",
+        "sha256": "126bbd1ba9c08ef9de826cfa21df3981720e4bc36cd993dff28e0de435cbebae"
+      },
+      {
+        "path": "test/fixtures/discrimination-check/fixture.py",
+        "sha256": "bb413a8b6e9dc597eb298e7646fb84e23ccd3e117eb61201776ef3e9e27a0e0a"
+      },
       {
         "path": "test/fixtures/install-layouts-helpers.ts",
         "sha256": "7c1d53c295ec4cb7ee8e3036b663f20d660a1acff35dbcb5c99257aed7268b68"
@@ -183,22 +239,42 @@
         "path": "test/install-layouts.test.ts",
         "sha256": "43cc6e3251500cd547997ac0916c250c8558f6c3d5c4a60254753e1e80ba24f5"
       },
+      {
+        "path": "test/install-sync-partial.test.ts",
+        "sha256": "35824489662dbe9315d78cd20ecf968d416fbe80685d74b6588c8521a08497ea"
+      },
+      {
+        "path": "test/list-partial.test.ts",
+        "sha256": "fd98385a9b1021cf8341d154abcdf4506a84aaadddd465fcc7e057ba1927fe64"
+      },
       {
         "path": "test/mutation-gate-cli.test.ts",
         "sha256": "3b33c786713e2dfaa192ea32df8cdcf534170c59d58ce285872a3fde008afbc4"
       },
       {
         "path": "test/mutation-registry.json",
-        "sha256": "fe8e5792626cf58678c1e2bcb809f63413655c2e171439157b74deb8b4fd80fb"
+        "sha256": "3e6f9bb105154121988da41568ff85573099235857ba25e76c4264c166b414ae"
+      },
+      {
+        "path": "test/skills-verify-static-advisories.test.ts",
+        "sha256": "b1140c20ec04d1c8ae67f97a42dbcece1e8e63c98a5de2c087f0359d27c25f17"
       },
       {
         "path": "test/statusline-panel.test.ts",
         "sha256": "b09b42c4ece1a83e5d3f3765629b0756a8f30a7122f3fc30363f93f092a44c0d"
       },
+      {
+        "path": "test/target-alias-cli.test.ts",
+        "sha256": "96df42acb1cc5ada5ca97912d3b7da5b486067e851b9dd395855b1b540ce738c"
+      },
       {
         "path": "test/trace-bundle-cli.test.ts",
         "sha256": "fdaad63359ca7ce351e505e613b547bbc653e0847403edfae88d22a8a524b7a0"
       },
+      {
+        "path": "test/version-flag.test.ts",
+        "sha256": "7acd80deb073fb2987c6d14a028a64c6d44324ac61a05410b7d4b6c87ff5acc6"
+      },
       {
         "path": "test/workflow-init-lint-clean.test.ts",
         "sha256": "b7a64462983901adca86ecc29e76b3f95885210e5aaba68352356191e6bfac7f"
@@ -221,5 +297,5 @@
       }
     ]
   },
-  "signature": "6IQyjN4aazsr6EyD1+y/VrZ1+bclvxc9nXsCLR3WVDomAn6AhNtlTJQWdfbvw49A4/HH+KTW+KkJlj/gFFnqCw=="
+  "signature": "jyIwJnH5LH3+Wrq8W19HGqMpqt8e0srMnfZH/atV2H3ddnlrYzMe0f7bvyigDpdLzVApxiq+Xna5z4psVILMDg=="
 }

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 dzhechko
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -125,6 +125,140 @@ point any tool at (a skill is just Markdown). Dedicated targets are on the [road
 **❌ No target applies:** `nemoclaw` (NVIDIA agent-safety runtime — not a code editor, no rules file) ·
 `v0` (UI-only, no repo file). *(`pi` is a real coder but reads `AGENTS.md` → covered by `agents-md`.)*
 
+#### `--target` aliases and did-you-mean
+
+`--target claude` used to be rejected outright — the canonical name is `claude-code`, and the error
+just re-printed the list. All **eight** `--target`-taking commands (`init`, `verify`, `install`,
+`compose`, `setup`, `upgrade`, `parity`, `feature-adr-setup`) now resolve the value first.
+
+*(This sentence used to say "every" and name only seven: `dz parity` was missed, and shipped the
+original defect verbatim. It is now checked rather than promised — `test/target-alias-cli.test.ts`
+asserts that no command reads `--target` without reaching the resolver, and that every command whose
+`--help` advertises `--target` appears in the per-command sweep.)*
+
+**Accepted aliases** (a table, so adding one is a data edit):
+
+| You type | You get | Why it is a row |
+|----------|---------|-----------------|
+| `claude` · `cc` | `claude-code` | the tool's everyday name |
+| `agents` | `agents-md` | the everyday name of the `AGENTS.md` target |
+| `gpt` · `openai` | `codex` | the vendor name, not the CLI's |
+
+Case, padding and separators are handled **without** a row: `CLAUDE`, `Claude_Code`, `claudecode`
+and `  claude-code  ` all resolve to `claude-code`; `agentsmd` and `agents.md` resolve to `agents-md`.
+
+**A typo is SUGGESTED, never silently accepted** — installing to the wrong target on a guess is worse
+than one round-trip:
+
+```console
+$ dz init --target clade-code --preset devops > out.txt   # the refusal is on STDERR
+dz init: unknown --target "clade-code" — did you mean "claude-code"?
+  --target must be one of: agents-md, claude-code, codex, copilot, cursor, gemini, hermes, openclaude, opencode, windsurf
+$ echo $?
+1
+$ wc -c out.txt
+0 out.txt        # stdout stays a clean data channel, even on a refusal
+```
+
+**Both lines go to stderr** — the refusal, like the alias note below, is diagnosis, not data. `dz
+parity --target <bad> --json` likewise writes its structured error to stderr and leaves stdout empty,
+so `| jq` is never handed a diagnostic.
+
+An ambiguous prefix gets no guess at all (`--target co` could be `codex` or `copilot`), and neither
+does nonsense (`--target totally-bogus` prints the plain list). When an alias IS accepted, the
+substitution is announced **on stderr**, so piped stdout stays machine-readable:
+
+```console
+$ dz init --target claude --preset devops > installed.txt
+dz init: --target "claude" → claude-code (alias)
+```
+
+**When this matters:** you are following a blog post or a teammate's snippet that says `--target claude`.
+It now works, and you are told what it resolved to.
+
+### `dz list` — one broken skill never hides the rest
+
+`dz list` used to abort on the FIRST unparseable `SKILL.md`: exit 1, an error naming neither the file
+nor a count, and every other skill in the tree invisible. A pack you installed could blank your whole
+listing. Now the loadable skills are listed on **stdout** and the unloadable ones are named on
+**stderr**:
+
+```console
+$ dz list --skills-dir .claude/skills
+105 skill(s) in /home/you/proj/.claude/skills:
+
+  api-design                          Designs REST and GraphQL APIs with OpenAPI specs…
+  …103 more…
+  test-writer                         Writes focused unit and integration tests…
+$ echo $?
+1
+```
+
+…with the diagnosis kept out of the data:
+
+```console
+$ dz list --skills-dir .claude/skills 2>/dev/null   # stdout only — clean, pipeable
+105 skill(s) in …
+
+$ dz list --skills-dir .claude/skills 1>/dev/null   # stderr only — the actionable part
+dz list: 105 listed, 1 skipped in /home/you/proj/.claude/skills
+⚠ 1 skill(s) skipped (unparseable SKILL.md):
+  /home/you/proj/.claude/skills/broken-one/SKILL.md
+    SKILL.md must begin with a "---" frontmatter fence
+    (line 1: "# Broken One")
+```
+
+The full contract:
+
+| valid skills | skipped | stdout | stderr | exit |
+|--------------|---------|--------|--------|------|
+| >0 | 0 | the listing | *empty* | 0 |
+| >0 | >0 | the listing of the valid ones | named summary | 1 |
+| 0 | >0 | *nothing* | named summary (`0 listed, N skipped`) | 1 |
+| 0 | 0 | *nothing* | `dz list: no skills found in <dir>` | 1 |
+
+`dz init`, `dz install` and `dz sync` behave the same way — the good skills are installed, the bad ones
+are named, and the command exits 1.
+
+**Two failure kinds, two headers, two subjects.** A skill that will not PARSE and a skill that will not
+WRITE are different accusations, so `dz init` reports them separately:
+
+```console
+$ dz init --target claude-code --skills-dir ./skills --project ./proj
+dz init --target claude-code: 1 skill(s), 1 file(s) written, 0 skipped
+dz init: 1 installed, 1 failed to write                       # ← stderr
+✗ 1 skill(s) failed to install (compile/write error):
+  alpha
+    EEXIST: file already exists, mkdir './proj/.claude/skills/alpha'
+```
+
+The header names the **target**, not `alpha/SKILL.md` — which is perfectly valid. (It used to print
+`⚠ 1 skill(s) skipped (unparseable SKILL.md)` and quote `line 1: "---"`, a valid frontmatter fence, as
+its evidence: a failure that names the wrong artifact is worse than an anonymous one.)
+
+`dz install` renders the offending path **relative to the package**
+and says so explicitly, because a `node_modules/**` path is not something you can act on:
+
+```console
+$ dz install @someone/skills-pack
+dz install @someone/skills-pack: 12 skill(s), 24 file(s) written, 0 skipped
+dz install: @someone/skills-pack ships 1 unparseable skill(s) —
+⚠ 1 skill(s) skipped (unparseable SKILL.md):
+  skills/broken-one/SKILL.md
+    SKILL.md must begin with a "---" frontmatter fence
+This is a defect in the package, not in your project.
+Workaround: npx -y @someone/skills-pack init
+```
+
+**When this matters:** a package you installed shipped a broken skill — you still see everything else,
+you know exactly which file is at fault, and you know whose defect it is.
+
+> **`dz` requires `@dzhechkov/harness-core >= 0.4.7`.** If you ever see
+> `dz: needs @dzhechkov/harness-core >= 0.4.7, found 0.4.1`, a stale core was reused from a cache:
+> `rm -rf ~/.npm/_npx && npx @dzhechkov/harness-cli@latest --version`. That named message replaced a
+> bare `SyntaxError: … does not provide an export named 'GRADE_SUCCESS_FLOOR'` that used to kill even
+> `dz --version`.
+
 > **"Nothing installs" / "no skills found"?** Update the CLI:
 > `cd /tmp && npm i -g @dzhechkov/harness-cli@latest`. Older global installs couldn't locate their
 > own bundled packs outside the monorepo — now fixed, so `dz registry`/`dz init`/`dz setup` work
@@ -132,7 +266,7 @@ point any tool at (a skill is just Markdown). Dedicated targets are on the [road
 
 ## User Journey — from install to mastery
 
-All 66 commands (MEASURED — reproducer: `grep -c "^      case '" src/cli.ts`, the dispatch cases) mapped to a real workflow:
+All 67 commands (MEASURED — reproducer: `grep -c "^      case '" src/cli.ts`, the dispatch cases) mapped to a real workflow:
 
 ```
 DISCOVER → INSTALL → USE → CREATE → MAINTAIN → SHARE
@@ -1015,7 +1149,7 @@ green: re-sign reminder (`dz sign …` — the publish signature gate is refuse-
 before a multi-package npm release, or whenever a broken dist/bin must be impossible to ship; keep plain
 `dz publish` for routine pushes. `dz publish` itself is byte-identical whether or not release exists.
 
-### Skill Packs (23 packs · 179 skills)
+### Skill Packs (18 packs · 189 skills)
 
 Each pack is an npm package — click through for the **full per-skill documentation** (what each skill does + how to trigger it). Install a whole pack with `dz install <pkg>`, or pick skills with `dz init --select` / a `--preset`.
 
@@ -1038,6 +1172,7 @@ Each pack is an npm package — click through for the **full per-skill documenta
 | [@dzhechkov/skills-taste](https://www.npmjs.com/package/@dzhechkov/skills-taste) | 1 | *imported (MIT)* — `design-taste-frontend`: anti-slop landing/portfolio/redesign framework (dials + pre-flight + GSAP skeletons); complements frontend-design (`dz init --select design-taste-frontend`) ([ADR-0002](https://github.com/djd1m/dz-harness-hub/blob/main/docs/adr/0002-product-and-design-expansion.md)) |
 | [@dzhechkov/skills-book-digitizer](https://www.npmjs.com/package/@dzhechkov/skills-book-digitizer) | 8 | *dz-original* — book → installable methodology pack: `digitize-book` (orchestrator) + ingest/extract/distill/pack/kb-index + `book-brain-register` (CP6 promote → cross-project brain) + `source-brain-ingest` (repo sibling). Verified provenance, IP-safe, resumable (`dz init --select digitize-book`) ([ADR-001](https://github.com/djd1m/dz-harness-hub/blob/main/features/book-knowledge-digitizer/03_adr/001-book-to-skillpack-pipeline.md)) |
 | [@dzhechkov/skills-12factor](https://www.npmjs.com/package/@dzhechkov/skills-12factor) | 12 | *generated by the digitizer, CC BY 4.0* — The Twelve-Factor App distilled into 12 decision-moment skills (one per factor). The first PUBLIC digitized-book pack; paraphrased (shingling-gated), routing-gated (every factor carries triggers), attributed (`NOTICE`) (`dz init --select 12factor-config-in-environment,…`) |
+| [@dzhechkov/skills-book-ai-apps](https://www.npmjs.com/package/@dzhechkov/skills-book-ai-apps) | 17 | *generated by the digitizer, CP5-published* — «Building Applications with AI Agents» (Albada, рус. пер.) distilled into 17 decision-moment skills across the whole agent-building arc: agent-fit & model choice, single-vs-multi, orchestration, tool design, knowledge & memory, context engineering, evaluation, probabilistic behaviour checks, release gates, improvement loops, drift, human-in-the-loop, agent UX, governance, security. Ships our page-anchored Knowledge Units, NOT the book text — shingling-gated at 0 uncited verbatim runs >=8 words; publication is the recorded CP5 owner decision; `trust_tier 1` (routing-gated, not human-reviewed) Since 0.2.2 it also ships `brain/ai-apps.sqlite`, the 223-KU knowledge slice: `dz brain add --from-pack @dzhechkov/skills-book-ai-apps` loads it into your `~/.dz/brain`, then `dz brain query --source ai-apps` answers in any project (`dz install @dzhechkov/skills-book-ai-apps --target claude-code`) |
 
 ### Available Presets (14)
 
@@ -1376,9 +1511,9 @@ only at their documented scopes (plan + step), and `fanouts[].registry` items mu
 ItemKey domain the trace plane enforces — `trace.emit` can never decide whether a valid plan runs.
 Deferred options are on the loop-designer roadmap.
 
-## All Commands (66)
+## All Commands (68)
 
-*(66 MEASURED — reproducer: `grep -c "^      case '" src/cli.ts`, the dispatch cases.)*
+*(67 MEASURED — reproducer: `grep -c "^      case '" src/cli.ts`, the dispatch cases.)*
 
 ```
 dz setup             --target <name> [--preset <name>] [--select id,id,...] [--skills-dir <dir>] [--memory agentdb] [--no-memory] [--no-hooks] [--install-driver] [--force]
@@ -1433,7 +1568,7 @@ dz feature-adr-setup [--plan] [--from-spec <f>] [--apply]   # guided project onb
 dz challenge --plan <plan.md> [--json] [--context-only] [--author <model>]   # adversarial plan-gate (behind the `challenge-panel` skill): assemble a WIDE context pack (plan + vision + testing + map + degradations) + the fixed C1-C8 "break it" brief for a FRESH adversary (≠ plan author); advisory, never blocks
 dz routing [--stage <s>] [--json]   # inspect the learned cost-optimal routing store: what `args.models.<stage>='auto-cost'` believes per (stage, complexity-tier, model) — gated attempts/successes/rate (feeds feature-adr model selection)
 dz bto-optimize --split|--plan|--select|--scope-check|--diff [--json]   # deterministic engine behind /bto-optimize: hold-out split + hard-capped budget + no-regress-on-holdout winner selection (defeats judge-gaming); prose-only, diff-confirmed, never auto-writes
-dz discrimination-check --test <f[,f]> [--base <ref>] [--name <filter>] [--runner <cmd>] [--json]   # §42 test-discrimination gate for feature-adr Step-8: run the ADR's property test in an isolated git worktree at pre-feature base — it MUST go red without the fix; a green is a false green (HIGH finding, advisory, never auto-aborts)
+dz discrimination-check --test <f[,f]> [--base <ref>] [--name <filter>] [--runner <cmd>] [--timeout <ms>] [--json]   # §42 test-discrimination gate for feature-adr Step-8: run the ADR's property test in an isolated git worktree at pre-feature base — it MUST go red without the fix. SEVEN verdicts, each gated on EXECUTION evidence: DISCRIMINATES · DISCRIMINATES_VIA_ERROR · NON_DISCRIMINATING (false green) · TEST_FILE_ABSENT · LOAD_ERROR_AT_BOTH_REVS · FAILS_AT_TIP · CANNOT_ISOLATE (+ typed reason). Advisory, never auto-aborts
 dz mutation-gate [--package <dir>] [--registry <file>] [--test-cmd "<cmd>"] [--only <id[,id]>] [--timeout <ms>] [--rebaseline per-entry|final] [--keep-scratch] [--json]   # the mutation gate: for each NAMED protection in a declarative registry, copy the package to a scratch dir (shadow-repo layout, node_modules symlinked, git-initialized), verify the baseline is green, apply the entry's exact {find, replace} mutation, run the suite, REQUIRE red, restore — and require the red to be ATTRIBUTABLE to the protection: a mutated file that no longer parses is MUTATION_UNPARSEABLE, a failing count far above the entry's bound (maxFailing, default from observed) is OVER_FAILING, and a restored tree that does not reproduce green makes the entry INCONCLUSIVE (flaky suite). A mutation that does not apply, a green suite, or an inconclusive run is a FAILURE — never a skip. exit 0 all proven / 1 gate failed / 2 setup error
 dz delivery-check --slug <slug> [--context-only] [--findings <f.json>] [--strict] [--author <model>] [--json]   # portable Step-10 Delivery Gate: the `manual` form that travels to every shell target — prints the 4-plane review brief (regressions ‖ security ‖ code-quality ‖ product-honesty) + artifact probes; --findings classifies a fed-back review into a fail-closed ready|blocked hand-off (only cross-validated BLOCKER/HIGH count) and writes features/<slug>/10_delivery_review.md; --strict exits 1 on blocked
 dz skills-verify     [--dir <project>] [--expect a,b] [--static] [--strict] [--timeout <s>] [--json]   # does .claude/skills/ actually REGISTER? --static = instant layout scan (CI-safe, no session): flags dirs that can never register; default also starts a real session and reads the authoritative system/init listing. exit 0 pass / 1 fail / 2 inconclusive — an unobservable registration is NEVER a pass
@@ -1456,6 +1591,8 @@ dz release           [--filter <name>] [--affected] [--audit-dev] [--tag] [--pub
 dz auto-canonicalize --source <github-url> --pack <skills-pack>
 dz sync-upstream     [--package <dir>] [--list] [--all]
 dz drift-check       [--all] [--json] [--project <dir>]   # CI gate: exit 1 on NEW shared-skill drift (baseline: .dz/drift-allowlist.json; --all incl .claude dogfood)
+dz agents-sync       [--check] [--json] [--project <dir>] # sync anchored bearing rules into the root AGENTS.md policy fence; exit 0 sync / 1 drift / 3 inconclusive
+dz hooks-sync        --target codex [--check] [--remove] [--json]  # install + ARM the dz veto/recall hooks in $CODEX_HOME/hooks.json; exit 0 armed+trusted / 1 not armed / 3 inconclusive
 dz sync-canonical    <skill> [--check] [--from <dir>] [--auto] [--project <dir>]   # heal every copy from skills-meta/<skill> or --from; no canonical + --check = compare copies to each other (exit 1 on drift); no canonical + write = refuse unless --auto (LOUD, picks most-complete copy); --check writes nothing
 dz scout             [--topics <list>] [--since <date>] [--deep] [--output <file>] [--diff] [--report]
 dz workflow          init --name <n> [--pattern pipeline|barrier|fanout|gate] [--o <plan.json>] | validate <plan.json> [--json] | render <plan.json> --o <script.js> [--check] [--force] | blobs [--check]   # loop-plan/1 authoring (the ADR-005 templates are retired)
@@ -1477,8 +1614,8 @@ dz help
 ## Global: `dz --version` / `-v` / `dz version`
 
 ```bash
-dz --version          # 0.4.6
-dz --version --json   # {"name":"dz","version":"0.4.6","node":"v22.22.0","schemas":{"loopPlan":"loop-plan/1"}}
+dz --version          # 0.4.8
+dz --version --json   # {"name":"dz","version":"0.4.8","node":"v22.22.0","schemas":{"loopPlan":"loop-plan/1"}}
 ```
 
 One line, exit 0. Unresolvable ⇒ the literal `unknown` and exit **1** — never a fabricated number,
@@ -2083,6 +2220,78 @@ dz sync-upstream --package packages/@dzhechkov/skills-devops  # check one packag
 
 Discovers all skill packs with `sources.json`, fetches SKILL.md from origin repos, reports which skills have upstream changes.
 
+### dz agents-sync — Codex starts with the repository's bearing rules
+
+Use this after changing an anchored policy clause in `CLAUDE.md` or `.claude/rules/*.md`, and run
+the check form in CI. It updates only the `dz:policies` fence in the root `AGENTS.md`; authored
+content and the independent `dz:skills` fence remain untouched.
+
+```console
+$ dz agents-sync
+dz agents-sync: wrote — 9 policy section(s), 8097 bytes (24.71% of 32768)
+
+$ dz agents-sync --check
+dz agents-sync: in sync — 9 policy section(s), 8097 bytes (24.71% of 32768)
+```
+
+Exit codes are **0** for synchronized, **1** for drift and **3** when fixed source evidence is
+missing or unreadable. `--check` never writes. Each section carries a 12-hex hash recomputed from
+its source anchor; this proves synchronization only — not that Codex read or obeyed the rule. The
+separate cold-start acceptance probe establishes runtime visibility.
+
+### dz hooks-sync — Codex runs the same veto and recall hooks Claude Code does
+
+**When to use it.** Once per machine, after `npm i -g @dzhechkov/harness-cli`, if you drive Codex as
+well as Claude Code. It installs two hooks into the **user-global** `$CODEX_HOME/hooks.json`
+(default `~/.codex/hooks.json`) and **arms** them — Codex hooks are trust-gated, and an untrusted
+entry is silently never run. Re-run it after a dz upgrade; it is byte-idempotent, so an unchanged
+install rewrites nothing and the hook keeps its trust.
+
+```console
+$ dz hooks-sync --target codex
+dz hooks-sync: codex hooks installed and ARMED (trust: trusted) — ready
+
+$ dz hooks-sync --target codex --check
+dz hooks-sync: codex hooks installed and ARMED (trust: trusted) — ready
+
+$ dz hooks-sync --target codex --remove
+dz hooks-sync: removed 2 managed entr(ies) from /root/.codex/hooks.json
+```
+
+Exit codes are **0** for armed **and** trusted, **1** for not-armed / drift / a refusal, and **3**
+when the answer is inconclusive (including "no `codex` binary on PATH", where dz writes **nothing**).
+`--check` writes nothing and is **silent** in a home that never opted in.
+
+**What the two hooks do.**
+
+| Hook | Event | Behaviour |
+|---|---|---|
+| `dz-codex-veto.cjs` | `PreToolUse` | judges the shell command against one rule, `ssh-explicit-auth-weakening` |
+| `dz-codex-recall.cjs` | `UserPromptSubmit` | injects matching learned lessons and records the use with `runtime: "codex"` |
+
+**The veto WARNS by default and never blocks.** A hit prints `DZ-VETO-WARN:` and exits 0. Enforcement
+is opt-in **per project**:
+
+```console
+$ cat .dz/config.json
+{"hooks": {"shellVeto": "block"}}     # off | warn (default) | block
+```
+
+Only then does a hit exit 2 and stop the command. The rule fires only on tokens by which the command
+*explicitly* asks for weaker ssh authentication — `sshpass`, `-o PasswordAuthentication=yes`,
+`-o PubkeyAuthentication=no`, `-o PreferredAuthentications=…password…`. A bare `ssh myhost` whose
+identity comes from `~/.ssh/config` or `ssh-agent` is **allowed**: this guard is user-global, so a
+rule that blocks the normal secure case is not a guard, it is an outage.
+
+**Radius.** Both helpers are INERT outside an opted-in dz project — the activation marker is a `.dz`
+directory, not `.git`. In a plain git checkout they take no decision, print nothing, and create
+nothing.
+
+**Removal is conservative.** `--remove` deletes only entries whose command hash is recorded in dz's
+own manifest. An entry that merely *looks* like dz's is kept and reported — dz never deletes what it
+cannot prove it wrote. Foreign entries are preserved byte-for-byte by every operation, and a
+`hooks.json.bak-<ISO>` copy (newest 3 kept) is taken before each modifying write.
+
 ### dz drift-check / dz sync-canonical — intra-monorepo skill-drift guard
 
 **What.** The same skill is physically duplicated across many packages (`packages/@dzhechkov/*/​<skill>/` + `.claude/skills/<skill>/`). These two commands make that duplication safe:
@@ -2756,23 +2965,56 @@ feature-adr Step-8 asserts the ADR's load-bearing safety property **has** a test
 false green — it may never exercise the property, so it would stay green even if the property regressed. The
 `§42` gate (learned from rUv's `cve-bench/evaluate.mjs`) proves the test **discriminates**: it runs the property
 test in a throwaway git worktree at the pre-feature base (no fix) and requires it to go **red**.
+
+**Use it when** you are about to accept "the property has a test" as evidence — in Step-8 QE, in a review of
+someone else's fix, or before trusting a regression test you did not write. Run it against `HEAD` while your
+change is still uncommitted; that is what makes `HEAD` the pre-feature base.
+
 ```bash
 # the Step-7 feature diff is uncommitted mid-pipeline, so HEAD is the pre-feature base
 dz discrimination-check --test packages/x/test/auth-property.test.ts --base HEAD --json
+
+# human output, a longer suite, and a runner that is not vitest
+dz discrimination-check --test packages/x/test/auth-property.test.ts \
+  --base HEAD --runner "node --test" --timeout 600000
 ```
 ```
 discrimination-check @ HEAD — verdict: NON_DISCRIMINATING
   ✗ packages/x/test/auth-property.test.ts: NON_DISCRIMINATING
+  measurementValid: true · primaryAction: strengthen-test
 
   [high] non-discriminating property test (false green)
-  1 property test(s) PASS at pre-feature base — they do not exercise the ADR safety property … (Advisory — the pipeline continues; the owner decides.)
+  1 property test(s) PASS at pre-feature base WITH execution evidence — they do not exercise the ADR safety
+  property and would stay green if the fix regressed … Action: strengthen-test. (Advisory — the pipeline
+  continues; the owner decides.)
 ```
-Verdicts: `DISCRIMINATES` (red by assertion — good) · `DISCRIMINATES_VIA_ERROR` (couldn't load at base, e.g. a
-brand-new module — inferred) · `NON_DISCRIMINATING` (green at base — a false green, HIGH finding) ·
-`CANNOT_ISOLATE` (no runnable property test — folds into "property untested"). It **never auto-aborts** (dz's
-rule: a false gate kills trust) — exit 0 on any verdict, exit 2 only on a usage/setup error. The worktree +
-sanitation live in tested CLI code; base ref, paths, name filter, and runner are all injection-checked, and the
-worktree is always removed. Step-8 runs this on the ADR Confirmation's `Required automated check` automatically.
+
+**Every verdict is gated on EXECUTION evidence.** The gate reads the runner's own output shape (vitest /
+node --test) and requires it to demonstrate that the *named* test actually ran. An outcome nobody can prove
+degrades loudly instead of minting trust — MEASURED before this change, `--runner false` (a command that
+executes nothing and prints nothing) returned `DISCRIMINATES`; it now returns `CANNOT_ISOLATE` with
+reason `unrecognised-runner-output`.
+
+| Verdict | Means | ✓/✗ | Action |
+|---|---|---|---|
+| `DISCRIMINATES` | assertion-red at base, execution-evidenced | ✓ | none |
+| `DISCRIMINATES_VIA_ERROR` | evidenced load error at base **and** an evidenced pass at TIP | ✓ | none (inference — note it) |
+| `NON_DISCRIMINATING` | evidenced pass at base — a proven false green | ✗ | `strengthen-test` |
+| `TEST_FILE_ABSENT` | the named check is not a regular file (stat+isFile, before any worktree) | ✗ | `create-missing-test` |
+| `LOAD_ERROR_AT_BOTH_REVS` | could not execute at EITHER rev — zero signal | ✗ | `fix-runner-invocation` |
+| `FAILS_AT_TIP` | the feature's own test is red **with** the feature present | ✗ | `fix-red-feature-test` |
+| `CANNOT_ISOLATE` | no established observation; the row carries a typed `reason` | ✗ | `map-a-test` / `fix-runner-invocation` |
+
+`--json` carries the full reading: `perTest[]` (verdict + `reason`), the per-run `evidence` rows, `findings[]`
+(**one per distinct non-clean verdict** — the scalar `aggregate` can only name the worst), `measurementValid`
+(`true | false | 'partial'` — did the instrument measure at all), `primaryAction`, and `tipTree` (the live
+tree's HEAD + dirty-file count when a tip control ran). The singular `finding` is a **deprecated** alias for
+`findings[0]`; read `findings[]`. `--timeout <ms>` (default 300000) bounds each run — a timed-out run is
+`CANNOT_ISOLATE` reason `timeout`, never a pass.
+
+It **never auto-aborts** (dz's rule: a false gate kills trust) — exit 0 on any verdict, exit 2 only on a
+usage/setup error. Base ref, paths, name filter, and runner are all injection-checked, and the worktree is
+always removed. Step-8 runs this on the ADR Confirmation's `Required automated check` automatically.
 
 ### `dz guard` — when a self-mutating operation should be refused, not regretted
 
@@ -3506,9 +3748,20 @@ npx @dzhechkov/p-replicator init
 
 ## Status
 
-`v0.4.6` — published on npm. Also available as [Claude Plugin](#claude-plugin). Part of [DZ Harness Hub](https://github.com/djd1m/dz-harness-hub).
+`v0.4.8` — staged (not yet published). Also available as [Claude Plugin](#claude-plugin). Part of [DZ Harness Hub](https://github.com/djd1m/dz-harness-hub).
+
+New in 0.4.8 (feature `crossrt-1-agents-md`): `dz agents-sync` ports the fixed registry of bearing
+rules into an early root-`AGENTS.md` fence, `--check` exposes source drift to CI, and both surfaces
+report the measured Codex project-doc byte budget. A live cold-start probe, not file presence,
+remains the runtime acceptance gate.
+
+New in this change (feature `dz-cli-defects`, slice A — three defects confirmed by RUNNING the CLI, then fixed):
+
+- **`dz list` skips and collects** — one unparseable `SKILL.md` no longer hides the rest; the broken files are named on stderr and the exit code stays 1. Same for `dz init` / `dz install` / `dz sync`. [Details](#dz-list--one-broken-skill-never-hides-the-rest)
+- **`--target` aliases + did-you-mean** — `--target claude` (and `cc`, `agents`, `gpt`/`openai`) resolve; typos are suggested, never silently accepted. [Details](#--target-aliases-and-did-you-mean)
+- **A named refusal instead of a `SyntaxError`** — `dz` now requires `@dzhechkov/harness-core >= 0.4.7` (was `^0.4.0`, which npm could legally resolve to a core too old to link) and says so in words, before anything is imported.
 
-New in this change: the global `dz --version` / `-v` / `dz version` surface (one parseable line), and `dz skills-verify --plugin-dir` / `--expect-commands` so slash-command registration is gate-visible. Both exist for `@dzhechkov/loop-designer-plugin`, which requires `dz` in `^0.4`, verifies it at run time, and falls back to `npx -y @dzhechkov/harness-cli@^0.4` when the `dz` on PATH is stale, unparseable or missing.
+Previously: the global `dz --version` / `-v` / `dz version` surface (one parseable line), and `dz skills-verify --plugin-dir` / `--expect-commands` so slash-command registration is gate-visible. Both exist for `@dzhechkov/loop-designer-plugin`, which requires `dz` in `^0.4`, verifies it at run time, and falls back to `npx -y @dzhechkov/harness-cli@^0.4` when the `dz` on PATH is stale, unparseable or missing.
 
 ## Claude Plugin
 

package/dist/bin.d.ts

@@ -1,6 +1,16 @@
 #!/usr/bin/env node
 /**
  * `dz` executable entry point.
+ *
+ * Two phases, and the split is load-bearing (feature dz-cli-defects, D5):
+ *
+ *   phase 1 — ZERO `@dzhechkov/harness-core` imports: probe the installed core version
+ *             and refuse with a NAMED message if it is below `MIN_CORE`;
+ *   phase 2 — `await import('./cli.js')`, which is where the ~100-name static graph is
+ *             linked. A STATIC import here would link that graph before any guard could
+ *             run, which is exactly how a cached lower core produced a bare
+ *             `SyntaxError: … does not provide an export named 'GRADE_SUCCESS_FLOOR'`
+ *             with nothing pointing at the cause.
  */
 export {};
 //# sourceMappingURL=bin.d.ts.map

package/dist/bin.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"bin.d.ts","sourceRoot":"","sources":["../src/bin.ts"],"names":[],"mappings":";AACA;;GAEG"}
+{"version":3,"file":"bin.d.ts","sourceRoot":"","sources":["../src/bin.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;GAYG"}