@vrtmrz/livesync-commonlib 0.1.0-rc.5 → 0.1.0-rc.7

package/dist/services/base/CommonlibMessages.js

@@ -0,0 +1,313 @@
+const commonlibEnglishMessages = {
+  "(BETA) Always overwrite with a newer file": "(BETA) Always overwrite with a newer file",
+  "(Beta) Use ignore files": "(Beta) Use ignore files",
+  "(Days passed, 0 to disable automatic-deletion)": "(Days passed, 0 to disable automatic-deletion)",
+  "(MB) If this is set, changes to local and remote files that are larger than this will be skipped. If the file becomes smaller again, a newer one will be used.": "(MB) If this is set, changes to local and remote files that are larger than this will be skipped. If the file becomes smaller again, a newer one will be used.",
+  "(Mega chars)": "(Mega chars)",
+  "(Not recommended) If set, credentials will be stored in the file.": "(Not recommended) If set, credentials will be stored in the file.",
+  "(Obsolete) Use an old adapter for compatibility": "(Obsolete) Use an old adapter for compatibility",
+  "(ex. Read chunks online) If this option is enabled, LiveSync reads chunks online directly instead of replicating them locally. Increasing Custom chunk size is recommended.": "(ex. Read chunks online) If this option is enabled, LiveSync reads chunks online directly instead of replicating them locally. Increasing Custom chunk size is recommended.",
+  "Access Key": "Access Key",
+  "Active Remote Type": "Active Remote Type",
+  "Always prompt merge conflicts": "Always prompt merge conflicts",
+  "Application ID": "Application ID",
+  "Apply Latest Change if Conflicting": "Apply Latest Change if Conflicting",
+  "Apply preset configuration": "Apply preset configuration",
+  "Auto-accept compatible tweak mismatches": "Auto-accept compatible tweak mismatches",
+  "Automatically Sync all files when opening Obsidian.": "Automatically Sync all files when opening Obsidian.",
+  "Automatically accepts mismatches that are compatible but potentially lossy by comparing tweak modification times.": "Automatically accepts mismatches that are compatible but potentially lossy by comparing tweak modification times.",
+  "Automatically broadcast changes to connected peers": "Automatically broadcast changes to connected peers",
+  "Automatically start P2P connection on launch": "Automatically start P2P connection on launch",
+  "Batch database update": "Batch database update",
+  "Batch limit": "Batch limit",
+  "Batch size": "Batch size",
+  "Batch size of on-demand fetching": "Batch size of on-demand fetching",
+  "Before v0.17.16, we used an old adapter for the local database. Now the new adapter is preferred. However, it needs local database rebuilding. Please disable this toggle when you have enough time. If leave it enabled, also while fetching from the remote database, you will be asked to disable this.": "Before v0.17.16, we used an old adapter for the local database. Now the new adapter is preferred. However, it needs local database rebuilding. Please disable this toggle when you have enough time. If leave it enabled, also while fetching from the remote database, you will be asked to disable this.",
+  "Bucket Name": "Bucket Name",
+  "Chunk Splitter": "Chunk Splitter",
+  "Chunk revisions are always derived from their content. This stored key is retained only for compatibility.": "Chunk revisions are always derived from their content. This stored key is retained only for compatibility.",
+  "Comma separated `.gitignore, .dockerignore`": "Comma separated `.gitignore, .dockerignore`",
+  "Content-derived chunk revisions (obsolete setting)": "Content-derived chunk revisions (obsolete setting)",
+  "Custom Headers": "Custom Headers",
+  "Custom headers for requesting the CouchDB. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": "Custom headers for requesting the CouchDB. e.g. `x-custom-header1: value1\n x-custom-header2: value2`",
+  "Custom headers for requesting the bucket. e.g. `x-custom-header1: value1\n x-custom-header2: value2`": "Custom headers for requesting the bucket. e.g. `x-custom-header1: value1\n x-custom-header2: value2`",
+  "Data Compression": "Data Compression",
+  "Database Name": "Database Name",
+  "Database suffix": "Database suffix",
+  "Delay conflict resolution of inactive files": "Delay conflict resolution of inactive files",
+  "Delay merge conflict prompt for inactive files.": "Delay merge conflict prompt for inactive files.",
+  "Delete old metadata of deleted files on start-up": "Delete old metadata of deleted files on start-up",
+  "Desktop only; uses more battery and network.": "Desktop only; uses more battery and network.",
+  "Device name": "Device name",
+  "Disables logging, only shows notifications. Please disable if you report an issue.": "Disables logging, only shows notifications. Please disable if you report an issue.",
+  "Display Language": "Display Language",
+  "Do not check configuration mismatch before replication": "Do not check configuration mismatch before replication",
+  "Do not keep metadata of deleted files.": "Do not keep metadata of deleted files.",
+  "Do not split chunks in the background": "Do not split chunks in the background",
+  "Do not use internal API": "Do not use internal API",
+  "Doctor.Button.DismissThisVersion": "No, and do not ask again until the next release",
+  "Doctor.Button.Fix": "Fix it",
+  "Doctor.Button.FixButNoRebuild": "Fix it but no rebuild",
+  "Doctor.Button.No": "No",
+  "Doctor.Button.Skip": "Leave it as is",
+  "Doctor.Button.Yes": "Yes",
+  "Doctor.Dialogue.Main": "Hi! Config Doctor has been activated because of ${activateReason}!\nAnd, unfortunately some configurations were detected as potential problems.\nPlease be assured. Let's solve them one by one.\n\nTo let you know ahead of time, we will ask you about the following items.\n\n${issues}\n\nShall we get started?",
+  "Doctor.Dialogue.MainFix": "\n## ${name}\n\n| Current | Ideal |\n|:---:|:---:|\n| ${current} | ${ideal} |\n\n**Recommendation Level:** ${level}\n\n### Why this has been detected?\n\n${reason}\n\n${note}\n\nFix this to the ideal value?",
+  "Doctor.Dialogue.Title": "Self-hosted LiveSync Config Doctor",
+  "Doctor.Dialogue.TitleAlmostDone": "Almost done!",
+  "Doctor.Dialogue.TitleFix": "Fix issue ${current}/${total}",
+  "Doctor.Level.Must": "Must",
+  "Doctor.Level.Necessary": "Necessary",
+  "Doctor.Level.Optional": "Optional",
+  "Doctor.Level.Recommended": "Recommended",
+  "Doctor.Message.NoIssues": "No issues detected!",
+  "Doctor.Message.RebuildLocalRequired": "Attention! A local database rebuild is required to apply this!",
+  "Doctor.Message.RebuildRequired": "Attention! A rebuild is required to apply this!",
+  "Doctor.Message.SomeSkipped": "We left some issues as is. Shall I ask you again on next startup?",
+  "Doctor.RULES.E2EE_V02500.REASON": "The End-to-End Encryption has got now more robust and faster. Also because, the previous E2EE was found to be compromised in a re-conducted code review. It should be applied as soon as possible. Really apologises for your inconvenience. And, this setting is not forward compatible. All synchronised devices must be updated to v0.25.0 or higher. Rebuilds are not required and will be converted from the new transfer to the new format, However, it is recommended to rebuild whenever possible.",
+  "Effectively a directory. Should end with `/`. e.g., `vault-name/`.": "Effectively a directory. Should end with `/`. e.g., `vault-name/`.",
+  "Enable Developers' Debug Tools (If available).": "Enable Developers' Debug Tools (If available).",
+  "Enable P2P Synchronization": "Enable P2P Synchronization",
+  "Enable advanced features": "Enable advanced features",
+  "Enable customization sync": "Enable customization sync",
+  "Enable edge case treatment features": "Enable edge case treatment features",
+  "Enable forcePathStyle": "Enable forcePathStyle",
+  "Enable per-file customization sync": "Enable per-file customization sync",
+  "Enable poweruser features": "Enable poweruser features",
+  "Enable this if your Object Storage doesn't support CORS": "Enable this if your Object Storage doesn't support CORS",
+  "Enable this option to automatically apply the most recent change to documents even when it conflicts": "Enable this option to automatically apply the most recent change to documents even when it conflicts",
+  "Encrypt contents on the remote database. If you use the plugin's synchronization feature, enabling this is recommended.": "Encrypt contents on the remote database. If you use the plugin's synchronization feature, enabling this is recommended.",
+  "Encrypting sensitive configuration items": "Encrypting sensitive configuration items",
+  "Encryption passphrase. If changed, you should overwrite the server's database with the new (encrypted) files.": "Encryption passphrase. If changed, you should overwrite the server's database with the new (encrypted) files.",
+  "End-to-End Encryption": "End-to-End Encryption",
+  "End-to-End Encryption Algorithm": "End-to-End Encryption Algorithm",
+  "Endpoint URL": "Endpoint URL",
+  "Enhance chunk size": "Enhance chunk size",
+  "Fetch chunks on demand": "Fetch chunks on demand",
+  "Fetch database with previous behaviour": "Fetch database with previous behaviour",
+  "File prefix on the bucket": "File prefix on the bucket",
+  Filename: "Filename",
+  "Files with modification times greater than this value (in seconds since the Unix epoch) will not have their events reflected. Set to 0 to disable this limit.": "Files with modification times greater than this value (in seconds since the Unix epoch) will not have their events reflected. Set to 0 to disable this limit.",
+  "Forces the file to be synced when opened.": "Forces the file to be synced when opened.",
+  "Handle files as Case-Sensitive": "Handle files as Case-Sensitive",
+  "How to display network errors when the sync server is unreachable.": "How to display network errors when the sync server is unreachable.",
+  "If disabled(toggled), chunks will be split on the UI thread (Previous behaviour).": "If disabled(toggled), chunks will be split on the UI thread (Previous behaviour).",
+  "If enabled per-filed efficient customization sync will be used. We need a small migration when enabling this. And all devices should be updated to v0.23.18. Once we enabled this, we lost a compatibility with old versions.": "If enabled per-filed efficient customization sync will be used. We need a small migration when enabling this. And all devices should be updated to v0.23.18. Once we enabled this, we lost a compatibility with old versions.",
+  "If enabled, changes will be automatically broadcasted to all connected peers. Notified peers will start fetching the changes.": "If enabled, changes will be automatically broadcasted to all connected peers. Notified peers will start fetching the changes.",
+  "If enabled, chunks will be split into no more than 100 items. However, dedupe is slightly weaker.": "If enabled, chunks will be split into no more than 100 items. However, dedupe is slightly weaker.",
+  "If enabled, efficient per-file customization sync will be used. A minor migration is required when enabling this feature, and all devices must be updated to v0.23.18. Enabling this feature will result in losing compatibility with older versions.": "If enabled, efficient per-file customization sync will be used. A minor migration is required when enabling this feature, and all devices must be updated to v0.23.18. Enabling this feature will result in losing compatibility with older versions.",
+  "If enabled, newly created chunks are temporarily kept within the document, and graduated to become independent chunks once stabilised.": "If enabled, newly created chunks are temporarily kept within the document, and graduated to become independent chunks once stabilised.",
+  "If enabled, the P2P connection will be automatically started when the application launches.": "If enabled, the P2P connection will be automatically started when the application launches.",
+  "If enabled, the file properties will be encrypted in the remote database. This is useful for protecting sensitive information in file paths, sizes, and IDs of its chunks. If you are using V1 E2EE, this only obfuscates the file path.": "If enabled, the file properties will be encrypted in the remote database. This is useful for protecting sensitive information in file paths, sizes, and IDs of its chunks. If you are using V1 E2EE, this only obfuscates the file path.",
+  "If enabled, the file under 1kb will be processed in the UI thread.": "If enabled, the file under 1kb will be processed in the UI thread.",
+  "If enabled, the forcePathStyle option will be used for bucket operations.": "If enabled, the forcePathStyle option will be used for bucket operations.",
+  "If enabled, the notification of hidden files change will be suppressed.": "If enabled, the notification of hidden files change will be suppressed.",
+  "If enabled, the plugin will not attempt to connect to the remote database even if the chunk was not found locally.": "If enabled, the plugin will not attempt to connect to the remote database even if the chunk was not found locally.",
+  "If enabled, the request API will be used to avoid `inevitable` CORS problems. This is a workaround and may not work in all cases. PLEASE READ THE DOCUMENTATION BEFORE USING THIS OPTION. This is a less-secure option.": "If enabled, the request API will be used to avoid `inevitable` CORS problems. This is a workaround and may not work in all cases. PLEASE READ THE DOCUMENTATION BEFORE USING THIS OPTION. This is a less-secure option.",
+  "If enabled, the \u26D4 icon will be shown inside the status instead of the file warnings banner. No details will be shown.": "If enabled, the \u26D4 icon will be shown inside the status instead of the file warnings banner. No details will be shown.",
+  "If this enabled, All files are handled as case-Sensitive (Previous behaviour).": "If this enabled, All files are handled as case-Sensitive (Previous behaviour).",
+  "If this enabled, JWT will be used for authentication.": "If this enabled, JWT will be used for authentication.",
+  "If this enabled, chunks will be split into semantically meaningful segments. Not all platforms support this feature.": "If this enabled, chunks will be split into semantically meaningful segments. Not all platforms support this feature.",
+  "If this is set, changes to local files which are matched by the ignore files will be skipped. Remote changes are determined using local ignore files.": "If this is set, changes to local files which are matched by the ignore files will be skipped. Remote changes are determined using local ignore files.",
+  "If this option is enabled, PouchDB will hold the connection open for 60 seconds, and if no change arrives in that time, close and reopen the socket, instead of holding it open indefinitely. Useful when a proxy limits request duration but can increase resource usage.": "If this option is enabled, PouchDB will hold the connection open for 60 seconds, and if no change arrives in that time, close and reopen the socket, instead of holding it open indefinitely. Useful when a proxy limits request duration but can increase resource usage.",
+  "Ignore files": "Ignore files",
+  "Incubate Chunks in Document": "Incubate Chunks in Document",
+  "Internal timestamp for resolving compatible tweak mismatches.": "Internal timestamp for resolving compatible tweak mismatches.",
+  "Interval (sec)": "Interval (sec)",
+  "JWT Algorithm": "JWT Algorithm",
+  "K.long_p2p_sync": "%{title_p2p_sync}",
+  "K.title_p2p_sync": "Peer-to-Peer Sync",
+  "Keep empty folder": "Keep empty folder",
+  "Keep replication active in the background": "Keep replication active in the background",
+  "Key ID": "Key ID",
+  "Keypair or pre-shared key": "Keypair or pre-shared key",
+  "Last tweak modified timestamp": "Last tweak modified timestamp",
+  "LiveSync could not handle multiple vaults which have same name without different prefix, This should be automatically configured.": "LiveSync could not handle multiple vaults which have same name without different prefix, This should be automatically configured.",
+  "Longest chunk line threshold value (Not Configurable from the UI Now).": "Longest chunk line threshold value (Not Configurable from the UI Now).",
+  "MB (0 to disable).": "MB (0 to disable).",
+  "MB per request": "MB per request",
+  "Maximum Incubating Chunk Size": "Maximum Incubating Chunk Size",
+  "Maximum Incubating Chunks": "Maximum Incubating Chunks",
+  "Maximum Incubation Period": "Maximum Incubation Period",
+  "Maximum delay for batch database updating": "Maximum delay for batch database updating",
+  "Maximum file modification time for reflected file events": "Maximum file modification time for reflected file events",
+  "Maximum file size": "Maximum file size",
+  "Maximum request size for manually resending chunks": "Maximum request size for manually resending chunks",
+  "Memory cache size (by total characters)": "Memory cache size (by total characters)",
+  "Memory cache size (by total items)": "Memory cache size (by total items)",
+  "Minimum Chunk Size (Not Configurable from the UI Now).": "Minimum Chunk Size (Not Configurable from the UI Now).",
+  "Minimum delay for batch database updating": "Minimum delay for batch database updating",
+  "Minimum interval for syncing": "Minimum interval for syncing",
+  "Move remotely deleted files to the trash, instead of deleting. (This setting is ineffective from Obsidian v1.7.2 onwards, as deletion always respects your Obsidian preferences.)": "Move remotely deleted files to the trash, instead of deleting. (This setting is ineffective from Obsidian v1.7.2 onwards, as deletion always respects your Obsidian preferences.)",
+  "Network warning style": "Network warning style",
+  'Not all messages have been translated. And, please revert to "Default" when reporting errors.': 'Not all messages have been translated. And, please revert to "Default" when reporting errors.',
+  "Notify all setting files": "Notify all setting files",
+  "Notify customized": "Notify customized",
+  "Notify when other device has newly customized.": "Notify when other device has newly customized.",
+  "Notify when the estimated remote storage size exceeds on start up": "Notify when the estimated remote storage size exceeds on start up",
+  "Now we can choose how to split the chunks; V3 is the most efficient. If you have troubled, please make this Default or Legacy.": "Now we can choose how to split the chunks; V3 is the most efficient. If you have troubled, please make this Default or Legacy.",
+  "Number of batches to process at a time. Defaults to 40. Minimum is 2. This along with batch size controls how many docs are kept in memory at a time.": "Number of batches to process at a time. Defaults to 40. Minimum is 2. This along with batch size controls how many docs are kept in memory at a time.",
+  "Number of changes to sync at a time. Defaults to 50. Minimum is 2.": "Number of changes to sync at a time. Defaults to 50. Minimum is 2.",
+  "P2P.AskPassphraseForDecrypt": "The remote peer shared the configuration. Please input the passphrase to decrypt the configuration.",
+  "P2P.AskPassphraseForShare": "The remote peer requested this device configuration. Please input the passphrase to share the configuration. You can ignore the request by cancelling this dialogue.",
+  "P2P.DisabledButNeed": "%{title_p2p_sync} is disabled. Do you really want to enable it?",
+  "P2P.NoAutoSyncPeers": "No auto-sync peers found. Please set peers on the %{long_p2p_sync} pane.",
+  "P2P.NoKnownPeers": "No peers has been detected, waiting incoming other peers...",
+  "P2P.NotEnabled": "%{title_p2p_sync} is not enabled. We cannot open a new connection.",
+  "P2P.ReplicatorInstanceMissing": "P2P Sync replicator is not found, possibly not have been configured or enabled.",
+  "P2P.SeemsOffline": "Peer ${name} seems offline, skipped.",
+  "P2P.SyncAlreadyRunning": "P2P Sync is already running.",
+  "P2P.SyncCompleted": "P2P Sync completed.",
+  "P2P.SyncStartedWith": "P2P Sync with ${name} have been started.",
+  Passphrase: "Passphrase",
+  "Passphrase of sensitive configuration items": "Passphrase of sensitive configuration items",
+  Password: "Password",
+  "Per-file-saved customization sync": "Per-file-saved customization sync",
+  "Periodic Sync interval": "Periodic Sync interval",
+  "Please select 'Cancel' explicitly to cancel this operation.": "Please select 'Cancel' explicitly to cancel this operation.",
+  "Please use V2, V1 is deprecated and will be removed in the future, It was not a very appropriate algorithm. Only for compatibility V1 is kept.": "Please use V2, V1 is deprecated and will be removed in the future, It was not a very appropriate algorithm. Only for compatibility V1 is kept.",
+  Presets: "Presets",
+  "Process files even if seems to be corrupted": "Process files even if seems to be corrupted",
+  "Process small files in the foreground": "Process small files in the foreground",
+  "Property Encryption": "Property Encryption",
+  "Reducing the frequency with which on-disk changes are reflected into the DB": "Reducing the frequency with which on-disk changes are reflected into the DB",
+  Region: "Region",
+  "Remote server type": "Remote server type",
+  "Replicator.Message.Cleaned": "Database cleaning up is in process. replication has been cancelled",
+  "Replicator.Message.InitialiseFatalError": "No replicator is available, this is the fatal error.",
+  "Replicator.Message.Pending": "Some file events are pending. Replication has been cancelled.",
+  "Replicator.Message.SomeModuleFailed": "Replication has been cancelled by some module failure",
+  "Replicator.Message.VersionUpFlash": "An update has been detected. Please open the Settings dialogue and check the Change Log. Replication has been cancelled.",
+  "Requires restart of Obsidian.": "Requires restart of Obsidian.",
+  "Room ID": "Room ID",
+  "Rotation Duration": "Rotation Duration",
+  "Save settings to a markdown file. You will be notified when new settings arrive. You can set different files by the platform.": "Save settings to a markdown file. You will be notified when new settings arrive. You can set different files by the platform.",
+  "Saving will be performed forcefully after this number of seconds.": "Saving will be performed forcefully after this number of seconds.",
+  "Scan changes on customization sync": "Scan changes on customization sync",
+  "Scan customization automatically": "Scan customization automatically",
+  "Scan customization before replicating.": "Scan customization before replicating.",
+  "Scan customization every 1 minute.": "Scan customization every 1 minute.",
+  "Scan customization periodically": "Scan customization periodically",
+  "Scan for hidden files before replication": "Scan for hidden files before replication",
+  "Scan hidden files periodically": "Scan hidden files periodically",
+  "Seconds, 0 to disable": "Seconds, 0 to disable",
+  "Seconds. Saving to the local database will be delayed until this value after we stop typing or saving.": "Seconds. Saving to the local database will be delayed until this value after we stop typing or saving.",
+  "Secret Key": "Secret Key",
+  "Server URI": "Server URI",
+  "Setup.QRCode": 'We have generated a QR code to transfer the settings. Please scan the QR code with your phone or other device.\nNote: The QR code is not encrypted, so be careful to open this.\n\n>[!FOR YOUR EYES ONLY]-\n> <div class="sls-qr">${qr_image}</div>',
+  "Should we keep folders that don't have any files inside?": "Should we keep folders that don't have any files inside?",
+  "Should we only check for conflicts when a file is opened?": "Should we only check for conflicts when a file is opened?",
+  "Should we prompt you about conflicting files when a file is opened?": "Should we prompt you about conflicting files when a file is opened?",
+  "Should we prompt you for every single merge, even if we can safely merge automatcially?": "Should we prompt you for every single merge, even if we can safely merge automatcially?",
+  "Show only notifications": "Show only notifications",
+  "Show status as icons only": "Show status as icons only",
+  "Show status icon instead of file warnings banner": "Show status icon instead of file warnings banner",
+  "Show status inside the editor": "Show status inside the editor",
+  "Show status on the status bar": "Show status on the status bar",
+  "Show verbose log. Please enable if you report an issue.": "Show verbose log. Please enable if you report an issue.",
+  "Signalling Relays": "Signalling Relays",
+  "Starts synchronisation when a file is saved.": "Starts synchronisation when a file is saved.",
+  "Stop reflecting database changes to storage files.": "Stop reflecting database changes to storage files.",
+  "Stop watching for file changes.": "Stop watching for file changes.",
+  "Subject (whoami)": "Subject (whoami)",
+  "Suppress notification of hidden files change": "Suppress notification of hidden files change",
+  "Suspend database reflecting": "Suspend database reflecting",
+  "Suspend file watching": "Suspend file watching",
+  "Sync Mode": "Sync Mode",
+  "Sync after merging file": "Sync after merging file",
+  "Sync automatically after merging files": "Sync automatically after merging files",
+  "Sync on Editor Save": "Sync on Editor Save",
+  "Sync on File Open": "Sync on File Open",
+  "Sync on Save": "Sync on Save",
+  "Sync on Startup": "Sync on Startup",
+  "TURN Credential": "TURN Credential",
+  "TURN Servers": "TURN Servers",
+  "TURN Username": "TURN Username",
+  "Testing only - Resolve file conflicts by syncing newer copies of the file, this can overwrite modified files. Be Warned.": "Testing only - Resolve file conflicts by syncing newer copies of the file, this can overwrite modified files. Be Warned.",
+  "The Application ID for P2P connection. This should be same among your devices. Default is 'self-hosted-livesync' and could not be modified from the UI.": "The Application ID for P2P connection. This should be same among your devices. Default is 'self-hosted-livesync' and could not be modified from the UI.",
+  "The Hash algorithm for chunk IDs": "The Hash algorithm for chunk IDs",
+  "The Nostr relay servers to establish connections for P2P connections. Multiple servers can be separated by commas.": "The Nostr relay servers to establish connections for P2P connections. Multiple servers can be separated by commas.",
+  "The Passphrase for P2P connection. This should be same among your devices.": "The Passphrase for P2P connection. This should be same among your devices.",
+  "The Room ID for P2P connection. This should be same among your devices.": "The Room ID for P2P connection. This should be same among your devices.",
+  "The Rotation duration of token in minutes. Each generated tokens will be valid only within this duration.": "The Rotation duration of token in minutes. Each generated tokens will be valid only within this duration.",
+  "The TURN servers to use for P2P connections. Multiple servers can be separated by commas.": "The TURN servers to use for P2P connections. Multiple servers can be separated by commas.",
+  "The algorithm used for JWT authentication.": "The algorithm used for JWT authentication.",
+  "The credential/password for the TURN servers.": "The credential/password for the TURN servers.",
+  "The delay for consecutive on-demand fetches": "The delay for consecutive on-demand fetches",
+  "The key (PSK in HSxxx in base64, or private key in ESxxx in PEM) used for JWT authentication.": "The key (PSK in HSxxx in base64, or private key in ESxxx in PEM) used for JWT authentication.",
+  "The key ID. this should be matched with CouchDB->jwt_keys->ALG:_`kid`.": "The key ID. this should be matched with CouchDB->jwt_keys->ALG:_`kid`.",
+  "The maximum duration for which chunks can be incubated within the document. Chunks exceeding this period will graduate to independent chunks.": "The maximum duration for which chunks can be incubated within the document. Chunks exceeding this period will graduate to independent chunks.",
+  "The maximum number of chunks that can be incubated within the document. Chunks exceeding this number will immediately graduate to independent chunks.": "The maximum number of chunks that can be incubated within the document. Chunks exceeding this number will immediately graduate to independent chunks.",
+  "The maximum total size of chunks that can be incubated within the document. Chunks exceeding this size will immediately graduate to independent chunks.": "The maximum total size of chunks that can be incubated within the document. Chunks exceeding this size will immediately graduate to independent chunks.",
+  "The minimum interval for automatic synchronisation on event.": "The minimum interval for automatic synchronisation on event.",
+  "The subject for JWT authentication. Mostly username.": "The subject for JWT authentication. Mostly username.",
+  "The username for the TURN servers.": "The username for the TURN servers.",
+  "This passphrase will not be copied to another device. It will be set to `Default` until you configure it again.": "This passphrase will not be copied to another device. It will be set to `Default` until you configure it again.",
+  "Unique name between all synchronized devices. To edit this setting, please disable customization sync once.": "Unique name between all synchronized devices. To edit this setting, please disable customization sync once.",
+  "Use Custom HTTP Handler": "Use Custom HTTP Handler",
+  "Use JWT instead of Basic Authentication": "Use JWT instead of Basic Authentication",
+  "Use Only Local Chunks": "Use Only Local Chunks",
+  "Use Request API to avoid `inevitable` CORS problem": "Use Request API to avoid `inevitable` CORS problem",
+  "Use Segmented-splitter": "Use Segmented-splitter",
+  "Use dynamic iteration count": "Use dynamic iteration count",
+  "Use splitting-limit-capped chunk splitter": "Use splitting-limit-capped chunk splitter",
+  "Use the trash bin": "Use the trash bin",
+  "Use timeouts instead of heartbeats": "Use timeouts instead of heartbeats",
+  Username: "Username",
+  "Verbose Log": "Verbose Log",
+  "Warning! This will have a serious impact on performance. And the logs will not be synchronised under the default name. Please be careful with logs; they often contain your confidential information.": "Warning! This will have a serious impact on performance. And the logs will not be synchronised under the default name. Please be careful with logs; they often contain your confidential information.",
+  "When you save a file in the editor, start a sync automatically": "When you save a file in the editor, start a sync automatically",
+  "While enabled, it causes very performance impact but debugging replication testing and other features will be enabled. Please disable this if you have not read the source code. Requires restart of Obsidian. Sometimes there is no implementation.": "While enabled, it causes very performance impact but debugging replication testing and other features will be enabled. Please disable this if you have not read the source code. Requires restart of Obsidian. Sometimes there is no implementation.",
+  "Write credentials in the file": "Write credentials in the file",
+  "Write logs into the file": "Write logs into the file",
+  "You can enable this setting to process the files with size mismatches, these files can be created by some APIs or integrations.": "You can enable this setting to process the files with size mismatches, these files can be created by some APIs or integrations.",
+  "liveSyncReplicator.beforeLiveSync": "Before LiveSync, start OneShot once...",
+  "liveSyncReplicator.cantReplicateLowerValue": "We can't replicate more lower value.",
+  "liveSyncReplicator.checkingLastSyncPoint": "Looking for the point last synchronized point.",
+  "liveSyncReplicator.couldNotConnectTo": "Could not connect to ${uri} : ${name}\n(${db})",
+  "liveSyncReplicator.couldNotConnectToRemoteDb": "Could not connect to remote database: ${d}",
+  "liveSyncReplicator.couldNotConnectToServer": "The connection to the remote has been prevented, or failed.",
+  "liveSyncReplicator.couldNotConnectToURI": "Could not connect to ${uri}:${dbRet}",
+  "liveSyncReplicator.couldNotMarkResolveRemoteDb": "Could not mark resolve remote database.",
+  "liveSyncReplicator.liveSyncBegin": "LiveSync begin...",
+  "liveSyncReplicator.lockRemoteDb": "Lock remote database to prevent data corruption",
+  "liveSyncReplicator.markDeviceResolved": "Mark this device as 'resolved'.",
+  "liveSyncReplicator.mismatchedTweakDetected": "Some mismatches have been detected in the configuration between devices. Running a manual replication will attempt to resolve this issue.",
+  "liveSyncReplicator.oneShotSyncBegin": "OneShot Sync begin... (${syncMode})",
+  "liveSyncReplicator.remoteDbCorrupted": "Remote database is newer or corrupted, make sure to latest version of self-hosted-livesync installed",
+  "liveSyncReplicator.remoteDbCreatedOrConnected": "Remote Database Created or Connected",
+  "liveSyncReplicator.remoteDbDestroyError": "Something happened on Remote Database Destroy:",
+  "liveSyncReplicator.remoteDbDestroyed": "Remote Database Destroyed",
+  "liveSyncReplicator.remoteDbMarkedResolved": "Remote database has been marked resolved.",
+  "liveSyncReplicator.replicationClosed": "Replication closed",
+  "liveSyncReplicator.replicationInProgress": "Replication is already in progress",
+  "liveSyncReplicator.retryLowerBatchSize": "Retry with lower batch size:${batch_size}/${batches_limit}",
+  "liveSyncReplicator.unlockRemoteDb": "Unlock remote database to prevent data corruption",
+  "moduleCheckRemoteSize.logCheckingStorageSizes": "Checking storage sizes",
+  "moduleCheckRemoteSize.logCurrentStorageSize": "Remote storage size: ${measuredSize}",
+  "moduleCheckRemoteSize.logExceededWarning": "Remote storage size: ${measuredSize} exceeded ${notifySize}",
+  "moduleCheckRemoteSize.logThresholdEnlarged": "Threshold has been enlarged to ${size}MB",
+  "moduleCheckRemoteSize.msgConfirmRebuild": "This may take a bit of a long time. Do you really want to rebuild everything now?",
+  "moduleCheckRemoteSize.msgDatabaseGrowing": "**Your database is getting larger!** But do not worry, we can address it now. The time before running out of space on the remote storage.\n\n| Measured size | Configured size |\n| --- | --- |\n| ${estimatedSize} | ${maxSize} |\n\n> [!MORE]-\n> If you have been using it for many years, there may be unreferenced chunks - that is, garbage - accumulating in the database. Therefore, we recommend rebuilding everything. It will probably become much smaller.\n>\n> If the volume of your vault is simply increasing, it is better to rebuild everything after organizing the files. Self-hosted LiveSync does not delete the actual data even if you delete it to speed up the process. It is roughly [documented](https://github.com/vrtmrz/obsidian-livesync/blob/main/docs/tech_info.md).\n>\n> If you don't mind the increase, you can increase the notification limit by 100MB. This is the case if you are running it on your own server. However, it is better to rebuild everything from time to time.\n>\n\n> [!WARNING]\n> If you perform rebuild everything, make sure all devices are synchronised. The plug-in will merge as much as possible, though.\n",
+  "moduleCheckRemoteSize.msgSetDBCapacity": "We can set a maximum database capacity warning, **to take action before running out of space on the remote storage**.\nDo you want to enable this?\n\n> [!MORE]-\n> - 0: Do not warn about storage size.\n>   This is recommended if you have enough space on the remote storage especially you have self-hosted. And you can check the storage size and rebuild manually.\n> - 800: Warn if the remote storage size exceeds 800MB.\n>   This is recommended if you are using fly.io with 1GB limit or IBM Cloudant.\n> - 2000: Warn if the remote storage size exceeds 2GB.\n\nIf we have reached the limit, we will be asked to enlarge the limit step by step.\n",
+  "moduleCheckRemoteSize.noticeExceeded": "Remote storage size is ${measuredSize}, above the configured ${notifySize} notification threshold. {HERE}",
+  "moduleCheckRemoteSize.noticeNotConfigured": "Remote storage size notifications are not configured. {HERE}",
+  "moduleCheckRemoteSize.option2GB": "2GB (Standard)",
+  "moduleCheckRemoteSize.option800MB": "800MB (Cloudant, fly.io)",
+  "moduleCheckRemoteSize.optionAskMeLater": "Ask me later",
+  "moduleCheckRemoteSize.optionDismiss": "Dismiss",
+  "moduleCheckRemoteSize.optionIncreaseLimit": "increase to ${newMax}MB",
+  "moduleCheckRemoteSize.optionNoWarn": "No, never warn please",
+  "moduleCheckRemoteSize.optionRebuildAll": "Rebuild Everything Now",
+  "moduleCheckRemoteSize.optionReview": "Review options",
+  "moduleCheckRemoteSize.titleDatabaseSizeLimitExceeded": "Remote storage size exceeded the limit",
+  "moduleCheckRemoteSize.titleDatabaseSizeNotify": "Setting up database size notification",
+  "moduleLiveSyncMain.logUnloadingPlugin": "Unloading plugin...",
+  "moduleLocalDatabase.logWaitingForReady": "Waiting for ready...",
+  password: "password",
+  username: "username",
+  "xxhash64 is the current default.": "xxhash64 is the current default."
+};
+export {
+  commonlibEnglishMessages
+};

package/dist/services/base/MessageTranslator.d.ts

@@ -1,6 +1,9 @@
+import { type CommonlibMessageKey } from "./CommonlibMessages.js";
 /** Placeholder values substituted by a host translator. */
 export type TranslationParameters = Readonly<Record<string, string>>;
 /** A message translator supplied by the host for one service context. */
-export type MessageTranslator = <TKey extends string>(key: TKey, params?: TranslationParameters) => string;
-/** Default translator for headless clients which returns the message key unchanged. */
+export type MessageTranslator<TKey extends string = CommonlibMessageKey> = (key: TKey, params?: TranslationParameters) => string;
+/** Default translator which renders Commonlib's canonical English messages. */
+export declare const englishMessageTranslator: MessageTranslator;
+/** Compatibility translator for hosts which intentionally render raw message keys. */
 export declare const passthroughMessageTranslator: MessageTranslator;

package/dist/services/base/MessageTranslator.js

@@ -1,4 +1,25 @@
+import { commonlibEnglishMessages } from "./CommonlibMessages.js";
+function resolveEnglishMessage(key, seen = /* @__PURE__ */ new Set()) {
+  if (seen.has(key)) return key;
+  seen.add(key);
+  const message = commonlibEnglishMessages[key] ?? key;
+  return message.replace(/%\{([^}]+)\}/g, (_token, referencedKey) => {
+    const directKey = referencedKey;
+    const keywordKey = `K.${referencedKey}`;
+    if (directKey in commonlibEnglishMessages) return resolveEnglishMessage(directKey, new Set(seen));
+    if (keywordKey in commonlibEnglishMessages) return resolveEnglishMessage(keywordKey, new Set(seen));
+    return `%{${referencedKey}}`;
+  });
+}
+const englishMessageTranslator = (key, params = {}) => {
+  let message = resolveEnglishMessage(key);
+  for (const [placeholder, value] of Object.entries(params)) {
+    message = message.replaceAll(`\${${placeholder}}`, value);
+  }
+  return message;
+};
 const passthroughMessageTranslator = (key) => key;
 export {
+  englishMessageTranslator,
   passthroughMessageTranslator
 };

package/dist/services/base/ServiceBase.d.ts

@@ -4,7 +4,7 @@ import { type MessageTranslator } from "./MessageTranslator.js";
 export interface ServiceContextOptions {
     /** An isolated event channel. A new channel is created when omitted. */
     events?: LiveSyncEventHub;
-    /** Host-provided message translation. Keys pass through unchanged when omitted. */
+    /** Optional host-provided translation. Canonical English is used when omitted. */
     translate?: MessageTranslator;
 }
 /**

package/dist/services/base/ServiceBase.js

@@ -1,13 +1,11 @@
 import { createLiveSyncEventHub } from "../../hub/hub.js";
-import {
-  passthroughMessageTranslator
-} from "./MessageTranslator.js";
+import { englishMessageTranslator } from "./MessageTranslator.js";
 class ServiceContext {
   events;
   translate;
   constructor(options = {}) {
     this.events = options.events ?? createLiveSyncEventHub();
-    this.translate = options.translate ?? passthroughMessageTranslator;
+    this.translate = options.translate ?? englishMessageTranslator;
   }
 }
 function createServiceContext(options = {}) {

package/dist/services/base/SettingService.d.ts

@@ -4,10 +4,13 @@ import { ServiceBase, type ServiceContext } from "./ServiceBase.js";
 import { createInstanceLogFunction } from "../lib/logUtils.js";
 export interface SettingServiceDependencies {
     APIService: IAPIService;
+    /** Optional host hook for applying the loaded display language to its catalogue. */
+    onDisplayLanguageChanged?: (language: ObsidianLiveSyncSettings["displayLanguage"]) => void;
 }
 export declare abstract class SettingService<T extends ServiceContext = ServiceContext> extends ServiceBase<T> implements ISettingService {
     deviceAndVaultName: string;
     protected APIService: IAPIService;
+    private readonly onDisplayLanguageChanged?;
     protected abstract setItem(key: string, value: string): void;
     protected abstract getItem(key: string): string;
     protected abstract deleteItem(key: string): void;

package/dist/services/base/SettingService.js

@@ -12,7 +12,6 @@ import { ServiceBase } from "./ServiceBase.js";
 import { createInstanceLogFunction } from "../lib/logUtils.js";
 import { isCloudantURI } from "../../pouchdb/utils_couchdb.js";
 import { decryptString, encryptString } from "../../encryption/stringEncryption.js";
-import { setLang } from "../../common/i18n.js";
 import {
   activateP2PRemoteConfiguration,
   activateRemoteConfiguration,
@@ -23,6 +22,7 @@ import { ConnectionStringParser } from "../../common/ConnectionString.js";
 class SettingService extends ServiceBase {
   deviceAndVaultName = "";
   APIService;
+  onDisplayLanguageChanged;
   _settings;
   get settings() {
     return this._settings;
@@ -39,6 +39,7 @@ class SettingService extends ServiceBase {
   constructor(context, dependencies) {
     super(context);
     this.APIService = dependencies.APIService;
+    this.onDisplayLanguageChanged = dependencies.onDisplayLanguageChanged;
     this._log = createInstanceLogFunction("SettingService", this.APIService);
   }
   /**
@@ -475,7 +476,7 @@ class SettingService extends ServiceBase {
       }
     }
     this.settings = await this.decryptSettings(settings);
-    setLang(this.settings.displayLanguage);
+    this.onDisplayLanguageChanged?.(this.settings.displayLanguage);
     await this.adjustSettings(this.settings);
     const migratedLegacyRemoteConfigurations = !hadRemoteConfigurations && Object.keys(this.settings.remoteConfigurations ?? {}).length > 0;
     const migratedP2PActiveRemoteConfiguration = migratedLegacyRemoteConfigurations && migrateP2PActiveRemoteConfigurationIdInPlace(this.settings);

package/docs/development.md

@@ -6,9 +6,11 @@ This document is for Commonlib developers. Package consumers should begin with t
 
 The source tree is larger than the supported package surface. Consumers may import only paths in the generated package export map:
 
-- `src/index.ts`, `src/context.ts`, `src/settings.ts`, `src/remoteConfigurations.ts`, `src/platform/browser/index.ts`, `src/platform/node/index.ts`, and `src/rpc/index.ts` define the focused entries;
+- `src/index.ts`, `src/context.ts`, `src/settings.ts`, `src/remoteConfigurations.ts`, `src/platform/browser/index.ts`, and `src/platform/node/index.ts` define the focused entries;
+- `src/rpc/index.ts` defines a transitional entry for the existing LiveSync P2P composition, not a stable Commonlib 1.0 contract;
 - `_tools/build-package.mjs` compiles those entries and creates the publishable manifest under `.package`;
 - `docs/migration/downstream-imports.json` is the reviewed inventory from which explicit `compat/*` exports are generated;
+- `docs/migration/compatibility-classification.json` assigns every inventoried compatibility path to one reviewed owner and migration policy, with a boundary test preventing omissions and duplicate classifications;
 - colocated `*.unit.spec.ts` and `*.unit.test.ts` files exercise implementation and result contracts; and
 - colocated `*.integration.spec.ts` files, `test/integration`, and the integration runner own checks against disposable CouchDB and S3-compatible services.
 
@@ -57,7 +59,7 @@ The multiple-remote profile contract has focused unit coverage in `src/serviceFe
 
 ### P2P composition ownership
 
-`useP2PReplicatorFeature` is the sole owner of the active `LiveSyncTrysteroReplicator` and its lifecycle bindings. It creates or replaces the outer replicator when `ReplicatorService` requests one, closes the previous instance before replacement, and returns a stable result object whose `replicator` property resolves the current instance.
+`useP2PReplicatorFeature` is the sole owner of the active `LiveSyncTrysteroReplicator` and its lifecycle bindings. It creates or replaces the outer replicator when `ReplicatorService` requests one, closes the previous instance before replacement, shares an in-flight replacement between concurrent callers, and returns a stable result object whose `replicator` property resolves the current instance.
 
 Consumers must preserve that result object and read `result.replicator` at the point of use. Do not destructure the property into a command, event handler, view, or other long-lived closure: a database reinitialisation or remote-type transition can close and replace the captured instance, and calling `open()` on that obsolete outer object can create a second connection outside the active service state.
 
@@ -73,7 +75,11 @@ The physical room, WebRTC peer, and relay-socket boundaries are documented in [P
 
 Self-hosted LiveSync remains the principal downstream consumer. A Commonlib change is not ready for publication until the exact packed artefact has also passed the applicable LiveSync type checks, unit and integration tests, application builds, CLI E2E, and focused real-Obsidian E2E.
 
-The package publishes the generated production language catalogue as an ordinary ESM module. It does not duplicate that catalogue inside `dist/common/i18n.js`; the final application bundler remains responsible for composing the catalogue for environments such as Obsidian. Source development continues to use the JSON-derived development catalogue.
+Commonlib owner tests exercise the real implementation behind each focused result and lifecycle contract. A consumer-owned unit test may inject the smallest structural capability it uses and provide its own fake or spy when that current test needs isolation. Do not publish Vitest-specific mocks, expose private service constructors, or refactor a production boundary merely to create possible future test infrastructure. Mock and spy helpers are not a prerequisite for the LiveSync 1.0 package-boundary work; add them only with the consumer test which requires them, or after that release work.
+
+Prefer an object or callback injected at the host composition boundary over replacing an ESM module namespace. If a proposed focused API would require global mutation, import-order coupling, hidden construction, or private nominal types to substitute later, stop and review the production design before stabilising it. Exact-package downstream checks and focused real-runtime E2E remain responsible for proving the real package and host composition together.
+
+Commonlib publishes the typed English messages which it owns and uses them when a host does not provide a translator. A host may inject a translator through `ServiceContext`; the full multilingual catalogue and language-selection state belong to that host and are not part of the Commonlib package.
 
 Keep [the maintained-host evidence](proven-in-use.md) aligned with the downstream source and gates. If a host no longer consumes a focused entry, a test is retired, or a compatibility path receives a reviewed replacement, update the consumer-facing account as part of the same maintenance rather than leaving historical adoption as a current support claim.
 
@@ -89,15 +95,11 @@ This command requires Docker Compose, creates only test credentials and data, an
 
 To test services that are already running, use `npm run test:integration`. The runner accepts `hostname`, `username`, and `password` for CouchDB, and `minioEndpoint`, `accessKey`, `secretKey`, and `bucketName` for S3-compatible storage. Without overrides, it uses the endpoints and test credentials from the managed Compose environment. The selected MinIO bucket must already exist when services are not managed by the runner.
 
-## Translation catalogue
-
-Human-edited translations live under `src/common/messagesYAML`. Regenerate derived JSON and TypeScript resources with:
+## Messages and translation
 
-```bash
-npm run i18n:bake
-```
+`src/services/base/CommonlibMessages.ts` is the canonical English definition and key type for messages requested by Commonlib. Keep a meaningful English value for every symbolic key. Hosts may translate that typed key set, but translation is optional and omission must remain safe for users.
 
-The generated catalogue remains an optional dependency surface. Core and context imports must not load it.
+Application language catalogues and their generation tools belong to the application repository. Do not add a process-global language selection or a complete application catalogue to Commonlib.
 
 ## Public API documentation
 
@@ -105,18 +107,29 @@ New reviewed public entry points require TSDoc describing ownership, lifecycle,
 
 Generated API reference is deferred until the compatibility export surface has been narrowed. Generating documentation for every current `compat/*` path would make migration-only implementation paths look like stable public API.
 
-TODO: introduce generated API reference for a reviewed allow-list of public entry points once the high-level client façade and its lifecycle contract have been accepted.
+The proposed generated-reference allow-list is deliberately entry-based:
+
+- include `/context`, `/browser`, `/node`, `/remote-configurations`, and `/settings`;
+- exclude the root entry until `createLiveSyncFileClient` replaces `DirectFileManipulator` after the LiveSync 1.0 work;
+- leave possible `/setup-uri` and `/database-version` entries for later review rather than creating them to clean up imports before LiveSync 1.0; and
+- exclude `/rpc`, every `compat/*` path, and the metadata-only `package.json` export.
+
+Generate reference only for this reviewed current allow-list. Future entries require their own accepted result and lifecycle contracts before joining it.
 
 ## Open 1.0 documentation decisions
 
 Resolve these questions before describing the corresponding behaviour as stable:
 
-- define the high-level client façade and the readiness, enumeration, watch, failure, conflict, concurrency, and disposal semantics currently left open by `DirectFileManipulator`;
-- classify the selected Node built-in convenience exports as either supported platform contracts or migration-only compatibility exports;
-- decide whether the RPC entry and its draft wire protocol belong to the Commonlib 1.0 contract, remain experimental, or move to a separately versioned package;
 - classify compatibility paths whose owner or migration destination is still unclear, and remove obsolete paths rather than preserving the source layout; and
 - introduce generated API reference only for the reviewed public allow-list, with TSDoc coverage for ownership, lifecycle, errors, platform constraints, and disposal.
 
+The platform and RPC ownership decisions are accepted:
+
+- `/node` and `/browser` are supported platform façades. They deliberately hide platform-specific imports, adapters, and review exceptions behind package-owned boundaries. The selected Node built-in re-exports are part of that boundary; package tests must continue to prove that browser-capable entries do not reach Node-only code.
+- `/rpc` is transitional and is not part of the stable Commonlib 1.0 contract. Keep it only while the maintained LiveSync P2P composition requires the existing implementation. The RPC core, transport integration, wire protocol, and PouchDB bridge are planned for an independently owned rewrite in Fancy Kit; do not encourage new Commonlib consumers to adopt the current entry.
+- The high-level composition target is a narrow asynchronous `createLiveSyncFileClient` factory, not a general Service Hub factory. It must keep the context, service graph, database implementation, protocol setup, watches, reconnect work, and shutdown order private. It resolves only after readiness and returns a small file façade with `list`, `get`, `put`, `delete`, `watch`, and `close`. Full Obsidian, CLI, and browser applications retain host-specific composition because they own UI, persistence, permissions, storage events, and process policy.
+- `DirectFileManipulator` is a migration source for that file client rather than the stable target contract. Do not carry its fire-and-forget constructor initialisation, exposed service graph and database documents, incomplete enumeration, implicit watch retry, or deprecated settings options into the new public API. Define the exact result, conflict, concurrency, watch checkpoint, retry, and error semantics only after the LiveSync 1.0 work rather than making that future client a release gate.
+
 ## Compatibility exports
 
 The package build records each compatibility path explicitly. Do not add a wildcard export. A new compatibility path requires a real downstream import, a packed-consumer or downstream test, and a migration plan towards a focused public entry or the owning package.
@@ -129,6 +142,6 @@ npm run update:downstream-import-inventory -- --downstream /path/to/obsidian-liv
 
 The command recognises both the former `@lib/*` source aliases and current `@vrtmrz/livesync-commonlib/compat/*` package imports. It ignores focused package entries. Review the resulting paths and recorded downstream commit before accepting them. Regenerate the export map only for a new package version: do not change the contents represented by an immutable published version.
 
-TODO: classify and document compatibility paths whose purpose is still unclear before stabilising the first public release. Remove obsolete paths rather than documenting accidental layout as API.
+The classification in `docs/migration/compatibility-classification.json` is accepted for LiveSync 1.0 planning. A destination still requires its own result and lifecycle contract before it becomes a stable public entry. Remove obsolete paths rather than documenting accidental layout as API.
 
 Release preparation and staged-publication checks are documented in [the maintainer runbook](releasing.md).

package/docs/p2p-transport-lifecycle.md

@@ -31,10 +31,18 @@ It is therefore a logical LiveSync disconnection and a physical signalling-serve
 
 ## Reconnection and replacement
 
-An explicit open resumes Trystero relay reconnection before joining the configured room. Settings application may change the relay URLs, room ID, passphrase, or TURN configuration, so the owning service closes and discards the former LiveSync instance before constructing the replacement. No fixed close-to-open delay is required: lifecycle operations are serialised, and peer readiness is observed through discovery.
+An explicit open resumes Trystero relay reconnection before joining the configured room. Settings application may change the relay URLs, room ID, passphrase, or TURN configuration, so the owning service closes and discards the former LiveSync instance before constructing the replacement. Concurrent replacement requests share the same in-flight replacement and receive the same new owner. No fixed close-to-open delay is required: lifecycle operations are serialised, and peer readiness is observed through discovery.
+
+Saving settings with P2P or automatic start disabled always requests `close()`, even when the room has not started serving. This cancels an in-flight open through the same lifecycle queue, so a connection cannot appear after the disabling setting has been applied.
 
 Do not replace a relay socket's `onclose` handler. Trystero 0.25 shares relay clients by URL and uses its own handler to retire and recreate them. Use the exported pause and resume functions around explicit disconnection instead.
 
+## First-device and additional-device setup
+
+P2P has no central remote database. A first-device rebuild initialises the local database, then returns without attempting to lock, reset, or seed a remote database.
+
+An additional-device Fetch uses one explicit peer-selection pass. The selected peer supplies the complete finite replication from the beginning, after which the rebuild service resumes database and Vault reflection. The generic second convergence pass remains appropriate for central remote types, but must not be applied to P2P: an injected Obsidian rebuild UI would otherwise ask the user to select the same peer twice and leave reflection suspended while the second dialogue waits.
+
 ## Unsupported forced close
 
 Do not close the raw values returned by `room.getPeers()`. Both closing them before room departure and closing captured values after departure have prevented the same peer from being rediscovered within 60 seconds in the real-transport replacement test.
@@ -43,10 +51,12 @@ Commonlib consequently does not expose a forced physical-disconnection command.
 
 ## Verification
 
-Maintain all three boundaries when this lifecycle changes:
+Maintain all five boundaries when this lifecycle changes:
 
-- Commonlib unit tests must prove that normal close leaves the room without directly closing Trystero-owned peers, and that overlapping open and close requests leave one current owner;
-- the Self-hosted LiveSync Compose P2P lifecycle test must replace a current replicator, rediscover the same real peer, perform bidirectional RPC, and verify transferred content from a separate process; and
+- Commonlib unit tests must prove that normal close leaves the room without directly closing Trystero-owned peers, that disabling settings cancel a pending open, and that concurrent replacement requests leave one current owner;
+- Commonlib rebuild tests must prove that first-device P2P initialisation does not reset a remote database and that an additional-device P2P Fetch performs one explicit peer-selection pass before resuming reflection;
+- the Self-hosted LiveSync Compose P2P lifecycle test must replace a current replicator, rediscover the same real peer, perform bidirectional RPC, and verify transferred content from a separate process;
+- the Self-hosted LiveSync real-Obsidian P2P Setup URI workflow must generate the second-device URI on the first device, accept both peer directions visibly, and verify a two-way note round-trip; and
 - the relay-disconnect test must observe the original WebSocket reach `CLOSED`, remain closed while reconnection is paused, and be replaced after reconnection resumes.
 
 The corresponding product decision and rejected alternatives are recorded in Self-hosted LiveSync's P2P room and transport lifecycle ADR.