@lmzhen/dsh-evolution-agent-preset 0.3.82 → 0.4.0

package/README.md

@@ -1,23 +1,12 @@
-# @deepseek-ai/dsh-evolution-agent-preset
+# @lmzhen/dsh-evolution-agent-preset
 
 Agent preset exposing memory and skill evolution tools to a session
 
+## Model surface
 
-## Model Experience
-
-### Indirect model surface
-
-#### What the model sees
-
-`@deepseek-ai/dsh-evolution-agent-preset` registers no direct prompt or tool schema itself. Model-visible effects are owned by the packages that consume this service.
-
-#### Token effect
-
-Zero direct token effect from this package; consumers add any model-visible tokens.
-
-#### KV Cache effect
-
-Independent of request-prefix construction. This package does not alter the assembled prompt or tool list.
+- **Model-visible:** nothing of its own: the delta registers no prompt and no tool schema; it mounts the four model rows (`tool-memory`, `tool-skill-manage`, `tool-session-query`, `evolution-skill-catalog`), which own what the model sees.
+- **Prompt prefix / KV cache:** the composed preset is the platform's own base composition plus this delta; this package adds no prompt text of its own. Family rules: `packages/README.md` §"Model-visible prompt prefix and the KV cache".
+- **Mount it?** yes — the agent preset DELTA (`agent.cordis.yml`), installed by `install-layered.mjs` (agent/layered modes) or `/evolution preset install`; not a profile row.
 
 ## Preset variants
 
@@ -34,20 +23,20 @@ vendored — the preset follows whichever platform the user actually has.
 | `cordis` (`requires: dynamicCordisRunner`) | `<platform>/cordis/agent.cordis.yml` | `evolution-cordis` | `preset.cordis.yml` |
 | `minimal` (unsupported) | — | `evolution-minimal` | `preset.minimal.yml` |
 
-`bases.json` in this package is the single table behind all four columns — the installer
+`bases.json` in this package is the single table behind all four columns: the installer
 (`AGENT_PRESET_BASES`) and the host command (`/evolution preset install --base <name>`) both
 read THIS file, so a base cannot be half-added (a directory one consumer knows about and
 another does not) and the two install paths cannot disagree. It also carries `default`. A base whose
-runtime composition is absent — an older platform with no `ptc` preset, a preset root that does
-not carry it — is REFUSED with a named error; it is never composed from another base. The V10-14
+runtime composition is absent (an older platform with no `ptc` preset, a preset root that does
+not carry it) is REFUSED with a named error; it is never composed from another base. The V10-14
 `tool-skill` catalog-cap injection (`injectToolSkillCap`) runs on the composed output
 for every base, and the row-collision guard still fails loud when a delta row id appears in the
 platform composition.
 
 ### PTC base (`--base ptc`)
 
-Composes the platform's `ptc` preset — the standard coding agent with `run_code` as the model's
-composition surface — plus this delta, so the family's `memory`, `skill_manage` and
+Composes the platform's `ptc` preset (the standard coding agent with `run_code` as the model's
+composition surface) plus this delta, so the family's `memory`, `skill_manage` and
 `session_search` entry points reach a PTC session.
 
 Known limitations of this base:
@@ -59,17 +48,13 @@ Known limitations of this base:
 - **A deployment without a code runtime refuses the preset at mount**, naming
   `tool-presentation`; that row and its requirement come from the platform `ptc` preset and are
   not something this variant can soften.
-- **Both install paths produce this variant** (0.3.75): `/evolution preset install --base ptc`
-  (npm, `evolution-commands`) and `install-layered.mjs --base ptc` (source checkout) read the same
-  `bases.json` and write `.agent-presets/evolution-ptc/`. It still only composes a platform that
-  actually ships the `ptc` preset; a `standard`-only runtime is refused by name.
+- **Both install paths produce this variant**. The npm command and the source installer read the same `bases.json`.
 - **Tool-use observation under PTC** depends on the family reading dispatches through
   `evolution-core`'s dispatch normalizer rather than matching a platform event vocabulary; a
   consumer that matches `tool/call` directly goes blind in this mode (the arch guard rejects that
   form).
 
-## Known Limitations and Deferred Work
-
+## Known limitations
 
 - No known durable consumer gaps at this time. Runtime contracts are covered by package and boundary tests.
 
@@ -81,16 +66,20 @@ above: `standard` (default), `ptc`, `cordis` and `minimal`. Two of them carry a
 precondition the table itself declares, and both install paths refuse them by
 name when it is unmet — the preset is never composed from another base:
 
-- `cordis` — `requires: { service: 'dynamicCordisRunner' }`. The cordis preset's
+- `cordis`: `requires: { service: 'dynamicCordisRunner' }`. The cordis preset's
   extra row is `tool-cordis`, which injects `dynamicCordisRunner`, and that
   service is mounted only by the `web-app` bundle. A cordis-based preset on a
   headless, ACP or SDK profile would mount a row whose injection cannot be
   satisfied, and a preset row that never activates is refused at mount time
   rather than degraded. Cordis sessions otherwise get the family through the
   profile-wide `all` install, which needs no variant.
-- `minimal` — `unsupported`: the platform minimal composition is only persona +
+- `minimal`: `unsupported`: the platform minimal composition is only persona +
   persistent-shell, so it mounts no skill or file tool rows for the family to
   write through (see `packages/INSTALL.md` §Platform mode × self-evolution).
 
 **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).
 
+## Notes and history
+
+- **Both install paths produce this variant** (0.3.75): `/evolution preset install --base ptc` (npm, `evolution-commands`) and `install-layered.mjs --base ptc` (source checkout) read the same `bases.json` and write `.agent-presets/evolution-ptc/`. It still only composes a platform that actually ships the `ptc` preset; a `standard`-only runtime is refused by name.
+- The V10-14 `tool-skill` catalog-cap injection (`injectToolSkillCap`) runs on the composed output for every base, and the row-collision guard still fails loud when a delta row id appears in the platform composition.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@lmzhen/dsh-evolution-agent-preset",
   "description": "Agent preset exposing memory and skill evolution tools to a session (community build)",
-  "version": "0.3.82",
+  "version": "0.4.0",
   "publishConfig": {
     "access": "public"
   },
@@ -25,9 +25,9 @@
   "license": "MIT",
   "dependencies": {
     "@deepseek-ai/dsh-tool-session-query": "^0.1.5-rc.2",
-    "@lmzhen/dsh-tool-memory": "^0.3.82",
-    "@lmzhen/dsh-tool-skill-manage": "^0.3.82",
-    "@lmzhen/dsh-evolution-skill-catalog": "^0.3.82"
+    "@lmzhen/dsh-tool-memory": "^0.4.0",
+    "@lmzhen/dsh-tool-skill-manage": "^0.4.0",
+    "@lmzhen/dsh-evolution-skill-catalog": "^0.4.0"
   },
   "exports": {
     ".": {