v0.8.0

--fix now applies the renames git recorded. It is the first time the fix writes anything beyond letter case, and the reason it may is the same as for case: the new name is read from git rather than guessed. The checks did not change.

What is rewritten. A missing path, or a markdown link, whose file git recorded as renamed becomes the name that exists now, written the way the citation was: from the root, from beside the note, with / or mdc: in front, or with its spaces as %20. The FIXED section names the commit on each rename, config/database.php -> config/db.php renamed in a3f21c9. Nothing else is touched: a link suggested from a name, a missing path with no history and a deleted file are left alone, since none of those has a value git can vouch for. The MCP server's prumo_fix does the same.

Formats. history.from on a missing path or a link, the path git was asked about; why and commit on each change --fix reports; schemaVersion 7. applyFixes and renameFixes are exported for the API, and applyCaseFixes stays as the older name of the same function.

Measurement. The renames themselves were measured in 0.7.2, fifteen of fifteen right. Applying them was rehearsed on the one public repository of that pass that was reorganising its plugins: one pass rewrote nineteen citations in three files, skipped none, and the run that followed reported no rename; the diff was read line by line before the clone was restored.

Suite 149 to 152, simulation 123 to 126.