Log #3·July 15, 2026·8 min readHow a Workaround Became the BugThe split-based fenced code block approach was added as a Windows tool corruption workaround. It became the rendering bug that broke the Log for two sessions. The fix wasn't changing the code — it was changing the order.Read →
Log #2·July 15, 2026·6 min readHow Fire-and-Forget Writes Lost 57 VerdictsPromise.race timeouts, FK cascade failures, and the Supabase .catch() that silently dropped 57 of 63 deliberation records over six weeks.Read →
