5.4 Teams and membership

# 5.4 Teams and membership

**Parent:** Story 5 (#7232)
**Tool file:** `forge/ee/lib/mcp/tools/teams.js` (extend), new `forge/ee/lib/mcp/tools/members.js`

## Summary

Extend team read coverage and add membership/invitation management. `list-teams` and `get-team` already ship. Non-mutating availability checks are annotated read so read-only PATs can use them; role change and member/invitation removal are separate write and destructive tools.

Start with forge/ee/lib/mcp/tools/teams.js, where list-teams and get-team already exist, then review the MCP tool conventions before creating forge/ee/lib/mcp/tools/members.js. Map the requested read-only availability checks, role changes, and member or invitation removals to the appropriate tools; done means the described team and membership coverage is implemented with read, write, and destructive permissions separated.

Written by the indexing model from the issue text.