Release · S385-S385
A critical save must finish its changes first
A critical save now refuses an unsupported asynchronous callback before accepting its draft. Previously, that callback could report success while changes made after a pause never reached the durable record. Refused drafts cannot change the live cache, and an ordinary synchronous save can still follow. If a previously accepted change becomes asynchronous during a conflict retry, its receipt reports that the intent remains retained rather than claiming a successful save. This correction covers both storage formats. Participant data controls and the independent retention-reserve readiness limits remain unchanged.