One combined release for the approved issue follow-up.
Fixed
- Historical missing fuel readings no longer dilute consumption. Existing zero readings remain stored but need explicit confirmation; genuinely recorded zero readings remain valid. Unknown fill spans are excluded without affecting other valid spans. (#367)
- Fuel CSV and backup round-trips preserve unknown readings. Editing historical entries no longer substitutes today's Tessie reading.
- Unrecorded AdBlue readings do not affect diesel consumption.
- Fuel-feed failures preserve saved prices and report source availability. Ambiguous station matches and non-finite prices are rejected. (#371, partial)
Added
- Maintenance History preserves service snapshots across schedule edits/deletion and records completions without requiring an expense. Existing maintenance expenses also appear. (#370)
- Independent front/rear tire fittings, partial-pair replacement and continuous distance history. Existing fittings retain all-axles behavior. (#357)
- JSON and full backup/restore include maintenance events and axle-specific fitting periods, with duplicate and active-fitment conflict checks.
- New interface text translated into all 19 locales.
Upgrade notes
The additive migration preserves existing readings and the latest known maintenance snapshot. Previously overwritten maintenance details cannot be recovered. To confirm an old zero reading, edit the fuel log and enter 0; leave it blank if the reading is unknown.
Validation
All 1,455 Python tests passed on Python 3.12, along with the amd64/arm64 container build, migration and backup round-trip checks, translations, JavaScript behavior checks, and desktop/mobile browser checks.
Remaining work
#371 remains open for the authenticated government Fuel Finder API integration: its official contract could not be verified in this environment. Admin visibility policy (#360), external repair estimates (#373), and the unavailable harness cleanup (#355) also remain open.