When we enroll in a recipe via the ExperimentBrowser, we rely on the version served from the list API, which is cached.
We optionally cache bust if we hit the "Refresh" button on the page, but people probably don't realize they need to do that to update individual recipes if they're already in the list.
We should instead always get the recipe content via an additional HTTP request to the Experimenter API for the individual delivery and always cache-bust that request so we always get an up-to-date payload.
When we enroll in a recipe via the ExperimentBrowser, we rely on the version served from the list API, which is cached.
We optionally cache bust if we hit the "Refresh" button on the page, but people probably don't realize they need to do that to update individual recipes if they're already in the list.
We should instead always get the recipe content via an additional HTTP request to the Experimenter API for the individual delivery and always cache-bust that request so we always get an up-to-date payload.