alera-orchestration

# Alera Inter-Agent Orchestration Use this skill for structured multi-agent work in Alera. The runtime-host owns lifecycle authority; do not emulate completion, cancellation, leases, or ownership with generic messages. ## Preconditions - Run inside an Alera terminal so `ALERA_TERMINAL_HANDLE` identifies the caller. - `ALERA_WORKSPACE_ID` supplies the default workspace for task creation, direct spawn, coordinator runs, and terminal listings. Use `alera orchestration current` to inspect both inferred identities. - Use `alera version --json` when CLI/host/skill compatibility is uncertain. - Keep every coordinated task scoped to a workspace and coordinator. A workspace may have one active coordinator run; different workspaces may run concurrently. Tasks created for a run and injected worker terminals must match that run's workspace and coordinator. ## Coordinator Workflow ```bash alera orchestration --json task-create --task-title "Review Tests" --spec "Review automated test coverage" alera orchestration --json run --agent codex --spec "Audit the repository" alera orchestration --json run-list --workspace <workspace-id> alera orchestration --json status --id <run-id> ``` Use `--agent codex|claude|copilot|cursor|agy|opencode|pi|amp`. The runtime may create workers through the built-in adapter registry. To discover the launch configurations the user declared, read the catalog: ```bash alera orchestration --json agent-profiles ``` Each profile carries `name`, `agentType`, `...