@vrtmrz/livesync-commonlib 0.1.40 → 0.1.41

package/dist/managers/EntryManager/EntryManagerImpls.js

@@ -247,12 +247,29 @@ async function getDBEntryMetaByPath(host, { localDatabase }, path, opt, includeD
   const id = await host.services.path.path2id(path);
   try {
     let obj = null;
-    if (opt) {
-      obj = await localDatabase.get(id, opt);
-    } else {
-      obj = await localDatabase.get(id);
+    try {
+      if (opt) {
+        obj = await localDatabase.get(id, opt);
+      } else {
+        obj = await localDatabase.get(id);
+      }
+    } catch (ex) {
+      if (!includeDeleted || opt?.rev !== void 0 || !isErrorOfMissingDoc(ex)) throw ex;
+      for (let attempt = 0; attempt < 3; attempt++) {
+        const result = await localDatabase.allDocs({ keys: [id] });
+        const row = result.rows[0];
+        if (!row || !("value" in row) || !row.value.rev) return false;
+        const candidate = await localDatabase.get(id, { ...opt, rev: row.value.rev });
+        const current = (await localDatabase.allDocs({ keys: [id] })).rows[0];
+        if (!current || !("value" in current) || !current.value.rev) return false;
+        if (current.value.rev === candidate._rev) {
+          obj = candidate;
+          break;
+        }
+      }
+      if (!obj) return false;
     }
-    const deleted = obj?.deleted ?? obj._deleted ?? void 0;
+    const deleted = obj._deleted || obj.deleted;
     if (!includeDeleted && deleted) return false;
     if (obj.type && obj.type == "leaf") {
       return false;

package/docs/conflict-resolution.md

@@ -18,6 +18,8 @@ A1
 
 Resolving a conflict writes the selected or merged result on one branch and deletes every losing live leaf which the resolver has observed. Deleted leaves remain part of the tree until compaction removes their bodies. A stale client can therefore receive the resolved branch and the tombstone for a branch whose old content is still present in its storage.
 
+Metadata reads which explicitly include deleted entries also return a current PouchDB `_deleted` winner. An ordinary read still excludes deleted entries, and a request for an unavailable specific revision does not fall back to the current winner. A deleted-winner lookup rechecks the winning revision after fetching its body. If it changes, the lookup follows the new winner for at most three attempts and returns no entry if it cannot establish a stable revision. Incoming file reflection uses the current winner and rechecks it before deleting storage, so an older deletion notification does not override a subsequent restoration. Existing conflict and unsynchronised-edit protection still applies.
+
 ## Chunk reachability during conflicts
 
 A host which collects unreferenced chunks must include the current winner, every other live conflict leaf, their available divergent revisions, and their nearest available shared ancestor in its reachability scan. This preserves the content and merge base required to review an unresolved conflict. Chunk identifiers are shared across documents, so one reachability set must cover the whole database.

package/docs/proven-in-use.md

@@ -8,6 +8,8 @@ The code paths below identify the maintained Self-hosted LiveSync composition po
 
 ## Obsidian plug-in
 
+Unreleased deletion tests exercise `deleteMetadataOfDeletedFiles` enabled and disabled with two in-memory PouchDB replicas and injected file storage. They verify deletion and rename reflection, preservation of genuine local edits, and restoration before or during a deleted-winner lookup, including the final revision check before deletion. They also verify that missing provenance or a compacted base preserves local storage, and that continuously advancing deleted revisions do not return stale Metadata. These tests cover the Commonlib file handler and revision lookup, including the latest-revision check before deletion; they do not exercise Obsidian file watchers or a remote CouchDB server.
+
 Unreleased configuration-encryption tests cover changing the wrapper key without changing connection, E2EE, profile, or independent ID values. They also cover custom-key input before loading, failed writes, concurrent saves, cancellation, and unreadable-payload retention. Commonlib owns these service results. LiveSync owns the Apply controls, setting-tab registration, and database startup order; actual Apply and restart behaviour requires its focused real-Obsidian scenario.
 
 The CouchDB connection fix bypasses browser HTTP caching so encrypted replication can continue after a remote Rebuild preserves document IDs and revisions. Commonlib's regression tests cover Metadata and Chunks encrypted with a replacement Security Seed while an earlier response remains cached. Self-hosted LiveSync's `couchdb-http-cache` scenario additionally populates the real browser HTTP cache before rebuilding, confirms that the Seed and ciphertext change while the revision remains unchanged, and requires subsequent replication to succeed without clearing that cache. The released LiveSync 1.0.34 fails this scenario; a local checked Commonlib artefact passes in the maintained LiveSync 1.0.34 composition on Linux Obsidian 1.12.7. This establishes the tested build's behaviour, with the reporter's Windows and Obsidian 1.13.7 environment still unverified.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vrtmrz/livesync-commonlib",
-  "version": "0.1.40",
+  "version": "0.1.41",
   "description": "Shared data, storage, and replication primitives for Self-hosted LiveSync clients.",
   "type": "module",
   "types": "./dist/index.d.ts",