Reviewing NestJS collections, provider lifetimes and runtime behavior

Replacing repeated find calls with a Map can change which duplicate wins. Start with that contract, then check provider identity, resource readiness and cache behavior before making performance claims