1.3.0

Added

• Follow heading renames (Links, Settings). Obsidian repairs links when a file is renamed, but not when a heading is: edit ## Projectile to ## Projectiles and every [[Guide#Projectile]] in the vault is quietly broken. The plugin is the one thing that can notice, since it already keeps every heading it indexed — rename one and it offers to retarget the links pointing at it, through the same preview the other bulk actions use. The new Follow heading renames setting chooses between offering it, opening the preview straight away, and doing nothing. The link's target is what changes; the wording around it is your prose and is left alone, unless it repeated the old heading word for word.
• Find heading links that no longer land (Commands). For a heading renamed while the plugin was off, when which heading replaced which can no longer be told: a note listing every link that names a heading its source file no longer has, so the reader decides rather than the plugin guessing.
• A breadcrumb for every heading (Matching). The Which one? picker and the autocomplete popup show where a heading sits — its file and the headings enclosing it, as Guide › Combat › Spawn — so two same-named headings are told apart by their place, not only by their file.
• A warning for headings repeated inside one file (Indexing). Only the first of them can be linked, since File#Heading cannot say which. Rebuilding the index says how many there are and names them in the console.
• A public API (Integrations). A small read-only surface at app.plugins.plugins['heading-linker'].api for other plugins and DataviewJS: the indexed headings, what a label or alias resolves to, the morphology keys and base form of a word, matches in arbitrary text, a per-heading usage report and the frequent words that have no heading yet. The scans behind it are cached per note, so a second call only re-reads what changed.

Fixed

• The status bar counted a heading link only when it was written the way the plugin writes it. Link resolution now goes through one helper, so a link written by hand — or completed by Obsidian with a path — is counted the same as the plugin's own.

Internal

• Notes are rewritten through vault.process rather than a separate read and write, as Obsidian's guidelines ask: the read and the write are one step, so a note edited in between cannot be clobbered.
• The wikilink grammar, the usage and candidate scans, the report writer and the settings-tab redraw all moved to the shared module the four linkers draw on.