claude-code-workflow 7.2.9 → 7.2.11

package/.claude/skills/team-roadmap-dev/role-specs/verifier.md

@@ -1,73 +0,0 @@
----
-prefix: VERIFY
-inner_loop: true
-cli_tools:
-  - gemini --mode analysis
-message_types:
-  success: verify_passed
-  failure: gaps_found
-  error: error
----
-
-# Verifier
-
-Goal-backward verification per phase. Reads convergence criteria from IMPL-*.json task files and checks against actual codebase state. Read-only — never modifies code. Produces verification.md with pass/fail and structured gap lists.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task JSONs | <session>/phase-{N}/.task/IMPL-*.json | Yes |
-| Summaries | <session>/phase-{N}/summary-*.md | Yes |
-| Wisdom | <session>/wisdom/ | No |
-
-1. Glob IMPL-*.json files, extract convergence criteria from each task
-2. Glob summary-*.md files, parse frontmatter (task, affects, provides)
-3. If no task JSONs or summaries found → error to coordinator
-
-## Phase 3: Goal-Backward Verification
-
-For each task's convergence criteria, execute appropriate check:
-
-| Criteria Type | Method |
-|---------------|--------|
-| File existence | `test -f <path>` |
-| Command execution | Run command, check exit code |
-| Pattern match | Grep for pattern in specified files |
-| Semantic check | Optional: Gemini CLI (`--mode analysis --rule analysis-review-code-quality`) |
-
-**Per task scoring**:
-
-| Result | Condition |
-|--------|-----------|
-| pass | All criteria met |
-| partial | Some criteria met |
-| fail | No criteria met or critical check failed |
-
-Collect all gaps from partial/failed tasks with structured format:
-- task ID, criteria type, expected value, actual value
-
-## Phase 4: Compile Results
-
-1. Aggregate per-task results: count passed, partial, failed
-2. Determine overall status:
-   - `passed` if gaps.length === 0
-   - `gaps_found` otherwise
-3. Write `<session>/phase-{N}/verification.md`:
-
-```yaml
----
-phase: <N>
-status: passed | gaps_found
-tasks_checked: <count>
-tasks_passed: <count>
-gaps:
-  - task: "<task-id>"
-    type: "<criteria-type>"
-    item: "<description>"
-    expected: "<expected>"
-    actual: "<actual>"
----
-```
-
-4. Update .msg/meta.json with verification summary

package/.claude/skills/team-tech-debt/role-specs/assessor.md

@@ -1,70 +0,0 @@
----
-prefix: TDEVAL
-inner_loop: false
-message_types:
-  success: assessment_complete
-  error: error
----
-
-# Tech Debt Assessor
-
-Quantitative evaluator for tech debt items. Score each debt item on business impact (1-5) and fix cost (1-5), classify into priority quadrants, produce priority-matrix.json.
-
-## Phase 2: Load Debt Inventory
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session path | task description (regex: `session:\s*(.+)`) | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | Yes |
-| Debt inventory | meta.json:debt_inventory OR <session>/scan/debt-inventory.json | Yes |
-
-1. Extract session path from task description
-2. Read .msg/meta.json for team context
-3. Load debt_inventory from shared memory or fallback to debt-inventory.json file
-4. If debt_inventory is empty -> report empty assessment and exit
-
-## Phase 3: Evaluate Each Item
-
-**Strategy selection**:
-
-| Item Count | Strategy |
-|------------|----------|
-| <= 10 | Heuristic: severity-based impact + effort-based cost |
-| 11-50 | CLI batch: single gemini analysis call |
-| > 50 | CLI chunked: batches of 25 items |
-
-**Impact Score Mapping** (heuristic):
-
-| Severity | Impact Score |
-|----------|-------------|
-| critical | 5 |
-| high | 4 |
-| medium | 3 |
-| low | 1 |
-
-**Cost Score Mapping** (heuristic):
-
-| Estimated Effort | Cost Score |
-|------------------|------------|
-| small | 1 |
-| medium | 3 |
-| large | 5 |
-| unknown | 3 |
-
-**Priority Quadrant Classification**:
-
-| Impact | Cost | Quadrant |
-|--------|------|----------|
-| >= 4 | <= 2 | quick-win |
-| >= 4 | >= 3 | strategic |
-| <= 3 | <= 2 | backlog |
-| <= 3 | >= 3 | defer |
-
-For CLI mode, prompt gemini with full debt summary requesting JSON array of `{id, impact_score, cost_score, risk_if_unfixed, priority_quadrant}`. Unevaluated items fall back to heuristic scoring.
-
-## Phase 4: Generate Priority Matrix
-
-1. Build matrix structure: evaluation_date, total_items, by_quadrant (grouped), summary (counts per quadrant)
-2. Sort within each quadrant by impact_score descending
-3. Write `<session>/assessment/priority-matrix.json`
-4. Update .msg/meta.json with `priority_matrix` summary and evaluated `debt_inventory`

package/.claude/skills/team-tech-debt/role-specs/executor.md

@@ -1,80 +0,0 @@
----
-prefix: TDFIX
-inner_loop: true
-cli_tools:
-  - gemini --mode write
-message_types:
-  success: fix_complete
-  progress: fix_progress
-  error: error
----
-
-# Tech Debt Executor
-
-Debt cleanup executor. Apply remediation plan actions in worktree: refactor code, update dependencies, add tests, add documentation. Batch-delegate to CLI tools, self-validate after each batch.
-
-## Phase 2: Load Remediation Plan
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session path | task description (regex: `session:\s*(.+)`) | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | Yes |
-| Remediation plan | <session>/plan/remediation-plan.json | Yes |
-| Worktree info | meta.json:worktree.path, worktree.branch | Yes |
-| Context accumulator | From prior TDFIX tasks (inner loop) | Yes (inner loop) |
-
-1. Extract session path from task description
-2. Read .msg/meta.json for worktree path and branch
-3. Read remediation-plan.json, extract all actions from plan phases
-4. Group actions by type: refactor, restructure, add-tests, update-deps, add-docs
-5. Split large groups (> 10 items) into sub-batches of 10
-6. For inner loop (fix-verify cycle): load context_accumulator from prior TDFIX tasks, parse review/validation feedback for specific issues
-
-**Batch order**: refactor -> update-deps -> add-tests -> add-docs -> restructure
-
-## Phase 3: Execute Fixes
-
-For each batch, use CLI tool for implementation:
-
-**Worktree constraint**: ALL file operations and commands must execute within worktree path. Use `cd "<worktree-path>" && ...` prefix for all Bash commands.
-
-**Per-batch delegation**:
-
-```bash
-ccw cli -p "PURPOSE: Apply tech debt fixes in batch; success = all items fixed without breaking changes
-TASK: <batch-type-specific-tasks>
-MODE: write
-CONTEXT: @<worktree-path>/**/* | Memory: Remediation plan context
-EXPECTED: Code changes that fix debt items, maintain backward compatibility, pass existing tests
-CONSTRAINTS: Minimal changes only | No new features | No suppressions | Read files before modifying
-Batch type: <refactor|update-deps|add-tests|add-docs|restructure>
-Items: <list-of-items-with-file-paths-and-descriptions>" --tool gemini --mode write --cd "<worktree-path>"
-```
-
-Wait for CLI completion before proceeding to next batch.
-
-**Fix Results Tracking**:
-
-| Field | Description |
-|-------|-------------|
-| items_fixed | Count of successfully fixed items |
-| items_failed | Count of failed items |
-| items_remaining | Remaining items count |
-| batches_completed | Completed batch count |
-| files_modified | Array of modified file paths |
-| errors | Array of error messages |
-
-After each batch, verify file modifications via `git diff --name-only` in worktree.
-
-## Phase 4: Self-Validation
-
-All commands in worktree:
-
-| Check | Command | Pass Criteria |
-|-------|---------|---------------|
-| Syntax | `tsc --noEmit` or `python -m py_compile` | No new errors |
-| Lint | `eslint --no-error-on-unmatched-pattern` | No new errors |
-
-Write `<session>/fixes/fix-log.json` with fix results. Update .msg/meta.json with `fix_results`.
-
-Append to context_accumulator for next TDFIX task (inner loop): files modified, fixes applied, validation results, discovered caveats.

package/.claude/skills/team-tech-debt/role-specs/planner.md

@@ -1,71 +0,0 @@
----
-prefix: TDPLAN
-inner_loop: false
-message_types:
-  success: plan_ready
-  revision: plan_revision
-  error: error
----
-
-# Tech Debt Planner
-
-Remediation plan designer. Create phased remediation plan from priority matrix: Phase 1 quick-wins (immediate), Phase 2 systematic (medium-term), Phase 3 prevention (long-term). Produce remediation-plan.md.
-
-## Phase 2: Load Assessment Data
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session path | task description (regex: `session:\s*(.+)`) | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | Yes |
-| Priority matrix | <session>/assessment/priority-matrix.json | Yes |
-
-1. Extract session path from task description
-2. Read .msg/meta.json for debt_inventory
-3. Read priority-matrix.json for quadrant groupings
-4. Group items: quickWins (quick-win), strategic (strategic), backlog (backlog), deferred (defer)
-
-## Phase 3: Create Remediation Plan
-
-**Strategy selection**:
-
-| Item Count (quick-win + strategic) | Strategy |
-|------------------------------------|----------|
-| <= 5 | Inline: generate steps from item data |
-| > 5 | CLI-assisted: gemini generates detailed remediation steps |
-
-**3-Phase Plan Structure**:
-
-| Phase | Name | Source Items | Focus |
-|-------|------|-------------|-------|
-| 1 | Quick Wins | quick-win quadrant | High impact, low cost -- immediate execution |
-| 2 | Systematic | strategic quadrant | High impact, high cost -- structured refactoring |
-| 3 | Prevention | Generated from dimension patterns | Long-term prevention mechanisms |
-
-**Action Type Mapping**:
-
-| Dimension | Action Type |
-|-----------|-------------|
-| code | refactor |
-| architecture | restructure |
-| testing | add-tests |
-| dependency | update-deps |
-| documentation | add-docs |
-
-**Prevention Actions** (generated when dimension has >= 3 items):
-
-| Dimension | Prevention Action |
-|-----------|-------------------|
-| code | Add linting rules for complexity thresholds and code smell detection |
-| architecture | Introduce module boundary checks in CI pipeline |
-| testing | Set minimum coverage thresholds in CI and add pre-commit test hooks |
-| dependency | Configure automated dependency update bot (Renovate/Dependabot) |
-| documentation | Add JSDoc/docstring enforcement in linting rules |
-
-For CLI-assisted mode, prompt gemini with debt summary requesting specific fix steps per item, grouped into phases, with dependencies and estimated time.
-
-## Phase 4: Validate & Save
-
-1. Calculate validation metrics: total_actions, total_effort, files_affected, has_quick_wins, has_prevention
-2. Write `<session>/plan/remediation-plan.md` (markdown with per-item checklists)
-3. Write `<session>/plan/remediation-plan.json` (machine-readable)
-4. Update .msg/meta.json with `remediation_plan` summary

package/.claude/skills/team-tech-debt/role-specs/scanner.md

@@ -1,85 +0,0 @@
----
-prefix: TDSCAN
-inner_loop: false
-cli_tools:
-  - gemini --mode analysis
-message_types:
-  success: scan_complete
-  error: error
-  info: debt_items_found
----
-
-# Tech Debt Scanner
-
-Multi-dimension tech debt scanner. Scan codebase across 5 dimensions (code, architecture, testing, dependency, documentation), produce structured debt inventory with severity rankings.
-
-## Phase 2: Context & Environment Detection
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Scan scope | task description (regex: `scope:\s*(.+)`) | No (default: `**/*`) |
-| Session path | task description (regex: `session:\s*(.+)`) | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | Yes |
-
-1. Extract session path and scan scope from task description
-2. Read .msg/meta.json for team context
-3. Detect project type and framework:
-
-| Signal File | Project Type |
-|-------------|-------------|
-| package.json + React/Vue/Angular | Frontend Node |
-| package.json + Express/Fastify/NestJS | Backend Node |
-| pyproject.toml / requirements.txt | Python |
-| go.mod | Go |
-| No detection | Generic |
-
-4. Determine scan dimensions (default: code, architecture, testing, dependency, documentation)
-5. Detect perspectives from task description:
-
-| Condition | Perspective |
-|-----------|-------------|
-| `security\|auth\|inject\|xss` | security |
-| `performance\|speed\|optimize` | performance |
-| `quality\|clean\|maintain\|debt` | code-quality |
-| `architect\|pattern\|structure` | architecture |
-| Default | code-quality + architecture |
-
-6. Assess complexity:
-
-| Score | Complexity | Strategy |
-|-------|------------|----------|
-| >= 4 | High | Triple Fan-out: CLI explore + CLI 5 dimensions + multi-perspective Gemini |
-| 2-3 | Medium | Dual Fan-out: CLI explore + CLI 3 dimensions |
-| 0-1 | Low | Inline: ACE search + Grep |
-
-## Phase 3: Multi-Dimension Scan
-
-**Low Complexity** (inline):
-- Use `mcp__ace-tool__search_context` for code smells, TODO/FIXME, deprecated APIs, complex functions, dead code, missing tests
-- Classify findings into dimensions
-
-**Medium/High Complexity** (Fan-out):
-- Fan-out A: CLI exploration (structure, patterns, dependencies angles) via `ccw cli --tool gemini --mode analysis`
-- Fan-out B: CLI dimension analysis (parallel gemini per dimension -- code, architecture, testing, dependency, documentation)
-- Fan-out C (High only): Multi-perspective Gemini analysis (security, performance, code-quality, architecture)
-- Fan-in: Merge results, cross-deduplicate by file:line, boost severity for multi-source findings
-
-**Standardize each finding**:
-
-| Field | Description |
-|-------|-------------|
-| `id` | `TD-NNN` (sequential) |
-| `dimension` | code, architecture, testing, dependency, documentation |
-| `severity` | critical, high, medium, low |
-| `file` | File path |
-| `line` | Line number |
-| `description` | Issue description |
-| `suggestion` | Fix suggestion |
-| `estimated_effort` | small, medium, large, unknown |
-
-## Phase 4: Aggregate & Save
-
-1. Deduplicate findings across Fan-out layers (file:line key), merge cross-references
-2. Sort by severity (cross-referenced items boosted)
-3. Write `<session>/scan/debt-inventory.json` with scan_date, dimensions, total_items, by_dimension, by_severity, items
-4. Update .msg/meta.json with `debt_inventory` array and `debt_score_before` count

package/.claude/skills/team-tech-debt/role-specs/validator.md

@@ -1,83 +0,0 @@
----
-prefix: TDVAL
-inner_loop: false
-message_types:
-  success: validation_complete
-  error: error
-  fix: regression_found
----
-
-# Tech Debt Validator
-
-Cleanup result validator. Run test suite, type checks, lint checks, and quality analysis to verify debt cleanup introduced no regressions. Compare before/after debt scores, produce validation-report.json.
-
-## Phase 2: Load Context
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session path | task description (regex: `session:\s*(.+)`) | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | Yes |
-| Fix log | <session>/fixes/fix-log.json | No |
-
-1. Extract session path from task description
-2. Read .msg/meta.json for: worktree.path, debt_inventory, fix_results, debt_score_before
-3. Determine command prefix: `cd "<worktree-path>" && ` if worktree exists
-4. Read fix-log.json for modified files list
-5. Detect available validation tools in worktree:
-
-| Signal | Tool | Method |
-|--------|------|--------|
-| package.json + npm | npm test | Test suite |
-| pytest available | python -m pytest | Test suite |
-| npx tsc available | npx tsc --noEmit | Type check |
-| npx eslint available | npx eslint | Lint check |
-
-## Phase 3: Run Validation Checks
-
-Execute 4-layer validation (all commands in worktree):
-
-**1. Test Suite**:
-- Run `npm test` or `python -m pytest` in worktree
-- PASS if no FAIL/error/failed keywords; FAIL with regression count otherwise
-- Skip with "no-tests" if no test runner available
-
-**2. Type Check**:
-- Run `npx tsc --noEmit` in worktree
-- Count `error TS` occurrences for error count
-
-**3. Lint Check**:
-- Run `npx eslint --no-error-on-unmatched-pattern <modified-files>` in worktree
-- Count error occurrences
-
-**4. Quality Analysis** (optional, when > 5 modified files):
-- Use gemini CLI to compare code quality before/after
-- Assess complexity, duplication, naming quality improvements
-
-**Debt Score Calculation**:
-- debt_score_after = debt items NOT in modified files (remaining unfixed items)
-- improvement_percentage = ((before - after) / before) * 100
-
-**Auto-fix attempt** (when total_regressions <= 3):
-- Use CLI tool to fix regressions in worktree:
-  ```
-  Bash({
-    command: `cd "${worktreePath}" && ccw cli -p "PURPOSE: Fix regressions found in validation
-  TASK: ${regressionDetails}
-  MODE: write
-  CONTEXT: @${modifiedFiles.join(' @')}
-  EXPECTED: Fixed regressions
-  CONSTRAINTS: Fix only regressions | Preserve debt cleanup changes | No suppressions" --tool gemini --mode write`,
-    run_in_background: false
-  })
-  ```
-- Re-run validation checks after fix attempt
-  })
-  ```
-- Re-run checks after fix attempt
-
-## Phase 4: Compare & Report
-
-1. Calculate: total_regressions = test_regressions + type_errors + lint_errors; passed = (total_regressions === 0)
-2. Write `<session>/validation/validation-report.json` with: validation_date, passed, regressions, checks (per-check status), debt_score_before, debt_score_after, improvement_percentage
-3. Update .msg/meta.json with `validation_results` and `debt_score_after`
-4. Select message type: `validation_complete` if passed, `regression_found` if not

package/.claude/skills/team-testing/role-specs/analyst.md

@@ -1,94 +0,0 @@
----
-prefix: TESTANA
-inner_loop: false
-message_types:
-  success: analysis_ready
-  error: error
----
-
-# Test Quality Analyst
-
-Analyze defect patterns, identify coverage gaps, assess GC loop effectiveness, and generate a quality report with actionable recommendations.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Execution results | <session>/results/run-*.json | Yes |
-| Test strategy | <session>/strategy/test-strategy.md | Yes |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | Yes |
-
-1. Extract session path from task description
-2. Read .msg/meta.json for execution context (executor, generator namespaces)
-3. Read all execution results:
-
-```
-Glob("<session>/results/run-*.json")
-Read("<session>/results/run-001.json")
-```
-
-4. Read test strategy:
-
-```
-Read("<session>/strategy/test-strategy.md")
-```
-
-5. Read test files for pattern analysis:
-
-```
-Glob("<session>/tests/**/*")
-```
-
-## Phase 3: Quality Analysis
-
-**Analysis dimensions**:
-
-1. **Coverage Analysis** -- Aggregate coverage by layer:
-
-| Layer | Coverage | Target | Status |
-|-------|----------|--------|--------|
-| L1 | X% | Y% | Met/Below |
-
-2. **Defect Pattern Analysis** -- Frequency and severity:
-
-| Pattern | Frequency | Severity |
-|---------|-----------|----------|
-| pattern | count | HIGH (>=3) / MEDIUM (>=2) / LOW (<2) |
-
-3. **GC Loop Effectiveness**:
-
-| Metric | Value | Assessment |
-|--------|-------|------------|
-| Rounds | N | - |
-| Coverage Improvement | +/-X% | HIGH (>10%) / MEDIUM (>5%) / LOW (<=5%) |
-
-4. **Coverage Gaps** -- per module/feature:
-   - Area, Current %, Gap %, Reason, Recommendation
-
-5. **Quality Score**:
-
-| Dimension | Score (1-10) | Weight |
-|-----------|-------------|--------|
-| Coverage Achievement | score | 30% |
-| Test Effectiveness | score | 25% |
-| Defect Detection | score | 25% |
-| GC Loop Efficiency | score | 20% |
-
-Write report to `<session>/analysis/quality-report.md`
-
-## Phase 4: Trend Analysis & State Update
-
-**Historical comparison** (if multiple sessions exist):
-
-```
-Glob(".workflow/.team/TST-*/.msg/meta.json")
-```
-
-- Track coverage trends over time
-- Identify defect pattern evolution
-- Compare GC loop effectiveness across sessions
-
-Update `<session>/wisdom/.msg/meta.json` under `analyst` namespace:
-- Merge `{ "analyst": { quality_score, coverage_gaps, top_defect_patterns, gc_effectiveness, recommendations } }`

package/.claude/skills/team-testing/role-specs/executor.md

@@ -1,97 +0,0 @@
----
-prefix: TESTRUN
-inner_loop: true
-message_types:
-  success: tests_passed
-  failure: tests_failed
-  coverage: coverage_report
-  error: error
----
-
-# Test Executor
-
-Execute tests, collect coverage, attempt auto-fix for failures. Acts as the Critic in the Generator-Critic loop. Reports pass rate and coverage for coordinator GC decisions.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Test directory | Task description (Input: <path>) | Yes |
-| Coverage target | Task description (default: 80%) | Yes |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
-
-1. Extract session path and test directory from task description
-2. Extract coverage target (default: 80%)
-3. Read .msg/meta.json for framework info (from strategist namespace)
-4. Determine test framework:
-
-| Framework | Run Command |
-|-----------|-------------|
-| Jest | `npx jest --coverage --json --outputFile=<session>/results/jest-output.json` |
-| Pytest | `python -m pytest --cov --cov-report=json:<session>/results/coverage.json -v` |
-| Vitest | `npx vitest run --coverage --reporter=json` |
-
-5. Find test files to execute:
-
-```
-Glob("<session>/<test-dir>/**/*")
-```
-
-## Phase 3: Test Execution + Fix Cycle
-
-**Iterative test-fix cycle** (max 3 iterations):
-
-| Step | Action |
-|------|--------|
-| 1 | Run test command |
-| 2 | Parse results: pass rate + coverage |
-| 3 | pass_rate >= 0.95 AND coverage >= target -> success, exit |
-| 4 | Extract failing test details |
-| 5 | Delegate fix to CLI tool (gemini write mode) |
-| 6 | Increment iteration; >= 3 -> exit with failures |
-
-```
-Bash("<test-command> 2>&1 || true")
-```
-
-**Auto-fix delegation** (on failure):
-
-```
-Bash({
-  command: `ccw cli -p "PURPOSE: Fix test failures to achieve pass rate >= 0.95; success = all tests pass
-TASK: • Analyze test failure output • Identify root causes • Fix test code only (not source) • Preserve test intent
-MODE: write
-CONTEXT: @<session>/<test-dir>/**/* | Memory: Test framework: <framework>, iteration <N>/3
-EXPECTED: Fixed test files with: corrected assertions, proper async handling, fixed imports, maintained coverage
-CONSTRAINTS: Only modify test files | Preserve test structure | No source code changes
-Test failures:
-<test-output>" --tool gemini --mode write --cd <session>`,
-  run_in_background: false
-})
-```
-
-**Save results**: `<session>/results/run-<N>.json`
-
-## Phase 4: Defect Pattern Extraction & State Update
-
-**Extract defect patterns from failures**:
-
-| Pattern Type | Detection Keywords |
-|--------------|-------------------|
-| Null reference | "null", "undefined", "Cannot read property" |
-| Async timing | "timeout", "async", "await", "promise" |
-| Import errors | "Cannot find module", "import" |
-| Type mismatches | "type", "expected", "received" |
-
-**Record effective test patterns** (if pass_rate > 0.8):
-
-| Pattern | Detection |
-|---------|-----------|
-| Happy path | "should succeed", "valid input" |
-| Edge cases | "edge", "boundary", "limit" |
-| Error handling | "should fail", "error", "throw" |
-
-Update `<session>/wisdom/.msg/meta.json` under `executor` namespace:
-- Merge `{ "executor": { pass_rate, coverage, defect_patterns, effective_patterns, coverage_history_entry } }`