Where did a missing link target go? Pure, no App: every question about which file a broken link most likely meant is answerable from a list of paths, the notes’ aliases and titles, and the vault’s git renames.
A rename is not recoverable from the link alone: a link to alpha/bravo/charlie/!.md says nothing about charlie having become delta. So every candidate carries the evidence that produced it, from outside the link, and the finder never picks one of several: a caller offers a one-click fix only when exactly one candidate exists.
| Function |
Description |
| getParentPath |
The parent folder of a vault path. |
| getPathMapping |
The part of a missing path that a candidate path replaced, found by dropping the path segments they end with in common. |
| Enum |
Description |
| BrokenLinkEvidenceKind |
The kind of evidence that makes a file a candidate for a missing link target. Candidates list evidence strongest first, in EVIDENCE_KIND_ORDER below. |