v1.4.2 — fix --output-html broken image references

Bug fix (please upgrade from v1.4.0 / v1.4.1 if you use --output-html)

--output-html mode was emitting Microsoft Graph multipart-form placeholders (<img src=\"name:part1\" />) into the static HTML, leaving images and attachments broken in every browser, OneNote desktop, Notion, Obsidian, Apple Notes, etc. Discovered by running v1.4.1 against a real 2073-note Evernote export — 12% of output files had broken image refs.

What's fixed

• --output-html now writes each used resource to a sibling <noteName>.assets/<partN>.<ext> file (extension picked from MIME — covers common image, audio, video, and PDF types) and rewrites every src= and data= attribute to the relative path. Each .html + .assets pair is self-contained.
• The completion message no longer hardcodes "Your notes are in OneNote" — --output-html mode now reports the actual output folder + a brief drag-this-into-your-note-app hint.

Why this matters

--output-html is the no-Microsoft-account path through the tool. v1.4.0 and v1.4.1 silently produced broken HTML for any note with an inline image — making the tool unusable as an Evernote-to-anything converter for image-heavy users. v1.4.2 makes the output actually portable.

End-to-end verified

Tested against a real 87-note Moores Jewellers ENEX export:

• 24 .assets/ folders created (notes with attachments)
• All 87 .html files use relative paths — zero name: refs
• Sibling files are valid JPEGs (verified via file — JPEG image data, 1948x2567)
• Drops cleanly into note apps via folder drag

Compatibility

• Same flags, same exit codes, same progress.json format as v1.4.1
• --batch (Microsoft Graph) path unchanged
• Test suite: 559 pass / 0 fail / 7 skipped (+1 regression test on top of 1.4.1)

Install / upgrade

```sh
npm install -g evernote-to-onenote@1.4.2
```

🤖 Caught by integration testing on a real-world ENEX export.