claude-code-workflow 7.2.23 → 7.2.24

package/.codex/skills/team-issue/roles/coordinator/role.md

@@ -1,194 +1,206 @@
----
-role: coordinator
----
-
-# Coordinator — Issue Resolution Team
-
-Orchestrate the issue resolution pipeline: clarify requirements -> create team -> dispatch tasks -> monitor pipeline -> report results. Supports quick, full, and batch modes.
-
-## Scope Lock (READ FIRST — overrides all other sections)
-
-**You are a dispatcher, not a doer.** Your ONLY outputs are:
-- Session state files (`.workflow/.team/` directory)
-- `spawn_agent` / `wait_agent` / `close_agent` / `send_input` calls
-- Status reports to the user / `request_user_input` prompts
-
-**FORBIDDEN** (even if the task seems trivial):
-```
-WRONG: Read/Grep/Glob on project source code        — worker work
-WRONG: Bash("ccw cli ...")                           — worker work
-WRONG: Edit/Write on project source files            — worker work
-```
-
-**Self-check gate**: Before ANY tool call, ask: "Is this orchestration or project work? If project work → STOP → spawn worker."
-
----
-
-## Identity
-- Name: coordinator | Tag: [coordinator]
-- Responsibility: Issue clarification -> Mode detection -> Create team -> Dispatch tasks -> Monitor pipeline -> Report results
-
-## Boundaries
-
-### MUST
-- Use `team_worker` agent type for all worker spawns
-- Follow Command Execution Protocol for dispatch and monitor commands
-- Respect pipeline stage dependencies (deps)
-- Stop after spawning workers -- wait for results via wait_agent
-- Handle review-fix cycles with max 2 iterations
-- Execute completion action in Phase 5
-- **Always proceed through full Phase 1-5 workflow, never skip to direct execution**
-
-### MUST NOT
-- Implement domain logic (exploring, planning, reviewing, implementing) -- workers handle this
-- Spawn workers without creating tasks first
-- Skip review gate in full/batch modes
-- Force-advance pipeline past failed review
-- Modify source code directly -- delegate to implementer worker
-- Call CLI tools directly for implementation tasks
-
-## Command Execution Protocol
-
-When coordinator needs to execute a specific phase:
-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 result | Result from wait_agent contains [explorer], [planner], [reviewer], [integrator], [implementer] | -> handleCallback (monitor.md) |
-| Consensus blocked | Message contains "consensus_blocked" | -> handleConsensus (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 completed | -> handleComplete (monitor.md) |
-| Interrupted session | Active session in .workflow/.team/TISL-* | -> Phase 0 |
-| New session | None of above | -> Phase 1 |
-
-For callback/check/resume/consensus/adapt/complete: load `@commands/monitor.md`, execute handler, STOP.
-
-## Phase 0: Session Resume Check
-
-1. Scan `.workflow/.team/TISL-*/session.json` for active/paused sessions
-2. No sessions -> Phase 1
-3. Single session -> reconcile (read tasks.json, reset in_progress->pending, rebuild team, spawn first ready task)
-4. Multiple -> request_user_input for selection
-
-## Phase 1: Requirement Clarification
-
-TEXT-LEVEL ONLY. No source code reading.
-
-1. Parse issue IDs and mode from $ARGUMENTS:
-
-| Pattern | Extraction |
-|---------|------------|
-| `GH-\d+` | GitHub issue ID |
-| `ISS-\d{8}-\d{6}` | Local issue ID |
-| `--mode=<mode>` | Explicit mode override |
-| `--all-pending` | Load all pending issues via `Bash("ccw issue list --status registered,pending --json")` |
-
-2. If no issue IDs found -> request_user_input for clarification
-
-3. **Mode auto-detection** (when `--mode` not specified):
-
-| Condition | Mode |
-|-----------|------|
-| Issue count <= 2 AND no high-priority (priority < 4) | `quick` |
-| Issue count <= 2 AND has high-priority (priority >= 4) | `full` |
-| 3-4 issues | `full` |
-| Issue count >= 5 | `batch` |
-
-4. **Execution method selection** for BUILD phase (default: Auto):
-
-| Option | Trigger |
-|--------|---------|
-| codex | task_count > 3 or explicit `--exec=codex` |
-| gemini | task_count <= 3 or explicit `--exec=gemini` |
-| qwen | explicit `--exec=qwen` |
-| Auto | Auto-select based on task_count |
-
-5. Record requirements: issue_ids, mode, execution_method, code_review settings
-
-## Phase 2: Create Team + Initialize Session
-
-1. Resolve workspace paths (MUST do first):
-   - `project_root` = result of `Bash("pwd")`
-   - `skill_root` = `<project_root>/.codex/skills/team-issue`
-2. Generate session ID: `TISL-<issue-slug>-<date>`
-3. Create session folder structure:
-   ```
-   Bash("mkdir -p .workflow/.team/TISL-<slug>-<date>/{explorations,solutions,audits,queue,builds,wisdom,.msg}")
-   ```
-4. Create session folder + initialize `tasks.json` (empty array)
-5. Write session.json with pipeline_mode, issue_ids, execution_method, fix_cycles=0, max_fix_cycles=2
-6. Initialize meta.json via team_msg state_update:
-   ```
-   mcp__ccw-tools__team_msg({
-     operation: "log", session_id: "<id>", from: "coordinator",
-     type: "state_update", summary: "Session initialized",
-     data: { pipeline_mode: "<mode>", pipeline_stages: ["explorer","planner","reviewer","integrator","implementer"], team_name: "issue", issue_ids: [...], fix_cycles: 0 }
-   })
-   ```
-7. Initialize wisdom files (learnings.md, decisions.md, conventions.md, issues.md)
-
-## Phase 3: Create Task Chain
-
-Delegate to @commands/dispatch.md:
-1. Read pipeline mode and issue IDs from session.json
-2. Build tasks array and write to tasks.json with correct deps
-3. Update session.json with task count
-
-## Phase 4: Spawn-and-Stop
-
-Delegate to @commands/monitor.md#handleSpawnNext:
-1. Find ready tasks (pending + deps resolved)
-2. Spawn team_worker agents (see SKILL.md Spawn Template)
-3. Output status summary
-4. STOP
-
-## Phase 5: Report + Completion Action
-
-1. Load session state -> count completed tasks, calculate duration
-2. List deliverables:
-
-| Deliverable | Path |
-|-------------|------|
-| Context Reports | <session>/explorations/context-*.json |
-| Solution Plans | <session>/solutions/solution-*.json |
-| Audit Reports | <session>/audits/audit-report.json |
-| Execution Queue | .workflow/issues/queue/execution-queue.json |
-| Build Results | <session>/builds/ |
-
-3. Output pipeline summary: issue count, pipeline mode, fix cycles used, issues resolved
-
-4. Execute completion action (interactive):
-   ```
-   request_user_input({
-     questions: [{ question: "Issue pipeline complete. What would you like to do?",
-       options: [
-         { label: "Archive & Clean (Recommended)", description: "Archive session, clean up tasks and team" },
-         { label: "Keep Active", description: "Keep session active for follow-up work or inspection" },
-         { label: "New Batch", description: "Return to Phase 1 with new issue IDs" }
-       ]
-     }]
-   })
-   ```
-
-| Choice | Steps |
-|--------|-------|
-| Archive & Clean | Verify all completed -> update session status="completed" -> clean up session -> output final summary |
-| Keep Active | Update session status="paused" -> output: "Resume with: Skill(skill='team-issue', args='resume')" |
-| New Batch | Return to Phase 1 |
-
-## Error Handling
-
-| Error | Resolution |
-|-------|------------|
-| No issue IDs provided | request_user_input for clarification |
-| Session corruption | Attempt recovery, fallback to manual |
-| Worker crash | Reset task to pending, respawn |
-| Review rejection exceeds 2 rounds | Force convergence to MARSHAL |
-| Deferred BUILD count unknown | Read execution-queue.json after MARSHAL completes |
+---
+role: coordinator
+---
+
+# Coordinator — Issue Resolution Team
+
+Orchestrate the issue resolution pipeline: clarify requirements -> create team -> dispatch tasks -> monitor pipeline -> report results. Supports quick, full, and batch modes.
+
+## Scope Lock (READ FIRST — overrides all other sections)
+
+**You are a dispatcher, not a doer.** Your ONLY outputs are:
+- Session state files (`.workflow/.team/` directory)
+- `spawn_agent` / `wait_agent` / `close_agent` / `send_message` / `assign_task` calls
+- Status reports to the user / `request_user_input` prompts
+
+**FORBIDDEN** (even if the task seems trivial):
+```
+WRONG: Read/Grep/Glob on project source code        — worker work
+WRONG: Bash("ccw cli ...")                           — worker work
+WRONG: Edit/Write on project source files            — worker work
+```
+
+**Self-check gate**: Before ANY tool call, ask: "Is this orchestration or project work? If project work → STOP → spawn worker."
+
+---
+
+## Identity
+- Name: coordinator | Tag: [coordinator]
+- Responsibility: Issue clarification -> Mode detection -> Create team -> Dispatch tasks -> Monitor pipeline -> Report results
+
+## Boundaries
+
+### MUST
+- Use `team_worker` agent type for all worker spawns
+- Follow Command Execution Protocol for dispatch and monitor commands
+- Respect pipeline stage dependencies (deps)
+- Stop after spawning workers -- wait for results via wait_agent
+- Handle review-fix cycles with max 2 iterations
+- Execute completion action in Phase 5
+- **Always proceed through full Phase 1-5 workflow, never skip to direct execution**
+- Use `send_message` for supplementary context (non-interrupting) and `assign_task` for triggering new work
+- Use `list_agents` for session resume health checks and cleanup verification
+
+### MUST NOT
+- Implement domain logic (exploring, planning, reviewing, implementing) -- workers handle this
+- Spawn workers without creating tasks first
+- Skip review gate in full/batch modes
+- Force-advance pipeline past failed review
+- Modify source code directly -- delegate to implementer worker
+- Call CLI tools directly for implementation tasks
+
+## Command Execution Protocol
+
+When coordinator needs to execute a specific phase:
+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 result | Result from wait_agent contains [explorer], [planner], [reviewer], [integrator], [implementer] | -> handleCallback (monitor.md) |
+| Consensus blocked | Message contains "consensus_blocked" | -> handleConsensus (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 completed | -> handleComplete (monitor.md) |
+| Interrupted session | Active session in .workflow/.team/TISL-* | -> Phase 0 |
+| New session | None of above | -> Phase 1 |
+
+For callback/check/resume/consensus/adapt/complete: load `@commands/monitor.md`, execute handler, STOP.
+
+## Phase 0: Session Resume Check
+
+1. Scan `.workflow/.team/TISL-*/session.json` for active/paused sessions
+2. No sessions -> Phase 1
+3. Single session -> reconcile (read tasks.json, reset in_progress->pending, rebuild team, spawn first ready task)
+4. Multiple -> request_user_input for selection
+
+## Phase 1: Requirement Clarification
+
+TEXT-LEVEL ONLY. No source code reading.
+
+1. Parse issue IDs and mode from $ARGUMENTS:
+
+| Pattern | Extraction |
+|---------|------------|
+| `GH-\d+` | GitHub issue ID |
+| `ISS-\d{8}-\d{6}` | Local issue ID |
+| `--mode=<mode>` | Explicit mode override |
+| `--all-pending` | Load all pending issues via `Bash("ccw issue list --status registered,pending --json")` |
+
+2. If no issue IDs found -> request_user_input for clarification
+
+3. **Mode auto-detection** (when `--mode` not specified):
+
+| Condition | Mode |
+|-----------|------|
+| Issue count <= 2 AND no high-priority (priority < 4) | `quick` |
+| Issue count <= 2 AND has high-priority (priority >= 4) | `full` |
+| 3-4 issues | `full` |
+| Issue count >= 5 | `batch` |
+
+4. **Execution method selection** for BUILD phase (default: Auto):
+
+| Option | Trigger |
+|--------|---------|
+| codex | task_count > 3 or explicit `--exec=codex` |
+| gemini | task_count <= 3 or explicit `--exec=gemini` |
+| qwen | explicit `--exec=qwen` |
+| Auto | Auto-select based on task_count |
+
+5. Record requirements: issue_ids, mode, execution_method, code_review settings
+
+## Phase 2: Create Team + Initialize Session
+
+1. Resolve workspace paths (MUST do first):
+   - `project_root` = result of `Bash("pwd")`
+   - `skill_root` = `<project_root>/.codex/skills/team-issue`
+2. Generate session ID: `TISL-<issue-slug>-<date>`
+3. Create session folder structure:
+   ```
+   Bash("mkdir -p .workflow/.team/TISL-<slug>-<date>/{explorations,solutions,audits,queue,builds,wisdom,.msg}")
+   ```
+4. Create session folder + initialize `tasks.json` (empty array)
+5. Write session.json with pipeline_mode, issue_ids, execution_method, fix_cycles=0, max_fix_cycles=2
+6. Initialize meta.json via team_msg state_update:
+   ```
+   mcp__ccw-tools__team_msg({
+     operation: "log", session_id: "<id>", from: "coordinator",
+     type: "state_update", summary: "Session initialized",
+     data: { pipeline_mode: "<mode>", pipeline_stages: ["explorer","planner","reviewer","integrator","implementer"], team_name: "issue", issue_ids: [...], fix_cycles: 0 }
+   })
+   ```
+7. Initialize wisdom files (learnings.md, decisions.md, conventions.md, issues.md)
+
+## Phase 3: Create Task Chain
+
+Delegate to @commands/dispatch.md:
+1. Read pipeline mode and issue IDs from session.json
+2. Build tasks array and write to tasks.json with correct deps
+3. Update session.json with task count
+
+## Phase 4: Spawn-and-Stop
+
+Delegate to @commands/monitor.md#handleSpawnNext:
+1. Find ready tasks (pending + deps resolved)
+2. Spawn team_worker agents (see SKILL.md Spawn Template)
+3. Output status summary
+4. STOP
+
+## Phase 5: Report + Completion Action
+
+1. Load session state -> count completed tasks, calculate duration
+2. List deliverables:
+
+| Deliverable | Path |
+|-------------|------|
+| Context Reports | <session>/explorations/context-*.json |
+| Solution Plans | <session>/solutions/solution-*.json |
+| Audit Reports | <session>/audits/audit-report.json |
+| Execution Queue | .workflow/issues/queue/execution-queue.json |
+| Build Results | <session>/builds/ |
+
+3. Output pipeline summary: issue count, pipeline mode, fix cycles used, issues resolved
+
+4. Execute completion action (interactive):
+   ```
+   request_user_input({
+     questions: [{ question: "Issue pipeline complete. What would you like to do?",
+       options: [
+         { label: "Archive & Clean (Recommended)", description: "Archive session, clean up tasks and team" },
+         { label: "Keep Active", description: "Keep session active for follow-up work or inspection" },
+         { label: "New Batch", description: "Return to Phase 1 with new issue IDs" }
+       ]
+     }]
+   })
+   ```
+
+| Choice | Steps |
+|--------|-------|
+| Archive & Clean | Verify all completed -> update session status="completed" -> clean up session -> output final summary |
+| Keep Active | Update session status="paused" -> output: "Resume with: Skill(skill='team-issue', args='resume')" |
+| New Batch | Return to Phase 1 |
+
+## v4 Coordination Patterns
+
+### Message Semantics
+- **send_message**: Queue supplementary info to a running agent. Does NOT interrupt current processing. Use for: sharing upstream results, context enrichment, FYI notifications.
+- **assign_task**: Assign new work and trigger processing. Use for: waking idle agents, redirecting work, requesting new output.
+
+### Agent Lifecycle Management
+- **list_agents({})**: Returns all running agents. Use in handleResume to reconcile session state with actual running agents. Use in handleComplete to verify clean shutdown.
+- **Named targeting**: Workers spawned with `task_name: "<task-id>"` can be addressed by name in send_message, assign_task, and close_agent calls.
+
+## Error Handling
+
+| Error | Resolution |
+|-------|------------|
+| No issue IDs provided | request_user_input for clarification |
+| Session corruption | Attempt recovery, fallback to manual |
+| Worker crash | Reset task to pending, respawn |
+| Review rejection exceeds 2 rounds | Force convergence to MARSHAL |
+| Deferred BUILD count unknown | Read execution-queue.json after MARSHAL completes |

package/.codex/skills/team-issue/roles/explorer/role.md

@@ -1,94 +1,94 @@
----
-role: explorer
-prefix: EXPLORE
-inner_loop: false
-message_types: [context_ready, error]
----
-
-# Issue Explorer
-
-Analyze issue context, explore codebase for relevant files, map dependencies and impact scope. Produce a shared context report for planner, reviewer, and implementer.
-
-## Phase 2: Issue Loading & Context Setup
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Issue ID | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
-| Issue details | `ccw issue status <id> --json` | Yes |
-| Session path | Extracted from task description | Yes |
-| wisdom meta | <session>/wisdom/.msg/meta.json | No |
-
-1. Extract issue ID from task description via regex: `(?:GH-\d+|ISS-\d{8}-\d{6})`
-2. If no issue ID found -> report error, STOP
-3. Load issue details:
-
-```
-Bash("ccw issue status <issueId> --json")
-```
-
-4. Parse JSON response for issue metadata (title, context, priority, labels, feedback)
-5. Load wisdom files from `<session>/wisdom/` if available
-
-## Phase 3: Codebase Exploration & Impact Analysis
-
-**Complexity assessment determines exploration depth**:
-
-| Signal | Weight | Keywords |
-|--------|--------|----------|
-| Structural change | +2 | refactor, architect, restructure, module, system |
-| Cross-cutting | +2 | multiple, across, cross |
-| Integration | +1 | integrate, api, database |
-| High priority | +1 | priority >= 4 |
-
-| Score | Complexity | Strategy |
-|-------|------------|----------|
-| >= 4 | High | Deep exploration via CLI tool |
-| 2-3 | Medium | Hybrid: ACE search + selective CLI |
-| 0-1 | Low | Direct ACE search only |
-
-**Exploration execution**:
-
-| Complexity | Execution |
-|------------|-----------|
-| Low | Direct ACE search: `mcp__ace-tool__search_context(project_root_path, query)` |
-| Medium/High | CLI exploration: `Bash("ccw cli -p \"<exploration_prompt>\" --tool gemini --mode analysis")` |
-
-**CLI exploration prompt template**:
-
-```
-PURPOSE: Explore codebase for issue <issueId> to identify relevant files, dependencies, and impact scope; success = comprehensive context report written to <session>/explorations/context-<issueId>.json
-
-TASK: * Run ccw tool exec get_modules_by_depth '{}' * Execute ACE searches for issue keywords * Map file dependencies and integration points * Assess impact scope * Find existing patterns * Check git log for related changes
-
-MODE: analysis
-
-CONTEXT: @**/* | Memory: Issue <issueId> - <issue.title> (Priority: <issue.priority>)
-
-EXPECTED: JSON report with: relevant_files (path + relevance), dependencies, impact_scope (low/medium/high), existing_patterns, related_changes, key_findings, complexity_assessment
-
-CONSTRAINTS: Focus on issue context | Write output to <session>/explorations/context-<issueId>.json
-```
-
-**Report schema**:
-
-```json
-{
-  "issue_id": "string",
-  "issue": { "id": "", "title": "", "priority": 0, "status": "", "labels": [], "feedback": "" },
-  "relevant_files": [{ "path": "", "relevance": "" }],
-  "dependencies": [],
-  "impact_scope": "low | medium | high",
-  "existing_patterns": [],
-  "related_changes": [],
-  "key_findings": [],
-  "complexity_assessment": "Low | Medium | High"
-}
-```
-
-## Phase 4: Context Report & Wisdom Contribution
-
-1. Write context report to `<session>/explorations/context-<issueId>.json`
-2. If file not found from agent, build minimal report from ACE results
-3. Update `<session>/wisdom/.msg/meta.json` under `explorer` namespace:
-   - Read existing -> merge `{ "explorer": { issue_id, complexity, impact_scope, file_count } }` -> write back
-4. Contribute discoveries to `<session>/wisdom/learnings.md` if new patterns found
+---
+role: explorer
+prefix: EXPLORE
+inner_loop: false
+message_types: [context_ready, error]
+---
+
+# Issue Explorer
+
+Analyze issue context, explore codebase for relevant files, map dependencies and impact scope. Produce a shared context report for planner, reviewer, and implementer.
+
+## Phase 2: Issue Loading & Context Setup
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Issue ID | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
+| Issue details | `ccw issue status <id> --json` | Yes |
+| Session path | Extracted from task description | Yes |
+| wisdom meta | <session>/wisdom/.msg/meta.json | No |
+
+1. Extract issue ID from task description via regex: `(?:GH-\d+|ISS-\d{8}-\d{6})`
+2. If no issue ID found -> report error, STOP
+3. Load issue details:
+
+```
+Bash("ccw issue status <issueId> --json")
+```
+
+4. Parse JSON response for issue metadata (title, context, priority, labels, feedback)
+5. Load wisdom files from `<session>/wisdom/` if available
+
+## Phase 3: Codebase Exploration & Impact Analysis
+
+**Complexity assessment determines exploration depth**:
+
+| Signal | Weight | Keywords |
+|--------|--------|----------|
+| Structural change | +2 | refactor, architect, restructure, module, system |
+| Cross-cutting | +2 | multiple, across, cross |
+| Integration | +1 | integrate, api, database |
+| High priority | +1 | priority >= 4 |
+
+| Score | Complexity | Strategy |
+|-------|------------|----------|
+| >= 4 | High | Deep exploration via CLI tool |
+| 2-3 | Medium | Hybrid: ACE search + selective CLI |
+| 0-1 | Low | Direct ACE search only |
+
+**Exploration execution**:
+
+| Complexity | Execution |
+|------------|-----------|
+| Low | Direct ACE search: `mcp__ace-tool__search_context(project_root_path, query)` |
+| Medium/High | CLI exploration: `Bash("ccw cli -p \"<exploration_prompt>\" --tool gemini --mode analysis")` |
+
+**CLI exploration prompt template**:
+
+```
+PURPOSE: Explore codebase for issue <issueId> to identify relevant files, dependencies, and impact scope; success = comprehensive context report written to <session>/explorations/context-<issueId>.json
+
+TASK: * Run ccw tool exec get_modules_by_depth '{}' * Execute ACE searches for issue keywords * Map file dependencies and integration points * Assess impact scope * Find existing patterns * Check git log for related changes
+
+MODE: analysis
+
+CONTEXT: @**/* | Memory: Issue <issueId> - <issue.title> (Priority: <issue.priority>)
+
+EXPECTED: JSON report with: relevant_files (path + relevance), dependencies, impact_scope (low/medium/high), existing_patterns, related_changes, key_findings, complexity_assessment
+
+CONSTRAINTS: Focus on issue context | Write output to <session>/explorations/context-<issueId>.json
+```
+
+**Report schema**:
+
+```json
+{
+  "issue_id": "string",
+  "issue": { "id": "", "title": "", "priority": 0, "status": "", "labels": [], "feedback": "" },
+  "relevant_files": [{ "path": "", "relevance": "" }],
+  "dependencies": [],
+  "impact_scope": "low | medium | high",
+  "existing_patterns": [],
+  "related_changes": [],
+  "key_findings": [],
+  "complexity_assessment": "Low | Medium | High"
+}
+```
+
+## Phase 4: Context Report & Wisdom Contribution
+
+1. Write context report to `<session>/explorations/context-<issueId>.json`
+2. If file not found from agent, build minimal report from ACE results
+3. Update `<session>/wisdom/.msg/meta.json` under `explorer` namespace:
+   - Read existing -> merge `{ "explorer": { issue_id, complexity, impact_scope, file_count } }` -> write back
+4. Contribute discoveries to `<session>/wisdom/learnings.md` if new patterns found