Repository navigation
v5.5.1 — The One Where a Correction Stops Breaking Your Links
What this release is about
When your brain fixes a spelling for you, it no longer breaks the links in the note it is writing.
You can tell your brain a handful of things that are always true in a sphere of your working life: how a client's name is really spelled, and the versions of it you keep seeing in transcripts. From then on, when it writes a note for you, it puts the spelling right and says so. It deliberately leaves some passages alone — quoted words, code, the address inside a link — because correcting those would falsify them rather than tidy them.
The vault's own way of linking one note to another, [[like this]], was missing from that list. So if one of your note filenames happened to carry a spelling you had declared wrong, every link pointing at it was quietly rewritten, and the link then led nowhere. Worse, the message you saw said the spelling had been corrected: the breakage was announced as a success, in a note you had no reason to re-check.
It was reported from a real vault the day its owner declared their first spellings, and six links broke at once. Anyone who has declared spellings since v5.3.0 could be affected; anyone who has not declared any never was. And if you are in the first group, the repair costs you one sentence: ask your brain to tidy your notes and it puts those links back itself.
What you get
Every time your brain writes or edits a note
- 🔗 Links are left alone, always. A
[[link to another note]]is an address, like the address inside any other link, and your brain now treats it as one. The prose around it is still corrected, exactly as before. - 👀 It tells you what it left as written. Instead of claiming a correction it did not make, it says it left the passage alone, so you can decide whether it matters.
If you have already declared spellings, once after updating
- 🩹 Ask your brain to tidy your notes (
/lint) and it puts the broken links back, on its own. This release stops new ones from breaking; the ones already on disk are found by that check and repaired without a single question, because the note they should point at is right there and there is only one of it. Everything it writes is committed as it goes, so any repair is one undo away.
What you have to do
Ask your brain to update its engine (/update-engine), then restart Claude once. Your notes, your keys and your constitution are untouched, as always.
Under the hood
One entry in a list that could only ever subtract. The guard keeps a set of protected spans — frontmatter, fenced and inline code, a Markdown link's target, an autolink, blockquotes, quoted material in three typographies — and a declared spelling is never applied inside one. [[…]] now sits beside them. Every entry in that list removes text from rewriting and none can cause a rewrite, so the change cannot introduce a correction anywhere; it can only spare one.
The span is bounded to a single line, so a half-typed [[ cannot exempt every paragraph below it — a test says so, and it is the one that kills the mutant that would have removed that bound.
[[target|alias]] is spared whole, alias included, and that cost is deliberate. The second half of such a link is prose, and it stops being corrected. It is the reporter's own framing: a lost spelling costs a word, a rewritten target costs a link. Parsing the pipe to correct only the alias was rejected — it buys one word and adds a parser to a guard whose entire value is being dumb and total.
The truthful report needed no new surface. The write notice already had a sentence for what it deliberately left alone; the fix simply makes that sentence the one an owner sees in this case.
The exposure is three releases old, not one. It was reported on v5.5.0; the declared-spellings feature landed in v5.3.0, and every release since carried it.
Proof. Four tests on the guard — the reported repro, the alias, the prose on both sides of a link, an unclosed [[ — plus one end to end on the hook that rewrites the write, each of them red first for the right reason. Mutation pass on the changed file: 94.70 %, every mutant on the new span killed. The one killable survivor it surfaced was pre-existing and is now closed with no production change: nothing asserted that never : Axion, with the space before the colon that French typing puts there, yields a clean spelling.