@lmzhen/dsh-evolution-state-storage 0.32.3 → 0.32.5

package/README.md

@@ -1,36 +1,19 @@
 # @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).
+> 内部组件，保存审批/整理/运行状态。
 
-## Model surface
+## 你会看到
 
-- **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`.
+没有命令、面板或工具入口。
 
-## 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 '@lmzhen/dsh-evolution-state-storage'
-import { expect } from 'vitest' // or any runner wrapped into `ConformanceAssert`
+## 默认 / 前提
 
-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)
+用户只需要知道数据会保存在 `$DSH_HOME`。

package/lib/index.js

@@ -463,17 +463,13 @@ async function comparePendingReadings(left, right) {
 /**
 * G2b/2b.3: which medium carries each record type, and what PROCESS SCOPE that medium actually gives.
 *
-* The family has two serialization layers and only ever wrote one of them down, for the json provider: the
-* IO backend cross-process transact lock (first layer) and the caller own in-process chain (second). The
-* domain medium inherits its answer from whatever backend the platform storage facility routes, and nothing
-* stated it. So this file states it - and the criterion is the family one: a CLAIM must be produced by a
-* capability that can be DISPROVED. processScopeViolations takes the io the provider writes through and
-* reports every claim of cross-process that the io cannot back up.
+* The shipped IO backend declares single-process: its transaction serializes one process only.
+* The domain medium inherits whatever backend the platform storage facility routes, and that is also
+* single-process in this tree. This file states the weaker truth. processScopeViolations takes the io the
+* provider writes through and reports every claim of cross-process that the io cannot back up.
 *
-* MIGRATION NOTE: the plan allows naming storage-sqlite for a cross-process record type. That package does
-* not exist in this tree (0 hits), so today every entry is either backed by the IO transact lock or
-* declares single-process. When a backend carrying its own cross-process guarantee lands, it is named here
-* and the reasoning moves with it - one declaration, not two.
+* MIGRATION NOTE: when a platform backend carrying its own cross-process guarantee lands, name it here and
+* move the reasoning with it - one declaration, not two.
 *
 * @module @lmzhen/dsh-evolution-state-storage/medium-declaration
 */
@@ -482,20 +478,20 @@ const MEDIUM_PROCESS_DECLARATION = [
 	{
 		record: "review_state",
 		medium: "json",
-		scope: "cross-process",
-		because: "the json provider serializes through the IO backend transact lock, as its README states"
+		scope: "single-process",
+		because: "the shipped IO backend declares single-process; no cross-process medium exists in this tree"
 	},
 	{
 		record: "curator_state",
 		medium: "json",
-		scope: "cross-process",
-		because: "same provider and same lock as review_state; the run bookkeeping rides the same write path"
+		scope: "single-process",
+		because: "same provider and same single-process write path as review_state"
 	},
 	{
 		record: "pending",
 		medium: "json",
-		scope: "cross-process",
-		because: "a staged write is claimed by name across processes, so it needs the lock more than the other two"
+		scope: "single-process",
+		because: "the shipped IO backend has no cross-process claim primitive; a staged write is serialized only in-process"
 	},
 	{
 		record: "evolution-domain",
@@ -507,11 +503,12 @@ const MEDIUM_PROCESS_DECLARATION = [
 /**
 * Falsify the declaration against a capability reading.
 * @param io - the io backend the medium writes through, or undefined when none is mounted.
+* @param declaration - claims to falsify; defaults to the shipped declaration.
 * @returns one message per claim the capability cannot back up; empty when every claim holds.
 */
-function processScopeViolations(io) {
+function processScopeViolations(io, declaration = MEDIUM_PROCESS_DECLARATION) {
 	const backed = io?.processScope === "cross-process";
-	return MEDIUM_PROCESS_DECLARATION.filter((claim) => claim.scope === "cross-process" && !backed).map((claim) => claim.record + " claims cross-process (" + claim.because + ") but the mounted io declares " + (io?.processScope ?? "no process scope"));
+	return declaration.filter((claim) => claim.scope === "cross-process" && !backed).map((claim) => claim.record + " claims cross-process (" + claim.because + ") but the mounted io declares " + (io?.processScope ?? "no process scope"));
 }
 //#endregion
 //#region lib/types/index.js

package/lib/types/medium-declaration.d.ts

@@ -1,17 +1,13 @@
 /**
  * G2b/2b.3: which medium carries each record type, and what PROCESS SCOPE that medium actually gives.
  *
- * The family has two serialization layers and only ever wrote one of them down, for the json provider: the
- * IO backend cross-process transact lock (first layer) and the caller own in-process chain (second). The
- * domain medium inherits its answer from whatever backend the platform storage facility routes, and nothing
- * stated it. So this file states it - and the criterion is the family one: a CLAIM must be produced by a
- * capability that can be DISPROVED. processScopeViolations takes the io the provider writes through and
- * reports every claim of cross-process that the io cannot back up.
+ * The shipped IO backend declares single-process: its transaction serializes one process only.
+ * The domain medium inherits whatever backend the platform storage facility routes, and that is also
+ * single-process in this tree. This file states the weaker truth. processScopeViolations takes the io the
+ * provider writes through and reports every claim of cross-process that the io cannot back up.
  *
- * MIGRATION NOTE: the plan allows naming storage-sqlite for a cross-process record type. That package does
- * not exist in this tree (0 hits), so today every entry is either backed by the IO transact lock or
- * declares single-process. When a backend carrying its own cross-process guarantee lands, it is named here
- * and the reasoning moves with it - one declaration, not two.
+ * MIGRATION NOTE: when a platform backend carrying its own cross-process guarantee lands, name it here and
+ * move the reasoning with it - one declaration, not two.
  *
  * @module @lmzhen/dsh-evolution-state-storage/medium-declaration
  */
@@ -34,7 +30,8 @@ export interface ProcessScopeProbe {
 /**
  * Falsify the declaration against a capability reading.
  * @param io - the io backend the medium writes through, or undefined when none is mounted.
+ * @param declaration - claims to falsify; defaults to the shipped declaration.
  * @returns one message per claim the capability cannot back up; empty when every claim holds.
  */
-export declare function processScopeViolations(io: ProcessScopeProbe | undefined): readonly string[];
+export declare function processScopeViolations(io: ProcessScopeProbe | undefined, declaration?: readonly MediumProcessClaim[]): readonly string[];
 //# sourceMappingURL=medium-declaration.d.ts.map

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