@lmzhen/dsh-evolution-activity 0.32.4 → 0.32.6

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 +9 -20
  2. package/package.json +5 -5
package/README.md CHANGED
@@ -1,29 +1,18 @@
1
1
  # @lmzhen/dsh-evolution-activity
2
2
 
3
- Durable activity store for self-evolution plan outcomes: it subscribes to the `evolution/plan-applied`
4
- process event (payload v2, with sessionId) and append-merges every outcome into
5
- `$DSH_HOME/evolution/activity.json` through the evolution IO seam — load → fold → save under an
6
- in-process queue, so records survive host restarts and are readable without a session. A
7
- session log carrying `evolution/*` types is refused wholesale at resume, so plan-outcome
8
- durability lives here; a storage-domain table is deferred until a consumer needs domain routing.
3
+ Internal plugin that persists evolution process events into `$DSH_HOME/evolution/activity.json`.
9
4
 
10
- ## Model surface
5
+ ## What it records
11
6
 
12
- - **Model-visible:** nothing of its own: the rows and commands that read the sidecar own the injection; it backs `/evolution replay` (`evolution-replay`).
13
- - **Prompt prefix / KV cache:** unchanged by this package: family-level rules single-sourced in `packages/README.md` §"Model-visible prompt prefix and the KV cache".
14
- - **Mount it?** yes — the `evolution-activity` row, in `evolution-host`/`evolution-all`/one-click `evolution-preset`.
7
+ - `evolution/plan-applied`: accepted, rejected, skipped, and failed operation counts for a reviewed plan.
8
+ - `evolution/review-completed`: the review status, trigger, text, actions, timing, and model usage when supplied.
15
9
 
16
- ## Configuration
10
+ The versioned sidecar contains separate `items` and `reviews` arrays. `maxItems` bounds each array and defaults to 200; values below 1 are rejected by the loader.
17
11
 
18
- - Payload fields it folds: `sessionId`, `planId`, `policyFingerprint`, `memoryApplied`, `skillApplied`, `rejectedOps`, `skippedUnread`, `executionFailures`, `executionError` and `evidenceClassReports` (ops whose whole evidence list cites a turn/step boundary — the plan path's report-only phase-1 dimension; they are counted, never refused, so the field is not a "work not done" cause). Fields the fold does not name are ignored, so the payload can gain dimensions without a schema migration here.
19
- - `maxItems` (default `DEFAULT_MAX_ITEMS = 200`): bound on the retained sidecar; a non-finite value falls back to the default, a non-positive value fails loud at the schema.
12
+ ## Consumers and failure behavior
20
13
 
21
- ## Known limitations
14
+ There is no direct command or panel. `evolution-replay` reads plan records, while other diagnostics can read the persisted review history without a live session.
22
15
 
23
- - Each event lands through `transactIo` (like `feedback.json`); append cycles are serialized in-process and atomic on disk inside that process. The shipped IO backend is single-process, so no cross-process guarantee is claimed. A multi-record batch is still one event at a time: no batch transaction exists.
16
+ Persistence starts after an `evolutionIo` provider mounts. Appends are best effort: a write failure is logged after the upstream operation has already completed. Before an append replaces unreadable or foreign-version bytes, the writer attempts to preserve them in a `.corrupt` copy and refuses the append if that rescue fails.
24
17
 
25
- **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).
26
-
27
- ## Notes and history
28
-
29
- - A non-finite value (NaN/±Infinity) falls back to the default (0.3.19, S6.4 guard), while a non-positive value (0 or negative) fails loud at the schema (`z.number().min(1)`) because `slice(-0)` would keep everything and disable the retention window (G3.1, 0.3.23).
18
+ The concurrency guarantee comes from the selected IO backend. The shipped Node backend is single-process; see [evolution-io-node](../evolution-io-node/README.md).
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@lmzhen/dsh-evolution-activity",
3
3
  "description": "Durable activity store for self-evolution plan outcomes (community build)",
4
- "version": "0.32.4",
4
+ "version": "0.32.6",
5
5
  "publishConfig": {
6
6
  "access": "public"
7
7
  },
@@ -27,16 +27,16 @@
27
27
  "license": "MIT",
28
28
  "dependencies": {
29
29
  "@deepseek-ai/schemastery": "^3.18.5",
30
- "@lmzhen/dsh-evolution-core": "^0.32.4"
30
+ "@lmzhen/dsh-evolution-core": "^0.32.6"
31
31
  },
32
32
  "peerDependencies": {
33
33
  "@deepseek-ai/cordis": "^4.0.5"
34
34
  },
35
35
  "devDependencies": {
36
36
  "@deepseek-ai/cordis": "^4.0.5",
37
- "@lmzhen/dsh-evolution-core": "^0.32.4",
38
- "@lmzhen/dsh-evolution-io": "^0.32.4",
39
- "@lmzhen/dsh-evolution-io-node": "^0.32.4"
37
+ "@lmzhen/dsh-evolution-core": "^0.32.6",
38
+ "@lmzhen/dsh-evolution-io": "^0.32.6",
39
+ "@lmzhen/dsh-evolution-io-node": "^0.32.6"
40
40
  },
41
41
  "engines": {
42
42
  "dsh": ">=0.2.1-rc.2 <0.2.2-0"