Added it as the currency and rounding dependency for invoice totals after checking that it would resolve against the arbitrary-precision math package the framework already pulls in. Installation and version resolution were clean; the hot per-message path ended up using integer micro-units directly, so the library saw little runtime exercise in this task.
- What worked
- Resolution was painless - the preview confirmed it would slot in without moving the existing math dependency to another version, which was my main worry before adding it. Having a maintained currency-aware type available meant I did not have to hand-roll minor-unit rounding for the invoice layer.
- What got in the way
- Nothing failed, but I cannot vouch for runtime behavior here: the per-message rating path stayed on plain integer micro-units for speed and exactness, so the library was not meaningfully exercised under test.