We would only need the `eager_load!` in dev/test and could guard it as such -- but agreed that feels janky and would make development with guard pretty painful IMO. I think this approach is OK, even if it's just for now.