@lmzhen/dsh-evolution-core 0.30.43 → 0.31.1

package/lib/index.js

@@ -5905,9 +5905,10 @@ function buildLearnPrompt(userRequest) {
 /**
 * A process-local serial task queue: each task starts only after the previous
 * one settles (success or failure), so read-modify-write sequences that share
-* one file never interleave inside this process. The durable cross-process
-* serialization layer is the IO backend's transact lock; this chain is the
-* second layer (0.3.17 S2.8, T-1: the shape was duplicated in state-json and
+* one file never interleave inside this process. When the IO backend provides
+* a cross-process transact lock, that is the first layer; the node backend does
+* not, so this chain is its only serialization. (0.3.17 S2.8, T-1: the shape was
+* duplicated in state-json and
 * memory-files — one factory now).
 */
 function makeSerialQueue() {
@@ -9078,7 +9079,7 @@ function renderLongRunTable() {
 * `client` probes run in the browser half, where the host has no view of the seats.
 * @module @lmzhen/dsh-evolution-core
 */
-/** The 29 probes, in service-name order (the guard checks this list against the tree). */
+/** The 30 probes, in service-name order (the guard checks this list against the tree). */
 const PLATFORM_SERVICE_PROBES = Object.freeze([
 	{
 		service: "agentDefaultModel",
@@ -9224,6 +9225,11 @@ const PLATFORM_SERVICE_PROBES = Object.freeze([
 		service: "tools",
 		feature: "tool registration and the guard seam",
 		side: "host"
+	},
+	{
+		service: "workingDirectory",
+		feature: "the cwd used for skill snapshots and per-view policy files",
+		side: "host"
 	}
 ]);
 /**
@@ -9242,8 +9248,9 @@ function absentHostServices(has) {
 * B3 / G4 (0.3.78): the family's single-instance contract, made explicit.
 *
 * Every persisted sidecar is written under TWO assumptions: the IO backend's
-* cross-process write lock serializes different processes, and exactly ONE
-* instance of each writer service exists per evolution home. The second half
+* transact serializes different processes when the provider guarantees it (the
+* node backend is process-local only), and exactly ONE instance of each writer
+* service exists per evolution home. The second half
 * was implicit — `makeSerialQueue()` and the module-scope stores are
 * per-instance, so two rows writing one home interleave inside one file (the
 * "two instances, one file" class). This module makes that half enforceable: a
@@ -9260,8 +9267,9 @@ function absentHostServices(has) {
 * `claims` below is a module-scope Map: two ROWS over one home in ONE process
 * contend, while the SAME home in another process gets its own Map and is
 * granted the key. That is by construction, not a gap to close here — the
-* cross-process half of the contract is the IO backend's write lock
-* (`transactIo`, core/io.ts), which serializes a per-target read-modify-write.
+* cross-process half of the contract is the IO backend's transact
+* (`transactIo`, core/io.ts) when the provider guarantees it; the node backend
+* is process-local, so a shared home across processes is not protected by it alone.
 * The FLOW2-1 finding was three call sites reading a GRANTED claim as "no other
 * process can be doing this work", so the caller contract is stated here:
 * - granted means "no other row OF THIS PROCESS owns the key";

package/lib/types/instance-scope.d.ts

@@ -2,8 +2,9 @@
  * B3 / G4 (0.3.78): the family's single-instance contract, made explicit.
  *
  * Every persisted sidecar is written under TWO assumptions: the IO backend's
- * cross-process write lock serializes different processes, and exactly ONE
- * instance of each writer service exists per evolution home. The second half
+ * transact serializes different processes when the provider guarantees it (the
+ * node backend is process-local only), and exactly ONE instance of each writer
+ * service exists per evolution home. The second half
  * was implicit — `makeSerialQueue()` and the module-scope stores are
  * per-instance, so two rows writing one home interleave inside one file (the
  * "two instances, one file" class). This module makes that half enforceable: a
@@ -20,8 +21,9 @@
  * `claims` below is a module-scope Map: two ROWS over one home in ONE process
  * contend, while the SAME home in another process gets its own Map and is
  * granted the key. That is by construction, not a gap to close here — the
- * cross-process half of the contract is the IO backend's write lock
- * (`transactIo`, core/io.ts), which serializes a per-target read-modify-write.
+ * cross-process half of the contract is the IO backend's transact
+ * (`transactIo`, core/io.ts) when the provider guarantees it; the node backend
+ * is process-local, so a shared home across processes is not protected by it alone.
  * The FLOW2-1 finding was three call sites reading a GRANTED claim as "no other
  * process can be doing this work", so the caller contract is stated here:
  * - granted means "no other row OF THIS PROCESS owns the key";

package/lib/types/instance-scope.js

@@ -2,8 +2,9 @@
  * B3 / G4 (0.3.78): the family's single-instance contract, made explicit.
  *
  * Every persisted sidecar is written under TWO assumptions: the IO backend's
- * cross-process write lock serializes different processes, and exactly ONE
- * instance of each writer service exists per evolution home. The second half
+ * transact serializes different processes when the provider guarantees it (the
+ * node backend is process-local only), and exactly ONE instance of each writer
+ * service exists per evolution home. The second half
  * was implicit — `makeSerialQueue()` and the module-scope stores are
  * per-instance, so two rows writing one home interleave inside one file (the
  * "two instances, one file" class). This module makes that half enforceable: a
@@ -20,8 +21,9 @@
  * `claims` below is a module-scope Map: two ROWS over one home in ONE process
  * contend, while the SAME home in another process gets its own Map and is
  * granted the key. That is by construction, not a gap to close here — the
- * cross-process half of the contract is the IO backend's write lock
- * (`transactIo`, core/io.ts), which serializes a per-target read-modify-write.
+ * cross-process half of the contract is the IO backend's transact
+ * (`transactIo`, core/io.ts) when the provider guarantees it; the node backend
+ * is process-local, so a shared home across processes is not protected by it alone.
  * The FLOW2-1 finding was three call sites reading a GRANTED claim as "no other
  * process can be doing this work", so the caller contract is stated here:
  * - granted means "no other row OF THIS PROCESS owns the key";

package/lib/types/platform-services.d.ts

@@ -20,7 +20,7 @@ export interface PlatformServiceProbe {
     /** Where the probe runs. */
     readonly side: 'host' | 'client';
 }
-/** The 29 probes, in service-name order (the guard checks this list against the tree). */
+/** The 30 probes, in service-name order (the guard checks this list against the tree). */
 export declare const PLATFORM_SERVICE_PROBES: readonly PlatformServiceProbe[];
 /**
  * The HOST-side probes that do not resolve in this runtime — what `/evolution doctor` prints as

package/lib/types/platform-services.js

@@ -11,7 +11,7 @@
  * `client` probes run in the browser half, where the host has no view of the seats.
  * @module @lmzhen/dsh-evolution-core
  */
-/** The 29 probes, in service-name order (the guard checks this list against the tree). */
+/** The 30 probes, in service-name order (the guard checks this list against the tree). */
 export const PLATFORM_SERVICE_PROBES = Object.freeze([
     { service: 'agentDefaultModel', feature: 'the model route inherited by a plugin review branch', side: 'host' },
     { service: 'agentPresets', feature: 'the preset mount that gives a plugin review branch its tools/system', side: 'host' },
@@ -42,6 +42,7 @@ export const PLATFORM_SERVICE_PROBES = Object.freeze([
     { service: 'storageDomain', feature: 'the storage-domain state provider', side: 'host' },
     { service: 'systemPrompt', feature: 'the protected-skills prompt variable', side: 'host' },
     { service: 'tools', feature: 'tool registration and the guard seam', side: 'host' },
+    { service: 'workingDirectory', feature: 'the cwd used for skill snapshots and per-view policy files', side: 'host' },
 ]);
 /**
  * The HOST-side probes that do not resolve in this runtime — what `/evolution doctor` prints as

package/lib/types/run-registry.js

@@ -185,7 +185,8 @@ export function newRunRegistry(options) {
     };
     const persist = async () => {
         try {
-            // Read-modify-write under the io backend's cross-process lock. The file is the
+            // Read-modify-write under io.transact when the backend provides it; the node
+            // backend serializes in-process only. The file is the
             // BASE and only THIS process's rows are laid over it ("one writer per row"); the
             // single write a non-owner may make is the orphan verdict for a row whose owner is
             // gone. The row read inside this transaction IS the compare-and-swap: if its owner

package/lib/types/serial.d.ts

@@ -1,9 +1,10 @@
 /**
  * A process-local serial task queue: each task starts only after the previous
  * one settles (success or failure), so read-modify-write sequences that share
- * one file never interleave inside this process. The durable cross-process
- * serialization layer is the IO backend's transact lock; this chain is the
- * second layer (0.3.17 S2.8, T-1: the shape was duplicated in state-json and
+ * one file never interleave inside this process. When the IO backend provides
+ * a cross-process transact lock, that is the first layer; the node backend does
+ * not, so this chain is its only serialization. (0.3.17 S2.8, T-1: the shape was
+ * duplicated in state-json and
  * memory-files — one factory now).
  */
 export declare function makeSerialQueue(): <T>(task: () => Promise<T>) => Promise<T>;

package/lib/types/serial.js

@@ -1,9 +1,10 @@
 /**
  * A process-local serial task queue: each task starts only after the previous
  * one settles (success or failure), so read-modify-write sequences that share
- * one file never interleave inside this process. The durable cross-process
- * serialization layer is the IO backend's transact lock; this chain is the
- * second layer (0.3.17 S2.8, T-1: the shape was duplicated in state-json and
+ * one file never interleave inside this process. When the IO backend provides
+ * a cross-process transact lock, that is the first layer; the node backend does
+ * not, so this chain is its only serialization. (0.3.17 S2.8, T-1: the shape was
+ * duplicated in state-json and
  * memory-files — one factory now).
  */
 export function makeSerialQueue() {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@lmzhen/dsh-evolution-core",
   "description": "Shared stores, prompts, signals and lifecycle logic for the dsh-evolution plugin family (community build)",
-  "version": "0.30.43",
+  "version": "0.31.1",
   "publishConfig": {
     "access": "public"
   },