The terminal lists the teams of your organizations and who is in each, as the organization's Teams page does #7997

Intent: plain about who sees what, from the terminal too; today the org teams (/<org>/-/teams, src/web/pages/org.ts) have no terminal screen at all, while the crew's teams do (src/tui/screens/teams.ts, a different thing).

Done looks like:

• [ ] A new src/tui/screens/orgteams.ts with a palette entry (id "org-teams", title "Organization teams", hint "who is in each team of your organizations") offered to any signed-in person who belongs to an organization (listOrgsForUser from src/core/orgs.ts), registered in src/tui/screens/entries.ts beside teams.
• [ ] The screen lists, per organization, each team the viewer may see (listTeamsVisibleTo, so an org admin sees every team and a member only their own) with its member count; Enter on a team lists its members (listTeamMembers), @username and display name, esc goes back.
• [ ] Read-only in this issue: no key adds or removes anyone. An organization with no visible team says "No teams you can see."
• [ ] The module comment says what it shows and whose rule decides it, in the shape of the other screens' comments.
• [ ] A new test/tui-org-teams.test.ts proves: an org admin sees every team; a member sees only the teams they are in; Enter shows the right members; a person in no organization is not offered the entry. It fails without the change.

Files: src/tui/screens/orgteams.ts, src/tui/screens/entries.ts, test/tui-org-teams.test.ts Risks: entries.ts is a shared list; add one import and one entry line. Adding and removing members from the terminal is a follow-up once this lands. Brief: a builder who knows the terminal screens.

Parked by the crew: the check stayed red through 2 automatic tries (pull #8070 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Closed: already done on main in e1769cf3 (pull #8118).