claude-code-workflow 7.2.15 → 7.2.16

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

@@ -1,163 +0,0 @@
-# GC Loop Handler Agent
-
-Interactive agent that manages Generator-Critic loop iterations within the QA pipeline. 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
-- Consider scout findings when generating fixes (available in 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, scan results |
-| `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. Read discoveries.ndjson for scout-found issues (may inform additional test cases)
-4. 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 |
-
-5. Identify uncovered files from coverage report
-6. Cross-reference with scout findings for targeted coverage improvement
-
-**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
-   - Cross-reference with scout-discovered issues for high-value test targets
-   - 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>
-
-## Scout-Informed Additions
-- Added test for scout issue #<N>: <description> (if applicable)
-
-## 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 |
-| Scout findings not available | Proceed without scout context |
-| Timeout approaching | Output partial results with current state |

package/.codex/skills/team-quality-assurance/instructions/agent-instruction.md

@@ -1,185 +0,0 @@
-# Agent Instruction Template -- Team Quality Assurance
-
-Base instruction template for CSV wave agents in the QA pipeline. Used by scout, 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 Quality Assurance
-
-### 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 scan results: <session-folder>/scan/scan-results.json (if exists, for non-scout roles)
-4. Read test strategy: <session-folder>/strategy/test-strategy.md (if exists, for generator/analyst)
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Role**: {role}
-**Perspectives**: {perspective}
-**Layer**: {layer}
-**Coverage Target**: {coverage_target}%
-
-### Task Description
-{description}
-
-### Previous Tasks' Findings (Context)
-{prev_context}
-
----
-
-## Execution Protocol
-
-### If Role = scout
-
-1. **Determine scan scope**: Use git diff and task description to identify target files
-   ```bash
-   git diff --name-only HEAD~5 2>/dev/null || echo ""
-   ```
-2. **Load historical patterns**: Read discoveries.ndjson for known defect patterns
-3. **Execute multi-perspective scan**: For each perspective in {perspective} (semicolon-separated):
-   - **bug**: Scan for logic errors, crash paths, null references, unhandled exceptions
-   - **security**: Scan for vulnerabilities, hardcoded secrets, auth bypass, data exposure
-   - **test-coverage**: Identify untested code paths, missing assertions, uncovered branches
-   - **code-quality**: Detect anti-patterns, high complexity, duplicated logic, maintainability issues
-   - **ux** (if present): Check for user-facing issues, accessibility problems
-4. **Aggregate and rank**: Deduplicate by file:line, rank by severity (critical > high > medium > low)
-5. **Write scan results**: Save to <session-folder>/scan/scan-results.json:
-   ```json
-   {
-     "scan_date": "<ISO8601>",
-     "perspectives": ["bug", "security", ...],
-     "total_findings": <N>,
-     "by_severity": { "critical": <N>, "high": <N>, "medium": <N>, "low": <N> },
-     "findings": [{ "id": "<N>", "severity": "<level>", "perspective": "<name>", "file": "<path>", "line": <N>, "description": "<text>" }]
-   }
-   ```
-6. **Share discoveries**: For each critical/high finding:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"issue_found","data":{"file":"<path>","line":<N>,"severity":"<level>","perspective":"<name>","description":"<text>"}}' >> <session-folder>/discoveries.ndjson
-   ```
-
-### If Role = strategist
-
-1. **Read scout results**: Load <session-folder>/scan/scan-results.json (if discovery or full mode)
-2. **Analyze change scope**: Run `git diff --name-only HEAD~5` to identify changed files
-3. **Detect test framework**: Check for vitest.config.ts, jest.config.js, pytest.ini, pyproject.toml
-4. **Categorize files**: Source, Test, Config patterns
-5. **Select test layers**:
-
-   | Condition | Layer | Target |
-   |-----------|-------|--------|
-   | Has source file changes | L1: Unit Tests | 80% |
-   | >= 3 source files OR critical issues | L2: Integration Tests | 60% |
-   | >= 3 critical/high severity issues | L3: E2E Tests | 40% |
-
-6. **Generate strategy**: Write to <session-folder>/strategy/test-strategy.md with scope analysis, layer configs, priority issues, risk assessment
-7. **Share discoveries**: Append framework detection to 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 (limit 20 files)
-3. **Learn test patterns**: Find 3 existing test files to understand conventions (imports, structure, naming)
-4. **Detect if GC fix mode**: If task description contains "fix" -> read failure info from results/run-{layer}.json, fix failing tests only
-5. **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
-   - Include proper imports and mocks
-6. **Write test files**: Save to <session-folder>/tests/<layer-dir>/
-   - L1 -> tests/L1-unit/
-   - L2 -> tests/L2-integration/
-   - L3 -> tests/L3-e2e/
-7. **Syntax check**: Run `tsc --noEmit` or equivalent to verify syntax
-8. **Share discoveries**: Append test generation info to discoveries board
-
-### If Role = analyst
-
-1. **Read all results**: Load <session-folder>/results/run-*.json for execution data
-2. **Read scan results**: Load <session-folder>/scan/scan-results.json (if exists)
-3. **Read strategy**: Load <session-folder>/strategy/test-strategy.md
-4. **Read discoveries**: Parse <session-folder>/discoveries.ndjson for all findings
-5. **Analyze five dimensions**:
-   - **Defect patterns**: Group issues by type, identify patterns with >= 2 occurrences
-   - **Coverage gaps**: Compare achieved vs target per layer, identify per-file gaps
-   - **Test effectiveness**: Per layer -- pass rate, iterations, coverage achieved
-   - **Quality trend**: Compare against coverage_history if available
-   - **Quality score** (0-100): Start from 100, deduct for issues, gaps, failures; bonus for effective layers
-6. **Score-based recommendations**:
-
-   | Score | Recommendation |
-   |-------|----------------|
-   | >= 80 | Quality is GOOD. Maintain current practices. |
-   | 60-79 | Quality needs IMPROVEMENT. Focus on gaps and patterns. |
-   | < 60 | Quality is CONCERNING. Recommend comprehensive review. |
-
-7. **Generate report**: Write to <session-folder>/analysis/quality-report.md
-8. **Share discoveries**: Append quality metrics to board
-
----
-
-## Output (report_agent_job_result)
-
-Return JSON:
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Key discoveries and implementation notes (max 500 chars)",
-  "issues_found": "count of issues discovered (scout/analyst, empty for others)",
-  "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)",
-  "quality_score": "quality score 0-100 (analyst only, empty for others)",
-  "error": ""
-}
-```
-
----
-
-## Quality Requirements
-
-All agents must verify before reporting complete:
-
-| Requirement | Criteria |
-|-------------|----------|
-| Scan results written | Verify scan-results.json exists (scout) |
-| 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 |
-| `{perspective}` | 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-quality-assurance/schemas/tasks-schema.md

@@ -1,190 +0,0 @@
-# Team Quality Assurance -- 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) | `"SCOUT-001"` |
-| `title` | string | Yes | Short task title | `"Multi-perspective code scan"` |
-| `description` | string | Yes | Detailed task description (self-contained) | `"Scan codebase from multiple perspectives..."` |
-| `role` | enum | Yes | Worker role: `scout`, `strategist`, `generator`, `executor`, `analyst` | `"scout"` |
-| `perspective` | string | No | Scan perspectives (semicolon-separated, scout only) | `"bug;security;test-coverage;code-quality"` |
-| `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 | `"SCOUT-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"SCOUT-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) | `"[SCOUT-001] Found 5 security issues..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` -> `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Found 3 critical security issues..."` |
-| `issues_found` | string | Count of issues discovered (scout/analyst) | `"5"` |
-| `pass_rate` | string | Test pass rate as decimal (executor only) | `"0.95"` |
-| `coverage_achieved` | string | Actual coverage percentage (executor only) | `"82"` |
-| `test_files` | string | Semicolon-separated test file paths (generator only) | `"tests/L1-unit/auth.test.ts"` |
-| `quality_score` | string | Quality score 0-100 (analyst only) | `"78"` |
-| `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 |
-|------|--------|---------------------|
-| scout | SCOUT | read-only analysis (multi-perspective scan) |
-| strategist | QASTRAT | read-only analysis (strategy formulation) |
-| generator | QAGEN | code-gen (test file generation) |
-| executor | QARUN | validation (test execution + fix cycles) |
-| analyst | QAANA | read-only analysis (quality reporting) |
-
----
-
-### Example Data
-
-```csv
-id,title,description,role,perspective,layer,coverage_target,deps,context_from,exec_mode,wave,status,findings,issues_found,pass_rate,coverage_achieved,test_files,quality_score,error
-"SCOUT-001","Multi-perspective code scan","Scan codebase from bug, security, test-coverage, code-quality perspectives. Identify issues with severity ranking (critical/high/medium/low) and file:line references. Write scan results to <session>/scan/scan-results.json","scout","bug;security;test-coverage;code-quality","","","","","csv-wave","1","pending","","","","","","",""
-"QASTRAT-001","Test strategy formulation","Analyze scout findings and code changes. Determine test layers (L1/L2/L3), define coverage targets, detect test framework, identify priority files. Write strategy to <session>/strategy/test-strategy.md","strategist","","","","SCOUT-001","SCOUT-001","csv-wave","2","pending","","","","","","",""
-"QAGEN-L1-001","Generate L1 unit tests","Generate L1 unit tests based on strategy. Read source files, identify exports, generate test cases for happy path, edge cases, error handling. Follow project test conventions. Write tests to <session>/tests/L1-unit/","generator","","L1","80","QASTRAT-001","QASTRAT-001","csv-wave","3","pending","","","","","","",""
-"QAGEN-L2-001","Generate L2 integration tests","Generate L2 integration tests based on strategy. Focus on module interaction points and integration boundaries. Write tests to <session>/tests/L2-integration/","generator","","L2","60","QASTRAT-001","QASTRAT-001","csv-wave","3","pending","","","","","","",""
-"QARUN-L1-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","QAGEN-L1-001","QAGEN-L1-001","interactive","4","pending","","","","","","",""
-"QARUN-L2-001","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","QAGEN-L2-001","QAGEN-L2-001","interactive","4","pending","","","","","","",""
-"QAANA-001","Quality analysis report","Analyze defect patterns, coverage gaps, test effectiveness. Calculate quality score (0-100). Generate comprehensive report with recommendations. Write to <session>/analysis/quality-report.md","analyst","","","","QARUN-L1-001;QARUN-L2-001","QARUN-L1-001;QARUN-L2-001","csv-wave","5","pending","","","","","","",""
-"SCOUT-002","Regression scan","Post-fix regression scan. Verify no new issues introduced by test fixes. Focus on areas modified during GC loops.","scout","bug;security;code-quality","","","QAANA-001","QAANA-001","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)
-perspective ---------->  perspective ---------->  (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
-                                                   issues_found
-                                                   pass_rate
-                                                   coverage_achieved
-                                                   test_files
-                                                   quality_score
-                                                   error
-```
-
----
-
-## Output Schema (JSON)
-
-Agent output via `report_agent_job_result` (csv-wave tasks):
-
-```json
-{
-  "id": "SCOUT-001",
-  "status": "completed",
-  "findings": "Multi-perspective scan found 5 issues: 2 security (hardcoded keys, missing auth), 1 bug (null reference), 2 code-quality (duplicated logic, high complexity). All issues logged to discoveries.ndjson.",
-  "issues_found": "5",
-  "pass_rate": "",
-  "coverage_achieved": "",
-  "test_files": "",
-  "quality_score": "",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `issue_found` | `data.file+data.line` | `{file, line, severity, perspective, description}` | Issue discovered by scout |
-| `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 found during testing |
-| `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 |
-| `quality_metric` | `data.dimension` | `{dimension, score, details}` | Quality dimension score |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T10:00:00Z","worker":"SCOUT-001","type":"issue_found","data":{"file":"src/auth.ts","line":42,"severity":"high","perspective":"security","description":"Hardcoded secret key in auth module"}}
-{"ts":"2026-03-08T10:02:00Z","worker":"SCOUT-001","type":"issue_found","data":{"file":"src/user.ts","line":15,"severity":"medium","perspective":"bug","description":"Missing null check on user object"}}
-{"ts":"2026-03-08T10:05:00Z","worker":"QASTRAT-001","type":"framework_detected","data":{"framework":"vitest","config_file":"vitest.config.ts","test_pattern":"**/*.test.ts"}}
-{"ts":"2026-03-08T10:10:00Z","worker":"QAGEN-L1-001","type":"test_generated","data":{"file":"tests/L1-unit/auth.test.ts","source_file":"src/auth.ts","test_count":8}}
-{"ts":"2026-03-08T10:15:00Z","worker":"QARUN-L1-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:20:00Z","worker":"QAANA-001","type":"quality_metric","data":{"dimension":"coverage_achievement","score":85,"details":"L1: 82%, L2: 68%"}}
-```
-
-> Both csv-wave and interactive agents read/write the same discoveries.ndjson file.
-
----
-
-## Cross-Mechanism Context Flow
-
-| Source | Target | Mechanism |
-|--------|--------|-----------|
-| Scout findings | Strategist prev_context | CSV context_from column |
-| 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 |
-| Analyst quality score | Regression scout | Injected via prev_context |
-
----
-
-## 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 {scout, strategist, generator, executor, analyst} | "Invalid role: {role}" |
-| Layer valid | layer in {L1, L2, L3, ""} | "Invalid layer: {layer}" |
-| Perspective valid | If scout, perspective contains valid values | "Invalid perspective: {value}" |
-| Coverage target valid | If layer present, coverage_target is numeric | "Invalid coverage target: {value}" |