@skyf0xx/hedgehog-core-deepseek-harness 0.2.5 → 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.
@@ -123,7 +123,11 @@ the layer.
123
123
  SCOPE and RELEVANT RULES — not writing scaffold files freehand.
124
124
  - Write the tests the layer's `verify` command runs. A layer whose verify
125
125
  command passes because it has no tests is not built — the command is
126
- the gate, and an empty gate certifies nothing.
126
+ the gate, and an empty gate certifies nothing. `scaffold` through
127
+ `bundle` are internally-consistent-only (verify radius equals scope);
128
+ `join`'s `exclusive: true` marks it as the layer where the real,
129
+ cross-plugin test bar belongs (`hedgehog-authored-loop`'s "Test depth
130
+ follows verify radius" states the full rule).
127
131
  - Build this layer's share of the packet's INTENT goal, not just
128
132
  something plausible for the layer's name. Your `verify` command runs
129
133
  the checks you wrote or the ones `core.yaml` fixed for this layer, so it
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skyf0xx/hedgehog-core-deepseek-harness",
3
- "version": "0.2.5",
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`
@@ -167,7 +167,12 @@ step to work around by hand-writing the scaffold files.
167
167
  then relies on the layer's own `verify` command to prove it end to
168
168
  end; `bundle` confirms the package is pack-ready; `join` (once, after
169
169
  every plugin's `bundle` is complete) resolves any cross-plugin
170
- typecheck break the per-plugin layers couldn't see in isolation.
170
+ typecheck break the per-plugin layers couldn't see in isolation. Every
171
+ layer before `join` has its verify radius equal to its own scope —
172
+ internally-consistent-only; `join`'s `exclusive: true` is what marks it
173
+ as the layer where the real test bar and the `reviewer` pass belong
174
+ (`hedgehog-authored-loop`'s "Test depth follows verify radius" states
175
+ the full rule, shared across cores).
171
176
  Multiple claimed packets for different plugins can be worked in
172
177
  whatever order is convenient — they're independent unless a Correction
173
178
  Protocol patch links them (see below). If a dispatch by name reports
@@ -3,6 +3,7 @@
3
3
  # plugin per project just never has a second intent; nothing forces or
4
4
  # blocks multi-plugin.
5
5
  id: deepseek-harness
6
+ pattern: vertical-slice
6
7
  pluralizes: false
7
8
  layers:
8
9
  - id: scaffold