@vrtmrz/livesync-commonlib 0.3.0 → 0.3.2

package/docs/unicode-path-identity.md

@@ -2,7 +2,7 @@
 date: 2026-10-19
 commonlib-version: "0.1.42"
 self-hosted-livesync-version: "1.0.38"
-status: unreleased
+status: published
 ---
 
 # Unicode path identity
@@ -14,8 +14,11 @@ does not alter the Metadata path or require physical files to be renamed.
 Unsupported values are rejected.
 
 NFC identity shipped in Commonlib `0.1.42` and Self-hosted LiveSync `1.0.38`.
-The Journal and P2P extension described below is unreleased. The original
-CouchDB release remains the published baseline for this document.
+The Journal and P2P extension is published in
+[Commonlib 0.3.0](https://www.npmjs.com/package/@vrtmrz/livesync-commonlib/v/0.3.0).
+The original date and reviewed versions above retain the CouchDB baseline.
+CLI and Obsidian host adoption is pending in
+[Self-hosted LiveSync #1309](https://github.com/vrtmrz/obsidian-livesync/pull/1309).
 
 ## Package contract
 
@@ -29,10 +32,11 @@ to its existing physical entry.
 ## Initial host settings
 
 Commonlib's shared new-Vault and stored-setting defaults retain version `0`.
-The maintained CLI and Obsidian hosts use version `1` for newly created
-synchronisation settings in the unreleased extension, while retaining `0` for
-old settings and Setup URIs which omit the field. This policy does not enable
-NFC for WebApp or WebPeer, and does not migrate existing databases.
+The maintained CLI and Obsidian host extension uses version `1` for newly
+created synchronisation settings, while retaining `0` for old settings and
+Setup URIs which omit the field. Its application adoption is tracked above.
+This policy does not enable NFC for WebApp or WebPeer, and does not migrate
+existing databases.
 
 The focused replication entry exports `inspectDatabasePathIdentity` and
 `PathIdentityInspection`. The existing `RemoteConnectionProbe` may expose
@@ -97,13 +101,37 @@ does not itself perform the required reconstruction.
 
 ## Supported hosts
 
-The maintained CLI and Obsidian support NFC identity with CouchDB, Journal,
-and P2P in this unreleased extension.
-`PathService` owns logical ID derivation. The CLI resolves NFC-equivalent names
-against directory entries while preserving the actual entry spelling; its
-generic Node storage contract remains exact-path access. Obsidian supplies its
-normalised storage paths and preserves an existing physical spelling when it
-is NFC-equivalent to the received path.
+The published Commonlib `0.3.0` package includes NFC protocol support for
+Journal and P2P. The matching Self-hosted LiveSync CLI and Obsidian host
+adoption remains an unreleased candidate tracked by
+[pull request #1309](https://github.com/vrtmrz/obsidian-livesync/pull/1309);
+the package protocol support alone does not mean those host integrations have
+shipped.
+
+The shared `/storage` resolver, Node and File System Access adapters, and
+explicit `DirectFileManipulator` path-version option are published in
+[Commonlib 0.3.1](https://www.npmjs.com/package/@vrtmrz/livesync-commonlib/v/0.3.1),
+as described in the [shared storage path design](design_docs/storage_path_resolution.md).
+They are absent from the registry artefact `0.3.0`; select the new immutable
+version rather than a source checkout carrying an older version label. Shared
+path adoption remains in [LiveSync #1315](https://github.com/vrtmrz/obsidian-livesync/pull/1315)
+and [Bridge #92](https://github.com/vrtmrz/livesync-bridge/pull/92).
+
+| Consumer surface | Published baseline | Current candidate status |
+| --- | --- | --- |
+| CLI and Obsidian with CouchDB | NFC identity is released in Commonlib `0.1.42` and Self-hosted LiveSync `1.0.38`. | The unreleased LiveSync candidate adds the shared Node resolver in the CLI and shared namespace/comparison helpers in Obsidian. |
+| CLI and Obsidian with Journal or P2P | Commonlib `0.3.0` publishes the NFC protocol support. | Matching host adoption remains unreleased pending [LiveSync #1309](https://github.com/vrtmrz/obsidian-livesync/pull/1309). |
+| Bridge | Legacy version `0` remains the default baseline. | The Bridge candidate enables version `1` only by explicit peer opt-in; every peer in a group must use the same path version. Its ordinary case-mismatch check remains separate from the required version check. |
+| WebApp | Legacy version `0` only. | WebApp remains Legacy-only; an explicit version `1` is rejected at startup. The browser storage primitive alone does not enable application support. |
+| WebPeer | A vaultless P2P utility. | It is not an NFC filesystem host. |
+| `DirectFileManipulator` | Commonlib `0.3.1` supports explicit version `1`; omitted or `0` retains Legacy identity. A populated database in the opposite mode is rejected. | The caller still owns physical path handling and coordinated migration. |
+
+`PathService` owns logical ID derivation. In the unreleased LiveSync host
+candidate, the CLI resolves NFC-equivalent names against directory entries
+while preserving the actual entry spelling; its generic Node storage contract
+remains exact-path access. Obsidian supplies its normalised storage paths and
+preserves an existing physical spelling when it is NFC-equivalent to the
+received path.
 
 Journal uses compatibility range `4` for NFC identity, independently of
 encryption and path obfuscation. Legacy ranges remain unchanged. The existing
@@ -146,9 +174,13 @@ checkpoints; the P2P source mark and target checkpoint handle database
 replacement. These operations do not rewrite IDs or merge histories in place.
 P2P retains its existing source selection during Fetch.
 
-Direct file access refuses a remote which
-declares the NFC feature. Other host adapters must establish physical path
-resolution before offering this setting. The regression tests cover ASCII,
+Commonlib 0.3.1 `DirectFileManipulator` exposes explicit
+`pathNormalizationVersion` options, defaulting to `0`: missing or `0` retains
+Legacy and rejects an NFC database; `1` accepts NFC and rejects a populated
+Legacy database before feature negotiation can change its declaration. A
+confirmed empty database follows the existing first-write feature contract.
+Direct integrations must establish physical path resolution before offering
+this setting; database admission alone does not provide that host behaviour. The regression tests cover ASCII,
 NFC, NFD, and mixed paths through in-memory PouchDB Metadata lookup, with and
 without path obfuscation, plus database admission, reconstruction ordering,
 collisions, and physical path handling. These tests do not establish native

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vrtmrz/livesync-commonlib",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "Shared data, storage, and replication primitives for Self-hosted LiveSync clients.",
   "type": "module",
   "types": "./dist/index.d.ts",
@@ -92,6 +92,11 @@
       "import": "./dist/settings.js",
       "default": "./dist/settings.js"
     },
+    "./storage": {
+      "types": "./dist/storage.d.ts",
+      "import": "./dist/storage.js",
+      "default": "./dist/storage.js"
+    },
     "./setup-uri": {
       "types": "./dist/setupUri.d.ts",
       "import": "./dist/setupUri.js",
@@ -675,6 +680,9 @@
       "settings": [
         "dist/settings.d.ts"
       ],
+      "storage": [
+        "dist/storage.d.ts"
+      ],
       "setup-uri": [
         "dist/setupUri.d.ts"
       ],