RTerm ↔ AgentSpan Bridge

Make RTerm's operations durable. Normal RTerm agent runs are interactive and die if RTerm/your machine restarts; the bridge hands work to an AgentSpan (Netflix Conductor) server that keeps going and resumes from the last completed step — plus plan-execute determinism, Kafka/SQS/AMQP event triggers, and a visual execution UI.

Two agents, two LLMs (don't conflate): RTerm's own agent uses RTerm's model profiles. A durable agent you launch runs on the AgentSpan server and uses its own provider config. The bridge between them is just an HTTP URL.

1. Setup (one time)

1. Run the AgentSpan server (default port 6767):

   agentspan server start        # or: launchd/systemd service, Docker, or the runtime JAR
   curl http://localhost:6767/actuator/health   # → {"status":"UP",...}
   

2. Point RTerm at it: Settings → AgentSpan → serverUrl = http://localhost:6767 (default), enabled = true, Save. This is persisted (schema v5) and live — no RTerm restart.
3. Auth (only if the AgentSpan server has standalone auth on): put AGENTSPAN_AUTH_KEY/AGENTSPAN_AUTH_SECRET as a KEY=VAL blob in the RTerm vault (manage_secret), then set authSecretRef to that vault key. Never inline.

Verify from RTerm: ask the agent to "check AgentSpan health" (uses agentspan_health).

2. The bridge tools (RTerm agent)