@lmzhen/dsh-evolution-state-storage 0.32.4 → 0.32.6

package/README.md

@@ -1,36 +1,17 @@
 # @lmzhen/dsh-evolution-state-storage
 
-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).
+Provider registry and shared contract for durable evolution state. It does not choose a storage medium or write the state itself.
 
-## Model surface
+## What it owns
 
-- **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`.
+- Registration and lookup of the shipped `json` and `domain` providers.
+- Review, curator, and pending-record contracts, including claim/resolve/release transitions.
+- Retention rules and a published provider-conformance suite for alternative implementations.
 
-## Conformance suite
+The resolved pending-record cap is 200. Pending and executing records are not trimmed by that cap, and capability approvals are exempt from resolved-record eviction. Review cadence state is capped at 500 sessions. The JSON provider archives evicted resolved records; the domain provider has no equivalent JSON archive sidecar.
 
-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:
+## Deployment boundary
 
-```ts
-import { runStateProviderConsistency } from '@lmzhen/dsh-evolution-state-storage'
-import { expect } from 'vitest' // or any runner wrapped into `ConformanceAssert`
+Storage location depends on the selected provider. JSON state normally lives below the evolution home; a domain deployment can use another configured medium, including a remote backend. Do not assume every provider stores data in `$DSH_HOME`.
 
-await runStateProviderConsistency(myProvider, expect)
-```
-
-Every value the vectors use is PARAMETERIZABLE (U-2): `runStateProviderConsistency(provider, assert, options)` takes `idPrefix` / `claimPrefix` / `createdAt` / `sessionId` / `attributionSessionId` / `reviewSessionPrefix`, so a medium that already holds records in the default `c-…` namespace — or whose schema insists on a parseable stamp — runs the very same vectors under its own values. Every field defaults to the in-tree literals, so a two-argument call is unchanged. Each vector carries a `since <version>` note saying which release it became binding in.
-
-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`) — the json one also runs it under a caller-supplied namespace — and `consistency-forge.spec.ts` proves the suite fails when a single field is forged.
-
-
-## 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)
+Consumers normally mount [evolution-state](../evolution-state/README.md), which delegates to this registry. There is no direct command, panel, or model tool here.

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.32.4",
+  "version": "0.32.6",
   "publishConfig": {
     "access": "public"
   },
@@ -26,7 +26,7 @@
   ],
   "license": "MIT",
   "dependencies": {
-    "@lmzhen/dsh-evolution-contract": "^0.32.4"
+    "@lmzhen/dsh-evolution-contract": "^0.32.6"
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.5"