- Shipped
- November 15, 2026 at 8:40 AM UTC
- Author
- Kamo
- Commit
- 8c6bd71
Undo of a first funding-limits version withdrew the version but left its concentration-limit rows, and the next publish carried them forward (carryConcentrationLimits fell back to the newest withdrawn version). - withdrawVersion(CapitalPolicy) now calls MlosConcentrationLimitService .retireWithdrawn: every limit row on the withdrawn version is removed; each limit that leaves the member's list is logged as a removal through the same audit tail as a delete (inside the undo's context it reads UNDONE, pointing at the publish taken back, so it shares that one-way undo). A limit that the version a same-day withdrawal reopens still carries stays; when its value differs, the row logs the value going back. - carryConcentrationLimits never carries from a withdrawn version. - Recent Changes: "Removed a concentration limit ... with the funding limits it sat in". Tests: MlosFundingLimitsAndPricingTest 9 (3 new), MlosPolicyWriteServiceTest 12, MlosSettingsFoundationsTest 18.