mirror of
https://github.com/feder-cr/Jobs_Applier_AI_Agent.git
synced 2026-11-07 10:36:05 -10:00
feder-cr
c16e144f89
A Dot kept the browser of the golden image it was made from. runtime/dot-browser.sh (the old build-browser-env.sh, now on the runtime disk as well as the builder seed) is the one owner of where the Dot's browser lives: each release in an environment of its own, browser/<mcp>-<playwright>-<core>, and the Dot's browser the one ~dot/.local/bin/invisible-playwright-mcp links to. At every start install.sh switches that link to a release an earlier start staged, in one rename and before the Dot's units, and after them stages the newest release as uv resolves it, in the background: its environment and its browser engine, through the Dot's own way out. A start never waits for a release; without the network the Dot keeps its browser. provision.sh installs the golden image's browser with the same script. The switch has to come before the engine, and that ordering did not hold: the units were enabled, so on every boot after the first systemd started them at multi-user.target, before cloud-init's final stage ran install.sh (cloud-final.service is After=multi-user.target; a Dot's serial log shows dot-agentd and the engine up two seconds before install.sh). A Dot with a VM proxy went out before its proxy was set. The units are no longer enabled: install.sh starts them, after the proxy and the switch, and removes the links an earlier runtime made.