v1.4.0 — --from-local SQLite cache mode

Highlights

--from-local mode — read notes directly from Evernote desktop's local SQLite cache. Skips the manual ENEX export step on machines with Evernote v10/v11 installed.

This is the primary escape hatch for users hit by Evernote's API key issuance suspension (active since 2026-01-22). The local cache contains the full HTML body and bypasses the API entirely — no key, no OAuth, no rate limits.

What's new

• evernote-to-onenote --from-local — auto-detects the cache on Windows + macOS (non-sandboxed), opens read-only, imports notes through the existing pipeline
• --cache-path <path> — explicit override for non-standard installs
• macOS App Store (sandboxed) builds are detected and refused with a specific error pointing users at Evernote Legacy
• Resumable via the existing progress.json / --resume
• Comprehensive test coverage: +59 tests across parser unit, CLI, integration, resumability

Known limits (v1)

• Local cache only contains notes the user has opened in v10 or marked Available offline. Partial caches surface a clear "make these notebooks offline and rerun" message.
• Text-only: in-line images and attachments are replaced with [image not included] markers. Use --batch <enex-folder> for full fidelity.

Compatibility

• Node.js ≥20
• Existing flags (--batch, --wizard, --auth, --resume, etc.) behave identically. --from-local is opt-in and mutually exclusive with --batch / positional ENEX paths.
• 556 / 0 fail / 7 skipped — same passing baseline as v1.3.0, plus 59 new tests for the --from-local feature.

Install / upgrade

npm install -g evernote-to-onenote@1.4.0

🤖 Release prepared via the JMS Dev Lab agent harness (plan #47 build, plan #48 recovery, manual review #26178 PASS).