OpenWriterControle/evals/framework/README.md
Darren Hinde c8f7103cb6
refactor(evals): consolidate documentation and enhance test infrastructure (#56)
* feat(agents): implement category-based agent organization system

- Organize agents into domain categories (core, development, content, data, product, learning)
- Move 10 agents to category subdirectories with proper git rename tracking
- Update 13 subagents with category and type metadata in frontmatter
- Add category metadata files (0-category.json) documenting common patterns
- Implement local registry fallback in install script for offline development
- Add comprehensive validation suite with 15 automated tests (100% pass rate)
- Enhance registry validation with duplicate ID and consistency checks
- Update eval framework with intelligent path resolution (backward compatible)
- Archive legacy eval structure to _archive/ for reference
- Update all documentation to reflect category-based structure
- Bump version to 0.5.0 with accurate CHANGELOG

Technical Details:
- 23 agents organized (10 category agents, 13 subagents)
- 6 category directories created
- Path resolution supports both agent IDs and category paths
- Registry schema updated to v2.0.0
- 159 files changed, 872 insertions(+), 10738 deletions(-)

BREAKING CHANGE: Agent file paths now use category structure. Update references from .opencode/agent/openagent.md to .opencode/agent/core/openagent.md. Eval framework maintains backward compatibility via path resolution.

* refactor(evals): consolidate documentation and enhance test infrastructure

- Remove temporary project tracking files (PHASE_5_COMPLETE, PROJECT_COMPLETE, etc.)
- Consolidate evaluation framework docs into main README
- Enhance test execution with improved logging and multi-prompt support
- Move system-builder from core to meta category
- Add comprehensive test suites for openagent with organized structure
- Create evaluation test structure for all subagents
- Clean up archived workflows and redundant documentation
- Update registry to reflect new agent organization
- Add shared test templates and golden test patterns

* feat(ci): add manual trigger support for bot-created PRs in validate-registry workflow

- Add pr_number input to workflow_dispatch for manually triggering validation
- Fetch PR details dynamically when triggered manually
- Support both automatic (PR event) and manual (workflow_dispatch) triggers
- Enable validation of bot-created PRs like automated version bumps
- Update branch detection and push logic to handle both trigger types
- Add documentation explaining how to manually trigger for bot PRs

* feat(evals): add explicit context file validation to test framework

- Add expectedContextFiles field to test YAML schema for explicit context file specification
- Enhance context-loading-evaluator to support both auto-detect and explicit validation modes
- Update documentation with comprehensive guide and examples
- Clean up archived legacy test structure (90+ old test files)
- Add new example tests demonstrating explicit context validation
- Backward compatible with existing tests

* feat(evals): add multi-agent logging system and performance optimizations

Implement comprehensive multi-agent logging and performance improvements for the eval framework.

Task 01: Multi-Agent Logging System
- Add complete hierarchical logging module (evals/framework/src/logging/)
  - SessionTracker: tracks parent-child delegation hierarchies
  - MultiAgentLogger: pretty-prints logs with visual indentation
  - Formatters: box characters and emoji formatting
  - 37 passing unit tests (session-tracker, logger, integration)
- Integrate with SDK event stream handler
  - Hook into session.created, message.updated, message.part.updated events
  - Real-time child session detection via timestamp heuristics
  - Message deduplication for cleaner output
- Enable in debug mode only (<1% performance overhead)
- Add demo script and comprehensive documentation

Task 02: Performance Optimizations
- Reduce grace period from 5s to 2s (67% reduction, 10-20% faster tests)
- Add PerformanceMetricsEvaluator for bottleneck identification
  - Collects tool latencies, inference time, idle time
  - Provides full performance visibility
- Update smoke test to validate delegation (core feature)
  - Replace simple read test with multi-agent delegation test
  - Tests both parent and child agent functionality
  - Validates multi-agent logging system

Results:
- 37 unit tests passing
- Smoke test passing (95/100 score)
- Clean hierarchical logging output
- 10-20% faster test execution
- Full multi-agent visibility

Files changed: 16 files, +2678 lines
Time saved: ~6-8 days (completed in 6 hours vs 3-5 day estimate)

* feat(evals): show child agent execution in non-debug mode

- Enable MultiAgentLogger in both debug and non-debug modes
- Add verbose parameter to control output level
- Non-verbose mode shows concise child session lifecycle:
  - Child agent started message
  - Child agent completed with duration
- Verbose mode (--debug) shows full delegation hierarchy
- Update documentation to reflect new behavior

This provides visibility into delegation without overwhelming output,
giving confidence that child agents are actually running.

* feat(evals): improve delegation testing and behavior validation

Major improvements to eval framework:

Test Suite:
- Add 00-smoke-test.yaml (basic read operation)
- Rename 01-smoke-test.yaml → 02-delegation-test.yaml (delegation test)
- Add simple-responder test agent for delegation testing
- Add debug test: simple-subagent-call.yaml

Evaluators:
- Add agent-model-evaluator.ts for agent/model validation
- Enhance behavior-evaluator.ts with detailed task tool output
- Improve delegation-evaluator.ts with better evidence tracking

Schema & Execution:
- Add expectedAgent and expectedModel to test schema
- Improve test executor with better logging and error handling

Documentation:
- Update evals/README.md with new features and performance improvements
- Remove outdated MULTI_AGENT_LOGGING_COMPLETE.md

Registry:
- Add simple-responder test agent to registry

Fixes:
- Fix dashboard.sh path resolution

These changes provide better visibility into delegation, improved test
coverage, and clearer validation of agent behavior.

* chore: add GitHub Actions workflow and plugin documentation

- Add .github/workflows/evals/run-evaluations.yml for automated eval testing
- Add dev/ai-tools/opencode/plugins/Plugin-inspiration.md for plugin development reference
2025-12-18 09:52:11 +00:00

267 lines
7.6 KiB
Markdown

# Evaluation Framework (Technical)
Core framework for evaluating agent behavior. For user documentation, see [../README.md](../README.md).
## Architecture
```
framework/
├── src/
│ ├── sdk/ # Test execution
│ │ ├── test-runner.ts # Main orchestrator
│ │ ├── test-executor.ts # Executes individual tests
│ │ ├── client-manager.ts
│ │ └── event-stream-handler.ts
│ ├── evaluators/ # Rule validators
│ │ ├── base-evaluator.ts
│ │ ├── approval-gate-evaluator.ts
│ │ ├── context-loading-evaluator.ts
│ │ ├── execution-balance-evaluator.ts
│ │ ├── tool-usage-evaluator.ts
│ │ ├── behavior-evaluator.ts
│ │ ├── delegation-evaluator.ts
│ │ ├── stop-on-failure-evaluator.ts
│ │ └── performance-metrics-evaluator.ts # NEW
│ ├── logging/ # Multi-agent logging (NEW)
│ │ ├── types.ts
│ │ ├── session-tracker.ts
│ │ ├── logger.ts
│ │ ├── formatters.ts
│ │ ├── index.ts
│ │ └── __tests__/ # 37 unit tests
│ ├── collector/ # Session data
│ │ ├── session-reader.ts
│ │ └── timeline-builder.ts
│ └── types/
│ └── index.ts
└── package.json
```
## Evaluators
### approval-gate
Checks that approval is requested before risky operations (bash, write, edit, task).
### context-loading
Verifies context files are loaded before acting on tasks.
**NEW:** Supports explicit context file specification via `expectedContextFiles` in test YAML.
- Auto-detect mode: Infers expected files from user message keywords
- Explicit mode: Uses files specified in `behavior.expectedContextFiles`
### execution-balance
Ensures read operations happen before write operations.
### tool-usage
Validates dedicated tools are used instead of bash antipatterns.
### behavior
Checks expected tools are used and forbidden tools are avoided.
### delegation
Validates complex tasks are delegated to subagents.
### stop-on-failure
Ensures agent stops on errors instead of auto-fixing.
### performance-metrics (NEW)
Collects performance data for analysis:
- Total test duration
- Tool latencies (avg, min, max per tool)
- LLM inference time estimation
- Idle time between events
- Event distribution
Always passes - used for metrics collection only.
## Multi-Agent Logging (NEW)
The framework now includes comprehensive multi-agent logging that tracks delegation hierarchies in real-time.
### Features
- **Visual hierarchy** - Box characters and indentation show parent-child relationships (debug mode)
- **Session tracking** - Tracks all sessions (parent, child, grandchild, etc.)
- **Real-time capture** - Hooks into SDK event stream for live updates
- **Non-verbose mode** - Shows child agent execution in normal mode without full debug output
- **Verbose mode** - Full delegation hierarchy with `--debug` flag
### Usage
```bash
# Non-verbose mode (default) - shows child agent completion
npm run eval:sdk -- --agent=openagent --pattern="**/test.yaml"
# Verbose mode (debug) - shows full delegation hierarchy
npm run eval:sdk -- --agent=openagent --pattern="**/test.yaml" --debug
```
### Example Output (Non-Verbose Mode)
```
Running tests...
✓ Child agent completed (OpenAgent, 2.9s)
Running evaluator: approval-gate...
```
### Example Output (Verbose Mode - Debug)
```
┌────────────────────────────────────────────────────────────┐
│ 🎯 PARENT: OpenAgent (ses_xxx...) │
└────────────────────────────────────────────────────────────┘
🔧 TOOL: task
├─ subagent: simple-responder
└─ Creating child session...
┌────────────────────────────────────────────────────────────┐
│ 🎯 CHILD: simple-responder (ses_yyy...) │
│ Parent: ses_xxx... │
│ Depth: 1 │
└────────────────────────────────────────────────────────────┘
🤖 Agent: AWESOME TESTING
✅ CHILD COMPLETE (2.9s)
✅ PARENT COMPLETE (20.9s)
```
See [src/logging/README.md](src/logging/README.md) for API documentation.
## Adding an Evaluator
1. Create `src/evaluators/my-evaluator.ts`:
```typescript
import { BaseEvaluator } from './base-evaluator.js';
import { TimelineEvent, SessionInfo, EvaluationResult } from '../types/index.js';
export class MyEvaluator extends BaseEvaluator {
name = 'my-evaluator';
description = 'What this evaluator checks';
async evaluate(timeline: TimelineEvent[], sessionInfo: SessionInfo): Promise<EvaluationResult> {
const checks = [];
const violations = [];
const evidence = [];
// Your evaluation logic here
const toolCalls = this.getToolCalls(timeline);
// Example check
const passed = toolCalls.length > 0;
checks.push({
name: 'has-tool-calls',
passed,
weight: 100,
evidence: [this.createEvidence('tool-count', `Found ${toolCalls.length} tool calls`, {})]
});
if (!passed) {
violations.push(this.createViolation(
'no-tool-calls',
'error',
'No tool calls found',
Date.now(),
{}
));
}
return this.buildResult(this.name, checks, violations, evidence, {});
}
}
```
2. Register in `test-runner.ts`:
```typescript
import { MyEvaluator } from '../evaluators/my-evaluator.js';
// In setupEvaluators():
this.evaluatorRunner = new EvaluatorRunner({
evaluators: [
// ... existing evaluators
new MyEvaluator(),
],
});
```
3. Add to test schema in `test-case-schema.ts`:
```typescript
export const ExpectedViolationSchema = z.object({
rule: z.enum([
// ... existing rules
'my-evaluator',
]),
// ...
});
```
## Development
```bash
# Install
npm install
# Build
npm run build
# Run tests
npm test
# Run SDK tests
npm run eval:sdk -- --agent=openagent --pattern="**/golden/*.yaml"
```
## Key Types
```typescript
interface TimelineEvent {
timestamp: number;
type: 'user_message' | 'assistant_message' | 'tool_call' | 'text';
data: any;
}
interface EvaluationResult {
evaluator: string;
passed: boolean;
score: number;
violations: Violation[];
evidence: Evidence[];
checks: Check[];
}
interface Violation {
type: string;
severity: 'error' | 'warning' | 'info';
message: string;
timestamp: number;
evidence?: any;
}
```
## Base Evaluator Helpers
```typescript
// Get all tool calls
const toolCalls = this.getToolCalls(timeline);
// Get specific tool calls
const bashCalls = this.getToolCallsByName(timeline, 'bash');
// Get assistant messages
const messages = this.getAssistantMessages(timeline);
// Get read tools (read, glob, grep, list)
const reads = this.getReadTools(timeline);
// Get execution tools (bash, write, edit, task)
const executions = this.getExecutionTools(timeline);
// Create violation
this.createViolation(type, severity, message, timestamp, evidence);
// Create evidence
this.createEvidence(type, description, data, timestamp?);
// Build result
this.buildResult(name, checks, violations, evidence, metadata);
```