From 14a133588d96f4fcb25e8a66be232f34b77d43e2 Mon Sep 17 00:00:00 2001
From: vorotamoroz <vrtmrz@gmail.com>
Date: Sat, 5 Sep 2026 06:19:47 +0000
Subject: [PATCH] Use Commonlib 0.1.23 for stale deletion protection

---
 docs/tech_info.md | 7 ++++---
 package-lock.json | 8 ++++----
 package.json      | 2 +-
 updates.md        | 1 +
 4 files changed, 10 insertions(+), 8 deletions(-)

diff --git a/docs/tech_info.md b/docs/tech_info.md
index fb112d6b..217933ce 100644
--- a/docs/tech_info.md
+++ b/docs/tech_info.md
@@ -26,9 +26,10 @@ a stale file event from deleting Metadata and applying a valid replicated
 deletion are separate decisions.
 
 Commonlib's [Storage events and database-to-storage reflection](https://github.com/vrtmrz/livesync-commonlib/blob/main/docs/storage-events-and-reflection.md)
-documents the event boundary, the unreleased deletion revalidation, and its
-limits. In particular, deletion protection does not promise full support for
-external folder case changes or convergence of path spelling.
+documents the event boundary, the deletion revalidation introduced in
+Commonlib 0.1.23, and its limits. In particular, deletion protection does not
+promise full support for external folder case changes or convergence of path
+spelling.
 
 ## Current technical references
 
diff --git a/package-lock.json b/package-lock.json
index 51cfeed0..55ea80dc 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -23,7 +23,7 @@
                 "@smithy/types": "^4.14.3",
                 "@smithy/util-retry": "^4.4.5",
                 "@vrtmrz/browser-ui-kit": "0.1.0",
-                "@vrtmrz/livesync-commonlib": "0.1.22",
+                "@vrtmrz/livesync-commonlib": "0.1.23",
                 "@vrtmrz/obsidian-plugin-kit": "0.1.4",
                 "@vrtmrz/ui-interactions": "0.1.2",
                 "diff-match-patch": "^1.0.5",
@@ -4620,9 +4620,9 @@
             }
         },
         "node_modules/@vrtmrz/livesync-commonlib": {
-            "version": "0.1.22",
-            "resolved": "https://registry.npmjs.org/@vrtmrz/livesync-commonlib/-/livesync-commonlib-0.1.22.tgz",
-            "integrity": "sha512-8TsFo6xgEO/uZzkQ4TE3yydUyK8pCbuMm0C4DC/8KhG8z06N6hQQmwR7bV+a3Zgt9A5tXPImTFJWTMUIxJYV2g==",
+            "version": "0.1.23",
+            "resolved": "https://registry.npmjs.org/@vrtmrz/livesync-commonlib/-/livesync-commonlib-0.1.23.tgz",
+            "integrity": "sha512-hsaz2N04qNqM9HL0B+d5G/do1T0fe6Y4gVK3IueXvEnM6HM+3Jp17mdjbLn93FUOxkUVMcn4M+zIwPuppryVbw==",
             "license": "MIT",
             "dependencies": {
                 "@aws-sdk/client-s3": "^3.808.0",
diff --git a/package.json b/package.json
index 898fa37a..a36ad9cc 100644
--- a/package.json
+++ b/package.json
@@ -178,7 +178,7 @@
         "@smithy/types": "^4.14.3",
         "@smithy/util-retry": "^4.4.5",
         "@vrtmrz/browser-ui-kit": "0.1.0",
-        "@vrtmrz/livesync-commonlib": "0.1.22",
+        "@vrtmrz/livesync-commonlib": "0.1.23",
         "@vrtmrz/obsidian-plugin-kit": "0.1.4",
         "@vrtmrz/ui-interactions": "0.1.2",
         "diff-match-patch": "^1.0.5",
diff --git a/updates.md b/updates.md
index 0328c0f4..c98fd2c0 100644
--- a/updates.md
+++ b/updates.md
@@ -16,6 +16,7 @@ Earlier releases remain available in the 1.0 release history, the 1.0 preview hi
 
 #### Fixed
 
+- Watcher events from an external case-only parent-folder rename no longer let a stale deletion remove a note's Metadata while the file still exists. Moves out of the selected files retain the existing deletion behaviour; this fix does not add general folder-rename handling or path-case convergence. (#1168)
 - Conflict resolution dialogues now close when the same file is resolved elsewhere or the plug-in unloads. Requests for different files are shown one at a time, while a newer request for the same file replaces the stale dialogue.
 - An individual file-processing failure during ordinary start-up no longer keeps the entire application unready. A start-up notice asks the user to check the affected files and generate a report for details; each path is recorded in verbose logs and remains eligible for retry, while explicit Fetch and Rebuild operations retain strict completion.
 - Replication readiness diagnostics now state that application initialisation is incomplete instead of reporting only 'Not ready'. Database-preparation failures show a short notice, with the failed stage available in verbose logs.