@skyf0xx/hedgehog-core-deepseek-harness 0.2.8 → 0.2.9

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.
@@ -209,10 +209,12 @@ the layer.
209
209
  it at its source — the Correction Protocol, not a workaround layered on
210
210
  top.
211
211
  - You may be one of several agents building concurrently, each holding a
212
- lease on its own task and scoped to its own ALLOWED SCOPE — a file
213
- outside your scope changing while you work is another agent's task (very
214
- likely another plugin's, given the module axis this core builds along),
215
- not a stray edit to fix. Never edit, revert, or "clean up" a file
212
+ lease on its own task and scoped to its own ALLOWED SCOPE by `hedgehog
213
+ claim` — a file outside your scope changing while you work is most
214
+ likely another plugin's task (given the module axis this core builds
215
+ along), not a stray edit to fix, but scopes aren't guaranteed disjoint:
216
+ if you're unsure whether a change is really outside your task, report
217
+ it rather than assuming. Never edit, revert, or "clean up" a file
216
218
  outside your own scope, and never run a repo-wide command (a formatter
217
219
  over the whole workspace, `pnpm -r` with side effects, a codemod) unless
218
220
  it is exactly the packet's VERIFICATION command — it doesn't respect
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skyf0xx/hedgehog-core-deepseek-harness",
3
- "version": "0.2.8",
3
+ "version": "0.2.9",
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": {
@@ -8,10 +8,20 @@ description: Use whenever `harness-eng` is writing a DSH plugin's own TypeScript
8
8
  `harness-eng` decides *which* shape a given plugin intent needs — that
9
9
  judgment call belongs to the task, not to this skill. This skill covers
10
10
  *how* to write each shape once chosen: the plugin's own TypeScript body,
11
- catalogued against DSH's real, current docs. It doesn't cover the
12
- bundle/manifest wrapper (`package.json`'s `dsh.bundle`, `cordis.patch.yml`)
13
- that every shape shares regardless of which one it implements — that's
14
- the tool-plugin generator's concern, not this skill's.
11
+ catalogued against DSH's docs. It doesn't cover the bundle/manifest
12
+ wrapper (`package.json`'s `dsh.bundle`, `cordis.patch.yml`) that every
13
+ shape shares regardless of which one it implements — that's the
14
+ tool-plugin generator's concern, not this skill's.
15
+
16
+ **Verified against DSH tag `dsh-v0.1.0-rc.8`** (`docs/user/develop/framework/events.md`
17
+ and `service.md` at that tag), the same tag `workspace/package.json` pins
18
+ `@deepseek-ai/dsh` and `@deepseek-ai/dsh-tools` to. This is the one owning
19
+ statement of which DSH revision this skill's catalog was checked against —
20
+ every confirmed-event, confirmed-signature, and "doesn't exist" claim
21
+ below is only guaranteed true as of that tag. A re-pin to a newer `rc` or
22
+ stable tag needs this skill's claims re-checked against the new tag's own
23
+ docs before the pin line above is updated to match; don't bump the pin in
24
+ `workspace/package.json` without also re-verifying this file.
15
25
 
16
26
  ## v0.1 generator coverage: tool shape only
17
27
 
@@ -127,7 +137,7 @@ exposing a new callable. Registers on a Cordis event or a durable
127
137
  session-event type via `ctx.on`, inside function-form `apply`.
128
138
 
129
139
  **Confirmed Cordis-level events** (per `docs/user/develop/framework/events.md`
130
- on DSH's `master` branch): `agent/step`, `agent/request`,
140
+ at the tag pinned above): `agent/step`, `agent/request`,
131
141
  `agent/request-error`, `tools/result`, `session/event`.
132
142
 
133
143
  **Confirmed durable session-event types** (delivered through the
@@ -197,7 +207,7 @@ confirmed event or a different shape instead.
197
207
  A plugin that drives interactive input or contributes to the built-in Web
198
208
  Client, rather than registering a tool or a passive hook. Per DSH's own
199
209
  docs, this shape is real but less stable than the tool shape — the docs
200
- fetched for this skill describe it only at the level below, with no full
210
+ at the tag pinned above describe it only at the level below, with no full
201
211
  worked example:
202
212
 
203
213
  - Registers on `session/event` the same way a hook plugin does (see
@@ -205,11 +215,11 @@ worked example:
205
215
  step, tool-call, and compaction activity as it streams.
206
216
  - Drives input via `agent.followup()` / `agent.steer()` — named in DSH's
207
217
  docs as the mechanism a UI plugin uses to inject or redirect input, but
208
- no full signature or code example for either call was present in the
209
- fetched content.
218
+ no full signature or code example for either call was present at that
219
+ tag.
210
220
  - Can contribute a `ConversationNodeDefinition` to the built-in Web
211
221
  Client — named as a real extension point, but again with no worked
212
- example in what was fetched.
222
+ example at that tag.
213
223
 
214
224
  **Honesty note:** treat `agent.followup()`, `agent.steer()`, and
215
225
  `ConversationNodeDefinition` as confirmed to exist by name, but not
@@ -275,7 +285,7 @@ Dependency handling:
275
285
  **Honesty note (correcting an assumption, not the docs):** this shape is
276
286
  sometimes described as going through a `ctx.provide()` call. That call
277
287
  does not appear anywhere in DSH's `docs/user/develop/framework/service.md`
278
- as fetched for this skill — the only provisioning mechanism documented
288
+ at the tag pinned above — the only provisioning mechanism documented
279
289
  there is extending `Service` and calling `super(ctx, name)`, as shown
280
290
  above. Don't write `ctx.provide(...)` into a plugin on the assumption
281
291
  it's the real API; use the `Service` subclass form, and if a future task