v0.79.10
August 8, 2026
Reliable versions, honest baselines. Creating flow and Process Map versions is now concurrency-proof — no more duplicate numbers, even under bursts — and past duplicates are cleaned up for good. Savings proposals declare when the design changed underneath them, with guided regeneration.
-
Improvement
Concurrency-proof versioning
Ten simultaneous new-version requests produce exactly ten distinct versions, for flows and Process Maps alike. Duplicate numbers inherited from the past are renumbered with a stable criterion — references and history realigned — and from today a database-level constraint makes them impossible. Under extreme contention the response is a clear retry invitation, never an opaque error.
-
Improvement
Baselines know when they are stale
Freezing a savings proposal computed on a design that has since changed is rejected with an explanation; the "Stale" badge flags it at a glance and regeneration is guided step by step. Drafts created before this update need regenerating: a proposal based on an outdated design cannot claim to be current.