Repository navigation
v5.5 — The One Where It Stops Blaming You for an Edit You Never Made
What this release is about
The ready-made skills your brain came with start catching up again — and it stops telling you that you customized a file you never opened.
Your second brain ships with ready-made capabilities: tidying your notes, folding recent captures into your pages, moving between the different spheres of your working life. They are plain Markdown, yours to read and tweak, and when you update the engine the ones you never touched are brought up to date while the ones you tailored are left exactly as you wrote them.
On a brain that has crossed several releases, the first half of that quietly stopped happening. The newer version of a skill landed beside the old one as a .new file — so nothing was lost and nothing was hidden — but the report explained it with a sentence that was not true: "your customized lint skill was kept exactly as you wrote it", about a file you had never opened. From then on, every release arrived as homework: a list of files to take or ignore, for changes you never made.
The old design was the careful one, and it is worth saying why. To know whether a skill is still the one it shipped, your brain compared it against its own copy of what it had been given — which is exactly right for as long as the two move together. One update that advanced one copy and not the other made them disagree permanently, and from then on your brain genuinely could not tell "we shipped this" from "you wrote this". Faced with that doubt it did the protective thing, every single time. The judgement was sound; what it was judging against had drifted.
So this release gives it a better thing to judge against: what the engine really published, version by version, going back to v3.6.0. A skill nobody edited is recognised as ours and simply comes up to date — however many releases it sat out — and customized goes back to meaning what you would expect it to mean.
What you get
When you update your brain (/update-engine)
- 🔄 The ready-made skills catch up, however far behind they are. A brain installed a year ago and updated since finds
/lint,/consolidate,/switchand their siblings simply arriving at their current version, instead of being handed a pile of.newfiles to sort out by hand. - 🏷️ "Customized" goes back to meaning you. The update report only calls a file yours when your bytes are genuinely not ours — so the summary you read after an update describes your brain rather than a bookkeeping accident.
- 🛡️ A skill you really did tailor is protected exactly as before. Your version stands, what shipped since is merged around your words where they do not collide, and where they do you are asked which of the three you want. Nothing about that changed, and it is now proven against the published record rather than against a copy that could drift.
When you ask your brain to tidy your notes (/lint)
- 🩹 A note whose header your brain cannot read is put straight — and it says so. This is the one piece of untidiness that costs you answers rather than neatness: until it is fixed, that note keeps replying to your searches with what it said weeks ago. It is now repaired in the same batch as the other small tidy-ups, named in the summary rather than done silently.
When you rename one of your universes (/switch)
- 🔁 It tells you it is rebuilding the search, and starts — instead of asking your permission first. It costs minutes of computing and puts no note at risk, so the useful thing to hand you is the chance to stop it, not another question to answer.
When the note-watching had stopped (/rag)
- ⏱️ Same again when your searches need to catch up. Your brain says what it is about to re-read and how long it will take, then gets on with it. Saying nothing is a perfectly good answer.
What you have to do
Ask your brain to update its engine (/update-engine), then restart Claude once. Your notes, your keys, your constitution and the skills you genuinely tailored are left alone, as always.
Under the hood
The fix is a change of evidence, not of judgement. A delivered skill has no recorded provenance of its own; its stand-in was the brain's engine-skills/ copy, read at update time. That is a local artefact, and the two-pass update out of an old engine — the old-parent/new-child path no suite in this repo can observe (CONVENTIONS §10ter) — advances the staging copy without the installed one. After that they disagree for ever, and every release hands out another sidecar. The installed bytes are now recognised against scripts/lib/engine-fingerprints.json, the record of what each published version actually shipped, which the engine already used and already trusted for exactly this question.
🛑 The property that had to survive is that the proof is MEMBERSHIP, never arithmetic. A file may be marked as ours only because its bytes are recognised in that table — never because a checksum was computed from the bytes sitting on disk. The day that slips, a real edit reads as untouched and the next update pastes over it. Both poles are held by a test: a contaminated skill comes out as a refresh, and a genuinely edited one is still preserved with its sidecar with the table present, so the widening cannot quietly weaken the protection.
The table grew from 15 files and 104 byte-states to 24 and 129, and the reach is the point rather than the size: /lint now carries five published states back to v3.6.0, /consolidate six, /switch eight. Whichever version a brain is stuck on, the bytes it is holding are in a row — which is what makes the repair retroactive instead of merely correct from here on. A retired skill still cannot be healed back into recognition: the tombstone gate applies to both doors into the table, and that is why it was extracted rather than respelled.
The tidier design was rejected on purpose. Recording real provenance for delivered skills at install time is the cleaner mechanism and it heals nobody: a brain that has already diverged stays diverged, and diverged brains are the entire population this is about.
Three questions stopped being asked, and one of them had the wrong name in its own specification. The register and the issue both said "re-index after a universe is created or deleted". Read against the code, neither half exists: creating a universe re-indexes nothing and cannot (a universe one second old holds no notes), and deleting one already re-indexes behind a confirmation the owner types in their own terminal, which ADR 0045 freezes exactly where it is. Renaming is the operation the row actually describes, and it is the one that changed. Each of the three was also proven to land in the brain's own history — for three different reasons, which is why assuming it would have been wrong — and the end-of-turn sweep that catches the one running from a shell script turned out to be tested only on a brain wired to a remote. Push is opt-in, so that is most brains; it now has a test that fails if the sweep is put behind the remote.
The rehearsal, which is a release gate here (CONVENTIONS §10ter, mandatory because this release changes the update path by construction): run on a copy of a real brain sitting at v3.5.0 — the version the defect reproduces on — through the two-update sequence, with the contaminated state reproduced first and then repaired. A recent brain was used as the control, to prove the behaviour it must not change.
The figure this project published about itself is no longer owed. The v5.1.0 note told its readers, in as many words, that its mutation numbers were measured before a review whose fixes changed four of the files they covered. That debt is paid here, while the instrument was warm: the five files re-measured whole — 95.40 % to 99.43 % — plus lib/yaml-scalar.mjs, which that review added and which had never been measured at all, 80.39 % → 100.00 % on eleven new assertions and not one line of production changed. All ten of its survivors were the same shape: every test proved what gets quoted, none proved what does not — and quoting a value that needed no quotes rewrites the header of every note already written. Whole-file numbers answer a wider question than the ranges they replace, so the record says that rather than letting a lower number read as a regression.
The release's own quality gate — what this branch writes — is 103 mutants, 97.09 %, with the new recognition code and the line that wires it in at 100 %, no survivors; the three left are named equivalents, down to a regex anchor only a file path containing a line break could distinguish. It was paid wrongly the first time, and that is the more useful half of this paragraph. The gate asks for the score of what the branch wrote; it was recorded as paid on one file — the small one — because the list was written from the last commit instead of from the branch's own diff, so the five files that are the fix above had never been under a mutant. Re-run properly before the tag. Nothing had shipped and nothing was broken, but the shape is worth keeping: a gate that is skipped leaves nothing to notice, and this one left a green log saying it had run.