From 900cc89564275e9647d8ea45cb099a2e24b308ff Mon Sep 17 00:00:00 2001 From: David Snelling Date: Tue, 18 Aug 2026 13:18:55 -0700 Subject: [PATCH] =?UTF-8?q?docs(releases):=20the=2010.3.1=20consumer=20ent?= =?UTF-8?q?ry=20=E2=80=94=20the=20fold=20that=20behaves?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- RELEASES.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/RELEASES.md b/RELEASES.md index 49876f5a..cc0272c3 100644 --- a/RELEASES.md +++ b/RELEASES.md @@ -31,6 +31,33 @@ is sometimes cited as a 7.x removal — those methods never existed on 7.x; the --- +## v10.3.1 — 2026-08-18 (the fold that behaves) + +Three recovery cures from one production first-boot incident (a brain's first +process restart after a live storage-authority flip looked hung and was +restarted three times mid-recovery). **Adopt this version before flipping +brains with existing history** — it is the intended adoption target for +fleets moving to the crash-safe authority. + +- **Recovery streams.** The boot-time log fold now consumes the generation + log one segment-batch at a time — memory stays bounded at one segment for + any log size. Previously it materialized every fact into one array, which + on a ~7k-fact log produced multi-GB allocation pressure and a process that + looked wedged while it worked. +- **Recovery narrates.** The fold announces itself before the work begins + ("recovery fold beginning — do not restart, the fold is finite") and prints + progress every thousand facts. A visible fold gets to finish; a silent one + gets killed by a well-meaning operator, and each kill makes the next boot + pay the whole fold again. +- **Bounded recovery from the flip itself.** Adopting the log authority now + founds the recovery checkpoint at the moment of the flip (one paged + canonical sync, bounded memory, then the stamp) — so even the FIRST unclean + shutdown after a flip replays only the log's tail. Previously the bound + could only establish itself at a completed crash recovery, which is exactly + the recovery the incident kept interrupting. + +--- + ## v10.3.0 — 2026-08-18 (the trust-and-provenance release) Four consumer-driven cures. Pairs with the same native accelerator line