Refactor team collaboration skills and update documentation

- Renamed `team-lifecycle-v5` to `team-lifecycle` across various documentation files for consistency.
- Updated references in code examples and usage sections to reflect the new skill name.
- Added a new command file for the `monitor` functionality in the `team-iterdev` skill, detailing the coordinator's monitoring events and task management.
- Introduced new components for dynamic pipeline visualization and session coordinates display in the frontend.
- Implemented utility functions for pipeline stage detection and status derivation based on message history.
- Enhanced the team role panel to map members to their respective pipeline roles with status indicators.
- Updated Chinese documentation to reflect the changes in skill names and descriptions.

.claude/skills/team-lifecycle-v5/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: team-lifecycle-v5
+name: team-lifecycle
 description: Unified team skill for full lifecycle - spec/impl/test. Uses team-worker agent architecture with role-spec files for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents loaded with role-specific Phase 2-4 specs. Triggers on "team lifecycle".
 allowed-tools: TeamCreate(*), TeamDelete(*), SendMessage(*), TaskCreate(*), TaskUpdate(*), TaskList(*), TaskGet(*), Task(*), AskUserQuestion(*), TodoWrite(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*)
 ---
 
-# Team Lifecycle v5
+# Team Lifecycle
 
 Unified team skill: specification -> implementation -> testing -> review. Built on **team-worker agent architecture** — all worker roles share a single agent definition with role-specific Phase 2-4 loaded from markdown specs.
 
@@ -12,7 +12,7 @@ Unified team skill: specification -> implementation -> testing -> review. Built
 
 ```
 +---------------------------------------------------+
-|  Skill(skill="team-lifecycle-v5")                  |
+|  Skill(skill="team-lifecycle")                  |
 |  args="task description"                           |
 +-------------------+-------------------------------+
                     |
@@ -79,7 +79,7 @@ Always route to coordinator. Coordinator reads `roles/coordinator/role.md` and e
 
 User just provides task description.
 
-**Invocation**: `Skill(skill="team-lifecycle-v5", args="task description")`
+**Invocation**: `Skill(skill="team-lifecycle", args="task description")`
 
 **Lifecycle**:
 ```
@@ -118,7 +118,7 @@ Task({
   run_in_background: true,
   prompt: `## Role Assignment
 role: <role>
-role_spec: .claude/skills/team-lifecycle-v5/role-specs/<role>.md
+role_spec: .claude/skills/team-lifecycle/role-specs/<role>.md
 session: <session-folder>
 session_id: <session-id>
 team_name: <team-name>

.claude/skills/team-lifecycle-v5/roles/coordinator/commands/monitor.md

@@ -136,7 +136,7 @@ Collect task states from TaskList()
            run_in_background: true,
            prompt: `## Role Assignment
 role: <role>
-role_spec: .claude/skills/team-lifecycle-v5/role-specs/<role>.md
+role_spec: .claude/skills/team-lifecycle/role-specs/<role>.md
 session: <session-folder>
 session_id: <session-id>
 team_name: <team-name>

.claude/skills/team-lifecycle-v5/roles/coordinator/role.md

@@ -1,6 +1,6 @@
 # Coordinator Role
 
-Orchestrate the team-lifecycle-v5 workflow: team creation, task dispatching, progress monitoring, session state. Uses **team-worker agent** for all worker spawns — no Skill indirection.
+Orchestrate the team-lifecycle workflow: team creation, task dispatching, progress monitoring, session state. Uses **team-worker agent** for all worker spawns — no Skill indirection.
 
 ## Identity
 

.claude/skills/team-lifecycle-v5/specs/team-config.json

@@ -1,6 +1,6 @@
 {
   "team_name": "team-lifecycle",
-  "team_display_name": "Team Lifecycle v5",
+  "team_display_name": "Team Lifecycle",
   "description": "Unified team-worker agent architecture: shared Phase 1/5/Inner Loop in agent, role-specific Phase 2-4 from spec files",
   "version": "5.0.0",
   "architecture": "team-worker agent + role-specs",