ir:onboarding-factory/record

record

You run as a focused subagent with no parent context. This verb DRIVES A LIVE AGENT CLI and SPENDS API TOKENS — auth is set up out-of-band, so run it without ceremony (no key checks, no "this will spend money" prompts). It must be serialized: only one record runs against the live daemon at a time. When done, return only the "Return contract" block.

Preconditions

1. The cell is assessed and on a recordable route. Read it:

   of status --agent <agent> --scenario <scenario> --json
   

   • route record / record-known-failing → proceed.
   • route driver-gap → port the step first (Step 2), then proceed.
   • route frozen → STOP, return status: frozen (nothing to record).

2. Prerequisites met. of record prereq-check --agent <agent> lists the human actions a recording needs (auth mode, env vars, a mock, a local model server). If one is unmet and you can't satisfy it, STOP and return status: prereq_blocked naming the exact blocker — never ask the dispatcher.

3. Clean replaydata/ tree. The recording precheck refuses a dirty replaydata/ (re-records must be deliberate commits). If the assessment isn't committed yet, that's the dispatcher's ordering bug — return status: infra_fail with that note.

4. A recording daemon is up — attached OR coexisting. Which one is a decision you make per run, not a default:

   • Attach (--attach, against the user's running irrlichd --record) when you are re-recording an adapter the running daemon already ships, and that daemon is genuinely in --record mode. The dashboard stays connected and the session shows up live.

   • Coexist — an isolated daemon built from this branch, on its own IRRLICHT_HOME and port — when either half of that is false:

     IRRLICHT_ONBOARD_HOME=/tmp/irr-onb \
     IRRLICHT_ONBOARD_BIND_ADDR=127.0.0.1:7838 \
     IRRLICHT_PERMISSION_MODE=grant-all \
       of record run --agent <agent> --scenario <scenario>