Commit Graph

2 Commits

Author SHA1 Message Date
freemo db7e044b18 refactor: complete tier selector architecture migration for all agents
BREAKING CHANGE: Removed all tier-specific agents in favor of model-agnostic versions

Key changes:
- Create model-agnostic agents:
  - behave-tester.md (replaces 4 tier-specific versions)
  - robot-tester.md (replaces 4 tier-specific versions)
  - coverage-improver.md (replaces coverage-checker with escalation)
- Convert existing agents to support escalation:
  - lint-fixer.md (now model-agnostic)
  - test-fixer.md (now model-agnostic)
  - integration-test-runner.md (now model-agnostic)
- Update tier selectors to support all new agents
- Update quality-gate-escalator to handle all quality fixers
- Update subtask-loop to use quality-gate-escalator for all quality gates
- Empty redundant tier-specific agents for deletion:
  - All implementer-{tier}.md files
  - All behave-tester-{tier}.md files
  - All robot-tester-{tier}.md files
  - coverage-checker.md (replaced by coverage-improver.md)

Benefits:
- Eliminates ~90% code duplication
- All agents now support full 4-tier escalation (haiku→codex→sonnet→opus)
- Consistent escalation behavior across all agent types
- Single source of truth for each agent's logic
- Significant cost savings by defaulting to haiku for all quality gates

The system now uses tier selectors (tier-haiku, tier-codex, tier-sonnet, 
tier-opus) that set the model and invoke model-agnostic worker agents,
eliminating the need for separate implementations per model tier.
2026-04-06 17:52:33 -04:00
freemo 4aa236b7df feat: implement tier selector architecture for escalation without redundancy
BREAKING CHANGE: New escalation architecture eliminates duplicate agent code

Key changes:
- Add tier selector agents (tier-haiku, tier-codex, tier-sonnet, tier-opus)
  that set the model and invoke worker agents
- Create model-agnostic implementer.md that inherits model from caller
- Update unit-test-runner and typecheck-fixer to support escalation
- Add quality-gate-escalator to manage escalation for quality fixers
- Create subtask-loop-v2.md demonstrating the new architecture
- Document the new architecture in escalation-architecture-proposal.md

Benefits:
- Eliminates 90% code duplication across tier-specific agents
- Single source of truth for implementation logic
- Easy to add new tiers or modify escalation paths
- Consistent behavior across all model tiers
- Quality gate fixers now support full escalation starting from haiku

The architecture leverages the fact that agents without a model specification
inherit the model from their caller, allowing thin tier selectors to control
which model executes the actual work.
2026-04-06 21:26:20 +00:00