- Create automation-tracking-manager subagent as single source of truth
- Migrate 7 key agents to use centralized tracking manager
- Fix AUTO-WATCHDOG skipping cycles 22-23 (was commenting on old issues)
- Fix AUTO-IMP-POOL creating duplicate tracking issues for same cycle
- Fix AUTO-TIME and AUTO-PROJ-OWN potential issue reuse patterns
- Ensure cycle numbers persist across agent restarts
- Delete shared/automation_tracking.md in favor of subagent pattern
The new system ensures:
- One tracking issue per cycle (never reuse old issues)
- Sequential cycle numbers that persist across restarts
- Proper cleanup of previous cycles before creating new ones
- Consistent tracking patterns across all agents
- Impossible for agents to comment on old tracking issues
Migrated agents:
- system-watchdog (most problematic - missing cycles)
- implementation-orchestrator (duplicate issues)
- timeline-updater (potential reuse)
- project-owner (potential reuse)
- product-builder (critical orchestrator)
- backlog-groomer (for consistency)
Fixes the issue where agents incorrectly report future cycles as comments
on older status update tickets instead of creating new tracking issues.
BREAKING CHANGE: Migrate all CleverAgents from shared session state issue
system to individual tracking issues with 'Automation Tracking' labels
Changes:
- Replace SESSION_STATE_ISSUE_NUMBER with individual tracking issues
- Add automation tracking systems to 10 core agents
- Implement standardized agent prefixes (AUTO-UAT-POOL, AUTO-PROJ-OWN, etc.)
- Add cleanup protocols for one-issue-per-cycle management
- Remove session state dependencies from supervisor launch prompts
- Update health signaling to create individual tracking issues
- Preserve announcement issues while cleaning up cycle reports
Affected agents:
- agent-evolver.md: Added AUTO-EVLV tracking system
- bug-hunter.md: Updated tracking documentation
- epic-planner.md: Fixed remaining session state reference
- implementation-orchestrator.md: Updated health signaling
- product-builder.md: Major refactor of supervisor coordination
- project-owner.md: Added AUTO-PROJ-OWN tracking system
- spec-updater.md: Added AUTO-SPEC-UPD tracking system
- test-infra-improver.md: Added AUTO-TEST-INFRA tracking system
- uat-tester.md: Added AUTO-UAT-POOL tracking system
Benefits:
- Better isolation: no shared state conflicts between agents
- Cleaner tracking: one issue per agent per cycle
- Full traceability: each agent's work is independently tracked
- Systematic discovery: standardized labels enable monitoring
This migration follows the automation tracking specification in
.opencode/agents/shared/automation_tracking.md and maintains
compatibility with existing CleverAgents infrastructure.
- Fix tracking issues not always using 'Automation Tracking' label
- Convert agents from session state to individual tracking issues
- Add standardized automation tracking system for all agents
- Enable cross-agent discovery and coordination capabilities
Changes:
- Add shared/automation_tracking.md: standardized tracking functions
- Add shared/tracking_discovery_guide.md: agent coordination guide
- Update continuous-pr-reviewer.md: use AUTO-REV-POOL tracking
- Partial update bug-hunter.md: add AUTO-BUG-POOL system
- Add bug_hunter_tracking_update.md: completion guide
- Add tracking_system_fixes_summary.md: comprehensive overview
All tracking issues now guaranteed to have 'Automation Tracking' label
for auto-discovery. Agents can find each other's activities and coordinate
through standardized prefix system (AUTO-SESSION, AUTO-WATCHDOG, etc).
Resolves issue where tracking tickets weren't discoverable due to
missing required label.
- Remove maximum cap (16) on CA_MAX_PARALLEL_WORKERS in resources.yaml
- Can now be set to any positive value (32, 64, etc.)
- Only minimum validation remains (must be > 0)
- Remove dynamic backpressure/throttling from implementation-orchestrator
- Dispatch always runs at full configured speed
- Resource monitoring remains for visibility only
- No automatic reduction of slots_available based on failures
- Convert system-watchdog from auto-degradation to monitoring + suggestions
- Renamed DEGRADATION_THRESHOLDS to HEALTH_THRESHOLDS
- Removed apply_system_degradation() and check_degradation_recovery()
- Changed findings to include suggestions instead of actions
- Watchdog now reports issues with fix recommendations
- No automatic throttling or pausing of agents
The system now operates at maximum configured speed at all times,
with the watchdog providing diagnostic insights when issues arise.