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.
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.
Use the shared Node adapter and retain one comparison policy throughout
each CLI scan. Propagate permission and I/O failures instead of reporting
absence or a successful partial scan.
Use shared namespace and comparison helpers in Obsidian while preserving
its Vault APIs and alias policy. Cover native spelling and host filename
compatibility, and document the dependency and integration boundaries.
The packaged xxHash export has no resolved type declaration. Check the
factory, engine, and bigint result at the benchmark boundary, and treat
CLI fixture rejection values as unknown.
Add regression cases for invalid engines and hash results while retaining
the real-engine and initialisation-count assertions.
Split logical Vault paths on '/' on every platform so that internal database
files and hidden path segments remain excluded when the database and Vault
share a directory.
Cover POSIX and Windows host separators through the real CLI bootstrap
filter, preserving the omitted-Vault-path E2E scenario.
Run the CLI subprocess suites and benchmark tools as native TypeScript with
node:test, and move them under test/e2e-cli.
Update CI and Compose runners, run local smoke tests on Linux, macOS, and
Windows, and collect source-mapped CLI coverage with c8.
Align release metadata and audited development dependencies, and consolidate
release notes with contributor acknowledgements.
Cover upgrades, start-up integrity, text reflection, and interrupted saves
in real Obsidian. Document the accepted provenance persistence interval:
identical replayed content converges, safe merge retains the later remote
content and ancestry, and overlapping edits remain available for review.
vorotamoroz