aevatar-team-builderlisted

# 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`). A runnable workflow in Studio is normally a **Team-owned workflow member**, not a public template or an Ornn skill. Before creating anything, list the caller's Teams and resolve the intended Team. If more than one is plausible and the user did not choose, ask; never create a draft/member first and attach it to a guessed Team later. Follow `nextPageToken` on Team/member roster lists. Use workflow list/detail responses as returned, and apply documented server-side run filters and `take` without inventing a cursor. Choose the lifecycle from current state: - Existing Team member → edit/bind that exact member, wait for its exact revision readiness, then hand it to `aevatar_schedule_member_workflow` if scheduling was requested. - No member, user explicitly wants a new scheduled workflow → in-session `aevatar_provision_workflow_schedule` can create its own Team member and schedule after the Team is confirmed. Do not use it as an update path for an existing member. - New member without scheduling → use the REST create/bind flow below. `memberId`, draft `workflowId`, `publishedServiceId`, Definition actor ID