pilot-heartbeat-monitor

Agent health monitoring and automatic failover are triggered by tracking heartbeats and initiating task redistribution when peers become unreachable. This requires a running Pilot Protocol daemon and the pilotctl binary on PATH.

Leader election and swarm reconfiguration are triggered automatically in degraded conditions when peers become unreachable. The system detects the failure and reassigns leadership to a healthy agent.

Yes, the pilotctl binary on PATH and a running Pilot Protocol daemon are required to operate heartbeat monitoring correctly. Install the daemon, start pilotctl, and apply the skill to begin monitoring.

Automatic task reallocation to healthy agents is handled by monitoring heartbeats and redistributing tasks when failures are detected. This applies to distributed swarm deployments requiring load balancing and rapid recovery.

Yes, heartbeat monitoring applies to distributed swarm deployments requiring leader election, load balancing, and rapid recovery. It detects agent failures and initiates automatic task redistribution or leader re-election.

A running Pilot Protocol daemon is required because the skill relies on it to identify agent health and trigger automatic failover. Without the daemon and pilotctl on PATH, the monitoring cannot operate correctly.