Make scheduled LSCli heartbeat setup work from a standard verified installation #157

I want to use LocalSetup to keep a server aware of its installed tools, health, maintenance needs, and important security updates, with a short agent review every fifteen minutes. The routine data collection should keep working predictably, and the agent should help interpret the results within clearly bounded authority.

On the current stable release, v4.57.0, I can initialize the heartbeat and obtain the released framework wheel, but a normal source-backed installation does not provide a ready LSCli runtime. Setting up the released wheel addresses the SDK payload; the coding agent still requires a separately authenticated native sandbox bundle that is not included among that release's downloadable assets. The documented safeguards are valuable, and I do not want to weaken them or patch deployed software to get past this gap.

Please provide one supported way to get from a standard verified installation to a working scheduled heartbeat, including the required agent runtime and sandbox prerequisites. It should be possible to select an existing secret-provider-backed connection, run a small readiness check, and explicitly activate the recurring schedule. When a prerequisite is unavailable, the user should get a clear explanation and a supported next step. A read-only review mode would also be useful when autonomous tooling is unavailable, provided its limits are clear.

The practical benefit is that operators could rely on LocalSetup's own installation and upgrade process instead of assembling private runtime pieces and one-off launchers. Fresh inventory and health data could continue to accumulate even during an agent outage, while upgrades would preserve the selected schedule and the user's safety boundaries.

Success would mean a new installation can demonstrate a real scheduled review, missing prerequisites are understandable and recoverable, and existing installations can upgrade without rebuilding their integration. This complements the broader inventory and portability work in #49; the immediate need here is a complete, usable heartbeat onboarding experience.