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

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skyf0xx/hedgehog-core-deepseek-harness",
3
- "version": "0.2.4",
3
+ "version": "0.2.5",
4
4
  "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.",
5
5
  "type": "module",
6
6
  "scripts": {
@@ -170,7 +170,10 @@ step to work around by hand-writing the scaffold files.
170
170
  typecheck break the per-plugin layers couldn't see in isolation.
171
171
  Multiple claimed packets for different plugins can be worked in
172
172
  whatever order is convenient — they're independent unless a Correction
173
- Protocol patch links them (see below).
173
+ Protocol patch links them (see below). If a dispatch by name reports
174
+ `harness-eng` as not found — expected right after `init`/`update`
175
+ installed it this same session — see root CLAUDE.md's "Delegating on
176
+ this host" note rather than treating it as fatal.
174
177
  4. **`harness-eng` runs its own self-test** for the layer before
175
178
  presenting its work — necessary, not sufficient. This is a sanity
176
179
  check the agent does for itself; it does not move the task and does