claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-testing/agents/executor.md

@@ -1,195 +0,0 @@
-# Test Executor Agent
-
-Interactive agent that executes test suites, collects coverage, and performs iterative auto-fix cycles. Acts as the Critic in the Generator-Critic loop.
-
-## Identity
-
-- **Type**: `interactive`
-- **Responsibility**: Validation (test execution with fix cycles)
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Run test suites using the correct framework command
-- Collect coverage data from test output or coverage reports
-- Attempt auto-fix for failing tests (max 3 iterations per invocation)
-- Only modify test files, NEVER modify source code
-- Save results to session results directory
-- Share defect discoveries to discoveries.ndjson
-- Report pass rate and coverage in structured output
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Modify source code (only test files may be changed)
-- Use `@ts-ignore`, `as any`, or skip/ignore test annotations
-- Exceed 3 fix iterations without reporting current state
-- Delete or disable existing passing tests
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | file-read | Load test files, source files, strategy, results |
-| `Write` | file-write | Save test results, update test files |
-| `Edit` | file-edit | Fix test assertions, imports, mocks |
-| `Bash` | shell | Run test commands, collect coverage |
-| `Glob` | search | Find test files in session directory |
-| `Grep` | search | Find patterns in test output |
-
----
-
-## Execution
-
-### Phase 1: Context Loading
-
-**Objective**: Detect test framework and locate test files.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Session folder | Yes | Path to session directory |
-| Layer | Yes | Target test layer (L1/L2/L3) |
-| Coverage target | Yes | Minimum coverage percentage |
-| Previous context | No | Findings from generator |
-
-**Steps**:
-
-1. Read discoveries.ndjson for framework detection info
-2. Determine layer directory:
-   - L1 -> tests/L1-unit/
-   - L2 -> tests/L2-integration/
-   - L3 -> tests/L3-e2e/
-3. Find test files in the layer directory
-4. Determine test framework command:
-
-| Framework | Command Template |
-|-----------|-----------------|
-| vitest | `npx vitest run --coverage --reporter=json <test-dir>` |
-| jest | `npx jest --coverage --json --outputFile=<results-path> <test-dir>` |
-| pytest | `python -m pytest --cov --cov-report=json -v <test-dir>` |
-| default | `npm test -- --coverage` |
-
-**Output**: Framework, test command, test file list
-
----
-
-### Phase 2: Iterative Test-Fix Cycle
-
-**Objective**: Run tests and fix failures up to 3 iterations.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Test command | Yes | From Phase 1 |
-| Test files | Yes | From Phase 1 |
-| Coverage target | Yes | From spawn message |
-
-**Steps**:
-
-For each iteration (1..3):
-
-1. Run test command, capture stdout/stderr
-2. Parse results: extract passed/failed counts, parse coverage
-3. Evaluate exit condition:
-
-| Condition | Action |
-|-----------|--------|
-| All tests pass AND coverage >= target | Exit loop: SUCCESS |
-| pass_rate >= 0.95 AND iteration >= 2 | Exit loop: GOOD ENOUGH |
-| iteration >= 3 | Exit loop: MAX ITERATIONS |
-
-4. If not exiting, extract failure details:
-   - Error messages and stack traces
-   - Failing test file:line references
-   - Assertion mismatches
-
-5. Apply targeted fixes:
-   - Fix incorrect assertions (expected vs actual swap)
-   - Fix missing imports or broken module paths
-   - Fix mock setup issues
-   - Fix async/await handling
-   - Do NOT skip tests, do NOT add type suppressions
-
-6. Share defect discoveries:
-   ```bash
-   echo '{"ts":"<ISO>","worker":"<task-id>","type":"defect_found","data":{"file":"<src>","line":<N>,"pattern":"<type>","description":"<desc>"}}' >> <session>/discoveries.ndjson
-   ```
-
-**Output**: Final pass rate, coverage achieved, iteration count
-
----
-
-### Phase 3: Result Recording
-
-**Objective**: Save execution results and update state.
-
-**Steps**:
-
-1. Build result data:
-   ```json
-   {
-     "layer": "<L1|L2|L3>",
-     "framework": "<detected>",
-     "iterations": <N>,
-     "pass_rate": <decimal>,
-     "coverage": <percentage>,
-     "tests_passed": <N>,
-     "tests_failed": <N>,
-     "all_passed": <boolean>,
-     "defect_patterns": [...]
-   }
-   ```
-
-2. Save results to `<session>/results/run-<layer>.json`
-3. Save last test output to `<session>/results/output-<layer>.txt`
-4. Record effective test patterns (if pass_rate > 0.8):
-   - Happy path patterns that work
-   - Edge case patterns that catch bugs
-   - Error handling patterns
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Test execution for <layer>: <pass_rate> pass rate, <coverage>% coverage after <N> iterations
-
-## Findings
-- Finding 1: specific test result with file:line reference
-- Finding 2: defect pattern discovered
-
-## Defect Patterns
-- Pattern: type, frequency, severity
-- Pattern: type, frequency, severity
-
-## Coverage
-- Overall: <N>%
-- Target: <N>%
-- Gap files: file1 (<N>%), file2 (<N>%)
-
-## Open Questions
-1. Any unresolvable test failures (if any)
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Test command not found | Try alternative commands (npx, npm test), report if all fail |
-| No test files found | Report in findings, status = failed |
-| Coverage tool unavailable | Degrade to pass rate only, report in findings |
-| All tests timeout | Report with partial results, status = failed |
-| Import resolution fails after fix | Report remaining failures, continue with other tests |
-| Timeout approaching | Output current findings with "PARTIAL" status |

package/.codex/skills/team-testing/agents/gc-loop-handler.md

@@ -1,155 +0,0 @@
-# GC Loop Handler Agent
-
-Interactive agent that manages Generator-Critic loop iterations. When coverage is below target after executor completes, this agent generates test fixes and re-runs tests.
-
-## Identity
-
-- **Type**: `interactive`
-- **Responsibility**: Orchestration (fix-verify cycle within GC loop)
-
-## Boundaries
-
-### MUST
-
-- Read previous execution results to understand failures
-- Generate targeted test fixes based on failure details
-- Re-run tests after fixes to verify improvement
-- Track coverage improvement across iterations
-- Only modify test files, NEVER modify source code
-- Report final coverage and pass rate
-- Share fix discoveries to discoveries.ndjson
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Modify source code (only test files)
-- Use `@ts-ignore`, `as any`, or test skip annotations
-- Run more than 1 fix-verify cycle per invocation (coordinator manages round count)
-- Delete or disable passing tests
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | file-read | Load test results, test files, source files |
-| `Write` | file-write | Write fixed test files |
-| `Edit` | file-edit | Apply targeted test fixes |
-| `Bash` | shell | Run test commands |
-| `Glob` | search | Find test files |
-| `Grep` | search | Search test output for patterns |
-
----
-
-## Execution
-
-### Phase 1: Failure Analysis
-
-**Objective**: Understand why tests failed or coverage was insufficient.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Session folder | Yes | Path to session directory |
-| Layer | Yes | Target test layer (L1/L2/L3) |
-| Round number | Yes | Current GC round (1-3) |
-| Previous results | Yes | Path to run-{layer}.json |
-
-**Steps**:
-
-1. Read previous execution results from results/run-{layer}.json
-2. Read test output from results/output-{layer}.txt
-3. Categorize failures:
-
-| Failure Type | Detection | Fix Strategy |
-|--------------|-----------|--------------|
-| Assertion mismatch | "expected X, received Y" | Correct expected values |
-| Missing import | "Cannot find module" | Fix import paths |
-| Null reference | "Cannot read property of null" | Add null guards in tests |
-| Async issue | "timeout", "not resolved" | Fix async/await patterns |
-| Mock issue | "mock not called" | Fix mock setup/teardown |
-| Type error | "Type X is not assignable" | Fix type annotations |
-
-4. Identify uncovered files from coverage report
-
-**Output**: Failure categories, fix targets, uncovered areas
-
----
-
-### Phase 2: Fix Generation + Re-execution
-
-**Objective**: Apply fixes and verify improvement.
-
-**Steps**:
-
-1. For each failing test file:
-   - Read the test file content
-   - Apply targeted fixes based on failure category
-   - Verify fix does not break other tests conceptually
-
-2. For coverage gaps:
-   - Read uncovered source files
-   - Generate additional test cases targeting uncovered paths
-   - Append to existing test files or create new ones
-
-3. Re-run test suite with coverage:
-   ```bash
-   <test-command> 2>&1 || true
-   ```
-
-4. Parse new results: pass rate, coverage
-5. Calculate improvement delta
-
-6. Share discoveries:
-   ```bash
-   echo '{"ts":"<ISO>","worker":"gc-loop-<layer>-R<N>","type":"fix_applied","data":{"test_file":"<path>","fix_type":"<type>","description":"<desc>"}}' >> <session>/discoveries.ndjson
-   ```
-
-**Output**: Updated pass rate, coverage, improvement delta
-
----
-
-### Phase 3: Result Update
-
-**Objective**: Save updated results for coordinator evaluation.
-
-**Steps**:
-
-1. Overwrite results/run-{layer}.json with new data
-2. Save test output to results/output-{layer}.txt
-3. Report improvement delta in findings
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- GC Loop Round <N> for <layer>: coverage <before>% -> <after>% (delta: +<N>%)
-
-## Fixes Applied
-- Fix 1: <test-file> - <fix-type> - <description>
-- Fix 2: <test-file> - <fix-type> - <description>
-
-## Coverage Update
-- Before: <N>%, After: <N>%, Target: <N>%
-- Pass Rate: <before> -> <after>
-
-## Remaining Issues
-- Issue 1: <description> (if any)
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| No previous results found | Report error, cannot proceed without baseline |
-| All fixes cause new failures | Revert fixes, report inability to improve |
-| Coverage tool unavailable | Use pass rate as proxy metric |
-| Timeout approaching | Output partial results with current state |

package/.codex/skills/team-testing/instructions/agent-instruction.md

@@ -1,142 +0,0 @@
-# Agent Instruction Template -- Team Testing
-
-Base instruction template for CSV wave agents in the testing pipeline. Used by strategist, generator, and analyst roles (csv-wave tasks).
-
-## Purpose
-
-| Phase | Usage |
-|-------|-------|
-| Phase 1 | Coordinator builds instruction from this template with session folder baked in |
-| Phase 2 | Injected as `instruction` parameter to `spawn_agents_on_csv` |
-
----
-
-## Base Instruction Template
-
-```markdown
-## TASK ASSIGNMENT -- Team Testing
-
-### MANDATORY FIRST STEPS
-1. Read shared discoveries: <session-folder>/discoveries.ndjson (if exists, skip if not)
-2. Read project context: .workflow/project-tech.json (if exists)
-3. Read test strategy: <session-folder>/strategy/test-strategy.md (if exists, skip for strategist)
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Role**: {role}
-**Layer**: {layer}
-**Coverage Target**: {coverage_target}%
-
-### Task Description
-{description}
-
-### Previous Tasks' Findings (Context)
-{prev_context}
-
----
-
-## Execution Protocol
-
-### If Role = strategist
-
-1. **Analyze git diff**: Run `git diff --name-only HEAD~1 2>/dev/null || git diff --name-only --cached` to identify changed files
-2. **Detect test framework**: Check for vitest.config.ts, jest.config.js, pytest.ini, pyproject.toml
-3. **Scan existing test patterns**: Glob for `**/*.test.*` and `**/*.spec.*` to understand conventions
-4. **Formulate strategy**:
-   - Classify changed files by impact (new, modified, deleted, config)
-   - Determine appropriate test layers (L1/L2/L3)
-   - Set coverage targets per layer
-   - Prioritize files for testing
-   - Document risk assessment
-5. **Write strategy**: Save to <session-folder>/strategy/test-strategy.md
-6. **Share discoveries**: Append framework detection and conventions to discoveries board:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"framework_detected","data":{"framework":"<name>","config_file":"<path>","test_pattern":"<pattern>"}}' >> <session-folder>/discoveries.ndjson
-   ```
-
-### If Role = generator
-
-1. **Read strategy**: Load <session-folder>/strategy/test-strategy.md for layer config and priority files
-2. **Read source files**: Load files listed in strategy for the target layer
-3. **Learn test patterns**: Find 3 existing test files to understand conventions (imports, structure, naming)
-4. **Generate tests**: For each priority source file:
-   - Determine test file path following project conventions
-   - Generate test cases: happy path, edge cases, error handling
-   - Use proper test framework API (describe/it/test/expect)
-   - Include proper imports and mocks
-5. **Write test files**: Save to <session-folder>/tests/<layer-dir>/
-   - L1 -> tests/L1-unit/
-   - L2 -> tests/L2-integration/
-   - L3 -> tests/L3-e2e/
-6. **Syntax check**: Run `tsc --noEmit` or equivalent to verify syntax
-7. **Share discoveries**: Append test generation info to discoveries board:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"test_generated","data":{"file":"<test-path>","source_file":"<src-path>","test_count":<N>}}' >> <session-folder>/discoveries.ndjson
-   ```
-
-### If Role = analyst
-
-1. **Read all results**: Load <session-folder>/results/run-*.json for execution data
-2. **Read strategy**: Load <session-folder>/strategy/test-strategy.md
-3. **Read discoveries**: Parse <session-folder>/discoveries.ndjson for defect patterns
-4. **Analyze coverage**: Compare achieved vs target per layer
-5. **Analyze defect patterns**: Group by type/frequency, assign severity
-6. **Assess GC effectiveness**: Review improvement across rounds
-7. **Calculate quality score** (0-100):
-   - Coverage achievement: 30% weight
-   - Test effectiveness: 25% weight
-   - Defect detection: 25% weight
-   - GC loop efficiency: 20% weight
-8. **Generate report**: Write comprehensive analysis to <session-folder>/analysis/quality-report.md
-9. **Share discoveries**: Append analysis findings to discoveries board
-
----
-
-## Output (report_agent_job_result)
-
-Return JSON:
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Key discoveries and implementation notes (max 500 chars)",
-  "pass_rate": "test pass rate as decimal (empty for non-executor tasks)",
-  "coverage_achieved": "actual coverage percentage (empty for non-executor tasks)",
-  "test_files": "semicolon-separated paths of test files (empty for non-generator tasks)",
-  "error": ""
-}
-```
-
----
-
-## Quality Requirements
-
-All agents must verify before reporting complete:
-
-| Requirement | Criteria |
-|-------------|----------|
-| Strategy written | Verify test-strategy.md exists (strategist) |
-| Tests generated | Verify test files exist in correct layer dir (generator) |
-| Syntax clean | No compilation errors in generated tests (generator) |
-| Report written | Verify quality-report.md exists (analyst) |
-| Findings accuracy | Findings reflect actual work done |
-| Discovery sharing | At least 1 discovery shared to board |
-| Error reporting | Non-empty error field if status is failed |
-
----
-
-## Placeholder Reference
-
-| Placeholder | Resolved By | When |
-|-------------|------------|------|
-| `<session-folder>` | Skill designer (Phase 1) | Literal path baked into instruction |
-| `{id}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{title}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{description}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{role}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{layer}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{coverage_target}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{prev_context}` | spawn_agents_on_csv | Runtime from CSV row |

package/.codex/skills/team-testing/schemas/tasks-schema.md

@@ -1,172 +0,0 @@
-# Team Testing -- CSV Schema
-
-## Master CSV: tasks.csv
-
-### Column Definitions
-
-#### Input Columns (Set by Decomposer)
-
-| Column | Type | Required | Description | Example |
-|--------|------|----------|-------------|---------|
-| `id` | string | Yes | Unique task identifier (PREFIX-NNN) | `"STRATEGY-001"` |
-| `title` | string | Yes | Short task title | `"Analyze changes and define test strategy"` |
-| `description` | string | Yes | Detailed task description (self-contained) | `"Analyze git diff, detect framework..."` |
-| `role` | enum | Yes | Worker role: `strategist`, `generator`, `executor`, `analyst` | `"generator"` |
-| `layer` | string | No | Test layer: `L1`, `L2`, `L3`, or empty | `"L1"` |
-| `coverage_target` | string | No | Target coverage percentage for this layer | `"80"` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"STRATEGY-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"STRATEGY-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) | `"[STRATEGY-001] Detected vitest, L1 target 80%..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` -> `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Generated 5 test files covering auth module..."` |
-| `pass_rate` | string | Test pass rate as decimal | `"0.95"` |
-| `coverage_achieved` | string | Actual coverage percentage achieved | `"82"` |
-| `test_files` | string | Semicolon-separated paths of test files | `"tests/L1-unit/auth.test.ts;tests/L1-unit/user.test.ts"` |
-| `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 (executor fix cycles) |
-
-Interactive tasks appear in master CSV for dependency tracking but are NOT included in wave-{N}.csv files.
-
----
-
-### Role Prefixes
-
-| Role | Prefix | Responsibility Type |
-|------|--------|---------------------|
-| strategist | STRATEGY | read-only analysis |
-| generator | TESTGEN | code-gen (test files) |
-| executor | TESTRUN | validation (run + fix) |
-| analyst | TESTANA | read-only analysis |
-
----
-
-### Example Data
-
-```csv
-id,title,description,role,layer,coverage_target,deps,context_from,exec_mode,wave,status,findings,pass_rate,coverage_achieved,test_files,error
-"STRATEGY-001","Analyze changes and define test strategy","Analyze git diff for changed files. Detect test framework (vitest/jest/pytest). Determine test layers needed (L1/L2/L3). Define coverage targets per layer. Generate prioritized test strategy document at <session>/strategy/test-strategy.md","strategist","","","","","csv-wave","1","pending","","","","",""
-"TESTGEN-001","Generate L1 unit tests","Generate L1 unit tests for priority files from strategy. Read source files, identify exports, generate test cases covering happy path, edge cases, error handling. Write tests to <session>/tests/L1-unit/. Follow project test conventions.","generator","L1","80","STRATEGY-001","STRATEGY-001","csv-wave","2","pending","","","","",""
-"TESTRUN-001","Execute L1 tests and collect coverage","Run L1 test suite with coverage collection. Parse results for pass rate and coverage. If pass_rate < 0.95 or coverage < 80%, attempt auto-fix (max 3 iterations). Save results to <session>/results/run-L1.json","executor","L1","80","TESTGEN-001","TESTGEN-001","interactive","3","pending","","","","",""
-"TESTGEN-002","Generate L2 integration tests","Generate L2 integration tests based on L1 results and strategy. Focus on module interaction points. Write tests to <session>/tests/L2-integration/.","generator","L2","60","TESTRUN-001","TESTRUN-001","csv-wave","4","pending","","","","",""
-"TESTRUN-002","Execute L2 tests and collect coverage","Run L2 integration test suite with coverage. Auto-fix up to 3 iterations. Save results to <session>/results/run-L2.json","executor","L2","60","TESTGEN-002","TESTGEN-002","interactive","5","pending","","","","",""
-"TESTANA-001","Quality analysis report","Analyze defect patterns, coverage gaps, GC loop effectiveness. Generate quality report with score and recommendations. Write to <session>/analysis/quality-report.md","analyst","","","TESTRUN-002","TESTRUN-001;TESTRUN-002","csv-wave","6","pending","","","","",""
-```
-
----
-
-### Column Lifecycle
-
-```
-Decomposer (Phase 1)     Wave Engine (Phase 2)    Agent (Execution)
----------------------    --------------------     -----------------
-id          ---------->  id          ---------->  id
-title       ---------->  title       ---------->  (reads)
-description ---------->  description ---------->  (reads)
-role        ---------->  role        ---------->  (reads)
-layer       ---------->  layer       ---------->  (reads)
-coverage_target ------->  coverage_target ------->  (reads)
-deps        ---------->  deps        ---------->  (reads)
-context_from---------->  context_from---------->  (reads)
-exec_mode   ---------->  exec_mode   ---------->  (reads)
-                         wave         ---------->  (reads)
-                         prev_context ---------->  (reads)
-                                                   status
-                                                   findings
-                                                   pass_rate
-                                                   coverage_achieved
-                                                   test_files
-                                                   error
-```
-
----
-
-## Output Schema (JSON)
-
-Agent output via `report_agent_job_result` (csv-wave tasks):
-
-```json
-{
-  "id": "TESTGEN-001",
-  "status": "completed",
-  "findings": "Generated 5 L1 unit test files covering auth, user, and session modules. Total 24 test cases: 15 happy path, 6 edge cases, 3 error handling.",
-  "pass_rate": "",
-  "coverage_achieved": "",
-  "test_files": "tests/L1-unit/auth.test.ts;tests/L1-unit/user.test.ts;tests/L1-unit/session.test.ts",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `framework_detected` | `data.framework` | `{framework, config_file, test_pattern}` | Test framework identified |
-| `test_generated` | `data.file` | `{file, source_file, test_count}` | Test file created |
-| `defect_found` | `data.file+data.line` | `{file, line, pattern, description}` | Defect pattern discovered |
-| `coverage_gap` | `data.file` | `{file, current, target, gap}` | Coverage gap identified |
-| `convention_found` | `data.pattern` | `{pattern, example_file, description}` | Test convention detected |
-| `fix_applied` | `data.test_file+data.fix_type` | `{test_file, fix_type, description}` | Test fix during GC loop |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T10:00:00Z","worker":"STRATEGY-001","type":"framework_detected","data":{"framework":"vitest","config_file":"vitest.config.ts","test_pattern":"**/*.test.ts"}}
-{"ts":"2026-03-08T10:05:00Z","worker":"TESTGEN-001","type":"test_generated","data":{"file":"tests/L1-unit/auth.test.ts","source_file":"src/auth.ts","test_count":8}}
-{"ts":"2026-03-08T10:10:00Z","worker":"TESTRUN-001","type":"defect_found","data":{"file":"src/auth.ts","line":42,"pattern":"null_reference","description":"Missing null check on token payload"}}
-{"ts":"2026-03-08T10:12:00Z","worker":"TESTRUN-001","type":"fix_applied","data":{"test_file":"tests/L1-unit/auth.test.ts","fix_type":"assertion_fix","description":"Fixed expected return type assertion"}}
-```
-
-> 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 |
-| Interactive task result | CSV task prev_context | Read from interactive/{id}-result.json |
-| Any agent discovery | Any agent | Shared via discoveries.ndjson |
-| Executor coverage data | GC loop handler | Read from results/run-{layer}.json |
-
----
-
-## 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}" |
-| Role valid | role in {strategist, generator, executor, analyst} | "Invalid role: {role}" |
-| Layer valid | layer in {L1, L2, L3, ""} | "Invalid layer: {layer}" |
-| Coverage target valid | If layer present, coverage_target is numeric | "Invalid coverage target: {value}" |