More Reliable Provisioning, Site Logs, and Dispatch

New agents became more reliably ready after setup, site logs became clearer around active builds, and recurring agent dispatch became harder to skip.

This update tightened three places where uncertainty was too expensive: whether a new agent was truly ready, whether a site build was still running, and whether a recurring agent update actually reached the user.

Agent Provisioning Became More Dependable

Agent setup now does more readiness work before treating a new agent as ready to use.

That reduces the chance of landing in an agent workspace that looks available but still lacks the basics needed for execution.

Site Logs Became Easier To Interpret

Site logs now distinguish empty output, still-running work, and finished builds more clearly.

The goal is a better answer to a common question: "Is this stuck, done, or still moving?"

Recurring Dispatch Is Treated As Real Work

Agent dispatch messages became a non-optional part of the recurring heartbeat flow.

When an agent is meant to report or ask, the system is stricter about making that communication happen instead of letting it disappear as a skipped side effect.