@parcha/pi-durable-disk 0.1.0-beta.19 → 0.1.0-beta.20

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## Unreleased
 
+## 0.1.0-beta.20 (2026-10-20)
+
+- A start mark keeper whose rewrite fails because the run's directory moved after its check now warns that the directory is no longer the one it started on, and stops. Before, the `PDA_START_MARK` warning said the rewrite failed (ENOENT or ENOTDIR). Nothing is written in either case; only the stated reason changes.
+- The local-disk env conformance cases watch with a 100 ms poll, so pi's fixed 3 s wait for a report keeps seconds of slack on a loaded runner; the product's 1 s watch default is unchanged.
+
 ## 0.1.0-beta.19 (2026-10-20)
 
 - An instance whose app released the run ends by itself: `pi-durable-disk run --app` exits 0 once `onOpen` has returned and the run is released, so the unit does not stay up with no mount.

package/dist/status.js

@@ -184,8 +184,9 @@ export function parseStartMark(text) {
 // watchdog's is (src/watchdog.ts says why). One refresh at a time, all synchronous: a stop (the message) is handled only
 // between two refreshes, so none is still writing once the thread has exited. It writes only while `dir` is still the
 // directory it first saw (its device and inode, read on this thread, so a stalled mount never holds the caller's): a path
-// that names another (a descriptor number reused) or none is never written, and the keeper stops. Its first failure goes
-// to the main thread, once.
+// that names another (a descriptor number reused) or none is never written, and the keeper stops. A rewrite that fails is
+// checked the same way, so a directory that moved between the check and the write is reported as moved, not as a failed
+// write. Its first failure goes to the main thread, once.
 const KEEPER_SOURCE = `"use strict";
 const fs = require("node:fs");
 const path = require("node:path");
@@ -200,19 +201,23 @@ const report = (message) => {
   reported = true;
   parentPort.postMessage(message);
 };
-function refresh() {
-  if (stopped) return;
+// Why dir is no longer the directory the keeper first saw, or null while it is (the first call records it).
+function moved() {
   let now;
   try {
     now = fs.statSync(dir, { bigint: true });
   } catch (error) {
-    stopped = true;
-    return report("its directory cannot be reached (" + (error.code || error.message) + "), so it is no longer the directory the keeper started on");
+    return "its directory cannot be reached (" + (error.code || error.message) + "), so it is no longer the directory the keeper started on";
   }
   first ??= { dev: now.dev, ino: now.ino };
-  if (now.dev !== first.dev || now.ino !== first.ino) {
+  return now.dev === first.dev && now.ino === first.ino ? null : "its directory is no longer the directory the keeper started on";
+}
+function refresh() {
+  if (stopped) return;
+  const away = moved();
+  if (away) {
     stopped = true;
-    return report("its directory is no longer the directory the keeper started on");
+    return report(away);
   }
   let text;
   try {
@@ -245,6 +250,12 @@ function refresh() {
       fs.closeSync(handle);
     }
   } catch (error) {
+    // The directory may have moved after the check above: then that is the reason, and the keeper stops.
+    const away = moved();
+    if (away) {
+      stopped = true;
+      return report(away);
+    }
     report("rewriting it failed (" + (error.code || error.message) + ")");
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@parcha/pi-durable-disk",
-  "version": "0.1.0-beta.19",
+  "version": "0.1.0-beta.20",
   "description": "A durable pi host on a network disk (Archil): one owner per run, a fence, durable commits, and a supervisor.",
   "keywords": [
     "pi",