fix: stop resolveMdLinks from breaking dataview links

[oleeskild]

Fixes #399

Problem

The resolveMdLinks filter shipped in 1.83.0 (#398) sent every dataview-generated link to /404. Two defects compounded:

1. convertMdHrefs' anchor regex (<a\s[^>]*?href=") also matched the tail of data-href=". DataviewJS output contains Obsidian-rendered anchors like <a data-href="Folder/Note.md" href="Folder/Note.md" class="internal-link">. The lazy [^>]*? ate data-, so the filter rewrote the data-href attribute to /404. The pre-existing dataview-js-links transform — which resolves these anchors from data-href — then read the clobbered value and marked every dataview link unresolved.
2. resolveVaultPath treated vault-root targets as note-relative. Dataview (and Obsidian's "absolute path in vault" link setting) emit targets like Folder/Note.md with no .//../ prefix. For notes in subfolders these were joined with the note's directory, the lookup missed, and the href became /404.

Fix

• The anchor regex now requires href to be a standalone attribute ((?:[^>]*?\s)?href="), so data-href is never rewritten.
• Link targets now produce ordered candidate interpretations: note-relative first (preserving fix: resolve markdown-style relative .md links to permalinks #398's behavior for genuinely relative links), vault-root as fallback. resolveMdLinks picks the first candidate that resolves to a real note; only when none do does it keep the /404 + is-unresolved handling. Graph extraction emits all candidates; ones matching no note are dropped as before.

Verification

• TDD: 6 new tests written failing first, whole suite green (309 tests).
• End-to-end build of the test garden with notes in subfolders covering dataviewjs-style anchors, vault-absolute .md links, and relative .md links — all resolve to real permalinks; genuinely dead links still get /404 with is-unresolved.

🤖 Generated with Claude Code