claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-tech-debt/instructions/agent-instruction.md

@@ -1,390 +0,0 @@
-# Agent Instruction Template -- Team Tech Debt
-
-Role-specific instruction templates for CSV wave agents in the tech debt pipeline. Each role has a specialized instruction that is injected as the `instruction` parameter to `spawn_agents_on_csv`.
-
-## Purpose
-
-| Phase | Usage |
-|-------|-------|
-| Phase 1 | Orchestrator selects role-specific instruction based on task role |
-| Phase 2 | Injected as `instruction` parameter to `spawn_agents_on_csv` |
-
----
-
-## Scanner Instruction
-
-```markdown
-## TECH DEBT SCAN TASK
-
-### MANDATORY FIRST STEPS
-1. Read shared discoveries: <session-folder>/discoveries.ndjson (if exists)
-2. Read project context: .workflow/project-tech.json (if exists)
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Role**: scanner
-**Dimension Focus**: {debt_dimension}
-**Pipeline Mode**: {pipeline_mode}
-
-### Task Description
-{description}
-
-### Previous Context
-{prev_context}
-
----
-
-## Execution Protocol
-
-1. **Read discoveries**: Load <session-folder>/discoveries.ndjson
-2. **Detect project type**: Check package.json, pyproject.toml, go.mod, etc.
-3. **Scan 5 dimensions**:
-   - **Code**: Complexity > 10, TODO/FIXME, deprecated APIs, dead code, duplicated logic
-   - **Architecture**: Circular dependencies, god classes, layering violations, tight coupling
-   - **Testing**: Missing tests, low coverage, test quality issues, no integration tests
-   - **Dependency**: Outdated packages, known vulnerabilities, unused dependencies
-   - **Documentation**: Missing JSDoc/docstrings, stale API docs, no README sections
-4. **Use tools**: mcp__ace-tool__search_context for semantic search, Grep for pattern matching, Bash for static analysis tools
-5. **Standardize each finding**:
-   - id: TD-NNN (sequential)
-   - dimension: code|architecture|testing|dependency|documentation
-   - severity: critical|high|medium|low
-   - file: path, line: number
-   - description: issue description
-   - suggestion: fix suggestion
-   - estimated_effort: small|medium|large|unknown
-6. **Share discoveries**: Append each finding to discovery board:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"debt_item_found","data":{"id":"TD-NNN","dimension":"<dim>","severity":"<sev>","file":"<path>","line":<n>,"description":"<desc>","suggestion":"<fix>","estimated_effort":"<effort>"}}' >> <session-folder>/discoveries.ndjson
-   ```
-7. **Write artifact**: Save structured inventory to <session-folder>/scan/debt-inventory.json
-8. **Report result**
-
----
-
-## Output (report_agent_job_result)
-
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Scanned N dimensions. Found M debt items: X critical, Y high... (max 500 chars)",
-  "debt_items_count": "<total count>",
-  "artifacts_produced": "scan/debt-inventory.json",
-  "error": ""
-}
-```
-
----
-
-## Assessor Instruction
-
-```markdown
-## TECH DEBT ASSESSMENT TASK
-
-### MANDATORY FIRST STEPS
-1. Read shared discoveries: <session-folder>/discoveries.ndjson (if exists)
-2. Read debt inventory: <session-folder>/scan/debt-inventory.json
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Role**: assessor
-
-### Task Description
-{description}
-
-### Previous Context
-{prev_context}
-
----
-
-## Execution Protocol
-
-1. **Load debt inventory** from <session-folder>/scan/debt-inventory.json
-2. **Score each item**:
-   - **Impact Score** (1-5): critical=5, high=4, medium=3, low=1
-   - **Cost Score** (1-5): small=1, medium=3, large=5, unknown=3
-3. **Classify into priority quadrants**:
-   | Impact | Cost | Quadrant |
-   |--------|------|----------|
-   | >= 4 | <= 2 | quick-win |
-   | >= 4 | >= 3 | strategic |
-   | <= 3 | <= 2 | backlog |
-   | <= 3 | >= 3 | defer |
-4. **Sort** within each quadrant by impact_score descending
-5. **Share discoveries**: Append assessment summary to discovery board
-6. **Write artifact**: <session-folder>/assessment/priority-matrix.json
-7. **Report result**
-
----
-
-## Output (report_agent_job_result)
-
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Assessed M items. Quick-wins: X, Strategic: Y, Backlog: Z, Defer: W (max 500 chars)",
-  "debt_items_count": "<total assessed>",
-  "artifacts_produced": "assessment/priority-matrix.json",
-  "error": ""
-}
-```
-
----
-
-## Planner Instruction
-
-```markdown
-## TECH DEBT PLANNING TASK
-
-### MANDATORY FIRST STEPS
-1. Read shared discoveries: <session-folder>/discoveries.ndjson (if exists)
-2. Read priority matrix: <session-folder>/assessment/priority-matrix.json
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Role**: planner
-
-### Task Description
-{description}
-
-### Previous Context
-{prev_context}
-
----
-
-## Execution Protocol
-
-1. **Load priority matrix** from <session-folder>/assessment/priority-matrix.json
-2. **Group items**: quickWins (quick-win), strategic, backlog, deferred
-3. **Create 3-phase remediation plan**:
-   - **Phase 1: Quick Wins** -- High impact, low cost, immediate execution
-   - **Phase 2: Systematic** -- High impact, high cost, structured refactoring
-   - **Phase 3: Prevention** -- Long-term prevention mechanisms
-4. **Map action types** per dimension:
-   | Dimension | Action Type |
-   |-----------|-------------|
-   | code | refactor |
-   | architecture | restructure |
-   | testing | add-tests |
-   | dependency | update-deps |
-   | documentation | add-docs |
-5. **Generate prevention actions** for dimensions with >= 3 items:
-   | Dimension | Prevention |
-   |-----------|------------|
-   | code | Add linting rules for complexity thresholds |
-   | architecture | Introduce module boundary checks in CI |
-   | testing | Set minimum coverage thresholds |
-   | dependency | Configure automated update bot |
-   | documentation | Add docstring enforcement in linting |
-6. **Write artifacts**:
-   - <session-folder>/plan/remediation-plan.md (human-readable with checklists)
-   - <session-folder>/plan/remediation-plan.json (machine-readable)
-7. **Report result**
-
----
-
-## Output (report_agent_job_result)
-
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Created 3-phase plan. Phase 1: X quick-wins. Phase 2: Y systematic. Phase 3: Z prevention. Total actions: N (max 500 chars)",
-  "debt_items_count": "<total planned items>",
-  "artifacts_produced": "plan/remediation-plan.md;plan/remediation-plan.json",
-  "error": ""
-}
-```
-
----
-
-## Executor Instruction
-
-```markdown
-## TECH DEBT FIX EXECUTION TASK
-
-### MANDATORY FIRST STEPS
-1. Read shared discoveries: <session-folder>/discoveries.ndjson (if exists)
-2. Read remediation plan: <session-folder>/plan/remediation-plan.json
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Role**: executor
-
-### Task Description
-{description}
-
-### Previous Context
-{prev_context}
-
----
-
-## Execution Protocol
-
-**CRITICAL**: ALL file operations must execute within the worktree path.
-
-1. **Load remediation plan** from <session-folder>/plan/remediation-plan.json
-2. **Extract worktree path** from task description
-3. **Group actions by type**: refactor -> update-deps -> add-tests -> add-docs -> restructure
-4. **For each batch**:
-   - Read target files in worktree
-   - Apply changes following project conventions
-   - Validate changes compile/lint: `cd "<worktree>" && npx tsc --noEmit` or equivalent
-   - Track: items_fixed, items_failed, files_modified
-5. **After each batch**: Verify via `cd "<worktree>" && git diff --name-only`
-6. **Share discoveries**: Append fix_applied entries to discovery board:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"fix_applied","data":{"file":"<path>","change":"<desc>","lines_modified":<n>,"debt_id":"<TD-NNN>"}}' >> <session-folder>/discoveries.ndjson
-   ```
-7. **Self-validate**:
-   | Check | Command | Pass Criteria |
-   |-------|---------|---------------|
-   | Syntax | `cd "<worktree>" && npx tsc --noEmit` | No new errors |
-   | Lint | `cd "<worktree>" && npx eslint --no-error-on-unmatched-pattern` | No new errors |
-8. **Write artifact**: <session-folder>/fixes/fix-log.json
-9. **Report result**
-
----
-
-## Output (report_agent_job_result)
-
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Fixed X/Y items. Batches: refactor(N), update-deps(N), add-tests(N). Files modified: Z (max 500 chars)",
-  "debt_items_count": "<items fixed>",
-  "artifacts_produced": "fixes/fix-log.json",
-  "error": ""
-}
-```
-
----
-
-## Validator Instruction
-
-```markdown
-## TECH DEBT VALIDATION TASK
-
-### MANDATORY FIRST STEPS
-1. Read shared discoveries: <session-folder>/discoveries.ndjson (if exists)
-2. Read fix log: <session-folder>/fixes/fix-log.json (if exists)
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Role**: validator
-
-### Task Description
-{description}
-
-### Previous Context
-{prev_context}
-
----
-
-## Execution Protocol
-
-**CRITICAL**: ALL validation commands must execute within the worktree path.
-
-1. **Extract worktree path** from task description
-2. **Load fix results** from <session-folder>/fixes/fix-log.json
-3. **Run 4-layer validation**:
-
-   **Layer 1 -- Test Suite**:
-   - Command: `cd "<worktree>" && npm test` or `cd "<worktree>" && python -m pytest`
-   - PASS: No FAIL/error/failed keywords
-   - SKIP: No test runner available
-
-   **Layer 2 -- Type Check**:
-   - Command: `cd "<worktree>" && npx tsc --noEmit`
-   - Count: `error TS` occurrences
-
-   **Layer 3 -- Lint Check**:
-   - Command: `cd "<worktree>" && npx eslint --no-error-on-unmatched-pattern <modified-files>`
-   - Count: error occurrences
-
-   **Layer 4 -- Quality Analysis** (when > 5 modified files):
-   - Compare code quality before/after
-   - Assess complexity, duplication, naming improvements
-
-4. **Calculate debt score**:
-   - debt_score_after = debt items NOT in modified files (remaining unfixed)
-   - improvement_percentage = ((before - after) / before) * 100
-
-5. **Auto-fix attempt** (when total_regressions <= 3):
-   - Fix minor regressions inline
-   - Re-run validation checks
-
-6. **Share discoveries**: Append regression_found entries if any:
-   ```bash
-   echo '{"ts":"<ISO8601>","worker":"{id}","type":"regression_found","data":{"file":"<path>","test":"<test>","description":"<desc>","severity":"<sev>"}}' >> <session-folder>/discoveries.ndjson
-   ```
-
-7. **Write artifact**: <session-folder>/validation/validation-report.json with:
-   - validation_date, passed (bool), total_regressions
-   - checks: {tests, types, lint, quality} with per-check status
-   - debt_score_before, debt_score_after, improvement_percentage
-8. **Report result**
-
----
-
-## Output (report_agent_job_result)
-
-{
-  "id": "{id}",
-  "status": "completed" | "failed",
-  "findings": "Validation: PASSED|FAILED. Tests: OK/N failures. Types: OK/N errors. Lint: OK/N errors. Debt reduction: X% (max 500 chars)",
-  "debt_items_count": "<debt_score_after>",
-  "artifacts_produced": "validation/validation-report.json",
-  "error": ""
-}
-```
-
----
-
-## 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 |
-| `{debt_dimension}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{pipeline_mode}` | spawn_agents_on_csv | Runtime from CSV row |
-| `{prev_context}` | spawn_agents_on_csv | Runtime from CSV row |
-
----
-
-## Instruction Selection Logic
-
-The orchestrator selects the appropriate instruction section based on the task's `role` column:
-
-| Role | Instruction Section |
-|------|-------------------|
-| scanner | Scanner Instruction |
-| assessor | Assessor Instruction |
-| planner | Planner Instruction |
-| executor | Executor Instruction |
-| validator | Validator Instruction |
-
-Since each wave typically contains tasks from a single role (linear pipeline), the orchestrator uses the role of the first task in the wave to select the instruction template. The `<session-folder>` placeholder is replaced with the actual session path before injection.

package/.codex/skills/team-tech-debt/schemas/tasks-schema.md

@@ -1,196 +0,0 @@
-# Team Tech Debt -- CSV Schema
-
-## Master CSV: tasks.csv
-
-### Column Definitions
-
-#### Input Columns (Set by Decomposer)
-
-| Column | Type | Required | Description | Example |
-|--------|------|----------|-------------|---------|
-| `id` | string | Yes | Unique task identifier (TDPREFIX-NNN) | `"TDSCAN-001"` |
-| `title` | string | Yes | Short task title | `"Multi-dimension debt scan"` |
-| `description` | string | Yes | Detailed task description (self-contained) | `"Scan codebase across 5 dimensions..."` |
-| `role` | enum | Yes | Worker role: `scanner`, `assessor`, `planner`, `executor`, `validator` | `"scanner"` |
-| `debt_dimension` | string | Yes | Target dimensions: `all`, or specific dimension(s) | `"all"` |
-| `pipeline_mode` | enum | Yes | Pipeline mode: `scan`, `remediate`, `targeted` | `"remediate"` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"TDSCAN-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"TDSCAN-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 pipeline position) | `2` |
-| `prev_context` | string | Aggregated findings from context_from tasks (per-wave CSV only) | `"[TDSCAN-001] Found 42 debt items..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` -> `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Found 42 debt items: 5 critical, 12 high..."` |
-| `debt_items_count` | integer | Number of debt items processed | `42` |
-| `artifacts_produced` | string | Semicolon-separated artifact paths | `"scan/debt-inventory.json"` |
-| `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` | Plan approval, GC loop management |
-
-Interactive tasks appear in master CSV for dependency tracking but are NOT included in wave-{N}.csv files.
-
----
-
-### Role Registry
-
-| Role | Prefix | Responsibility | inner_loop |
-|------|--------|----------------|------------|
-| scanner | TDSCAN | Multi-dimension debt scanning | false |
-| assessor | TDEVAL | Quantitative severity assessment | false |
-| planner | TDPLAN | Phased remediation planning | false |
-| executor | TDFIX | Worktree-based debt cleanup | true |
-| validator | TDVAL | 4-layer validation | false |
-
----
-
-### Debt Dimensions
-
-| Dimension | Description | Tools/Methods |
-|-----------|-------------|---------------|
-| code | Code smells, complexity, duplication | Static analysis, complexity metrics |
-| architecture | Coupling, circular deps, layering violations | Dependency graph, coupling analysis |
-| testing | Missing tests, low coverage, test quality | Coverage analysis, test quality |
-| dependency | Outdated packages, vulnerabilities | Outdated check, vulnerability scan |
-| documentation | Missing docs, stale API docs | Doc coverage, API doc check |
-
----
-
-### Example Data
-
-```csv
-id,title,description,role,debt_dimension,pipeline_mode,deps,context_from,exec_mode,wave,status,findings,debt_items_count,artifacts_produced,error
-"TDSCAN-001","Multi-dimension debt scan","Scan codebase across code, architecture, testing, dependency, and documentation dimensions. Produce structured debt inventory with severity rankings.\nSession: .workflow/.csv-wave/td-auth-20260308\nScope: src/**","scanner","all","remediate","","","csv-wave","1","pending","","0","",""
-"TDEVAL-001","Severity assessment","Evaluate each debt item: impact score (1-5) x cost score (1-5). Classify into priority quadrants: quick-win, strategic, backlog, defer.\nSession: .workflow/.csv-wave/td-auth-20260308\nUpstream: TDSCAN-001 debt inventory","assessor","all","remediate","TDSCAN-001","TDSCAN-001","csv-wave","2","pending","","0","",""
-"TDPLAN-001","Remediation planning","Create 3-phase remediation plan: Phase 1 quick-wins, Phase 2 systematic, Phase 3 prevention.\nSession: .workflow/.csv-wave/td-auth-20260308\nUpstream: TDEVAL-001 priority matrix","planner","all","remediate","TDEVAL-001","TDEVAL-001","csv-wave","3","pending","","0","",""
-"PLAN-APPROVE","Plan approval gate","Review remediation plan and approve for execution","","all","remediate","TDPLAN-001","TDPLAN-001","interactive","3","pending","","0","",""
-"TDFIX-001","Debt cleanup execution","Apply remediation plan actions in worktree: refactor, update deps, add tests, add docs.\nSession: .workflow/.csv-wave/td-auth-20260308\nWorktree: .worktrees/td-auth-20260308","executor","all","remediate","PLAN-APPROVE","TDPLAN-001","csv-wave","4","pending","","0","",""
-"TDVAL-001","Cleanup validation","Run 4-layer validation: tests, type check, lint, quality analysis. Compare before/after debt scores.\nSession: .workflow/.csv-wave/td-auth-20260308\nWorktree: .worktrees/td-auth-20260308","validator","all","remediate","TDFIX-001","TDFIX-001","csv-wave","5","pending","","0","",""
-```
-
----
-
-### Column Lifecycle
-
-```
-Decomposer (Phase 1)     Wave Engine (Phase 2)    Agent (Execution)
----------------------    --------------------     -----------------
-id          ---------->  id          ---------->  id
-title       ---------->  title       ---------->  (reads)
-description ---------->  description ---------->  (reads)
-role        ---------->  role        ---------->  (reads)
-debt_dimension ------->  debt_dimension ------->  (reads)
-pipeline_mode -------->  pipeline_mode -------->  (reads)
-deps        ---------->  deps        ---------->  (reads)
-context_from---------->  context_from---------->  (reads)
-exec_mode   ---------->  exec_mode   ---------->  (reads)
-                         wave         ---------->  (reads)
-                         prev_context ---------->  (reads)
-                                                   status
-                                                   findings
-                                                   debt_items_count
-                                                   artifacts_produced
-                                                   error
-```
-
----
-
-## Output Schema (JSON)
-
-Agent output via `report_agent_job_result` (csv-wave tasks):
-
-```json
-{
-  "id": "TDSCAN-001",
-  "status": "completed",
-  "findings": "Scanned 5 dimensions. Found 42 debt items: 5 critical, 12 high, 15 medium, 10 low. Top issues: complex auth logic (code), circular deps in services (architecture), missing integration tests (testing).",
-  "debt_items_count": "42",
-  "artifacts_produced": "scan/debt-inventory.json",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `debt_item_found` | `data.file+data.line` | `{id, dimension, severity, file, line, description, suggestion, estimated_effort}` | Tech debt item identified |
-| `pattern_found` | `data.pattern_name+data.location` | `{pattern_name, location, description}` | Anti-pattern found |
-| `fix_applied` | `data.file+data.change` | `{file, change, lines_modified, debt_id}` | Fix applied |
-| `regression_found` | `data.file+data.test` | `{file, test, description, severity}` | Regression in validation |
-| `dependency_issue` | `data.package+data.issue` | `{package, current, latest, issue, severity}` | Dependency problem |
-| `metric_recorded` | `data.metric` | `{metric, value, dimension, file}` | Quality metric |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T10:00:00Z","worker":"TDSCAN-001","type":"debt_item_found","data":{"id":"TD-001","dimension":"code","severity":"high","file":"src/auth/jwt.ts","line":42,"description":"Cyclomatic complexity 18 exceeds threshold 10","suggestion":"Extract token validation logic","estimated_effort":"medium"}}
-{"ts":"2026-03-08T10:05:00Z","worker":"TDSCAN-001","type":"dependency_issue","data":{"package":"express","current":"4.17.1","latest":"4.19.2","issue":"Known security vulnerability CVE-2024-XXXX","severity":"critical"}}
-{"ts":"2026-03-08T10:30:00Z","worker":"TDFIX-001","type":"fix_applied","data":{"file":"src/auth/jwt.ts","change":"Extracted validateToken helper","lines_modified":25,"debt_id":"TD-001"}}
-```
-
-> Both csv-wave and interactive agents read/write the same discoveries.ndjson file.
-
----
-
-## Cross-Mechanism Context Flow
-
-| Source | Target | Mechanism |
-|--------|--------|-----------|
-| Scanner findings | Assessor | prev_context from TDSCAN + scan/debt-inventory.json |
-| Assessor matrix | Planner | prev_context from TDEVAL + assessment/priority-matrix.json |
-| Planner plan | Plan Approver | Interactive spawn reads plan/remediation-plan.md |
-| Plan approval | Executor | Interactive result in interactive/PLAN-APPROVE-result.json |
-| Executor fixes | Validator | prev_context from TDFIX + fixes/fix-log.json |
-| Validator results | GC Loop | Interactive read of validation/validation-report.json |
-| Any agent discovery | Any agent | Shared via discoveries.ndjson |
-
----
-
-## GC Loop Schema
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `gc_rounds` | integer | Current GC round (0-based) |
-| `max_gc_rounds` | integer | Maximum rounds (3) |
-| `fix_task_id` | string | Current fix task ID (TDFIX-fix-N) |
-| `val_task_id` | string | Current validation task ID (TDVAL-recheck-N) |
-| `regressions` | array | List of regression descriptions |
-
----
-
-## 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}" |
-| Role valid | role in {scanner, assessor, planner, executor, validator} | "Invalid role: {role}" |
-| Pipeline mode valid | pipeline_mode in {scan, remediate, targeted} | "Invalid pipeline_mode: {mode}" |
-| Description non-empty | Every task has description | "Empty description for task: {id}" |
-| Status enum | status in {pending, completed, failed, skipped} | "Invalid status: {status}" |
-| GC round limit | gc_rounds <= 3 | "GC round limit exceeded" |