Reject unsupported WebApp identity and align family guidance

Reject explicit NFC settings before WebApp services start and when settings
are loaded or saved. Preserve Legacy interoperability, and clarify host
support and the Commonlib-first publication prerequisite.

docs/design_docs/unicode_path_identity.md

@@ -22,20 +22,23 @@ and is included in current Commonlib `0.2.2`, used by Self-hosted LiveSync
 `1.0.42`. This later handling is distinct from the initial NFC identity
 release.
 
-An unreleased extension adds Journal and P2P for the same maintained CLI and
-Obsidian hosts, moves the setting to General Settings, and defaults new
-synchronisation environments to NFC. The original dates
-and reviewed versions above remain the historical baseline.
+Commonlib `0.3.0` publishes the Journal and P2P path-identity protocol
+extension. The matching Self-hosted LiveSync CLI and Obsidian host adoption,
+including moving the setting to General Settings and defaulting new
+synchronisation environments to NFC, remains an unreleased candidate tracked
+by [pull request #1309](https://github.com/vrtmrz/obsidian-livesync/pull/1309).
+The original dates and reviewed versions above remain the historical baseline.
 
 ## Unreleased shared storage boundary
 
-The CLI adopts Commonlib's shared Unicode resolver and typed physical-I/O
-ports. Each NFC scan retains one comparison-policy snapshot; directory and
+The current LiveSync candidate adopts Commonlib's shared Unicode resolver and
+typed physical-I/O ports in the CLI, and shared namespace and comparison
+helpers in Obsidian while retaining its Vault APIs and existing alias-guard
+policy. Each NFC scan retains one comparison-policy snapshot; directory and
 permission errors propagate instead of producing a successful partial scan.
-Obsidian uses the shared namespace and comparison helpers while retaining its
-Vault APIs and existing alias-guard policy. The [developer guide](../../devs.md#file-path-handling)
-links the Commonlib design and ADR. This extraction does not change Metadata
-IDs, defaults, database migration, or the host support matrix below.
+These additions are unreleased and do not change the support status of a
+published host. The [developer guide](../../devs.md#file-path-handling) links
+the Commonlib design and ADR.
 
 ## Scope
 
@@ -43,8 +46,8 @@ IDs, defaults, database migration, or the host support matrix below.
 | --- | --- |
 | Logical identity | Version `1` uses NFC for Metadata ID and path comparison keys. Existing case handling remains a separate rule. Missing and `0` retain legacy behaviour. |
 | Stored paths and content | Keep the spelling in `Metadata.path` and existing physical Vault names. NFC does not change Chunk IDs or content. |
-| Maintained hosts and transports | CLI and Obsidian with CouchDB; Journal and P2P are added by the unreleased extension. |
-| Other consumers | Direct file access refuses a remote declaring the NFC feature. Other host adapters remain outside the support matrix. |
+| Maintained hosts and transports | CLI and Obsidian with CouchDB are released; their Journal and P2P host adoption remains unreleased. See the support matrix below. |
+| Other consumers | Direct-file access and other host adapters are covered separately below; shared path primitives alone do not enable NFC in an application. |
 | Migration | Rebuild both databases from one complete authoritative Vault, then Fetch each remaining client. Do not rewrite IDs or merge histories in place. |
 
 ## Path identity contract
@@ -228,14 +231,15 @@ updates and deletions.
 
 ## Compatibility matrix
 
-| Client and remote | Version `0` | Version `1` |
+| Host or API | Published baseline | Unreleased or host-specific status |
 | --- | --- | --- |
-| CLI with CouchDB | Supported with legacy identity. | Supported with NFC path resolution. |
-| Obsidian with CouchDB | Supported with legacy identity. | Supported with NFC path resolution. |
-| CLI or Obsidian with Journal | Existing behaviour. | Added by the unreleased extension; Rebuild remote journals and Fetch other devices. |
-| CLI or Obsidian with P2P | Existing behaviour. | Added by the unreleased extension; update and migrate every peer. |
-| Direct file access | Existing behaviour. | Refuses a remote requiring `nfc-path-identity-v1`. |
-| Other host adapters, including WebApp | Existing behaviour, subject to their existing support. | Outside the initial support matrix until physical-path handling is verified. |
+| CLI and Obsidian with CouchDB | NFC identity is supported from Self-hosted LiveSync `1.0.38` with Commonlib `0.1.42`. | The shared resolver and typed path ports are in the current LiveSync candidate; they are not part of a published Commonlib package yet. |
+| CLI and Obsidian with Journal | Commonlib `0.3.0` publishes the NFC protocol support. | Matching LiveSync host adoption remains an unreleased candidate tracked by [pull request #1309](https://github.com/vrtmrz/obsidian-livesync/pull/1309). Update and migrate every client before using version `1`. |
+| CLI and Obsidian with P2P | Commonlib `0.3.0` publishes the NFC protocol support. | Matching LiveSync host adoption remains an unreleased candidate. All peers must use the same path version; P2P warns and continues for ordinary representation or case differences. |
+| Bridge | The published baseline uses Legacy version `0`. | The Bridge integration is an unreleased candidate with explicit per-peer opt-in to version `1`; every peer in a group must use the same version. Its ordinary case mismatch check remains enabled unless the Bridge-wide `disableCheckingConfigMismatch: true` override disables that case check. The override does not bypass a path-version mismatch. |
+| `DirectFileManipulator` | The published Commonlib baseline refuses a remote which declares `nfc-path-identity-v1`. | An unpublished addition accepts explicit `pathNormalizationVersion` values `0` or `1`, defaulting to `0`, and rejects a populated database in the opposite mode. This admission setting does not provide physical-path resolution. |
+| WebApp | Legacy version `0` only. | WebApp remains Legacy-only and rejects an explicit version `1` at startup. The browser resolver primitive does not enable NFC in WebApp. |
+| WebPeer | A vaultless P2P utility, not a filesystem host. | No NFC filesystem support is implied by its P2P role. |
 | Older client without this feature | Can use a legacy database. | Cannot join a database declaring `nfc-path-identity-v1`. |
 
 ## Journal and P2P extension
@@ -291,8 +295,11 @@ The implementation acceptance matrix covers:
   version-`0` clients against an NFC database, and enforcement when ordinary
   mismatch warnings are disabled;
 - URI round trips, checkpoint invalidation across path versions, and
-  rejection for Direct file access; Journal and P2P acceptance and identity
-  mismatch checks belong to the unreleased extension;
+  rejection by the published Direct file access baseline; the unpublished
+  `DirectFileManipulator` addition covers explicit Legacy/NFC admission.
+  Journal and P2P protocol support is published in Commonlib `0.3.0`, while
+  matching CLI and Obsidian host adoption and end-to-end checks remain
+  unreleased;
 - refusal for ambiguous file or parent-directory candidates before local or
   remote reset, preserving both databases on rejection, within the paths
   returned by each host's supported listing; and
@@ -417,8 +424,8 @@ This design does not:
 - choose among ambiguous NFC-equivalent files or parents, or merge their
   content;
 - automatically change existing settings or database identity;
-- enable version `1` for Direct file access, WebApp, or an
-  unverified host adapter; or
+- automatically enable version `1` for WebApp or an unverified host adapter;
+  or
 - claim native iOS or macOS filesystem compatibility.
 
 ## References