fix(links): resolve a relative link to a local file against the document

[PathGao]

5 / 5 of a stack. Base: #408. Related: #399 / #403.

The defect

[data](./data.csv) was handed to openUrl(anchor.href) — and anchor.href is what the DOM resolved against the webview origin, not a path on disk.

The two platforms then failed differently:

	origin	outcome
macOS / Linux	tauri://localhost	opener scope refuses it → ForbiddenUrl → the click does nothing, and since handleDocumentClick had no try/catch, an uncaught promise rejection
Windows	http://tauri.localhost	matches http://* → the browser really opens onto a dead link

The fix

resolveLocalFileLinkPath(rawHref, currentFile) reuses resolveExportImagePath from #363 for the entire scheme / drive-letter / UNC / query-suffix decision table, and adds the two rules a link needs that an image does not:

• //host/path is a web address — matching what the app's own getMarkdownLinkTarget already assumes, where the image resolver would read it as UNC;
• a relative link in an unsaved buffer resolves to nothing, rather than to something relative to the process working directory.

The branch sits after the markdown-target branch and before the openUrl fallback. Both OS calls are now inside try/catch with a toast, which removes the uncaught rejection and turns the silent macOS click into a visible failure.

The file still will not open yet

open_path is refused by the opener scope for every path — see #399, fixed in #403. Without that, this PR is still a strict improvement: no silent click, no uncaught rejection, and Windows no longer hands a dead link to the browser. With it, the link works.

The test here asserts only that opener:allow-open-path is still granted; it deliberately does not assert the scope's shape, so it does not prejudge whichever scope is chosen in #399.

Tests

scripts/localFileLinks.test.ts — the resolver tests run the real function.

Module absent (true state of #408)	suite fails to load
Module present, wiring reverted	3 red / 8 green
Final	11 / 11

npm run check   0 errors
npm test        469 / 469
cargo test      131 / 131

Not covered

• The OS call itself — blocked above.
• A link to a directory opens the folder. Reasonable, untested.
• No existence check before openPath; a missing file surfaces as the toast.

🤖 Generated with Claude Code