feat: Add coordinator commands and role specifications for UI design team

- Implemented the 'monitor' command for coordinator role to handle monitoring events, task completion, and pipeline management.
- Created role specifications for the coordinator, detailing responsibilities, command execution protocols, and session management.
- Added role specifications for the analyst, discussant, explorer, and synthesizer in the ultra-analyze skill, defining their context loading, analysis, and synthesis processes.

.claude/skills/team-perf-opt/role-specs/benchmarker.md

@@ -17,7 +17,7 @@ Run benchmarks comparing before/after optimization metrics. Validate that improv
 |-------|--------|----------|
 | Baseline metrics | <session>/artifacts/baseline-metrics.json (shared) | Yes |
 | Optimization plan / detail | Varies by mode (see below) | Yes |
-| shared-memory.json | <session>/wisdom/shared-memory.json | Yes |
+| .msg/meta.json | <session>/.msg/meta.json | Yes |
 
 1. Extract session path from task description
 2. **Detect branch/pipeline context** from task description:
@@ -37,7 +37,7 @@ Run benchmarks comparing before/after optimization metrics. Validate that improv
    - Fan-out branch: Read `<session>/artifacts/branches/B{NN}/optimization-detail.md` -- only this branch's criteria
    - Independent: Read `<session>/artifacts/pipelines/{P}/optimization-plan.md`
 
-5. Load shared-memory.json for project type and optimization scope
+5. Load .msg/meta.json for project type and optimization scope
 6. Detect available benchmark tools from project:
 
 | Signal | Benchmark Tool | Method |
@@ -101,7 +101,7 @@ Compare against baseline and plan criteria:
    - Independent: `<session>/artifacts/pipelines/{P}/benchmark-results.json`
    - Content: Per-metric: name, baseline value, current value, improvement %, verdict; Overall verdict: PASS / WARN / FAIL; Regression details (if any)
 
-2. Update `<session>/wisdom/shared-memory.json` under scoped namespace:
+2. Update `<session>/.msg/meta.json` under scoped namespace:
    - Single: merge `{ "benchmarker": { verdict, improvements, regressions } }`
    - Fan-out: merge `{ "benchmarker.B{NN}": { verdict, improvements, regressions } }`
    - Independent: merge `{ "benchmarker.{P}": { verdict, improvements, regressions } }`

.claude/skills/team-perf-opt/role-specs/optimizer.md

@@ -28,7 +28,7 @@ Implement optimization changes following the strategy plan. For FIX tasks, apply
 | Branch optimization detail | <session>/artifacts/branches/B{NN}/optimization-detail.md | Yes (IMPL with branch) |
 | Pipeline optimization plan | <session>/artifacts/pipelines/{P}/optimization-plan.md | Yes (IMPL with pipeline) |
 | Review/bench feedback | From task description | Yes (FIX) |
-| shared-memory.json | <session>/wisdom/shared-memory.json | Yes |
+| .msg/meta.json | <session>/.msg/meta.json | Yes |
 | Wisdom files | <session>/wisdom/patterns.md | No |
 | Context accumulator | From prior IMPL/FIX tasks | Yes (inner loop) |
 

.claude/skills/team-perf-opt/role-specs/profiler.md

@@ -17,7 +17,7 @@ Profile application performance to identify CPU, memory, I/O, network, and rende
 |-------|--------|----------|
 | Task description | From task subject/description | Yes |
 | Session path | Extracted from task description | Yes |
-| shared-memory.json | <session>/wisdom/shared-memory.json | No |
+| .msg/meta.json | <session>/.msg/meta.json | No |
 
 1. Extract session path and target scope from task description
 2. Detect project type by scanning for framework markers:
@@ -69,5 +69,5 @@ Execute profiling based on detected project type:
    - Evidence summary per bottleneck
    - Detected project type and profiling methods used
 
-3. Update `<session>/wisdom/shared-memory.json` under `profiler` namespace:
+3. Update `<session>/.msg/meta.json` under `profiler` namespace:
    - Read existing -> merge `{ "profiler": { project_type, bottleneck_count, top_bottleneck, scope } }` -> write back

.claude/skills/team-perf-opt/role-specs/reviewer.md

@@ -21,7 +21,7 @@ Review optimization code changes for correctness, side effects, regression risks
 | Optimization code changes | From IMPL task artifacts / git diff | Yes |
 | Optimization plan / detail | Varies by mode (see below) | Yes |
 | Benchmark results | Varies by mode (see below) | No |
-| shared-memory.json | <session>/wisdom/shared-memory.json | Yes |
+| .msg/meta.json | <session>/.msg/meta.json | Yes |
 
 1. Extract session path from task description
 2. **Detect branch/pipeline context** from task description:
@@ -37,7 +37,7 @@ Review optimization code changes for correctness, side effects, regression risks
    - Fan-out branch: Read `<session>/artifacts/branches/B{NN}/optimization-detail.md`
    - Independent: Read `<session>/artifacts/pipelines/{P}/optimization-plan.md`
 
-4. Load shared-memory.json for scoped optimizer namespace:
+4. Load .msg/meta.json for scoped optimizer namespace:
    - Single: `optimizer` namespace
    - Fan-out: `optimizer.B{NN}` namespace
    - Independent: `optimizer.{P}` namespace
@@ -83,7 +83,7 @@ Classify overall verdict based on findings:
    - Independent: `<session>/artifacts/pipelines/{P}/review-report.md`
    - Content: Per-dimension findings with severity, file:line, description; Overall verdict with rationale; Specific fix instructions for REVISE/REJECT verdicts
 
-2. Update `<session>/wisdom/shared-memory.json` under scoped namespace:
+2. Update `<session>/.msg/meta.json` under scoped namespace:
    - Single: merge `{ "reviewer": { verdict, finding_count, critical_count, dimensions_reviewed } }`
    - Fan-out: merge `{ "reviewer.B{NN}": { verdict, finding_count, critical_count, dimensions_reviewed } }`
    - Independent: merge `{ "reviewer.{P}": { verdict, finding_count, critical_count, dimensions_reviewed } }`

.claude/skills/team-perf-opt/role-specs/strategist.md

@@ -18,13 +18,13 @@ Analyze bottleneck reports and baseline metrics to design a prioritized optimiza
 |-------|--------|----------|
 | Bottleneck report | <session>/artifacts/bottleneck-report.md | Yes |
 | Baseline metrics | <session>/artifacts/baseline-metrics.json | Yes |
-| shared-memory.json | <session>/wisdom/shared-memory.json | Yes |
+| .msg/meta.json | <session>/.msg/meta.json | Yes |
 | Wisdom files | <session>/wisdom/patterns.md | No |
 
 1. Extract session path from task description
 2. Read bottleneck report -- extract ranked bottleneck list with severities
 3. Read baseline metrics -- extract current performance numbers
-4. Load shared-memory.json for profiler findings (project_type, scope)
+4. Load .msg/meta.json for profiler findings (project_type, scope)
 5. Assess overall optimization complexity:
 
 | Bottleneck Count | Severity Mix | Complexity |
@@ -88,7 +88,7 @@ Define measurable success criteria per optimization (target metric value or impr
    - Each optimization must be **non-overlapping** in target files (no two OPT-IDs modify the same file unless explicitly noted with conflict resolution)
    - Implementation guidance must be self-contained -- a branch optimizer should be able to work from a single OPT block without reading others
 
-2. Update `<session>/wisdom/shared-memory.json` under `strategist` namespace:
+2. Update `<session>/.msg/meta.json` under `strategist` namespace:
    - Read existing -> merge -> write back:
    ```json
    {