Start here
Overview
The short version: what the line-by-line port found, and the honest account of what Rust eliminated and what it did not.
Warm-up · findings published
freediag: C→Rust Port Findings
Porting a codebase line by line is an unusually thorough audit of it. Our warm-up resurrection of freediag, a dormant open-source OBD-II / K-line diagnostics stack, did more than recover its build and tests. The translation surfaced 70 confirmed findings in code that had been abandoned upstream for years, from memory-safety bugs reachable over five of six protocols down to comments that name their own logic backwards.
This is the full write-up: the argument, the evidence, the method, and the source it all cites. Start with the overview, or go straight to whichever face fits what you came for.
The report
Whitepaper
The full findings report as a readable, print-ready document, with every citation linked to the source it cites.
The evidence
Findings browser
All 70 findings, filterable by taxonomy and severity, searchable, each linked to the exact line in the frozen C tree.
The method
Timeline & cost
How the way of working changed over six days, plus the token economics of a roughly $2,771 multi-agent run.
The reference
Source browser
The frozen C reference tree: 86 files rendered line-addressable, with findings flagged in the gutter.
Wabi-sabi — beauty in the mend