@skyf0xx/hedgehog-core-deepseek-harness 0.2.4 → 0.2.6

package/agents/harness-eng.md

@@ -123,7 +123,11 @@ the layer.
   SCOPE and RELEVANT RULES — not writing scaffold files freehand.
 - Write the tests the layer's `verify` command runs. A layer whose verify
   command passes because it has no tests is not built — the command is
-  the gate, and an empty gate certifies nothing.
+  the gate, and an empty gate certifies nothing. `scaffold` through
+  `bundle` are internally-consistent-only (verify radius equals scope);
+  `join`'s `exclusive: true` marks it as the layer where the real,
+  cross-plugin test bar belongs (`hedgehog-authored-loop`'s "Test depth
+  follows verify radius" states the full rule).
 - Build this layer's share of the packet's INTENT goal, not just
   something plausible for the layer's name. Your `verify` command runs
   the checks you wrote or the ones `core.yaml` fixed for this layer, so it

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyf0xx/hedgehog-core-deepseek-harness",
-  "version": "0.2.4",
+  "version": "0.2.6",
   "description": "Hedgehog's deepseek-harness core: a pinned DSH/Cordis plugin workspace, a tool-plugin generator, and the skills that drive building DeepSeek Harness plugins with Hedgehog's build discipline.",
   "type": "module",
   "scripts": {

package/skills/hedgehog-dsh-loop/SKILL.md

@@ -167,10 +167,18 @@ step to work around by hand-writing the scaffold files.
    then relies on the layer's own `verify` command to prove it end to
    end; `bundle` confirms the package is pack-ready; `join` (once, after
    every plugin's `bundle` is complete) resolves any cross-plugin
-   typecheck break the per-plugin layers couldn't see in isolation.
+   typecheck break the per-plugin layers couldn't see in isolation. Every
+   layer before `join` has its verify radius equal to its own scope —
+   internally-consistent-only; `join`'s `exclusive: true` is what marks it
+   as the layer where the real test bar and the `reviewer` pass belong
+   (`hedgehog-authored-loop`'s "Test depth follows verify radius" states
+   the full rule, shared across cores).
    Multiple claimed packets for different plugins can be worked in
    whatever order is convenient — they're independent unless a Correction
-   Protocol patch links them (see below).
+   Protocol patch links them (see below). If a dispatch by name reports
+   `harness-eng` as not found — expected right after `init`/`update`
+   installed it this same session — see root CLAUDE.md's "Delegating on
+   this host" note rather than treating it as fatal.
 4. **`harness-eng` runs its own self-test** for the layer before
    presenting its work — necessary, not sufficient. This is a sanity
    check the agent does for itself; it does not move the task and does