#headless-browsers

Releases never owned the browser the worker depended on

The one worker that drives a headless browser only learned at job time whether a browser existed, because the browser lived in a user cache instead of the release. I sealed it into the release with a manifest, made health refuse promotion without it, and then caught my own guard looking for it in the wrong folder.