v0.7.1

Changes

• feat: Context path configuration and documentation reorganization (#143)

v0.7.0

Changes

• feat: add ExternalScout and optimize ContextScout with research-backed patterns (#128)

Documentation

• Updated README.md and QUICK_START.md for v0.6.0 accuracy
  • Updated version from 0.1.0-alpha.1 to 0.6.0
  • Added OpenImplementer agent to main agents list
  • Completed commands list with /analyze-patterns, /commit-openagents, /build-context-system
  • Highlighted ExternalScout with 18+ supported libraries
  • Updated installation profiles to mention new agents

v0.5.5

Changes

• fix(registry): add component-planning context and remove repo-specific contexts from user profiles (#125)

v0.5.2

Changes

• docs(core): refine project intelligence system and deprecate legacy context (#93)

v0.5.0

Changes

• refactor(evals): consolidate documentation and enhance test infrastructure (#56)

Added

• Explicit Context File Validation: New expectedContextFiles field in test YAML files allows explicit specification of which context files the agent must read
  • Overrides auto-detection when specified
  • Uses flexible pattern matching (includes() or endsWith())
  • Supports partial paths (e.g., standards/code.md) or full paths
  • See evals/agents/shared/tests/EXPLICIT_CONTEXT_FILES.md for detailed guide
  • Example test: evals/agents/shared/tests/golden/02-context-loading-explicit.yaml

Changed

• Context Loading Evaluator: Now accepts optional BehaviorExpectation config to support explicit file validation
  • Shows detection mode in evidence: "Explicit (from YAML test)" or "Auto-detect (from user message)"
  • Backward compatible - existing tests work unchanged

Documentation

• Added evals/agents/shared/tests/EXPLICIT_CONTEXT_FILES.md - Complete feature guide
• Added evals/PATTERN_MATCHING_GUIDE.md - Pattern matching reference
• Updated evals/CREATING_TESTS.md - Added expectedContextFiles documentation
• Updated evals/README.md - Added new feature section

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

Added

• Category-Based Agent Organization: Agents now organized by domain in subdirectories
  • core/ - Core system agents (openagent, opencoder)
  • meta/ - Meta-level agents (system-builder)
  • development/ - Development specialists (frontend-specialist, backend-specialist, devops-specialist, codebase-agent)
  • content/ - Content creation agents (copywriter, technical-writer)
  • data/ - Data and analysis agents (data-analyst)
  • product/ - Product management agents (directory created, ready for agents)
  • learning/ - Education and coaching agents (directory created, ready for agents)
• Category Metadata Files: Each category has 0-category.json documenting common subagents, tools, and context
• Subagent Organization: 13 subagents organized into 4 categories (code, core, system-builder, utils)
• Local Registry Fallback: Install script now supports local registry.json for development/testing
• Enhanced Registry Validation: Added checks for duplicate IDs and category consistency
• Comprehensive Test Suite: 15 automated validation tests for category system
• Audit Tools: Scripts to verify migration completeness and system integrity

Changed

• Agent File Structure: Agents moved from flat structure to category-based organization
  • Example: .opencode/agent/openagent.md → .opencode/agent/core/openagent.md
  • Example: .opencode/agent/opencoder.md → .opencode/agent/core/opencoder.md
• Registry Schema: Updated to include category-based paths for all agents
• Eval Framework: Enhanced with path resolution supporting both agent IDs and category paths
  • --agent=openagent resolves to core/openagent (backward compatible)
  • --agent=core/openagent works directly (new format)
• Documentation: Updated all docs to reference category-based structure
• Install Script: Enhanced with local registry fallback for offline/development use

Fixed

• Frontend Specialist: Renamed frontend-design-agent.md to frontend-specialist.md for consistency
• Eval Directory Structure: Archived legacy flat eval structure to _archive/ for clarity
• Registry Validation: Fixed validation script to handle category-based paths correctly

Developer Experience

• Backward Compatibility: Agent IDs like openagent still work via path resolution
• Local Testing: No need to push to GitHub to test registry changes
• Clear Organization: Agents grouped by domain make discovery easier
• Validation Tools: Automated tests ensure system integrity

Migration Notes

• Agent Paths: Update references from flat to category-based paths
  • Old: .opencode/agent/openagent.md
  • New: .opencode/agent/core/openagent.md
• Eval Framework: Both formats work due to path resolution
  • --agent=openagent (backward compatible)
  • --agent=core/openagent (new format)
• No Breaking Changes: Path resolution maintains backward compatibility

Technical Details

• Files Modified: 14+ files updated for category structure
• Agents Organized: 23 total agents (10 category agents, 13 subagents)
• Test Coverage: 15/15 validation tests passing (100%)
• Audit Status: 8/8 checks passing (100%)

v0.3.3

Version bump. See CHANGELOG.md for details.

v0.3.2

Automated version bump. See CHANGELOG.md for details.

v0.3.1

[0.3.1] - 2025-12-09

Changes

• fix(ci): resolve post-merge workflow heredoc parsing issue (#44)

Fixed

• Post-merge workflow now properly handles multiline commit messages
• Version bumping automation restored
• Changelog generation fixed

Previous Changes (from v0.3.0)

• Comprehensive verification and stabilization of main branch
• New prompt architecture (agent files as canonical defaults)
• Fixed PR #42 CI issues (prompt validation, package-lock, git merge base)
• Added execution-balance validation to 21 OpenAgent tests
• Enhanced OpenCoder agent with critical rules enforcement
• New agent creation system with templates and guides
• OpenCoder test suite with 8 comprehensive test cases
• Improved documentation and tooling

v0.0.1 - Initial Release

Initial Release

Features

• OpenAgent and OpenCoder evaluation framework
• Automated CI/CD testing pipeline
• Auto version bumping based on commit messages
• GitHub releases on version bump

Versioning

• feat: commits → minor bump (0.0.1 → 0.1.0)
• fix: commits → patch bump (0.0.1 → 0.0.2)
• Default → patch bump