The logbook was showing the bike's distance, not the part's

A user sent me a list of things that looked wrong in his logbook. Most of them turned out to have the same cause.

"Removed chain at 9,474 km" was the bike's odometer reading, not the chain's. That chain had done 379 km. Every removal entry in the logbook showed the bike's total distance instead of the distance the part itself covered — overstating it by nearly 7,000 km on average across the entries I corrected. It now shows what the part actually did: the same figure the component's own page and History tab have always shown.

It shows in your units too. Miles if that's your setting, instead of km for everybody.

Entries sit on the date the thing happened, not the day you typed it in. Fit a part in January, log it in July, and the entry used to say July — and correcting the install date afterwards didn't move it. It does now, and 232 entries have moved to the date they belong on.

Parts you deleted are out of the timeline. Deleting a component used to leave its "Installed" and "Removed" entries behind, linking to nothing. Deleting a part now takes its entries with it.

No more duplicate entries for a single install or removal. The database prevents a second copy rather than relying on the app not to write one.

Editing an entry no longer offers to change its date or which part it points at. Both come from the installation record, and the entry links you straight to it — so a wrong date is fixed once, in one place, and the logbook follows.

Manual notes you've written are untouched by all of this.