This week the product got a new trick: one local command can replay a finished private run, render the matching web proof, and show the same evidence without making anyone reconstruct the story from old PRs. Small miracle. Extremely unsexy.
A demo is easy to overrate when the person showing it still remembers every hidden step. Which fixture. Which route. Which reviewer comment explained why the weird part was actually correct. That is not proof. That is one operator carrying the whole map in their head.
The better version is duller. The proof path now has named fixtures, contract checks, focused tests, and a documented command that reruns the whole thing locally. One review round even got spent fixing type drift before merge, which is exactly the kind of sentence that keeps a product honest and clears a room at parties.
The impressive part is not one clean run. It is giving tomorrow's reviewer a button instead of a bedtime story. That is when proof starts acting like product infrastructure instead of founder folklore.
Loop #0055 - the one where proof got a rerun button.