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-arch-opt/role-specs/analyzer.md

@@ -17,7 +17,7 @@ Analyze codebase architecture to identify structural issues: dependency cycles,
 |-------|--------|----------|
 | 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>/wisdom/.msg/meta.json | No |
 
 1. Extract session path and target scope from task description
 2. Detect project type by scanning for framework markers:
@@ -76,5 +76,5 @@ Execute analysis based on detected project type:
    - Evidence summary per issue
    - Detected project type and analysis methods used
 
-3. Update `<session>/wisdom/shared-memory.json` under `analyzer` namespace:
+3. Update `<session>/wisdom/.msg/meta.json` under `analyzer` namespace:
    - Read existing -> merge `{ "analyzer": { project_type, issue_count, top_issue, scope, categories } }` -> write back

.claude/skills/team-arch-opt/role-specs/designer.md

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

.claude/skills/team-arch-opt/role-specs/refactorer.md

@@ -28,7 +28,7 @@ Implement architecture refactoring changes following the design plan. For FIX ta
 | Branch refactoring detail | <session>/artifacts/branches/B{NN}/refactoring-detail.md | Yes (REFACTOR with branch) |
 | Pipeline refactoring plan | <session>/artifacts/pipelines/{P}/refactoring-plan.md | Yes (REFACTOR with pipeline) |
 | Review/validation feedback | From task description | Yes (FIX) |
-| shared-memory.json | <session>/wisdom/shared-memory.json | Yes |
+| .msg/meta.json | <session>/wisdom/.msg/meta.json | Yes |
 | Wisdom files | <session>/wisdom/patterns.md | No |
 | Context accumulator | From prior REFACTOR/FIX tasks | Yes (inner loop) |
 
@@ -50,7 +50,7 @@ Implement architecture refactoring changes following the design plan. For FIX ta
 5. Use `explore` subagent to load implementation context for target files
 6. For inner loop (single mode only): load context_accumulator from prior REFACTOR/FIX tasks
 
-**Shared-memory namespace**:
+**Meta.json namespace**:
 - Single: write to `refactorer` namespace
 - Fan-out: write to `refactorer.B{NN}` namespace
 - Independent: write to `refactorer.{P}` namespace

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

@@ -21,7 +21,7 @@ Review refactoring code changes for correctness, pattern consistency, completene
 | Refactoring code changes | From REFACTOR task artifacts / git diff | Yes |
 | Refactoring plan / detail | Varies by mode (see below) | Yes |
 | Validation results | Varies by mode (see below) | No |
-| shared-memory.json | <session>/wisdom/shared-memory.json | Yes |
+| .msg/meta.json | <session>/wisdom/.msg/meta.json | Yes |
 
 1. Extract session path from task description
 2. **Detect branch/pipeline context** from task description:
@@ -37,7 +37,7 @@ Review refactoring code changes for correctness, pattern consistency, completene
    - Fan-out branch: Read `<session>/artifacts/branches/B{NN}/refactoring-detail.md`
    - Independent: Read `<session>/artifacts/pipelines/{P}/refactoring-plan.md`
 
-4. Load shared-memory.json for scoped refactorer namespace:
+4. Load .msg/meta.json for scoped refactorer namespace:
    - Single: `refactorer` namespace
    - Fan-out: `refactorer.B{NN}` namespace
    - Independent: `refactorer.{P}` namespace
@@ -108,7 +108,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>/wisdom/.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-arch-opt/role-specs/validator.md

@@ -17,7 +17,7 @@ Validate refactoring changes by running build checks, test suites, dependency me
 |-------|--------|----------|
 | Architecture baseline | <session>/artifacts/architecture-baseline.json (shared) | Yes |
 | Refactoring plan / detail | Varies by mode (see below) | Yes |
-| shared-memory.json | <session>/wisdom/shared-memory.json | Yes |
+| .msg/meta.json | <session>/wisdom/.msg/meta.json | Yes |
 
 1. Extract session path from task description
 2. **Detect branch/pipeline context** from task description:
@@ -37,7 +37,7 @@ Validate refactoring changes by running build checks, test suites, dependency me
    - Fan-out branch: Read `<session>/artifacts/branches/B{NN}/refactoring-detail.md` -- only this branch's criteria
    - Independent: Read `<session>/artifacts/pipelines/{P}/refactoring-plan.md`
 
-5. Load shared-memory.json for project type and refactoring scope
+5. Load .msg/meta.json for project type and refactoring scope
 6. Detect available validation tools from project:
 
 | Signal | Validation Tool | Method |
@@ -50,7 +50,7 @@ Validate refactoring changes by running build checks, test suites, dependency me
 | Makefile with test target | Custom tests | make test |
 | No tooling detected | Manual validation | File existence + import grep checks |
 
-7. Get changed files scope from shared-memory:
+7. Get changed files scope from .msg/meta.json:
    - Single: `refactorer` namespace
    - Fan-out: `refactorer.B{NN}` namespace
    - Independent: `refactorer.{P}` namespace
@@ -108,7 +108,7 @@ Compare against baseline and plan criteria:
    - Independent: `<session>/artifacts/pipelines/{P}/validation-results.json`
    - Content: Per-dimension: name, baseline value, current value, improvement/regression, verdict; Overall verdict: PASS / WARN / FAIL; Failure details (if any)
 
-2. Update `<session>/wisdom/shared-memory.json` under scoped namespace:
+2. Update `<session>/wisdom/.msg/meta.json` under scoped namespace:
    - Single: merge `{ "validator": { verdict, improvements, regressions, build_pass, test_pass } }`
    - Fan-out: merge `{ "validator.B{NN}": { verdict, improvements, regressions, build_pass, test_pass } }`
    - Independent: merge `{ "validator.{P}": { verdict, improvements, regressions, build_pass, test_pass } }`