🚀 TDD Enhancement: Comprehensive Test-Driven Development for OAC

[robbiebow]

📋 Summary

This PR adds comprehensive Test-Driven Development (TDD) capabilities to OpenAgentsControl, transforming it into a true TDD-first development framework with mandatory testing requirements at every level.

✅ Changes

NEW: TDD Standards Context

• Added .opencode/context/core/standards/tdd.md
• Establishes mandatory TDD practices with strict enforcement rules
• Red-Green-Refactor sequence enforcement
• Test quality requirements (positive/negative, AAA pattern, mocking)
• Blocking rules for CoderAgent

ENHANCED: CoderAgent

• Modified .opencode/agent/subagents/code/coder-agent.md
• Added @test_first rule: Write failing test BEFORE implementation
• Added @test_never_skip rule: Never complete without tests
• Added Step 3.5: Verify Test Exists (TDD Mandate)
• Enhanced Step 6: Implement with TDD Green Phase
• Added Check 5: TDD Verification in Self-Review Loop

ENHANCED: OpenCoder

• Modified .opencode/agent/core/opencoder.md
• Added TDD Verification (MANDATORY) to Stage 6: ValidateAndHandoff
• Verifies RED→GREEN pattern before handoff
• Rejects implementation if TDD checks fail
• Added TDD Enforcement statement to execution philosophy

🎯 Architecture

TDD enforcement is distributed across two levels:

1. CoderAgent (Implementation): Enforces TDD at code implementation time

   • RED phase: Write failing test first
   • GREEN phase: Implement to pass test

2. OpenCoder (Orchestration): Validates TDD at handoff time

   • Verifies all TDD checks passed
   • Rejects if any checks fail

✨ Benefits

• Mandatory test-first development: All code must follow RED→GREEN workflow
• Production-ready code: Comprehensive testing at every stage
• Reduced bugs: Early detection through TDD methodology
• Team consistency: Shared standards committed to repository
• Clear enforcement: Blocking rules prevent test-free completion

🔍 What This Means

• CoderAgent now blocks completion if tests are missing or failing
• OpenCoder validates TDD was followed before handoff
• All tests must follow Arrange-Act-Assert pattern
• Both positive and negative test cases required
• No exceptions to TDD workflow without documentation

---

TDD is now the foundation of OAC development!