Mochion build logWhat broke, what got fixed, and why — dispatches from the workshop.https://mochion.xyz/log2026-07-08T00:00:00ZMochionhttps://mochion.xyz/Our own README was lying to ushttps://mochion.xyz/log#2026-07-08-readme-lying2026-07-08T00:00:00Z2026-07-08T00:00:00Z<div class="caption">
<span class="kicker">What broke</span>
We checked our own notes against the actual code and found the notes were wrong —
they described the machine doing <em>less</em> than it really does. That's how you
end up confidently telling people the wrong thing about your own project.
</div>
<div class="caption">
<span class="kicker">The fix</span>
Now there's one place that counts as the truth, and every claim gets checked against
the real code before it goes anywhere — including this site.
</div>A bunch of tests kept failing for a silly reasonhttps://mochion.xyz/log#2026-07-08-flaky-tests2026-07-08T00:00:00Z2026-07-08T00:00:00Z<div class="caption">
<span class="kicker">What broke</span>
Our automatic checks were quietly reaching out to the real exchange over the internet
while they ran. So they'd pass on a good day and fail whenever the connection hiccuped —
nothing to do with the actual code.
</div>
<div class="caption">
<span class="kicker">The fix (in progress)</span>
We're cutting that cord so the checks run completely offline and give the same answer
every time. Boring — but boring is exactly what you want here.
</div>