feat(console-web): Member-first Invoke flow and Studio closeout

[AbigailDeng]

Part of #322

Background

Invoke 是 member-first 生命周期的最后一个核心交互页。
同时，Studio 还需要把剩余的 Observe、Team entry、深链、Workflow polish 和全链路回归一起收尾，才能真正完成 #322 的可验收闭环。

Goal

先把 Invoke 页面收口为“只调用当前 member”，再完成 Studio 剩余 closeout，让用户可以顺畅完成：
Build -> Bind -> Invoke -> Observe

Scope

Day 1

• Invoke 页面只围绕当前 member
• 收口 endpoint、request editor、send、history、transcript
• 保证从 Bind 进入 Invoke 的上下文稳定

Day 2

• Observe 做最小 member-first 收口
• Team Detail -> Studio entry handoff 收尾
• 深链语义稳定到 scopeId + memberId + step + focus
• Workflow 剩余 member-first polish 收尾
• 补全主链回归测试

Out of Scope

• 新后端 member API
• 超出 feat(console-web): Studio 重构 — Team Context + Member-first Workbench #322 范围的新功能扩张
• 独立的视觉大改版

Main Files

• apps/aevatar-console-web/src/pages/studio/components/StudioMemberInvokePanel.tsx
• apps/aevatar-console-web/src/pages/studio/index.tsx
• apps/aevatar-console-web/src/pages/teams/detail.tsx
• apps/aevatar-console-web/src/shared/studio/navigation.ts
• apps/aevatar-console-web/src/pages/studio/index.test.tsx

Checklist

• Invoke 目标明确为当前 member
• endpoint / request editor / send / history / transcript 收口
• Observe 最小 member-first 收口
• Team entry / 深链稳定
• Workflow 剩余 polish 收尾
• 主链回归测试补齐

Acceptance

• 用户能顺畅完成 Build -> Bind -> Invoke -> Observe
• 从 Team 进入 Studio 后上下文稳定
• Studio 主链不再出现明显主语漂移
• member-first 核心回归测试通过

[AbigailDeng]

Linking the backend blocker explicitly here: #364

Current read after frontend/codebase review:

• #340 can still complete a meaningful frontend closeout on the current legacy runtime/binding APIs
• but #340 cannot honestly become 100% pure member-first end-to-end until the backend gaps in #364 are resolved

The main blockers are:

1. no authoritative memberId -> publishedServiceId mapping
2. no member-centric binding API
3. no member-centric invoke API
4. no member-centric runs / observe API
5. no member roster/detail backend truth for stable Studio routing

Practical impact on the frontend deadline:

• if #364 is not ready before the #322 closeout target on April 30, 2026, frontend #340 can still ship a strong closeout for Build -> Bind -> Invoke -> Observe
• but that ship should be treated as a compatibility-mode member-first closeout, not the final fully pure member-first backend truth

So the suggested reading is:

• #340 = frontend closeout and flow stabilization
• #364 = backend blockers for fully pure member-first semantics
• #325 = broader backend member-model track