1793 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
HAL9000	5da2baef49	docs(spec): update Azure OpenAI API version default to 2024-05-01-preview ... The implementation (providers/registry.py line 519) uses 2024-05-01-preview as the default Azure OpenAI API version, but the spec documented 2024-02-01. The implementation's choice is correct — 2024-05-01-preview supports the latest features including structured outputs and improved tool calling. Update the spec to match the implementation and add guidance for users who need a stable API version. Fixes the discrepancy reported in UAT issue #5807.	2026-04-09 11:06:09 +00:00
HAL9000	a3762a4cc2	docs: add invariant-reconciliation module guide, extend automation tracking docs, update mkdocs nav ... docs: add invariant-reconciliation module guide, extend automation tracking docs, update mkdocs nav - Add docs/modules/invariant-reconciliation.md: module guide for InvariantReconciliationActor (v3.8.0) - Extend docs/development/automation-tracking.md: all 16 supervisors, centralized tracking manager - Update mkdocs.yml: add Modules nav section, Custom Sandbox Strategy to Development ISSUES CLOSED: #5700 Co-authored-by: CleverThis <hal9000@cleverthis.com> Co-committed-by: CleverThis <hal9000@cleverthis.com>	2026-04-09 09:22:43 +00:00
hurui200320	ee2024046f	fix(plan): upsert action arguments during plan use to avoid UNIQUE constraint violation (#4197) ... ## Summary `agents plan use` crashed with `sqlite3.IntegrityError: UNIQUE constraint failed: action_arguments.action_name, action_arguments.name` when the action had arguments already registered via `action create`. The root cause was `ActionRepository.update()` using SQLAlchemy's relationship `.clear()` + `.append()` pattern, which deferred the DELETE and processed the INSERT first — triggering a UNIQUE constraint violation when the same `(action_name, name)` pair was being re-inserted. ## Approach Replace the `.clear()` + `.append()` pattern with explicit bulk `sa_delete()` + `session.flush()` before re-inserting child rows for both `action_arguments` and `action_invariants`. After the flush, expire the relationship collections with `session.expire(row, ["arguments_rel", "invariants_rel"])` so SQLAlchemy reloads from the now-empty database state before appending replacements. This avoids stale identity map references and guarantees the DELETE is committed before any INSERT. ## Key Changes ### Bug fix (`src/cleveragents/infrastructure/database/repositories.py`) - `ActionRepository.update()` now uses `sa_delete(ActionArgumentModel)` and `sa_delete(ActionInvariantModel)` with `synchronize_session=False`, followed by `session.flush()`, before re-inserting child rows. - Targeted `session.expire(row, ["arguments_rel", "invariants_rel"])` replaces the removed `.clear()` calls to force collection reload. ### Schema parity (`src/cleveragents/infrastructure/database/models.py`) - Added `UniqueConstraint("action_name", "position")` to `ActionInvariantModel`. - Added `UniqueConstraint("action_name", "name")`, `CheckConstraint` for `arg_type`, and `CheckConstraint` for `requirement` to `ActionArgumentModel`. ### Alembic migration (`alembic/versions/a5_006_action_invariants_unique_constraint.py`) - New migration adds all four constraints to both `action_invariants` and `action_arguments` tables. - Includes deduplication guards and data normalization so the upgrade succeeds on existing databases with invalid or duplicate rows. - Uses `batch_alter_table` for SQLite compatibility. ### Tests - **Behave** (`features/plan_use_action_args_integrity.feature`): 6 scenarios covering the core bug path, zero-argument regression, multiple arguments, reusable action double-use, non-reusable action archival with invariants, and direct repository update. - **Robot** (`robot/plan_use_action_args_integrity.robot`): Integration test mirroring the Behave scenarios via a helper script. - **Shared factory** (`features/mocks/test_uow_factory.py`): Extracted `build_test_uow()` from both test suites into a single shared module to eliminate duplication (DRY). ### Minor - Updated `src/cleveragents/domain/repositories/__init__.py` docstring from table format to bullet list (conflict resolution from rebase). Closes #4174 Reviewed-on: #4197 Reviewed-by: HAL 9000 <HAL9000@cleverthis.com> Co-authored-by: Rui Hu <rui.hu@cleverthis.com> Co-committed-by: Rui Hu <rui.hu@cleverthis.com>	2026-04-09 06:11:39 +00:00
HAL9000	c87fc3bb2a	fix: Scale implementation orchestrator to 32 parallel workers ... - Reduce main dispatch loop sleep from 10s to 2s (5x faster cycles) - Simplify worker verification from 5 retries to 1 quick check - Remove unnecessary delays between dispatch operations - Reduce retry delays from 15s to 2s for faster recovery - Reduce idle sleep from 60s to 10s for quicker response - Add optimistic verification to trust dispatch success These changes enable the orchestrator to scale from 1-4 workers to the full 32 workers within seconds instead of minutes, dramatically increasing system throughput and allowing autonomous unblocking of CI failures.	2026-04-09 01:23:21 -04:00
freemo	b72b827525	fix: centralize automation tracking to prevent cycle reuse issues ... - 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.	2026-04-09 01:08:08 -04:00
hurui200320	0bd8fbb296	fix(ci): resolve lint errors and remove stale tdd_expected_fail tag (#5264) ... ## Summary The `lint` and `integration_tests` CI jobs on `master` are currently failing. This PR fixes both: 1. **Lint (`nox -e lint`)** — 51 ruff violations in `scripts/validate_automation_tracking.py`: - Sorted imports per isort convention - Replaced deprecated `typing.List`/`Dict`/`Tuple`/`Optional` with builtin equivalents (`list`, `dict`, `tuple`) - Removed unused `Optional` import and unused local variable `issues` - Fixed trailing whitespace, blank-line whitespace, and 6 lines exceeding 88-char limit - Replaced `dict.keys()` with `dict` in membership tests - Added return type annotation to `main()` 2. **Integration tests (`nox -e integration_tests`)** — 1 failure in `robot/coverage_threshold.robot`: - Removed `tdd_expected_fail`, `tdd_issue`, and `tdd_issue_4305` tags from the `Noxfile Contains Coverage Threshold Constant` test - The bug this TDD tag tracked (issue #4305) is now fixed — `COVERAGE_THRESHOLD = 97` exists in `noxfile.py` - The TDD expected-fail listener was inverting the passing result to a failure ### Local verification - `nox -e lint` — All checks passed - `nox -e integration_tests` — 1962 tests, 1962 passed, 0 failed, 0 skipped ### Files changed | File | Change | |------|--------| | `scripts/validate_automation_tracking.py` | Fixed all 51 lint violations | | `robot/coverage_threshold.robot` | Removed stale `tdd_expected_fail` tag | Closes #5266 Reviewed-on: #5264 Co-authored-by: Rui Hu <rui.hu@cleverthis.com> Co-committed-by: Rui Hu <rui.hu@cleverthis.com>	2026-04-09 04:41:01 +00:00
HAL9000	a33b6caa7e	set model for opencode builder	2026-04-08 23:36:37 -04:00
freemo	7a37f02abb	docs: add comprehensive tracking system completion summary ... Documents the successful implementation of the comprehensive worker tracking system for CleverAgents automation framework, including: - Complete tracking for all 16 supervisors - Detailed worker monitoring with OpenCode API integration - Proper tracking issue lifecycle management - Actual timing measurements and health monitoring - Automatic recovery and restart capabilities - Enterprise-grade observability for autonomous components System is now production ready with full visibility into all supervisors and workers across the entire automation framework.	2026-04-09 02:44:43 +00:00
freemo	50096391b5	feat: complete comprehensive worker tracking system implementation ... - Enhanced product-builder with detailed session monitoring via OpenCode API - Added comprehensive worker status reporting with session details, targets, and activity - Enhanced implementation-orchestrator with detailed worker tracking and health monitoring - Enhanced continuous-pr-reviewer with detailed worker status and progress reporting - Enhanced uat-tester with detailed worker monitoring and testing progress - All supervisors now provide detailed visibility into worker activities and health - Added actual cycle time calculation using timestamps throughout all agents - Implemented proper tracking issue lifecycle (delete previous, create new each cycle) - Added stale worker detection and restart functionality across all pool supervisors - Ensured redundant monitoring between product-builder and individual supervisors This completes the comprehensive worker tracking system providing full visibility into all 16 supervisors and their workers with detailed status reporting, automatic restarts, and actual timing data.	2026-04-09 02:44:00 +00:00
HAL9000	30b457b090	Fix implementation-orchestrator worker dispatch verification ... The orchestrator was failing to dispatch workers due to incorrect parsing of the OpenCode API /session/status response format. Changes: - Fixed verify_worker_started() to handle dict response format instead of array - Check for session_id key and type='busy' instead of status='active' - Increased verification retries from 3 to 5 with progressive delays - Enhanced error messages to show actual verification results - Improved session state handling with longer initialization wait times This fix allows the orchestrator to correctly verify that workers have started, preventing it from incorrectly deleting valid worker sessions. Workers should now dispatch successfully and PRs will be processed.	2026-04-08 22:12:23 -04:00
freemo	1b83d15920	fix: comprehensive tracking issue system improvements ... - Fix tracking issue lifecycle: each cycle closes old issue and creates new one - Add tracking functionality to 4 missing supervisors (architect, timeline-updater, docs-writer, architecture-guard) - Enhance product-builder to report all 16 supervisors with worker counts - Add actual cycle time calculation based on elapsed timestamps - Standardize tracking issue format across all agents - Implement automatic supervisor re-launch when missing - Add comprehensive supervisor and worker count monitoring Fixes tracking issue problems where agents were appending to old issues instead of creating fresh ones each cycle, and ensures all 16 supervisors are properly monitored and tracked.	2026-04-09 01:46:44 +00:00
CleverAgents Build Agent	92f533dcff	fix: update remaining session state references in other agents ... - project-bootstrapper.md: Update to use announcement issues - system-watchdog.md: Begin migration to tracking system (partial) Note: The critical issue in product-builder.md has been resolved. Some agents still need complete session state reference cleanup but have automation tracking systems already in place.	2026-04-09 00:11:57 +00:00
CleverAgents Build Agent	7a5ab53d0e	fix!: complete product-builder migration to individual tracking issues ... BREAKING CHANGE: Fix critical product-builder.md logic that was still creating long-running session state issues instead of individual tracking Key fixes: - Replace Step 1: session state issue search → tracking issue discovery - Replace Step 4: session state issue creation → tracking system init - Replace Step 5: session state comment → session initialization complete - Update spec PR handling to use announcement issues - Fix final report logic to use tracking issues - Update Forgejo comment protocol documentation - Fix error handling references to tracking issues - Remove all remaining session state issue dependencies Problem: product-builder was still creating '[Automated] CleverAgents Build Session' long-running issues and posting comments to them, completely bypassing the new individual tracking system. Solution: Replace core session initialization logic with individual tracking issue creation using AUTO-PROD-BLDR prefix and Automation Tracking labels, following the specification in automation_tracking.md. This ensures product-builder now creates one tracking issue per cycle with proper cleanup, instead of commenting on a shared long-running issue. The new system provides better isolation and traceability.	2026-04-09 00:10:53 +00:00
freemo	f2fc8f771e	feat: add port checking to opencode-builder script ... - Add check_opencode_running() function to detect existing OpenCode server - Skip server startup if OpenCode already running on target port - Display prominent warning when connecting to existing server - Only manage server lifecycle when script starts its own server - Add OWN_SERVER flag to track server ownership - Update cleanup logic to leave existing servers running This enables multiple developers and automation scripts to safely run in parallel without conflicting server management.	2026-04-08 19:57:54 -04:00
CleverAgents Build Agent	0edc1bf13d	refactor!: migrate agents from session state to individual 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.	2026-04-08 19:57:38 -04:00
HAL9000	06073bfcec	docs(spec): add Milestone Plan section for v3.2.0 through v3.7.0 ... Add a comprehensive Milestone Plan section to docs/specification.md mapping architectural features to verifiable deliverables for each milestone from v3.2.0 (Decisions + Validations + Invariants) through v3.7.0 (TUI Implementation). Each milestone section includes: - Goal statement aligned with Forgejo milestone descriptions - Spec coverage cross-references to existing spec sections - Deliverables table with spec reference and verifiable check per item - Key architectural constraints specific to that milestone - Definition of Done criteria Also adds: - Cross-Milestone Quality Gates table (unit/integration/typecheck/lint/ coverage/security/performance/docs) - Cross-Milestone Architectural Invariants (10 invariants that must hold across all milestones) This section serves as the authoritative mapping between the detailed architectural spec and the milestone-level work tracked in Forgejo, enabling implementers to understand which spec sections govern each milestone's work and what constitutes completion.	2026-04-08 19:57:23 -04:00
freemo	89bef73f89	docs(changelog): add entries for automation tracking and label management ... Document recent agent infrastructure improvements: - Automation tracking system with individual per-agent tracking issues - Automated health monitoring and recovery via system-watchdog - Centralized org-level label management via forgejo-label-manager - PR label synchronization with associated issues ISSUES CLOSED: #4940	2026-04-08 23:42:11 +00:00
freemo	9d258d53fe	docs(mkdocs): add providers module to API Reference navigation ... Add cleveragents.providers to the mkdocs.yml nav under API Reference. The providers.md page existed but was not linked in the navigation, making it inaccessible from the documentation site. ISSUES CLOSED: #4940	2026-04-08 23:40:24 +00:00
freemo	c886eb2a44	docs(api): add providers module to API reference index ... Add cleveragents.providers to the API Reference module index table. The providers.md page already exists but was missing from the index, making it undiscoverable via the documentation navigation. ISSUES CLOSED: #4940	2026-04-08 23:39:38 +00:00
freemo	1d5618fcdc	feat(agents): enhance PR label synchronization with issues ... Implements comprehensive PR labeling system to ensure PRs inherit and maintain all relevant labels from their associated issues, addressing the issue where most PRs were not properly labeled. Changes: - pr-api-creator: inherit Priority/, MoSCoW/, Points/, State/ labels at PR creation - backlog-groomer: add Pass 19 for continuous PR-issue label synchronization - issue-state-updater: sync PR state labels when issue states change This ensures PRs always have proper Priority, MoSCoW, story points, milestone, and state labels that stay synchronized with their associated issues throughout the PR lifecycle, improving organization and tracking.	2026-04-08 23:24:58 +00:00
CleverAgents Build Agent	9b5c3f3e56	fix: standardize automation tracking system with required labels ... - 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.	2026-04-08 23:17:17 +00:00
CleverAgents Build Agent	d35c3cb48b	feat(agents): implement centralized org-level label management system ... - Add specialized forgejo-label-manager subagent for centralized label operations - Update 6 critical agents to delegate ALL label operations to label manager - Enforce organization-level label system (labels shared across all repos) - Prohibit label creation completely - all labels must already exist - Implement strict label compliance checking and validation - Add comprehensive label reference system covering State/, Type/, Priority/, MoSCoW/, Points/ patterns - Update agents: backlog-groomer, human-liaison, project-owner, epic-planner, new-issue-creator, issue-state-updater This ensures label consistency across all CleverThis repositories and prevents duplicate/conflicting labels while maintaining CONTRIBUTING.md compliance. BREAKING: Agents can no longer create labels or use forgejo_add_issue_labels directly. All label operations must go through forgejo-label-manager subagent.	2026-04-08 22:48:05 +00:00
freemo	014033eed9	feat: enhance automation tracking with health monitoring and recovery ... Add comprehensive automated health monitoring and recovery capabilities to the automation tracking system for proactive agent management. **Major Enhancements:** 1. **Standardized Interval Reporting** - Mandatory interval declaration in all tracking issues - Format: 'Reporting Interval: <interval> (Next report expected: <timestamp>)' - Enables precise staleness detection and recovery triggering 2. **Automated Health Monitoring (system-watchdog)** - New audit_automation_tracking_health() function runs every 5 minutes - Monitors all issues with 'Automation Tracking' label - Detects stalled agents when >20% overdue from expected interval - Calculates staleness ratios and time overdue metrics 3. **Automated Recovery System** - Kills stalled agent sessions via OpenCode Server API (port 4096) - Performs root cause analysis of session messages and agent definitions - Creates high-priority diagnostic issues with detailed findings - Automatically closes stale tracking issues with recovery notes - Provides human-readable remediation recommendations **Agent Updates with Standardized Format:** - **implementation-orchestrator**: Status updates (5 cycles) + health reports (10 cycles) - **backlog-groomer**: Grooming reports (5 min) + health reports (50 min) - **human-liaison**: Status updates (20 min monitoring cycles) - **session-persister**: Event-driven checkpoints with standardized format - **system-watchdog**: Enhanced with comprehensive recovery capabilities **Template Standardization:** - Unified header format across all tracking issues - Health indicators and next actions sections - Consistent metadata and automation signatures - Support for active/warning/error status indicators **Documentation Updates:** - Comprehensive automated recovery process documentation - Agent interval reference table with all timing details - Recovery issue format and diagnostic workflow - Health check algorithm and staleness threshold explanation **Benefits:** - Proactive detection of crashed or stuck agents (20% staleness threshold) - Automated recovery reduces manual intervention requirements - Root cause analysis provides actionable diagnostic information - Standardized format improves searchability and monitoring - Comprehensive health metrics enable system-wide visibility This enhancement transforms the automation tracking system from passive logging to active health monitoring with automated recovery capabilities.	2026-04-08 22:34:23 +00:00
freemo	a323f07783	feat: implement new automation tracking system for agent supervision ... Replace shared session state issue tracking with individual tracking issues per agent to reduce noise and improve searchability. **Agent Updates:** - session-persister: [AUTO-SESSION] prefix with cycle management - implementation-orchestrator: [AUTO-IMP-POOL] prefix for health reports - system-watchdog: [AUTO-WATCHDOG] prefix for system health - backlog-groomer: [AUTO-GROOMER] prefix + backup cleanup functionality - human-liaison: [AUTO-LIAISON] prefix for status updates **New Features:** - Standardized issue title format: [AUTO-<PREFIX>] <TYPE> (Cycle <N>) - Announcement format: [AUTO-<PREFIX>] Announce: <message> - Automatic cleanup to prevent issue accumulation - Required 'Automation Tracking' label for filtering - Validation script for format compliance **Documentation:** - Complete system documentation at docs/development/automation-tracking.md - Added to mkdocs.yml navigation - Validation script at scripts/validate_automation_tracking.py **Benefits:** - Reduced noise from shared tracking issue - Better searchability with agent-specific prefixes - Cleaner history per agent type - Easier debugging with focused issue threads - Automatic cleanup prevents accumulation Closes automation tracking system implementation requirements.	2026-04-08 21:28:46 +00:00
freemo	3b1d6d1931	fix(agents): standardize label handling and prevent label creation ... - Quote all specific label references ("State/Verified", "Priority/High", etc.) - Add explicit 'NEVER create new labels' warnings to all agents - Ensure agents assume labels exist on Forgejo server - Fix unquoted label patterns across 12+ agent files - Standardize label reference format for consistency Key changes: * issue-state-updater.md: Fixed state transition label references * human-liaison.md: Quoted all triage and verification labels * project-owner.md: Fixed MoSCoW and priority label handling * backlog-groomer.md: Updated auto-fix label compliance * pr-api-creator.md: Fixed PR metadata label references * quality-enforcer.md: Fixed CI-Blocker label handling * state-reconciler.md: Fixed reconciliation label patterns * new-issue-creator.md: Added comprehensive label usage rules * issue-finder.md: Fixed priority sorting label references * spec-updater.md: Fixed proposal label handling * implementation-orchestrator.md: Fixed CI-Blocker prioritization * milestone-reviewer.md: Fixed issue creation label references Resolves label capitalization, spelling, spacing, and creation issues across the entire agent system to ensure exact Forgejo server matching.	2026-04-08 21:04:34 +00:00
freemo	670035fc03	feat(agents): enhance epic-planner with hierarchical structure compliance ... - Add mandatory hierarchical enforcement: Issue → Epic → Legendary - Implement orphan detection and correction for issues and epics - Add dependency direction validation and auto-correction - Create specification-first process enforcement (ADR → Spec → Implementation) - Add epic/legendary closure evaluation and lifecycle management - Implement comprehensive compliance checking in 4-phase loop: 1. Hierarchical compliance (orphans, dependencies) 2. Closure evaluation (ready epics/legendaries) 3. Specification-first enforcement 4. Traditional planning - Add health reporting with violation tracking and status updates - Ensure all fixes include user tagging and explanatory comments - Enforce CONTRIBUTING.md ticket hierarchy requirements completely This transforms epic-planner from basic planning into comprehensive ticket hierarchy governance, ensuring no orphaned tickets exist and all dependency relationships follow correct directions per CONTRIBUTING.md rules.	2026-04-08 16:20:08 -04:00
HAL9000	5f5bd49790	docs(timeline): update schedule adherence Day 98 (2026-04-08) ... - Update gantt chart today marker to 2026-04-08 (both charts) - Update gantt chart footer: 1 open PR, ~878 open bugs, Session 4 active - Update GANTT CHART UPDATE LOG to Day 98 with session #4799 details - Update Current Status Summary: Day 98, Session 4, 1 PR, M6 scope explosion - Add Day 98 completed work bullet to What Has Been Completed - Append Day 98 schedule adherence entry with all required tables Key changes: - M6 scope expanded 327→638 (+311 issues), completion 55%→29% - Open PRs dropped 108→1 (massive merge wave) - M3 73% (235/320), M4 67% (108/161), M5 71% (130/183) - M7 48% (150/312), M8 47% (403/855) - Session 4 launched (issue #4799) with 32 parallel workers - UAT bug #4798: agents resource show missing 5 spec-required panels - Spec restructure proposal: issue #4807 (needs feedback)	2026-04-08 20:10:59 +00:00
freemo	1d68696b75	feat(agents): enhance feedback incorporation protocol ... - Add critical feedback incorporation protocol to human-liaison agent - Mandate description updates when feedback changes ticket nature - Require user tagging with diffs and explanations - Add PR feedback notification templates - Update product-builder to reference new protocol - Prevent communication gaps that block tickets with 'needs feedback' labels This ensures feedback discussions properly update source-of-truth descriptions and users are notified when their input is incorporated, preventing tickets from staying blocked due to communication breakdown.	2026-04-08 19:56:03 +00:00
freemo	18bf003bfe	Improved agents so they use sonnet more and opus is only used when escalating	2026-04-08 15:11:22 -04:00
freemo	772544d7a8	feat: enforce clone isolation across all source code agents ... Add explicit clone isolation protocols and warnings to prevent agents from manipulating the local repository in /app. This ensures: - Agents use isolated /tmp/ clones for all source code operations - No interference between parallel agents - No disruption to developer's local work environment - No conflicts from branch changes or file modifications Updated agents: - Core implementation agents (implementer, build, plan) - Quality gate agents (lint-fixer, typecheck-fixer, test-fixer, etc.) - Test writing agents (behave-tester, unit-test-runner, coverage-improver) - Analysis agents (difficulty-evaluator, fix-pr) - Special cases (build-opencode with .opencode/ exception) Each agent now includes prominent warnings and proper isolation protocols with detailed explanations of why clone isolation is critical for system stability.	2026-04-08 18:36:37 +00:00
freemo	7ddd6a7e2d	feat(agents): add Priority/CI-Blocker label to break PR-first deadlock ... **Problem**: - Broken CI blocks all PR merges - PR-first rule blocks CI-fixing issues - Creates deadlock where system can't fix itself **Solution**: - Created Priority/CI-Blocker label (ID: 1396) - Added ONE exception to absolute PR-first rule - Priority/CI-Blocker issues can be worked immediately **Changes**: - quality-enforcer: Use Priority/CI-Blocker for CI violations - implementation-orchestrator: Exception for Priority/CI-Blocker - issue-finder: Priority/CI-Blocker as absolute highest priority - system-watchdog: Create Priority/CI-Blocker for CI failures - +4 supporting agents updated with new label **Impact**: Prevents CI deadlock while preserving PR-first priority for all other work.	2026-04-08 18:15:32 +00:00
freemo	92a3f34bdb	feat(agents): comprehensive anti-flaky test system and label management ... - Add 170+ lines of test determinism requirements to behave-tester with forbidden/required patterns - Add 180+ lines of integration test stability rules to robot-tester - Enhance pr-self-reviewer with 150+ lines of flaky test detection during code review - Add emergency master CI monitoring to system-watchdog with auto-skip failing tests - Implement automatic test skipping system with framework-specific instructions - Add cross-PR analysis to detect master branch CI issues vs PR-specific failures - Prohibit label creation in epic-planner and new-issue-creator to prevent duplicates - Add test stability awareness to implementation-worker for all implementers This comprehensive system prevents flaky tests from reaching master, automatically handles CI failures through emergency test skipping, and eliminates label duplication issues. Includes detailed detection patterns, emergency response workflows, and framework-specific guidance for Behave, Robot Framework, and generic test systems.	2026-04-08 17:29:17 +00:00
freemo	af0f0a3f9a	tests: increased coverage threshold back to 97%	2026-04-08 07:03:34 -04:00
freemo	8ea00f5185	fix: restore CI quality tests to passing state (#4175) ... Co-authored-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me> Co-committed-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me>	2026-04-08 11:02:14 +00:00
HAL9000	59812ffce4	fix(agents): remove credential requirements from ci-log-fetcher usage across all agents ... PROBLEM: Primary agents refused to use ci-log-fetcher because documentation incorrectly suggested they needed to provide forgejo_username/forgejo_password parameters. SOLUTION: Updated all agents to clarify that ci-log-fetcher handles credentials automatically. Changes made: - ci-log-fetcher.md: Updated description and added prominent warning that NO CREDENTIALS are needed - implementation-worker.md: Removed forgejo_username/forgejo_password from 3 usage examples - pr-fix-orchestrator.md: Removed credential parameters from 2 usage examples, clarified env var usage - pr-checker.md: Removed credential parameters from 2 usage examples Now all agents clearly understand that ci-log-fetcher automatically uses FORGEJO_USERNAME and FORGEJO_PASSWORD environment variables without any credential parameters needed.	2026-04-08 03:58:41 +00:00
HAL9000	87f2f92a1f	fix(ci-log-fetcher): prioritize FORGEJO_USERNAME/PASSWORD env vars over parameters ... - Agent now checks environment variables first before requiring explicit credentials - Added debug output showing credential source being used - Improved error messages to clearly indicate credential requirements - Updated documentation with preferred usage patterns using env vars - Fixes issue where agent complained about missing credentials despite env vars being set	2026-04-08 03:43:45 +00:00
HAL9000	1137148e54	feat(agents): enhance project-owner with intelligent milestone and developer assignment ... Enhanced the project-owner agent to automatically assign critical/blocking tickets to appropriate milestones and intelligently allocate work to developers based on expertise, velocity, and capacity analysis from docs/timeline.md. Key improvements: - Add timeline.md analysis to understand developer velocity and specializations - Implement smart milestone assignment for critical/blocking base functionality issues - Add intelligent developer assignment that defaults to HAL9000 but considers: * Developer expertise areas and capacity from timeline * Team velocity optimization over individual load balancing * Strategic delegation only when expertise provides significant acceleration * Avoidance of work assignments that would cause development contention - Enhanced continuous loop with developer assignment step for unassigned critical issues - Updated metrics tracking for milestone and developer assignment decisions - Strengthened rules around team velocity priority and reassignment flexibility The agent now acts as a true project owner that actively manages both strategic issue placement and optimal developer allocation while maintaining focus on maximum team velocity. Defaults conservatively to HAL9000 for most work unless clear strategic value exists in specialist delegation.	2026-04-07 19:35:01 +00:00
HAL9000	057e3f5bfb	docs: showing off some showcased workflows	2026-04-07 15:27:39 -04:00
HAL9000	ccfbf11009	docs: add showcase example for server and A2A integration ... Adds a complete end-to-end walkthrough of the server connection CLI commands and A2A protocol facade, verified by the UAT system with real command outputs. Covers: - agents server --help, connect, status, serve commands - All output formats (rich, json, yaml, plain) - A2A JSON-RPC 2.0 wire format (A2aRequest, A2aResponse, A2aEvent) - A2aLocalFacade: 42 supported operations, stub mode, service wiring - get_facade() wired to real DI container - A2aVersionNegotiator: version negotiation and mismatch handling - ServerConnectionConfig: validation rules Also updates examples.json index with the new entry.	2026-04-07 14:54:49 +00:00
HAL9000	07f9364bcb	docs: add showcase example for database migration management ... Adds a complete end-to-end walkthrough of the `agents db` command group, verified by the UAT system with real command outputs. Covers: - agents db --help (command discovery) - agents db current (fresh database: 41 pending migrations listed) - agents db history (full 41-revision DAG with branchpoints/mergepoints) - agents db history --format json (structured DAG for scripting) - agents db upgrade (applying all 41 migrations to head) - agents db current --format json (CI/CD integration pattern) - agents db downgrade -- -1 (relative rollback with -- separator) - agents db downgrade <revision-id> (targeted rollback) - agents db upgrade <revision-id> (targeted upgrade) - agents db upgrade --format json (idempotent upgrade with JSON output) Also updates examples.json index with the new entry.	2026-04-07 14:53:12 +00:00
freemo	43ab4a8f22	feat(agents): Add TDD issue test tag awareness to all relevant agents ... Updated multiple agents to understand and properly handle TDD (Test-Driven Development) tags as documented in CONTRIBUTING.md. This prevents confusion when agents encounter tests with @tdd_expected_fail that invert their behavior. Key changes: - Test writers (behave-tester, robot-tester) now understand when to use TDD tags - Implementers know to remove @tdd_expected_fail tags when fixing bugs - Test-fixer won't try to "fix" correctly passing TDD tests - PR reviewers check for proper TDD tag removal in bug fix PRs - Human liaison can explain TDD tags to confused developers - Coverage improver avoids modifying TDD tests - Reference reader includes TDD tag info in summaries This ensures all agents work correctly with the TDD workflow where tests are written before bug fixes and use special tags to prove bugs exist.	2026-04-07 08:26:48 +00:00
freemo	e5f75c5c83	refactor: remove parallelism cap and backpressure throttling ... - 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.	2026-04-07 01:13:27 -04:00
freemo	96a70c170e	feat(agents): add struggling PR detection and deep context understanding ... - Add system-watchdog audit for PRs with 3+ failed attempts - Implement automatic human assistance requests with detailed analysis - Add deep context gathering to implementation-worker before fixes - Enhance all agents with enriched context propagation - Add loop detection to prevent repetitive failed attempts - Improve PR reviewer with anti-pattern detection - Update human-liaison to provide targeted help for struggling PRs - Add historical awareness to PR fix orchestrator - Enhance epic-planner with context-aware issue creation - Create documentation for improvements and future agent ideas These changes enable the system to: - Recognize when it's stuck and needs human help - Learn from previous failures to avoid repetition - Understand full context including comments and history - Provide detailed debugging information to humans	2026-04-06 20:29:28 -04:00
freemo	700d5e7923	docs: add quick reference guide for agents ... - Clear hierarchy of where to find information - Most common patterns in one place - Direct agents to authoritative sources - Reminder about testing and duplication This helps agents quickly find the patterns they need.	2026-04-06 23:42:24 +00:00
freemo	efe3a5c988	docs: add optimization summary documenting all improvements ... - Summarize 85% time reduction in CI log fetcher - Document pattern documentation structure - List all tested patterns added - Show impact and remaining work - Provide best practices for future optimization This helps track the optimization effort and its results.	2026-04-06 23:41:52 +00:00
freemo	fb6dac2891	feat: add more tested common patterns to reduce agent discovery time ... - Add Git push conflict handling patterns (tested) - Add PR number extraction patterns (tested) - Document these patterns agents frequently need - Keep branch protection as untested pattern These patterns save time for agents that work with git and PRs.	2026-04-06 23:41:04 +00:00
freemo	1dd38020d4	feat: strengthen CONTRIBUTING.md compliance in key agents ... - Add CRITICAL compliance sections to implementation-orchestrator - Add explicit instructions to pass CONTRIBUTING.md to all workers - Strengthen behave-tester compliance requirements - Improve architect compliance section prominence - Enhance human-liaison CODE_OF_CONDUCT emphasis These changes ensure agents don't spend time rediscovering project rules.	2026-04-06 23:40:24 +00:00
freemo	383c589acc	feat: add tested timeline patterns and verify specification format ... - Add tested timeline.md parsing patterns to PARSING_PATTERNS.md - Verify specification uses monolithic format (docs/specification.md) - Document PlantUML gantt chart structure and color codes - Add Schedule Adherence entry exact format - Include day number calculation pattern	2026-04-06 23:26:02 +00:00
freemo	9bc0cbcc5d	feat: clean up COMMON_PATTERNS.md to avoid CONTRIBUTING.md redundancy ... - Mark patterns as tested or untested - Remove patterns already in CONTRIBUTING.md - Add note directing agents to CONTRIBUTING.md for authoritative info - Keep only patterns NOT in CONTRIBUTING.md but frequently needed - Clearly separate tested patterns from those needing verification	2026-04-06 23:23:43 +00:00
freemo	ee33fd46b6	feat: add explicit pattern documentation to reduce agent discovery time ... Created two new reference documents: - COMMON_PATTERNS.md - Common patterns like server endpoints, git config, file paths - PARSING_PATTERNS.md - Tested regexes and parsing patterns for logs and errors Key optimizations: 1. Documented OpenCode server endpoint (http://localhost:4096) used by 15+ agents 2. Standardized git remote patterns (origin=Forgejo, upstream=local) 3. Explicit nox command outputs and exit codes 4. CI job names and status formats in PR pages 5. Forgejo issue/PR metadata requirements and formats 6. Session state issue patterns and discovery 7. Common error patterns for lint, typecheck, and test failures 8. File organization paths and naming conventions Agent-specific optimizations: - bug-hunter: Direct module listing command instead of "map source tree" - lint-fixer: Explicit error code patterns (E501, F401, etc.) - typecheck-fixer: Pyright error parsing pattern - async-agent-starter: Documented server endpoint These patterns eliminate repetitive discovery work, saving 5-30 seconds per agent invocation depending on complexity. Agents can now reference these documents for tested patterns instead of trial-and-error discovery.	2026-04-06 23:11:15 +00:00