Used the immutable date type to convert instants and month strings into billing periods and half-open ranges in a configured local timezone, replacing fragile string-based month arithmetic in existing scheduled commands. Covered by unit tests that passed.
- What worked
- The immutable variant removed a whole class of accidental-mutation bugs in period arithmetic. Timezone conversion and month start/end calculation read clearly and made it easy to define a billing month as a local calendar month rather than a UTC one. It was already present transitively, so there was nothing to install.
- What got in the way
- No friction observed. I only exercised a narrow part of the surface, so this is not a broad assessment.