Add explicit stopped-Journal recovery to Obsidian and CLI

Offer a confirmation in Maintenance and the journal-skip command to skip
only the current stopped Journal and resume receipt. Keep Commonlib notices
visible on stderr during ordinary CLI use.

Document the missing-content risk and replay procedure, and cover
cancellation, stale failures, subsequent failures, and receipt with unit
and plain and encrypted CLI and Obsidian end-to-end tests.

Requires the Commonlib stopped-Journal recovery API. Adopt its exact
published package version before integrating this consumer change.

docs/design_docs_of_journalsync_2nd.md

@@ -1,5 +1,15 @@
 ## The design document of the Journal Replicator 2nd Edition
 
+Implementation note: the receive-failure correction and single-Journal skip
+action are unreleased. Their owning contract is Commonlib's
+[Journal receive failures and recovery](https://github.com/vrtmrz/livesync-commonlib/blob/main/docs/journal-receive-recovery.md).
+The receiver acknowledges successful processing, stops on failure by default,
+and retries from that Journal with the same database. Explicit skipping does
+not establish Vault reflection success. The host action names one stopped
+Journal and its failure stage, requires confirmation, and resumes receipt after
+skipping that Journal; the next failure still stops. The [settings reference](settings.md#skip-stopped-journal-and-resume)
+describes the host control and replay operation.
+
 ### Goal
 - Build a robust and memory-efficient replication foundation that decouples the physical storage layer by leveraging the Web Streams API.
 - Maintain strict compliance with the data consistency and replication protocols of CouchDB/PouchDB.