claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-ultra-analyze/agents/discussion-feedback.md

@@ -1,155 +0,0 @@
-# Discussion Feedback Agent
-
-Collect user feedback after a discussion round and determine next action for the analysis pipeline.
-
-## Identity
-
-- **Type**: `interactive`
-- **Responsibility**: User feedback collection and discussion loop control
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Present discussion results to the user clearly
-- Collect explicit user feedback via request_user_input
-- Return structured decision for orchestrator to act on
-- Respect max discussion round limits
-
-### MUST NOT
-
-- Perform analysis or exploration (delegate to csv-wave agents)
-- Create tasks directly (orchestrator handles dynamic task creation)
-- Skip user interaction (this is the user-in-the-loop checkpoint)
-- Exceed the configured max discussion rounds
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | builtin | Load discussion results and session state |
-| `request_user_input` | builtin | Collect user feedback on discussion |
-
----
-
-## Execution
-
-### Phase 1: Context Loading
-
-**Objective**: Load discussion results for user presentation
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Session folder | Yes | Path to session directory |
-| Discussion round | Yes | Current round number |
-| Max discussion rounds | Yes | Maximum allowed rounds |
-| Pipeline mode | Yes | quick, standard, or deep |
-
-**Steps**:
-
-1. Read the session's discoveries.ndjson for discussion_point entries
-2. Parse prev_context for the discussant's findings
-3. Extract key themes, conflicts, and open questions from findings
-4. Load current discussion_round from spawn message
-
-**Output**: Discussion summary ready for user presentation
-
----
-
-### Phase 2: User Feedback Collection
-
-**Objective**: Present results and collect next-step decision
-
-**Steps**:
-
-1. Format discussion summary for user:
-   - Convergent themes identified
-   - Conflicting views between perspectives
-   - Top open questions
-   - Round progress (current/max)
-
-2. Present options via request_user_input:
-
-```
-request_user_input({
-  questions: [{
-    question: "Discussion round <N>/<max> complete.\n\nThemes: <themes>\nConflicts: <conflicts>\nOpen Questions: <questions>\n\nWhat next?",
-    header: "Feedback",
-    id: "discussion_next",
-    options: [
-      { label: "Continue deeper (Recommended)", description: "Current direction is good, investigate open questions deeper" },
-      { label: "Adjust direction", description: "Shift analysis focus to a different area" },
-      { label: "Done", description: "Sufficient depth reached, proceed to final synthesis" }
-    ]
-  }]
-})
-```
-
-3. If user chooses "Adjust direction":
-   - Follow up with another request_user_input asking for the new focus area
-   - Capture the adjusted focus text
-
-**Output**: User decision and optional adjusted focus
-
----
-
-### Phase 3: Decision Formatting
-
-**Objective**: Package user decision for orchestrator
-
-**Steps**:
-
-1. Map user choice to decision string:
-
-| User Choice | Decision | Additional Data |
-|------------|----------|-----------------|
-| Continue deeper | `continue_deeper` | None |
-| Adjust direction | `adjust_direction` | `adjusted_focus: <user input>` |
-| Done | `done` | None |
-
-2. Format structured output for orchestrator
-
-**Output**: Structured decision
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Discussion Round: <current>/<max>
-- User Decision: continue_deeper | adjust_direction | done
-
-## Discussion Summary Presented
-- Themes: <list>
-- Conflicts: <list>
-- Open Questions: <list>
-
-## Decision Details
-- Decision: <decision>
-- Adjusted Focus: <focus text, if adjust_direction>
-- Rationale: <user's reasoning, if provided>
-
-## Next Action (for orchestrator)
-- continue_deeper: Create DISCUSS-<N+1> task, then FEEDBACK-<N+1>
-- adjust_direction: Create ANALYZE-fix-<N> task, then DISCUSS-<N+1>, then FEEDBACK-<N+1>
-- done: Create SYNTH-001 task blocked by last DISCUSS task
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| User does not respond | After timeout, default to "done" and proceed to synthesis |
-| Max rounds reached | Inform user this is the final round, only offer "Done" option |
-| No discussion data found | Present what is available, note limitations |
-| Timeout approaching | Output current state with default "done" decision |

package/.codex/skills/team-ultra-analyze/agents/topic-analyzer.md

@@ -1,153 +0,0 @@
-# Topic Analyzer Agent
-
-Parse analysis topic, detect dimensions, select pipeline mode, and assign perspectives.
-
-## Identity
-
-- **Type**: `interactive`
-- **Responsibility**: Topic analysis and pipeline configuration
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Perform text-level analysis only (no source code reading)
-- Produce structured output with pipeline configuration
-- Detect dimensions from topic keywords
-- Recommend appropriate perspectives for the topic
-
-### MUST NOT
-
-- Read source code or explore codebase (that is the explorer's job)
-- Perform any analysis (that is the analyst's job)
-- Make final pipeline decisions without providing rationale
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | builtin | Load project context if available |
-
----
-
-## Execution
-
-### Phase 1: Dimension Detection
-
-**Objective**: Scan topic keywords to identify analysis dimensions
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Topic text | Yes | The analysis topic from user |
-| Explicit mode | No | --mode override if provided |
-
-**Steps**:
-
-1. Scan topic for dimension keywords:
-
-| Dimension | Keywords |
-|-----------|----------|
-| architecture | architecture, design, structure |
-| implementation | implement, code, source |
-| performance | performance, optimize, speed |
-| security | security, auth, vulnerability |
-| concept | concept, theory, principle |
-| comparison | compare, vs, difference |
-| decision | decision, choice, tradeoff |
-
-2. Select matching dimensions (default to general if none match)
-
-**Output**: List of detected dimensions
-
----
-
-### Phase 2: Pipeline Mode Selection
-
-**Objective**: Determine pipeline mode and depth
-
-**Steps**:
-
-1. If explicit `--mode` provided, use it directly
-2. Otherwise, auto-detect from complexity scoring:
-
-| Factor | Points |
-|--------|--------|
-| Per detected dimension | +1 |
-| Deep-mode keywords (deep, thorough, detailed, comprehensive) | +2 |
-| Cross-domain (3+ dimensions) | +1 |
-
-| Score | Pipeline Mode |
-|-------|--------------|
-| 1-3 | quick |
-| 4-6 | standard |
-| 7+ | deep |
-
-3. Determine depth = number of selected perspectives
-
-**Output**: Pipeline mode and depth
-
----
-
-### Phase 3: Perspective Assignment
-
-**Objective**: Select analysis perspectives based on topic and dimensions
-
-**Steps**:
-
-1. Map dimensions to perspectives:
-
-| Dimension Match | Perspective | Focus |
-|----------------|-------------|-------|
-| architecture, implementation | technical | Implementation details, code patterns |
-| architecture, security | architectural | System design, scalability |
-| concept, comparison, decision | business | Value, ROI, strategy |
-| domain-specific keywords | domain_expert | Domain patterns, standards |
-
-2. Quick mode: always 1 perspective (technical by default)
-3. Standard/Deep mode: 2-4 perspectives based on dimension coverage
-
-**Output**: List of perspectives with focus areas
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Topic: <topic>
-- Pipeline Mode: <quick|standard|deep>
-- Depth: <number of perspectives>
-
-## Dimension Detection
-- Detected dimensions: <list>
-- Complexity score: <score>
-
-## Perspectives
-1. <perspective>: <focus area>
-2. <perspective>: <focus area>
-
-## Discussion Configuration
-- Max discussion rounds: <0|1|5>
-
-## Pipeline Structure
-- Total tasks: <count>
-- Parallel stages: <description>
-- Dynamic tasks possible: <yes/no>
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Topic too vague | Suggest clarifying questions, default to standard mode |
-| No dimension matches | Default to "general" dimension with technical perspective |
-| Timeout approaching | Output current analysis with "PARTIAL" status |

package/.codex/skills/team-ultra-analyze/instructions/agent-instruction.md

@@ -1,169 +0,0 @@
-## TASK ASSIGNMENT
-
-### MANDATORY FIRST STEPS
-1. Read shared discoveries: .workflow/.csv-wave/{session-id}/discoveries.ndjson (if exists, skip if not)
-2. Read project context: .workflow/project-tech.json (if exists)
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Role**: {role}
-**Description**: {description}
-**Perspective**: {perspective}
-**Dimensions**: {dimensions}
-**Discussion Round**: {discussion_round}
-**Discussion Type**: {discussion_type}
-
-### Previous Tasks' Findings (Context)
-{prev_context}
-
----
-
-## Execution Protocol
-
-1. **Read discoveries**: Load shared discoveries from the session's discoveries.ndjson for cross-task context
-2. **Use context**: Apply previous tasks' findings from prev_context above
-3. **Execute by role**:
-
-### Role: explorer (EXPLORE-* tasks)
-Explore codebase structure from the assigned perspective, collecting structured context for downstream analysis.
-
-- Determine exploration strategy by perspective:
-
-| Perspective | Focus | Search Depth |
-|-------------|-------|-------------|
-| general | Overall codebase structure and patterns | broad |
-| technical | Implementation details, code patterns, feasibility | medium |
-| architectural | System design, module boundaries, interactions | broad |
-| business | Business logic, domain models, value flows | medium |
-| domain_expert | Domain patterns, standards, best practices | deep |
-
-- Use available tools (Read, Glob, Grep, Bash) to search the codebase
-- Collect: relevant files (path, relevance, summary), code patterns, key findings, module relationships
-- Generate questions for downstream analysis
-- Focus exploration on the dimensions listed in the Dimensions field
-
-### Role: analyst (ANALYZE-* tasks)
-Perform deep analysis on exploration results from the assigned perspective.
-
-- Load exploration results from prev_context
-- Detect if this is a direction-fix task (description mentions "adjusted focus"):
-  - Normal: analyze from assigned perspective using corresponding exploration results
-  - Direction-fix: re-analyze from adjusted perspective using all available explorations
-
-- Select analysis approach by perspective:
-
-| Perspective | CLI Tool | Focus |
-|-------------|----------|-------|
-| technical | gemini | Implementation patterns, code quality, feasibility |
-| architectural | gemini | System design, scalability, component interactions |
-| business | gemini | Value, ROI, stakeholder impact |
-| domain_expert | gemini | Domain-specific patterns, best practices |
-
-- Use `ccw cli` for deep analysis:
-  ```bash
-  ccw cli -p "PURPOSE: Deep analysis of '<topic>' from <perspective> perspective
-  TASK: • Analyze patterns found in exploration • Generate insights with confidence levels • Identify discussion points
-  MODE: analysis
-  CONTEXT: @**/* | Memory: Exploration findings
-  EXPECTED: Structured insights with confidence levels and evidence" --tool gemini --mode analysis
-  ```
-
-- Generate structured output:
-  - key_insights: [{insight, confidence (high/medium/low), evidence (file:line)}]
-  - key_findings: [{finding, file_ref, impact}]
-  - discussion_points: [questions needing cross-perspective discussion]
-  - open_questions: [areas needing further exploration]
-  - recommendations: [{action, rationale, priority}]
-
-### Role: discussant (DISCUSS-* tasks)
-Process analysis results and generate discussion summary. Strategy depends on discussion type.
-
-- **initial**: Cross-perspective aggregation
-  - Aggregate all analysis results from prev_context
-  - Identify convergent themes across perspectives
-  - Identify conflicting views between perspectives
-  - Generate top 5 discussion points and open questions
-  - Produce structured round summary
-
-- **deepen**: Deep investigation of open questions
-  - Use CLI tool to investigate uncertain insights:
-    ```bash
-    ccw cli -p "PURPOSE: Investigate open questions and uncertain insights
-    TASK: • Focus on questions from previous round • Find supporting evidence • Validate uncertain insights
-    MODE: analysis
-    CONTEXT: @**/*
-    EXPECTED: Evidence-based findings" --tool gemini --mode analysis
-    ```
-
-- **direction-adjusted**: Re-analysis from adjusted focus
-  - Use CLI to re-analyze from adjusted perspective based on user feedback
-
-- **specific-questions**: Targeted Q&A
-  - Use CLI for targeted investigation of user-specified questions
-
-- For all types, produce round summary:
-  - updated_understanding: {confirmed[], corrected[], new_insights[]}
-  - convergent themes, conflicting views
-  - remaining open questions
-
-### Role: synthesizer (SYNTH-* tasks)
-Integrate all explorations, analyses, and discussions into final conclusions.
-
-- Read all available artifacts from prev_context (explorations, analyses, discussions)
-- Execute synthesis in four steps:
-  1. **Theme Extraction**: Identify convergent themes across perspectives, rank by cross-perspective confirmation
-  2. **Conflict Resolution**: Identify contradictions, present trade-off analysis
-  3. **Evidence Consolidation**: Deduplicate findings, aggregate by file reference, assign confidence levels
-  4. **Recommendation Prioritization**: Sort by priority, deduplicate, cap at 10
-
-- Confidence levels:
-
-| Level | Criteria |
-|-------|----------|
-| High | Multiple sources confirm, strong evidence |
-| Medium | Single source or partial evidence |
-| Low | Speculative, needs verification |
-
-- Produce final conclusions:
-  - Executive summary
-  - Key conclusions with evidence and confidence
-  - Prioritized recommendations
-  - Open questions
-  - Cross-perspective synthesis (convergent themes, conflicts resolved, unique contributions)
-
-4. **Share discoveries**: Append exploration findings to shared board:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"<type>","data":{...}}' >> .workflow/.csv-wave/{session-id}/discoveries.ndjson
-   ```
-
-   Discovery types to share:
-   - `exploration`: {perspective, file, relevance, summary, patterns[]} — explored file/module
-   - `analysis`: {perspective, insight, confidence, evidence, file_ref} — analysis insight
-   - `pattern`: {name, file, description, type} — code/architecture pattern
-   - `discussion_point`: {topic, perspectives[], convergence, open_questions[]} — discussion point
-   - `recommendation`: {action, rationale, priority, confidence} — recommendation
-   - `conclusion`: {point, evidence, confidence, perspectives_supporting[]} — final conclusion
-
-5. **Report result**: Return JSON via report_agent_job_result
-
----
-
-## Output (report_agent_job_result)
-
-Return JSON:
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Key discoveries and implementation notes (max 500 chars)",
-  "error": ""
-}
-
-**Role-specific findings guidance**:
-- **explorer**: List file count, key files, patterns found. Example: "Found 12 files related to auth. Key: src/auth/index.ts (entry), src/auth/strategies/*.ts (providers). Patterns: strategy, middleware chain."
-- **analyst**: List insight count, top insights with confidence. Example: "3 insights: (1) Strategy pattern for providers [high], (2) Missing token rotation [medium], (3) No rate limiting [high]. 2 discussion points."
-- **discussant**: List themes, conflicts, question count. Example: "Convergent: JWT security (2 perspectives). Conflict: middleware approach. 3 open questions on refresh tokens."
-- **synthesizer**: List conclusion count, top recommendations. Example: "5 conclusions, 4 recommendations. Top: Implement refresh token rotation [high priority, high confidence]."

package/.codex/skills/team-ultra-analyze/schemas/tasks-schema.md

@@ -1,180 +0,0 @@
-# Team Ultra Analyze — CSV Schema
-
-## Master CSV: tasks.csv
-
-### Column Definitions
-
-#### Input Columns (Set by Decomposer)
-
-| Column | Type | Required | Description | Example |
-|--------|------|----------|-------------|---------|
-| `id` | string | Yes | Unique task identifier | `"EXPLORE-001"` |
-| `title` | string | Yes | Short task title | `"Explore from technical perspective"` |
-| `description` | string | Yes | Detailed task description (self-contained) | `"Search codebase from technical perspective..."` |
-| `role` | string | Yes | Worker role: explorer, analyst, discussant, synthesizer | `"explorer"` |
-| `perspective` | string | No | Analysis perspective: technical, architectural, business, domain_expert | `"technical"` |
-| `dimensions` | string | No | Analysis dimensions (semicolon-separated) | `"architecture;implementation"` |
-| `discussion_round` | integer | No | Discussion round number (0 = N/A, 1+ = round) | `"1"` |
-| `discussion_type` | string | No | Discussion type: initial, deepen, direction-adjusted, specific-questions | `"initial"` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"EXPLORE-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"EXPLORE-001"` |
-| `exec_mode` | enum | Yes | Execution mechanism: `csv-wave` or `interactive` | `"csv-wave"` |
-
-#### Computed Columns (Set by Wave Engine)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `wave` | integer | Wave number (1-based, from topological sort) | `2` |
-| `prev_context` | string | Aggregated findings from context_from tasks (per-wave CSV only) | `"[Task EXPLORE-001] Found 12 relevant files..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` → `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Found 12 files related to auth module..."` |
-| `error` | string | Error message if failed | `""` |
-
----
-
-### exec_mode Values
-
-| Value | Mechanism | Description |
-|-------|-----------|-------------|
-| `csv-wave` | `spawn_agents_on_csv` | One-shot batch execution within wave |
-| `interactive` | `spawn_agent`/`wait`/`send_input`/`close_agent` | Multi-round individual execution |
-
-Interactive tasks appear in master CSV for dependency tracking but are NOT included in wave-{N}.csv files.
-
----
-
-### Example Data
-
-```csv
-id,title,description,role,perspective,dimensions,discussion_round,discussion_type,deps,context_from,exec_mode,wave,status,findings,error
-"EXPLORE-001","Explore from technical perspective","Search codebase from technical perspective. Collect files, patterns, and findings related to authentication module.","explorer","technical","architecture;implementation","0","","","","csv-wave","1","pending","",""
-"EXPLORE-002","Explore from architectural perspective","Search codebase from architectural perspective. Focus on module boundaries, component interactions, and system design patterns.","explorer","architectural","architecture;security","0","","","","csv-wave","1","pending","",""
-"ANALYZE-001","Deep analysis from technical perspective","Analyze exploration results from technical perspective. Generate insights with confidence levels and evidence references.","analyst","technical","architecture;implementation","0","","EXPLORE-001","EXPLORE-001","csv-wave","2","pending","",""
-"ANALYZE-002","Deep analysis from architectural perspective","Analyze exploration results from architectural perspective. Focus on system design quality and scalability.","analyst","architectural","architecture;security","0","","EXPLORE-002","EXPLORE-002","csv-wave","2","pending","",""
-"DISCUSS-001","Initial discussion round","Aggregate all analysis results across perspectives. Identify convergent themes, conflicting views, and top discussion points.","discussant","","","1","initial","ANALYZE-001;ANALYZE-002","ANALYZE-001;ANALYZE-002","csv-wave","3","pending","",""
-"FEEDBACK-001","Discussion feedback gate","Collect user feedback on discussion results. Decide: continue deeper, adjust direction, or proceed to synthesis.","","","","1","","DISCUSS-001","DISCUSS-001","interactive","4","pending","",""
-"SYNTH-001","Final synthesis","Integrate all explorations, analyses, and discussions into final conclusions with prioritized recommendations.","synthesizer","","","0","","FEEDBACK-001","EXPLORE-001;EXPLORE-002;ANALYZE-001;ANALYZE-002;DISCUSS-001","csv-wave","5","pending","",""
-```
-
----
-
-### Column Lifecycle
-
-```
-Decomposer (Phase 1)     Wave Engine (Phase 2)    Agent (Execution)
-─────────────────────    ────────────────────     ─────────────────
-id          ───────────►  id          ──────────►  id
-title       ───────────►  title       ──────────►  (reads)
-description ───────────►  description ──────────►  (reads)
-role        ───────────►  role        ──────────►  (reads)
-perspective ───────────►  perspective ──────────►  (reads)
-dimensions  ───────────►  dimensions  ──────────►  (reads)
-discussion_round ──────►  discussion_round ─────►  (reads)
-discussion_type ───────►  discussion_type ──────►  (reads)
-deps        ───────────►  deps        ──────────►  (reads)
-context_from───────────►  context_from──────────►  (reads)
-exec_mode   ───────────►  exec_mode   ──────────►  (reads)
-                          wave         ──────────►  (reads)
-                          prev_context ──────────►  (reads)
-                                                    status
-                                                    findings
-                                                    error
-```
-
----
-
-## Output Schema (JSON)
-
-Agent output via `report_agent_job_result` (csv-wave tasks):
-
-```json
-{
-  "id": "EXPLORE-001",
-  "status": "completed",
-  "findings": "Found 12 files related to auth module. Key files: src/auth/index.ts, src/auth/strategies/*.ts. Patterns: strategy pattern for provider switching, middleware chain for request validation.",
-  "error": ""
-}
-```
-
-Analyst output:
-
-```json
-{
-  "id": "ANALYZE-001",
-  "status": "completed",
-  "findings": "3 key insights: (1) Auth uses strategy pattern [high confidence], (2) JWT validation lacks refresh token rotation [medium], (3) Rate limiting missing on auth endpoints [high]. 2 discussion points identified.",
-  "error": ""
-}
-```
-
-Discussant output:
-
-```json
-{
-  "id": "DISCUSS-001",
-  "status": "completed",
-  "findings": "Convergent themes: JWT security concerns (2 perspectives agree), strategy pattern approval. Conflicts: architectural vs technical on middleware approach. Top questions: refresh token strategy, rate limit placement.",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `exploration` | `data.perspective+data.file` | `{perspective, file, relevance, summary, patterns[]}` | Explored file or module |
-| `analysis` | `data.perspective+data.insight` | `{perspective, insight, confidence, evidence, file_ref}` | Analysis insight |
-| `pattern` | `data.name` | `{name, file, description, type}` | Code or architecture pattern |
-| `discussion_point` | `data.topic` | `{topic, perspectives[], convergence, open_questions[]}` | Discussion point |
-| `recommendation` | `data.action` | `{action, rationale, priority, confidence}` | Recommendation |
-| `conclusion` | `data.point` | `{point, evidence, confidence, perspectives_supporting[]}` | Final conclusion |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T10:00:00+08:00","worker":"EXPLORE-001","type":"exploration","data":{"perspective":"technical","file":"src/auth/index.ts","relevance":"high","summary":"Auth module entry point with OAuth and JWT exports","patterns":["module-pattern","strategy-pattern"]}}
-{"ts":"2026-03-08T10:01:00+08:00","worker":"EXPLORE-001","type":"pattern","data":{"name":"strategy-pattern","file":"src/auth/strategies/","description":"Provider switching via strategy pattern","type":"behavioral"}}
-{"ts":"2026-03-08T10:05:00+08:00","worker":"ANALYZE-001","type":"analysis","data":{"perspective":"technical","insight":"JWT validation lacks refresh token rotation","confidence":"medium","evidence":"No rotation logic in src/auth/jwt/verify.ts","file_ref":"src/auth/jwt/verify.ts:42"}}
-{"ts":"2026-03-08T10:10:00+08:00","worker":"DISCUSS-001","type":"discussion_point","data":{"topic":"JWT Security","perspectives":["technical","architectural"],"convergence":"Both agree on rotation need","open_questions":["Sliding vs fixed window?"]}}
-{"ts":"2026-03-08T10:15:00+08:00","worker":"SYNTH-001","type":"conclusion","data":{"point":"Auth module needs refresh token rotation","evidence":"src/auth/jwt/verify.ts lacks rotation","confidence":"high","perspectives_supporting":["technical","architectural"]}}
-```
-
-> Both csv-wave and interactive agents read/write the same discoveries.ndjson file.
-
----
-
-## Cross-Mechanism Context Flow
-
-| Source | Target | Mechanism |
-|--------|--------|-----------|
-| CSV task findings | Interactive task | Injected via spawn message or send_input |
-| Interactive task result | CSV task prev_context | Read from interactive/{id}-result.json |
-| Any agent discovery | Any agent | Shared via discoveries.ndjson |
-
----
-
-## Validation Rules
-
-| Rule | Check | Error |
-|------|-------|-------|
-| Unique IDs | No duplicate `id` values | "Duplicate task ID: {id}" |
-| Valid deps | All dep IDs exist in tasks | "Unknown dependency: {dep_id}" |
-| No self-deps | Task cannot depend on itself | "Self-dependency: {id}" |
-| No circular deps | Topological sort completes | "Circular dependency detected involving: {ids}" |
-| context_from valid | All context IDs exist and in earlier waves | "Invalid context_from: {id}" |
-| exec_mode valid | Value is `csv-wave` or `interactive` | "Invalid exec_mode: {value}" |
-| Description non-empty | Every task has description | "Empty description for task: {id}" |
-| Status enum | status in {pending, completed, failed, skipped} | "Invalid status: {status}" |
-| Valid role | role in {explorer, analyst, discussant, synthesizer} | "Invalid role: {role}" |
-| Valid perspective | perspective in {technical, architectural, business, domain_expert, general, ""} | "Invalid perspective: {value}" |
-| Discussion round non-negative | discussion_round >= 0 | "Invalid discussion_round: {value}" |
-| Cross-mechanism deps | Interactive→CSV deps resolve correctly | "Cross-mechanism dependency unresolvable: {id}" |