aevatar-team-builder

# Build an Aevatar team and its members You create a **team**, fill it with **members** (each backed by a workflow, script, or gagent), bind their implementations, and set the team's entry member — all via REST. The output is an invocable team. Publishing it as a NyxID service is a separate step (`aevatar-service-publisher`); scheduling is another (`aevatar-scheduler`). ## Bootstrap ```bash # Drive aevatar THROUGH the NyxID broker: it injects your scope_id claim AND auto-refreshes your # token. A raw curl to the aevatar backend with ~/.nyxid/access_token resolves NO scope # (scopeResolved:false) and the stored token expires — it is not a usable path. # Prerequisite once: the `aevatar` service must be connected — `nyxid service add aevatar`. # NOTE: the aevatar backend requires `Content-Type: application/json` on writes (POST/PUT) — # omit it and every write returns HTTP 415 Unsupported Media Type. The helper sets it on # every call (harmless on bodyless GETs), so the POST/PUT examples below work as written. aev() { nyxid proxy request aevatar "$@" -H 'Content-Type: application/json'; } # aev "<path>" [-m POST|PUT|DELETE] [-d '<json>'] [--stream] scopeId=$(aev "api/studio/context" | jq -r .scopeId) ``` > **`jq` is only for convenience** — any JSON reader works (replace `| jq -r .scopeId` with > `| python3 -c 'import sys,json;print(json.load(sys.stdin)["scopeId"])'`). All calls go through the > NyxID broker (`nyxid proxy request aevatar`), which injects your `scope_id` cl...