- Shipped
- July 22, 2026 at 5:55 PM UTC
- Author
- kamo
- Commit
- eccf870
RateCommitmentService refuses a lock whenever the priced result carries no lockPolicyVersionId ("lock-policy version is required"), and a result only carries one if the investor has a published lock-policy version. No UI could publish one, so rate locking was unreachable for every tenant — while the endpoint itself was already built, org-gated and superseding correctly. Only the client method and this form were missing. The form takes the offered lock periods as an ordered list because the FIRST becomes the default, so it deliberately does not sort them; entries that are not a positive whole number of days are dropped rather than sent as a bad lock term.