[BUG] Agent Teams members don't have SendMessage tool

### Preliminary Checks - [x] I have read the [Code of Conduct](https://github.com/wshobson/agents/blob/main/.github/CODE_OF_CONDUCT.md) - [x] I have searched existing issues to ensure this is not a duplicate - [x] This report contains only technical information about a bug ### Affected Subagent Agent Teams plugin. ### Bug Description I usually got this message for all implementer members of the fullstack team even for team lead, so the team lead went idle because it wasn't able to send message back to orchestrator for creating tasks, I ended up recreating team in hope it would work. ``` Note: I don't see a SendMessage tool in my available toolset — only Read, Write, Edit, and Bash. Posting this readiness summary here as my acknowledgement to team-lead. If a messaging tool becomes available, I'll use it for future updates ``` Another issue is naming conflicts between orchestrator and team lead, there is a case orchestrator is named team-lead and team lead is named team-lead-2, team lead send message to wrong recipient and orchestrator never receive the message Orchestrator message: ``` Team is up. Roster: Team "Admin" spawned successfully! Members: - team-lead-2 (lead — coordinates the team) - frontend-impl (owns apps/web/) - backend-impl (owns apps/api/) - tests-impl (owns unit + e2e tests) Display mode: tmux Note: the lead's actual name is team-lead-2 because the team-lead@Admin slot was reserved by TeamCreate before I spawned my lead. I'll address messages to team-lead-2. You used --delegate, so we're in delegation mode. What should the team work on? Give me the feature, refactor, or task and I'll hand it to team-lead-2 to decompose and assign. ``` ``` I have enough context. team-lead-2's agent-teams:team-lead subagent type is restricted to read-only tools — that's why they idle without producing visible plans (likely can't SendMessage). I'll bypass them and decompose directly, then dispatch tasks to the implementers myself. ``` Sometimes team lead asked questions but orchestrator think it's idle then takes over the decomposition task and manage team. ``` Open questions from my prior draft (still need answers regardless of route chosen) You asked me not to guess on ambiguity. Five items from my last reply still need your call before owners are assigned: 1. Self-delete enforcement — server-only, client-only, or both? (My default: both.) 2. Org owner re-assignment — when PATCH changes owner, what happens to the previous owner: demote to member, remove entirely, or leave membership untouched? (My default: demote to member.) 3. Slug uniqueness check — client-side pre-flight or server 409 only? (My default: server-only.) 4. Admin nav-button placement on web top-nav — specific location/styling, or implementer's discretion? 5. Theme color for apps/admin — any preference (amber/violet/slate/etc.), or implementer picks something visibly distinct? --- For reference, the full draft (T1–T12, phased, with file scope + deps + acceptance criteria) is in my prior message in this thread. Happy to repaste if you'd like it inline once we resolve the tooling question. Standing by. ``` ### Steps to Reproduce ```bash /agent-teams:team-spawn fullstack --name Admin --delegate ``` ### Expected Behavior . ### Additional Context _No response_