The issue was measurement trust
Rev A could gather data, but the workflow around that data was too fragile. Test captures lived in separate places and there was no dependable landing zone for the supporting files.
Rev B is as much about documentation plumbing as it is about electronics.
Hardware and docs changed together
The board update improved connector robustness and rail visibility, while the site structure now gives those changes a clear home: product note, project summary, and artifact folders attached to the same slug.
The lesson is repeatability
If a future engineer cannot retrace the reasoning from revision note to schematic to firmware tag, the project is still under-documented. The site rebuild is meant to remove that gap.