@skyf0xx/hedgehog-core-deepseek-harness 0.2.3 → 0.2.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyf0xx/hedgehog-core-deepseek-harness",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "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

@@ -170,7 +170,10 @@ step to work around by hand-writing the scaffold files.
    typecheck break the per-plugin layers couldn't see in isolation.
    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
@@ -253,9 +256,11 @@ loop skill uses for turning real build friction into upstream fixes.
 ## Correction Protocol
 
 The same core mechanic every Hedgehog core's loop skill implements:
-stop, patch the upstream layer in place, fast-forward every dependent
-layer as its own commit, commit messages as the explanation, resume the
-loop. For this core specifically:
+stop, patch the upstream layer in place (checking the LSP tool's
+findReferences/incomingCalls against the symbol first, so a fix to one
+plugin's shared type doesn't miss a caller in another), fast-forward
+every dependent layer as its own commit, commit messages as the
+explanation, resume the loop. For this core specifically:
 
 - **A correction ripples forward through one plugin's own chain.** A
   wrong `logic` layer for a given plugin ripples through that same