pilot

# Pilot - One Autonomous Cycle JobPilot's autonomous mode: the host re-injects this skill perpetually, so each invocation is **one stateless cycle** - sense, decide, act, record, exit. All state lives in the API; nothing survives between invocations except what you write there. Do **exactly one** agenda item (at most one worker delegation, one browser activity), journal it, print the sentinel, stop. ## 0. Setup Follow `../_shared/setup.md` - health check `GET /api/health` first; abort with its standard message if down. Then generate a cycle id (uuidgen if present, else a portable fallback): ```bash CYCLE_ID=$(uuidgen 2>/dev/null || cat /proc/sys/kernel/random/uuid 2>/dev/null || od -An -tx1 -N16 /dev/urandom | tr -d ' \n' | sed -E 's/^(.{8})(.{4})(.{4})(.{4})(.{12})$/\1-\2-\3-\4-\5/') ``` Load the pilot state - step 2 breaks priority ties with its goals text. No run-state check here: the host gates the loop. ```bash curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" "$JOBPILOT_API/api/pilot" ``` ## 1. Sense ```bash AGENDA=$(curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" -X POST "$JOBPILOT_API/api/pilot/agenda/refresh") AGENDA_VERSION=$(echo "$AGENDA" | jq -r '.version') ``` A `409` means the pilot was stopped mid-cycle - a rare race the host normally gates. Journal and exit empty. ```bash curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" -X POST "$JOBPILOT_API/api/pilot/journal" \ -H 'content-type: application/json' \ -d "$(jq -n --arg cid...