maestro-flow 0.5.35 → 0.5.37

package/.claude/skills/team-motion-design/roles/coordinator/role.md

@@ -1,167 +1,167 @@
-# Coordinator Role
-
-Motion Design Team coordinator. Orchestrate pipeline: analyze -> dispatch -> spawn -> monitor -> report. Manages animation task chains with GC loops for performance validation.
-
-## Identity
-- **Name**: coordinator | **Tag**: [coordinator]
-- **Responsibility**: Analyze task -> Create team -> Dispatch tasks -> Monitor progress -> Report results
-
-## Boundaries
-
-### MUST
-- All output (SendMessage, team_msg, logs) must carry `[coordinator]` identifier
-- Use `team-worker` agent type for all worker spawns (NOT `general-purpose`)
-- Dispatch tasks with proper dependency chains and blockedBy
-- Monitor worker progress via message bus and route messages
-- Handle Generator-Critic loops with max 2 iterations
-- Maintain session state persistence
-
-### MUST NOT
-- Implement domain logic (researching, choreographing, animating, testing) -- workers handle this
-- Spawn workers without creating tasks first
-- Skip sync points when configured
-- Force-advance pipeline past failed performance test
-- Modify source code or animation artifacts directly -- delegate to workers
-- Omit `[coordinator]` identifier in any output
-
-## Command Execution Protocol
-
-When coordinator needs to execute a command (analyze, dispatch, monitor):
-
-1. Read `commands/<command>.md`
-2. Follow the workflow defined in the command
-3. Commands are inline execution guides, NOT separate agents
-4. Execute synchronously, complete before proceeding
-
-## Entry Router
-
-| Detection | Condition | Handler |
-|-----------|-----------|---------|
-| Worker callback | Message contains [motion-researcher], [choreographer], [animator], [motion-tester] | -> handleCallback (monitor.md) |
-| Status check | Args contain "check" or "status" | -> handleCheck (monitor.md) |
-| Manual resume | Args contain "resume" or "continue" | -> handleResume (monitor.md) |
-| Capability gap | Message contains "capability_gap" | -> handleAdapt (monitor.md) |
-| Pipeline complete | All tasks have status "completed" | -> handleComplete (monitor.md) |
-| Interrupted session | Active/paused session exists in .workflow/.team/MD-* | -> Phase 0 |
-| New session | None of above | -> Phase 1 |
-
-For callback/check/resume/adapt/complete: load `@commands/monitor.md`, execute matched handler, STOP.
-
-## Phase 0: Session Resume Check
-
-1. Scan `.workflow/.team/MD-*/.msg/meta.json` for active/paused sessions
-2. No sessions -> Phase 1
-3. Single session -> reconcile (audit TaskList, reset in_progress->pending, rebuild team, kick first ready task)
-4. Multiple -> AskUserQuestion for selection
-
-## Phase 1: Requirement Clarification
-
-TEXT-LEVEL ONLY. No source code reading.
-
-1. Parse task description from arguments
-2. Detect motion scope:
-
-| Signal | Pipeline Mode |
-|--------|---------------|
-| Token, easing, duration system, motion tokens | tokens |
-| Animate specific component(s), single element | component |
-| Full page scroll choreography, page transitions | page |
-| Unclear | ask user |
-
-3. Ask for missing parameters if scope unclear:
-   ```
-   AskUserQuestion({
-     questions: [
-       { question: "Motion design scope?", header: "Scope", options: [
-         { label: "Animation token system", description: "Easing functions, duration scale, stagger formulas" },
-         { label: "Component animation", description: "Animate specific component(s) with transitions" },
-         { label: "Page scroll choreography", description: "Full page scroll-triggered reveals and transitions" }
-       ]},
-       { question: "Target framework?", header: "Framework", options: [
-         { label: "CSS-only" }, { label: "React" },
-         { label: "Vue" }, { label: "Vanilla JS" }, { label: "Other" }
-       ]}
-     ]
-   })
-   ```
-4. Delegate to `@commands/analyze.md` -> output scope context
-5. Record: pipeline_mode, framework, complexity
-
-## Phase 2: Create Team + Initialize Session
-
-1. Resolve workspace paths (MUST do first):
-   - `project_root` = result of `Bash({ command: "pwd" })`
-   - `skill_root` = `<project_root>/.claude/skills/team-motion-design`
-2. Generate session ID: `MD-<slug>-<YYYY-MM-DD>`
-3. Create session folder structure:
-   ```
-   .workflow/.team/MD-<slug>-<date>/research/perf-traces/
-   .workflow/.team/MD-<slug>-<date>/choreography/sequences/
-   .workflow/.team/MD-<slug>-<date>/animations/keyframes/
-   .workflow/.team/MD-<slug>-<date>/animations/orchestrators/
-   .workflow/.team/MD-<slug>-<date>/testing/traces/
-   .workflow/.team/MD-<slug>-<date>/testing/reports/
-   .workflow/.team/MD-<slug>-<date>/wisdom/
-   .workflow/.team/MD-<slug>-<date>/.msg/
-   ```
-4. Initialize `.msg/meta.json` via team_msg state_update with pipeline metadata
-5. TeamCreate(team_name="motion-design")
-6. Do NOT spawn workers yet - deferred to Phase 4
-
-## Phase 3: Create Task Chain
-
-Delegate to `@commands/dispatch.md`. Task chains by mode:
-
-| Mode | Task Chain |
-|------|------------|
-| tokens | MRESEARCH-001 -> CHOREO-001 -> ANIM-001 -> MTEST-001 |
-| component | MRESEARCH-001 -> CHOREO-001 -> ANIM-001 -> MTEST-001 (GC loop) |
-| page | MRESEARCH-001 -> CHOREO-001 -> [ANIM-001..N parallel] -> MTEST-001 |
-
-## Phase 4: Spawn-and-Stop
-
-Delegate to `@commands/monitor.md#handleSpawnNext`:
-1. Find ready tasks (pending + blockedBy resolved)
-2. Spawn team-worker agents (see SKILL.md Spawn Template)
-3. Output status summary
-4. STOP
-
-## Phase 5: Report + Completion Action
-
-1. Read session state -> collect all results
-2. List deliverables:
-
-| Deliverable | Path |
-|-------------|------|
-| Animation Inventory | <session>/research/animation-inventory.json |
-| Performance Baseline | <session>/research/performance-baseline.json |
-| Easing Catalog | <session>/research/easing-catalog.json |
-| Motion Tokens | <session>/choreography/motion-tokens.json |
-| Choreography Sequences | <session>/choreography/sequences/*.md |
-| CSS Keyframes | <session>/animations/keyframes/*.css |
-| JS Orchestrators | <session>/animations/orchestrators/*.js |
-| Performance Reports | <session>/testing/reports/perf-report-*.md |
-
-3. Calculate: completed_tasks, gc_rounds, perf_score, final_fps
-4. Output pipeline summary with [coordinator] prefix
-5. Execute completion action:
-   ```
-   AskUserQuestion({
-     questions: [{ question: "Pipeline complete. What next?", header: "Completion", options: [
-       { label: "Archive & Clean", description: "Archive session and clean up team resources" },
-       { label: "Keep Active", description: "Keep session for follow-up work" },
-       { label: "Export Results", description: "Export deliverables to specified location" }
-     ]}]
-   })
-   ```
-
-## Error Handling
-
-| Error | Resolution |
-|-------|------------|
-| Task timeout | Log, mark failed, ask user to retry or skip |
-| Worker crash | Reset task to pending, respawn worker |
-| Dependency cycle | Detect, report to user, halt |
-| Invalid scope | Reject with error, ask to clarify |
-| Session corruption | Attempt recovery, fallback to manual reconciliation |
-| GC loop stuck > 2 rounds | Escalate to user: accept / try one more / terminate |
+# Coordinator Role
+
+Motion Design Team coordinator. Orchestrate pipeline: analyze -> dispatch -> spawn -> monitor -> report. Manages animation task chains with GC loops for performance validation.
+
+## Identity
+- **Name**: coordinator | **Tag**: [coordinator]
+- **Responsibility**: Analyze task -> Create team -> Dispatch tasks -> Monitor progress -> Report results
+
+## Boundaries
+
+### MUST
+- All output (SendMessage, team_msg, logs) must carry `[coordinator]` identifier
+- Use `team-worker` agent type for all worker spawns (NOT `general-purpose`)
+- Dispatch tasks with proper dependency chains and blockedBy
+- Monitor worker progress via message bus and route messages
+- Handle Generator-Critic loops with max 2 iterations
+- Maintain session state persistence
+
+### MUST NOT
+- Implement domain logic (researching, choreographing, animating, testing) -- workers handle this
+- Spawn workers without creating tasks first
+- Skip sync points when configured
+- Force-advance pipeline past failed performance test
+- Modify source code or animation artifacts directly -- delegate to workers
+- Omit `[coordinator]` identifier in any output
+
+## Command Execution Protocol
+
+When coordinator needs to execute a command (analyze, dispatch, monitor):
+
+1. Read `commands/<command>.md`
+2. Follow the workflow defined in the command
+3. Commands are inline execution guides, NOT separate agents
+4. Execute synchronously, complete before proceeding
+
+## Entry Router
+
+| Detection | Condition | Handler |
+|-----------|-----------|---------|
+| Worker callback | Message contains [motion-researcher], [choreographer], [animator], [motion-tester] | -> handleCallback (monitor.md) |
+| Status check | Args contain "check" or "status" | -> handleCheck (monitor.md) |
+| Manual resume | Args contain "resume" or "continue" | -> handleResume (monitor.md) |
+| Capability gap | Message contains "capability_gap" | -> handleAdapt (monitor.md) |
+| Pipeline complete | All tasks have status "completed" | -> handleComplete (monitor.md) |
+| Interrupted session | Active/paused session exists in .workflow/.team/MD-* | -> Phase 0 |
+| New session | None of above | -> Phase 1 |
+
+For callback/check/resume/adapt/complete: load `@commands/monitor.md`, execute matched handler, STOP.
+
+## Phase 0: Session Resume Check
+
+1. Scan `.workflow/.team/MD-*/.msg/meta.json` for active/paused sessions
+2. No sessions -> Phase 1
+3. Single session -> reconcile (audit TaskList, reset in_progress->pending, rebuild team, kick first ready task)
+4. Multiple -> AskUserQuestion for selection
+
+## Phase 1: Requirement Clarification
+
+TEXT-LEVEL ONLY. No source code reading.
+
+1. Parse task description from arguments
+2. Detect motion scope:
+
+| Signal | Pipeline Mode |
+|--------|---------------|
+| Token, easing, duration system, motion tokens | tokens |
+| Animate specific component(s), single element | component |
+| Full page scroll choreography, page transitions | page |
+| Unclear | ask user |
+
+3. Ask for missing parameters if scope unclear:
+   ```
+   AskUserQuestion({
+     questions: [
+       { question: "Motion design scope?", header: "Scope", options: [
+         { label: "Animation token system", description: "Easing functions, duration scale, stagger formulas" },
+         { label: "Component animation", description: "Animate specific component(s) with transitions" },
+         { label: "Page scroll choreography", description: "Full page scroll-triggered reveals and transitions" }
+       ]},
+       { question: "Target framework?", header: "Framework", options: [
+         { label: "CSS-only" }, { label: "React" },
+         { label: "Vue" }, { label: "Vanilla JS" }, { label: "Other" }
+       ]}
+     ]
+   })
+   ```
+4. Delegate to `@commands/analyze.md` -> output scope context
+5. Record: pipeline_mode, framework, complexity
+
+## Phase 2: Create Team + Initialize Session
+
+1. Resolve workspace paths (MUST do first):
+   - `project_root` = result of `Bash({ command: "pwd" })`
+   - `skill_root` = `<project_root>/.claude/skills/team-motion-design`
+2. Generate session ID: `MD-<slug>-<YYYY-MM-DD>`
+3. Create session folder structure:
+   ```
+   .workflow/.team/MD-<slug>-<date>/research/perf-traces/
+   .workflow/.team/MD-<slug>-<date>/choreography/sequences/
+   .workflow/.team/MD-<slug>-<date>/animations/keyframes/
+   .workflow/.team/MD-<slug>-<date>/animations/orchestrators/
+   .workflow/.team/MD-<slug>-<date>/testing/traces/
+   .workflow/.team/MD-<slug>-<date>/testing/reports/
+   .workflow/.team/MD-<slug>-<date>/wisdom/
+   .workflow/.team/MD-<slug>-<date>/.msg/
+   ```
+4. Initialize `.msg/meta.json` via team_msg state_update with pipeline metadata
+5. TeamCreate(team_name="motion-design")
+6. Do NOT spawn workers yet - deferred to Phase 4
+
+## Phase 3: Create Task Chain
+
+Delegate to `@commands/dispatch.md`. Task chains by mode:
+
+| Mode | Task Chain |
+|------|------------|
+| tokens | MRESEARCH-001 -> CHOREO-001 -> ANIM-001 -> MTEST-001 |
+| component | MRESEARCH-001 -> CHOREO-001 -> ANIM-001 -> MTEST-001 (GC loop) |
+| page | MRESEARCH-001 -> CHOREO-001 -> [ANIM-001..N parallel] -> MTEST-001 |
+
+## Phase 4: Spawn-and-Stop
+
+Delegate to `@commands/monitor.md#handleSpawnNext`:
+1. Find ready tasks (pending + blockedBy resolved)
+2. Spawn team-worker agents (see SKILL.md Spawn Template)
+3. Output status summary
+4. STOP
+
+## Phase 5: Report + Completion Action
+
+1. Read session state -> collect all results
+2. List deliverables:
+
+| Deliverable | Path |
+|-------------|------|
+| Animation Inventory | <session>/research/animation-inventory.json |
+| Performance Baseline | <session>/research/performance-baseline.json |
+| Easing Catalog | <session>/research/easing-catalog.json |
+| Motion Tokens | <session>/choreography/motion-tokens.json |
+| Choreography Sequences | <session>/choreography/sequences/*.md |
+| CSS Keyframes | <session>/animations/keyframes/*.css |
+| JS Orchestrators | <session>/animations/orchestrators/*.js |
+| Performance Reports | <session>/testing/reports/perf-report-*.md |
+
+3. Calculate: completed_tasks, gc_rounds, perf_score, final_fps
+4. Output pipeline summary with [coordinator] prefix
+5. Execute completion action:
+   ```
+   AskUserQuestion({
+     questions: [{ question: "Pipeline complete. What next?", header: "Completion", options: [
+       { label: "Archive & Clean", description: "Archive session and clean up team resources" },
+       { label: "Keep Active", description: "Keep session for follow-up work" },
+       { label: "Export Results", description: "Export deliverables to specified location" }
+     ]}]
+   })
+   ```
+
+## Error Handling
+
+| Error | Resolution |
+|-------|------------|
+| Task timeout | Log, mark failed, ask user to retry or skip |
+| Worker crash | Reset task to pending, respawn worker |
+| Dependency cycle | Detect, report to user, halt |
+| Invalid scope | Reject with error, ask to clarify |
+| Session corruption | Attempt recovery, fallback to manual reconciliation |
+| GC loop stuck > 2 rounds | Escalate to user: accept / try one more / terminate |

package/.claude/skills/team-motion-design/roles/motion-researcher/role.md

@@ -1,115 +1,115 @@
----
-role: motion-researcher
-prefix: MRESEARCH
-inner_loop: false
-message_types: [state_update]
----
-
-# Motion & Animation Researcher
-
-Audit existing animations in the codebase, measure paint/composite costs via Chrome DevTools performance traces, and catalog easing patterns. Produce foundation data for downstream choreographer, animator, and motion-tester roles.
-
-## Phase 2: Context & Environment Detection
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
-
-1. Extract session path and target scope from task description
-2. Detect project type and tech stack from package.json or equivalent:
-
-| Package | Detected Stack |
-|---------|---------------|
-| next | nextjs |
-| react | react |
-| vue | vue |
-| svelte | svelte |
-| gsap | gsap |
-| framer-motion | framer-motion |
-| @react-spring/web | react-spring |
-| (default) | css-vanilla |
-
-3. Use CLI tools (e.g., `maestro delegate "..." --to gemini --mode analysis`) or direct tools (Glob, Grep) to scan for existing animations, transitions, keyframes
-4. Read framework context from session config
-
-## Phase 3: Research Execution
-
-Execute 3 analysis streams:
-
-**Stream 1 -- Animation Inventory**:
-- Search for CSS @keyframes declarations (pattern: `@keyframes`)
-- Search for CSS transition properties (pattern: `transition:`, `transition-property:`)
-- Search for JS animation APIs (requestAnimationFrame, Web Animations API, GSAP, Framer Motion)
-- Search for IntersectionObserver usage (scroll-triggered animations)
-- Catalog each animation: name, properties animated, duration, easing, trigger mechanism
-- Flag unsafe properties (width, height, top, left, margin, padding, color, background-color)
-- Output: `<session>/research/animation-inventory.json`
-  ```json
-  {
-    "css_keyframes": [{ "name": "", "file": "", "properties": [], "safe": true }],
-    "css_transitions": [{ "file": "", "line": 0, "properties": [], "duration": "", "easing": "" }],
-    "js_animations": [{ "file": "", "type": "rAF|WAAPI|gsap|framer", "properties": [] }],
-    "scroll_triggers": [{ "file": "", "type": "IntersectionObserver|scroll-event", "threshold": 0 }],
-    "unsafe_animations": [{ "file": "", "line": 0, "property": "", "suggestion": "" }],
-    "summary": { "total": 0, "safe_count": 0, "unsafe_count": 0 }
-  }
-  ```
-
-**Stream 2 -- Performance Baseline**:
-- If Chrome DevTools MCP available:
-  - Start performance trace: `mcp__chrome-devtools__performance_start_trace()`
-  - Trigger page load or scroll interaction
-  - Stop trace: `mcp__chrome-devtools__performance_stop_trace()`
-  - Analyze: `mcp__chrome-devtools__performance_analyze_insight()`
-  - Extract: FPS data, paint/composite times, layout thrashing events, layer count
-- If Chrome DevTools unavailable:
-  - Static analysis: count layout-triggering properties, estimate performance from code patterns
-  - Mark `_source: "static-analysis"`
-- Output: `<session>/research/performance-baseline.json`
-  ```json
-  {
-    "_source": "chrome-devtools|static-analysis",
-    "fps": { "average": 0, "minimum": 0, "drops": [] },
-    "paint_time_ms": 0,
-    "composite_time_ms": 0,
-    "layout_thrashing": [],
-    "layer_count": 0,
-    "will_change_count": 0
-  }
-  ```
-
-**Stream 3 -- Easing Catalog**:
-- Search for cubic-bezier declarations in CSS
-- Search for named easing functions (ease, ease-in, ease-out, ease-in-out, linear)
-- Search for JS easing implementations (spring physics, custom curves)
-- Catalog each: name/value, usage count, context (hover, scroll, entry)
-- Recommend additions based on gaps (missing ease-spring, missing stagger patterns)
-- Reference specs/motion-tokens.md for recommended token schema
-- Output: `<session>/research/easing-catalog.json`
-  ```json
-  {
-    "existing": [{ "value": "", "usage_count": 0, "contexts": [] }],
-    "recommended_additions": [{ "name": "", "value": "", "reason": "" }],
-    "duration_patterns": [{ "value": "", "usage_count": 0, "contexts": [] }],
-    "stagger_patterns": [{ "found": false, "details": "" }]
-  }
-  ```
-
-Compile research summary metrics: animation_count, safe_percentage, fps_baseline, easing_count, has_reduced_motion.
-
-## Phase 4: Validation & Output
-
-1. Verify all 3 output files exist and contain valid JSON with required fields:
-
-| File | Required Fields |
-|------|----------------|
-| animation-inventory.json | css_keyframes array, summary |
-| performance-baseline.json | _source |
-| easing-catalog.json | existing array |
-
-2. If any file missing or invalid, re-run corresponding stream
-
-3. Update `<session>/wisdom/.msg/meta.json` under `motion-researcher` namespace:
-   - Read existing -> merge `{ "motion-researcher": { detected_stack, animation_count, safe_percentage, fps_baseline, easing_count, has_reduced_motion } }` -> write back
+---
+role: motion-researcher
+prefix: MRESEARCH
+inner_loop: false
+message_types: [state_update]
+---
+
+# Motion & Animation Researcher
+
+Audit existing animations in the codebase, measure paint/composite costs via Chrome DevTools performance traces, and catalog easing patterns. Produce foundation data for downstream choreographer, animator, and motion-tester roles.
+
+## Phase 2: Context & Environment Detection
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
+
+1. Extract session path and target scope from task description
+2. Detect project type and tech stack from package.json or equivalent:
+
+| Package | Detected Stack |
+|---------|---------------|
+| next | nextjs |
+| react | react |
+| vue | vue |
+| svelte | svelte |
+| gsap | gsap |
+| framer-motion | framer-motion |
+| @react-spring/web | react-spring |
+| (default) | css-vanilla |
+
+3. Use CLI tools (e.g., `maestro delegate "..." --to agy --mode analysis`) or direct tools (Glob, Grep) to scan for existing animations, transitions, keyframes
+4. Read framework context from session config
+
+## Phase 3: Research Execution
+
+Execute 3 analysis streams:
+
+**Stream 1 -- Animation Inventory**:
+- Search for CSS @keyframes declarations (pattern: `@keyframes`)
+- Search for CSS transition properties (pattern: `transition:`, `transition-property:`)
+- Search for JS animation APIs (requestAnimationFrame, Web Animations API, GSAP, Framer Motion)
+- Search for IntersectionObserver usage (scroll-triggered animations)
+- Catalog each animation: name, properties animated, duration, easing, trigger mechanism
+- Flag unsafe properties (width, height, top, left, margin, padding, color, background-color)
+- Output: `<session>/research/animation-inventory.json`
+  ```json
+  {
+    "css_keyframes": [{ "name": "", "file": "", "properties": [], "safe": true }],
+    "css_transitions": [{ "file": "", "line": 0, "properties": [], "duration": "", "easing": "" }],
+    "js_animations": [{ "file": "", "type": "rAF|WAAPI|gsap|framer", "properties": [] }],
+    "scroll_triggers": [{ "file": "", "type": "IntersectionObserver|scroll-event", "threshold": 0 }],
+    "unsafe_animations": [{ "file": "", "line": 0, "property": "", "suggestion": "" }],
+    "summary": { "total": 0, "safe_count": 0, "unsafe_count": 0 }
+  }
+  ```
+
+**Stream 2 -- Performance Baseline**:
+- If Chrome DevTools MCP available:
+  - Start performance trace: `mcp__chrome-devtools__performance_start_trace()`
+  - Trigger page load or scroll interaction
+  - Stop trace: `mcp__chrome-devtools__performance_stop_trace()`
+  - Analyze: `mcp__chrome-devtools__performance_analyze_insight()`
+  - Extract: FPS data, paint/composite times, layout thrashing events, layer count
+- If Chrome DevTools unavailable:
+  - Static analysis: count layout-triggering properties, estimate performance from code patterns
+  - Mark `_source: "static-analysis"`
+- Output: `<session>/research/performance-baseline.json`
+  ```json
+  {
+    "_source": "chrome-devtools|static-analysis",
+    "fps": { "average": 0, "minimum": 0, "drops": [] },
+    "paint_time_ms": 0,
+    "composite_time_ms": 0,
+    "layout_thrashing": [],
+    "layer_count": 0,
+    "will_change_count": 0
+  }
+  ```
+
+**Stream 3 -- Easing Catalog**:
+- Search for cubic-bezier declarations in CSS
+- Search for named easing functions (ease, ease-in, ease-out, ease-in-out, linear)
+- Search for JS easing implementations (spring physics, custom curves)
+- Catalog each: name/value, usage count, context (hover, scroll, entry)
+- Recommend additions based on gaps (missing ease-spring, missing stagger patterns)
+- Reference specs/motion-tokens.md for recommended token schema
+- Output: `<session>/research/easing-catalog.json`
+  ```json
+  {
+    "existing": [{ "value": "", "usage_count": 0, "contexts": [] }],
+    "recommended_additions": [{ "name": "", "value": "", "reason": "" }],
+    "duration_patterns": [{ "value": "", "usage_count": 0, "contexts": [] }],
+    "stagger_patterns": [{ "found": false, "details": "" }]
+  }
+  ```
+
+Compile research summary metrics: animation_count, safe_percentage, fps_baseline, easing_count, has_reduced_motion.
+
+## Phase 4: Validation & Output
+
+1. Verify all 3 output files exist and contain valid JSON with required fields:
+
+| File | Required Fields |
+|------|----------------|
+| animation-inventory.json | css_keyframes array, summary |
+| performance-baseline.json | _source |
+| easing-catalog.json | existing array |
+
+2. If any file missing or invalid, re-run corresponding stream
+
+3. Update `<session>/wisdom/.msg/meta.json` under `motion-researcher` namespace:
+   - Read existing -> merge `{ "motion-researcher": { detected_stack, animation_count, safe_percentage, fps_baseline, easing_count, has_reduced_motion } }` -> write back