Going to /blueprint-tracker for the initial page load will cause the data to be fetched while the blueprint tracker is already loaded. Once it is fetched, it is not reactively displayed in blueprint tracker.
However, going to /blueprint-tracker with a user in the route query is fine.