Private location agent: published image, versions, and update notices

The private location agent is now published as a Docker image, for linux/amd64 and linux/arm64:

• ghcr.io/reverse-sweep-ltd/yorker-agent runs HTTP, MCP, and browser monitors.
• ghcr.io/reverse-sweep-ltd/yorker-agent-light runs HTTP and MCP monitors only, in a much smaller image.

Install it with the Compose file from the private locations guide, and update it with:

docker compose pull && docker compose up -d

Yorker tells you when an agent falls behind

Hosted locations update themselves. A private agent runs on your infrastructure, so it stays on the release it was started with. Each agent now reports its version when it polls, and Settings > Locations shows it in a new Agent column, flagged Update available when a newer release exists. yorker locations list shows the same thing from @yorker/cli@0.10.0.

Monitors an agent cannot run are named

A monitor assigned to a private location that the agent cannot run used to fail without explanation. The location is now flagged, with the monitor's name and the reason:

• A browser monitor assigned to an agent running the light image, which has no browser.
• A scripted browser monitor. These run on hosted locations only; private locations run URL-mode browser monitors.

The docker run command in the CLI and dashboard was wrong

yorker locations create, yorker locations keys create, and the runner key panel in the dashboard printed a docker run command for an image that did not exist. The dashboard's also used environment variable names the agent does not read. All three now print the same working command for the published image.