bug-triage

# Bug Triage Skill Triage bugs into well-structured GitHub issues on the upstream **`AgentWrapper/agent-orchestrator`** repo (issues are enabled there; the `origin` fork is not the issue tracker). > **Agent Orchestrator (AO) is Go + Electron.** The backend is a Go daemon > (`backend/`) exposing a loopback HTTP API on `127.0.0.1:3001`; the frontend is an > Electron + React supervisor (`frontend/`). There is **no** pm2/tmux-per-session > Node runtime here: the daemon owns lifecycle and terminals run under the **tmux** > runtime adapter (ConPTY on Windows). Triage against _this_ Go rewrite, not the old > TypeScript agent-orchestrator implementation. ## ⚠️ Which `ao` are you running? **A bare `ao` on your PATH may resolve to a different AO install** (for example an old npm build at `~/.nvm/.../bin/ao` that talks to port **:3000**). Triaging with the wrong binary produces bugs that don't exist in this rewrite (and misses ones that do). Before any diagnostics: ```bash which -a ao # see every ao on PATH; expect surprises ao status 2>/dev/null # if this shows port 3000, it is NOT this rewrite ``` Use a rewrite binary explicitly: ```bash # Option A: build from this repo (preferred during triage) cd backend && go build -o /tmp/ao ./cmd/ao /tmp/ao status # must report port: 3001 # Option B: the packaged app's bundled daemon "/Applications/Agent Orchestrator.app/Contents/Resources/daemon/ao" status ``` **Confirm `ao status` repo...