@lmzhen/dsh-tool-skill-manage 0.3.83 → 0.4.0

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.
Files changed (2) hide show
  1. package/README.md +15 -20
  2. package/package.json +8 -8
package/README.md CHANGED
@@ -1,36 +1,31 @@
1
1
  # @lmzhen/dsh-tool-skill-manage
2
2
 
3
- Model-facing skill_manage tool
3
+ Model-facing `skill_manage` tool: it exposes skill-library mutations to the model and
4
+ routes them through the evolution approval seam when one is mounted; it owns neither the
5
+ library nor its lifecycle rules.
4
6
 
5
- ## Model Experience
7
+ ## Model surface
6
8
 
7
- ### skill_manage tool surface
8
-
9
- #### What the model sees
10
-
11
- The model sees the `skill_manage` tool schema and tool results containing success or validation messages.
12
-
13
- #### Token effect
14
-
15
- Adds the `skill_manage` tool schema to the request catalog; result tokens scale with returned messages.
16
-
17
- #### KV Cache effect
18
-
19
- Tool schema is prefix-stable. Skill writes do not alter the current request prompt; catalog invalidation affects the next request.
9
+ - **Model-visible:** the `skill_manage` tool schema and its success/validation messages; result tokens scale with what is returned.
10
+ - **Prompt prefix / KV cache:** the tool schema is prefix-stable, and skill writes do not alter the current request prompt; catalog invalidation affects the next request; family rules: `packages/README.md` §"Model-visible prompt prefix and the KV cache".
11
+ - **Mount it?** yes — the `tool-skill-manage` row, carried by the `evolution-all` and one-click `evolution-preset` bundles and the Evolution agent preset delta.
20
12
 
21
13
  ## Safety model
22
14
 
23
15
  ### Approval seam
24
16
 
25
- Mutations (create/edit/update/patch/delete/write_file/remove_file/restructure) pass through the evolution approval seam when `evolution-approval` is mounted; approved/staged writes are replayed by the registered runner with the library origin preserved.
26
-
27
- ### pin/unpin: explicit exception (0.3.18, E-70)
17
+ Mutations (create/edit/update/patch/delete/write_file/remove_file/restructure) pass through the evolution approval seam when `evolution-approval` is mounted; approved/staged writes are replayed by the registered runner with the library origin preserved. The missing-required-argument pre-check runs BEFORE that boundary — one shared table and one refusal builder with `executeCore`, so the stage boundary and the execution check cannot diverge: a write that cannot execute is refused, never staged for approval.
28
18
 
29
- `pin` and `unpin` are deliberately **outside** the approval seam. Pinning only lifts/restores the curator-lifecycle freeze — it changes a lifecycle flag, never content — and is fully reversible by the same tool. Routing it through `policy:'ask'` would let a staged-but-never-approved request hold the library in a pinned state invisibly. Tradeoff accepted: no approval on a lifecycle-flag flip; if product policy changes, pin/unpin should be wired into the same staging path as `patch`.
19
+ ### pin/unpin: explicit exception
30
20
 
31
- ## Known Limitations and Deferred Work
21
+ `pin` and `unpin` are deliberately **outside** the approval seam. Pinning only lifts/restores the curator-lifecycle freeze (a lifecycle flag, never content) and is fully reversible by the same tool. Routing it through `policy:'ask'` would let a staged-but-never-approved request hold the library in a pinned state invisibly. Tradeoff accepted: no approval on a lifecycle-flag flip; if product policy changes, pin/unpin should be wired into the same staging path as `patch`.
32
22
 
23
+ ## Known limitations
33
24
 
34
25
  - No known durable consumer gaps at this time. Runtime contracts are covered by package and boundary tests.
35
26
 
36
27
  **Runtime invariant:** No companion is published. The platform auto-assembles nothing and the family mounts no `<pkg>/invariant` cordis row, so a companion here would never execute (v37 S2.1 / I-3).
28
+
29
+ ## Notes and history
30
+
31
+ - pin/unpin: explicit exception (0.3.18, E-70)
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@lmzhen/dsh-tool-skill-manage",
3
3
  "description": "Model-facing skill_manage tool (community build)",
4
- "version": "0.3.83",
4
+ "version": "0.4.0",
5
5
  "publishConfig": {
6
6
  "access": "public"
7
7
  },
@@ -27,24 +27,24 @@
27
27
  "license": "MIT",
28
28
  "dependencies": {
29
29
  "@deepseek-ai/schemastery": "^3.18.1",
30
- "@lmzhen/dsh-evolution-approval": "^0.3.83",
31
- "@lmzhen/dsh-evolution-core": "^0.3.83"
30
+ "@lmzhen/dsh-evolution-approval": "^0.4.0",
31
+ "@lmzhen/dsh-evolution-core": "^0.4.0"
32
32
  },
33
33
  "peerDependencies": {
34
34
  "@deepseek-ai/cordis": "^4.0.1",
35
35
  "@deepseek-ai/dsh-skill": "^0.1.5-rc.2",
36
36
  "@deepseek-ai/dsh-system-prompt": "^0.1.5-rc.2",
37
37
  "@deepseek-ai/dsh-tools": "^0.1.5-rc.2",
38
- "@lmzhen/dsh-evolution-io": "^0.3.83",
39
- "@lmzhen/dsh-skill-usage": "^0.3.83"
38
+ "@lmzhen/dsh-evolution-io": "^0.4.0",
39
+ "@lmzhen/dsh-skill-usage": "^0.4.0"
40
40
  },
41
41
  "devDependencies": {
42
42
  "@deepseek-ai/dsh-agent-loop-testkit": "^0.1.5-rc.2",
43
43
  "@deepseek-ai/dsh-skill": "^0.1.5-rc.2",
44
44
  "@deepseek-ai/dsh-system-prompt": "^0.1.5-rc.2",
45
45
  "@deepseek-ai/dsh-tools": "^0.1.5-rc.2",
46
- "@lmzhen/dsh-evolution-core": "^0.3.83",
47
- "@lmzhen/dsh-evolution-io": "^0.3.83",
48
- "@lmzhen/dsh-skill-usage": "^0.3.83"
46
+ "@lmzhen/dsh-evolution-core": "^0.4.0",
47
+ "@lmzhen/dsh-evolution-io": "^0.4.0",
48
+ "@lmzhen/dsh-skill-usage": "^0.4.0"
49
49
  }
50
50
  }