For /browse/recipes, the nodes should still be viewed on www.drupal.org since they are not ready to really move over yet. I haven’t done anything special in the View to link to the legacy site. Instead, this change redirects to the same node on www.drupal.org when the content type is not ready. This way when there's any relative link in migrated content, there’s some capability to route to the right site without updating the content; and we're not hard-coding the sites into Views or elsewhere.
This also removes the bypass node access ability. I think for production, less differences in what admins can see vs. other user accounts is always good. We could open up a "preview" phase where a separate allowlist of content types is viewable by admins with bypass node access. I'm guessing the bypass node access exception might have been added so we can preview how something like credit records are migrating.