Worker protocol

Internal HTTP used by cmd/worker. The console only calls GET /api/v1/worker/stats. Operators: Workers.

All of these require X-API-Key. Bodies are unwrapped.

Method	Path	Role
POST	/api/v1/worker/register	Upsert worker_heartbeats
POST	/api/v1/worker/claim	Atomic claim; returns JobBundle[] (pipeline + decrypted config + schemas)
POST	/api/v1/worker/executions/{id}/running	Mark running (409 if claim lost)
POST	/api/v1/worker/executions/{id}/heartbeat	Extend lease; { cancel_requested: bool }
POST	/api/v1/worker/executions/{id}/finish	completed / failed / cancelled; may requeue (scheduled)
GET	/api/v1/worker/stats	Queue counts, workers, leases

The worker process is an HTTP client. It has no HTTP listen port and no probes. TCP/UDP listen datasources bind a socket for the run and, when listener_services is on, publish a ClusterIP Service.