@skyf0xx/hedgehog-core-deepseek-harness 0.2.6 → 0.2.7
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.
|
|
3
|
+
"version": "0.2.7",
|
|
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": {
|
|
@@ -15,7 +15,7 @@ truth, defines the six compiled layers and this core's module axis:
|
|
|
15
15
|
`{module}` is a plugin name, and a project builds one intent per plugin
|
|
16
16
|
it wants to add to the workspace. This is the same module-axis mechanism
|
|
17
17
|
`full-stack-app` uses per domain module — not the linear, single-module
|
|
18
|
-
degenerate case `landing-page`'s loop implements. Because layers vary
|
|
18
|
+
degenerate case `landing-page`'s loop implements — which is why `workspace/core.yaml` declares `pattern: vertical-slice`. Because layers vary
|
|
19
19
|
independently per plugin, a single `hedgehog claim` call can return
|
|
20
20
|
**multiple** ready tasks at once (e.g. `logic` for one plugin and
|
|
21
21
|
`scaffold` for another, claimed together) — never assume `--count N`
|