Import a module

Import the date utilities from the shared library at src/lib/date-utils.js and use the formatIso function in this module. Add the import statement at the top and replace the existing inline formatter with a call to formatIso(date).

Before I open the pull request, make the import and usage review-friendly: show the exact import line, explain whether formatIso is a named or default export, include the one-line reason we prefer the shared util over the inline formatter, and list any bundle or circular-dependency risks a reviewer should watch for.

I replaced an inline formatter with an import from src/lib/date-utils.js and bundle size increased by 30KB. I don't know whether formatIso pulls in heavy dependencies. Who on the team decides acceptable bundle growth, what do I ask them, and what immediate steps can I take to check whether the import pulls in extra modules so I can revert or optimize?

Across multiple features we keep importing small helpers instead of sharing a single lightweight utility, and bundle size creeps up. Where are we losing time and credibility — in local fixes, lack of bundle checks, or unclear ownership — and what policy and tooling change will stop this pattern without blocking everyday work?