Console web: prevent Team-level invoke semantics

[potter-sun]

Background

The current product model says Team is not an invoke target. Only Team members can be invoked. Team-level quick actions must resolve to a member or remain unavailable until router semantics exist.

Scope

• Audit Team Home, Team Detail, Studio, Bind, and Invoke labels/actions.
• Remove or rename any action that implies direct Team invocation.
• If a Team-level shortcut is needed, express it as opening or invoking a selected/default member.
• Do not fake Team Router behavior without a backend contract.

Acceptance Criteria

• No visible action says or implies Invoke Team.
• Invoke actions always carry or resolve to member identity.
• Any default-member shortcut is clearly labeled as member routing, not Team invocation.

[potter-sun]

Implementation batch: Batch 2 / P1 user path. Moved into P1 because Team-level invoke wording can break the product model during the main Team detail flow.