@lmzhen/dsh-evolution-state-storage 0.3.82 → 0.4.0

package/README.md

@@ -1,30 +1,20 @@
-# @deepseek-ai/dsh-evolution-state-storage
+# @lmzhen/dsh-evolution-state-storage
 
-Provider registry seam for durable evolution state
+Provider registry seam for durable evolution state: the consumer (`evolution-state`) never touches
+a medium — providers register here (`json` = IO-seam files, `domain` = storage-domain KV).
 
+## Model surface
 
-## Model Experience
+- **Model-visible:** nothing of its own: the consumer rows own the injection.
+- **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".
+- **Mount it?** yes — the `evolution-state-storage` row, in `evolution-host`/`evolution-all`/one-click `evolution-preset`; a seam consumed by `evolution-state`, `evolution-state-json`, `evolution-state-domain` and `evolution-approval`.
 
-### Indirect model surface
-
-#### What the model sees
-
-`@deepseek-ai/dsh-evolution-state-storage` 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.
-
-## Conformance suite (S3-2 / J-5)
+## Conformance suite
 
 The package publishes `runStateProviderConsistency(provider, assert)` — the whole seam contract as one call: field-complete pending round-trips, claim/resolve rollback, refusals at the write boundary, clone/alias independence, unknown-field preservation, and the two caps (resolved pending tail, review-state session rows). A third-party provider checks itself by running the suite against its own instance:
 
 ```ts
-import { runStateProviderConsistency } from '@deepseek-ai/dsh-evolution-state-storage'
+import { runStateProviderConsistency } from '@lmzhen/dsh-evolution-state-storage'
 import { expect } from 'vitest' // or any runner wrapped into `ConformanceAssert`
 
 await runStateProviderConsistency(myProvider, expect)
@@ -32,10 +22,13 @@ await runStateProviderConsistency(myProvider, expect)
 
 The assertion surface is INJECTED rather than imported, which is what lets this module ship: it carries no test-runner dependency, so loading the package never loads vitest. Both shipped providers run the same suite (`evolution-state-json` / `evolution-state-domain` `tests/provider-consistency.spec.ts`), and `consistency-forge.spec.ts` proves the suite fails when a single field is forged.
 
-## Known Limitations and Deferred Work
 
+## Known limitations
 
 - Provider registry has no default medium. Mount `evolution-state-domain` or `evolution-state-json` before state reads.
 
 **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
+
+- Conformance suite (S3-2 / J-5)

package/lib/index.js

@@ -254,6 +254,19 @@ async function runStateProviderConsistency(provider, assert) {
 		lastSummary: "updated",
 		paused: false
 	});
+	await provider.transactCuratorState((current) => {
+		if (current !== null) {
+			current.runCount = 999;
+			current.paused = true;
+		}
+		return null;
+	});
+	assert(await provider.loadCuratorState()).toEqual({
+		lastRunAt: 10,
+		runCount: 0,
+		lastSummary: "updated",
+		paused: false
+	});
 	const live = pendingOf("c-live");
 	await provider.savePending(live);
 	assert((await provider.listPending("pending")).map((record) => record.id)).toContain("c-live");

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@lmzhen/dsh-evolution-state-storage",
   "description": "Provider registry seam for durable evolution state (community build)",
-  "version": "0.3.82",
+  "version": "0.4.0",
   "publishConfig": {
     "access": "public"
   },