1928 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
HAL9000	1e543e8fa3	docs(development): add developer setup guide ... Add comprehensive developer setup guide covering prerequisites, development workflow, testing, linting, type checking, commit guidelines, devcontainer setup, and troubleshooting. Refs: #9123	2026-04-14 08:12:26 +00:00
HAL9000	1031fd0fb1	fix(agents): make bug-hunt-pool-supervisor tracking non-blocking to prevent initialization hangs	2026-04-14 05:25:30 +00:00
CleverAgents Build Agent	64b1f4c0b6	Build: improve grooming worker permissions, milestone enforcement, and PR merge throughput ... - Fix grooming-worker Forgejo permissions (deny → allow) to unblock direct API calls - Route PR label fetching through forgejo-label-manager subagent - Replace priority-alignment check with milestone enforcement (every issue must have a milestone) - Add step 11: address non-code review remarks (labels, description, milestone) during grooming - Clarify grooming-pool-supervisor stale threshold to explicit 24-hour window - Refactor pr-merge-pool-supervisor main loop into explicit numbered steps - Add triage strategy section emphasising parallel review checks and immediate worker dispatch - Tighten merge criteria: explicit APPROVED state, no unresolved REQUEST_CHANGES on current head - Dispatch workers for all PR processing, not only rebase operations - Add rule to batch forgejo_list_pull_reviews calls instead of checking serially	2026-04-14 00:49:34 -04:00
HAL9000	e757ca9db0	docs(contributors): add HAL 9000 concurrency-fix contribution detail ... Add a Details entry for HAL 9000 describing the plan lifecycle concurrency race-condition fix (#7989) — wiring LockService into execute_plan/apply_plan with unique per-invocation owner identities. ISSUES CLOSED: #7989	2026-04-14 03:59:50 +00:00
HAL9000	b1f7b51a80	fix(concurrency): fix lock owner identity to prevent re-entrant acquisition ... The original implementation used plan_id as the owner_id when acquiring the advisory lock. Because LockService treats owner_id as the caller identity and allows re-entrant acquisition for the same owner, concurrent sessions attempting to lock the same plan would all present the same owner_id and thus silently renew the lock instead of raising LockConflictError. This fix generates a unique UUID for each invocation as the owner_id, ensuring that concurrent sessions present different owners and thus trigger LockConflictError when attempting to acquire the same plan lock. The lock is still acquired before the phase transition and released in a finally block to ensure cleanup even on error. ISSUES CLOSED: #8067	2026-04-14 03:58:16 +00:00
HAL9000	b83f575cb5	fix(concurrency): wire LockService into plan lifecycle — guard execute_plan and apply_plan ... LockService was implemented but never integrated into the plan execution path, leaving execute_plan() and apply_plan() unprotected against concurrent calls on the same plan_id (race condition, issue #7989). Changes: - container.py: add _build_lock_service() factory and register LockService as a Singleton provider; inject it into PlanLifecycleService via the DI container. - plan_lifecycle_service.py: accept optional lock_service parameter in __init__; in execute_plan() and apply_plan() acquire a plan-level advisory lock before the critical section and release it in a finally block so the lock is always freed even when exceptions occur. When lock_service is None (existing tests without DI wiring) the behaviour is unchanged — locking is silently skipped for backward compatibility. Closes #7989	2026-04-14 03:58:16 +00:00
CleverAgents Build Agent	38bcd41338	Build: Better protection against agents editing the main working directory	2026-04-13 23:36:46 -04:00
HAL9000	c11b05b773	docs(changelog): add v3.3.0 changelog entry for #7582 fail_fast fix	2026-04-14 02:51:16 +00:00
HAL9000	3cfa24854a	fix(concurrency): fix SubplanExecutionService._execute_parallel() #7582 ... Ensure fail_fast cancels in-flight futures and reports them as CANCELLED. Add Behave coverage that reproduces the concurrency regression. ISSUES CLOSED: #7582	2026-04-14 02:51:16 +00:00
CleverAgents Build Agent	a71c142854	Build: Made conflict resolution a more explicit part of the pr-merge agents	2026-04-13 21:33:01 -04:00
CleverAgents Build Agent	a0664ad662	Build: enforce pagination with agents	2026-04-13 20:47:32 -04:00
CleverAgents Build Agent	ad069c2012	Build: Fixed forgejo tool permissions in the agents and fixed the label manager so it reliably works with org level labels	2026-04-13 19:45:22 -04:00
clever-agent	fd68b85c7b	Revert "Build: Removed unnessecary status-check target as well" ... This reverts commit 9998b4f9ad.	2026-04-13 19:15:55 -04:00
clever-agent	9998b4f9ad	Build: Removed unnessecary status-check target as well	2026-04-13 17:55:41 -04:00
HAL9000	836b0e19c3	docs: confirm HAL 9000 contributor entry in CONTRIBUTORS.md ... HAL 9000 was already listed in the Contributors section. This commit adds a detail entry in the Details section to explicitly document the nature of HAL 9000's contributions (automated implementation, bug fixes, and feature development), satisfying the CONTRIBUTING.md requirement to update CONTRIBUTORS.md when making a change. ISSUES CLOSED: #8232	2026-04-13 21:16:55 +00:00
HAL9000	c0d631b6cc	fix: custom automation profiles silently fall back to manual ... _resolve_profile_for_plan in PlanLifecycleService now raises a clear ValidationError when a plan's automation profile name is not a known built-in profile, instead of silently falling back to 'manual'. Users who configured custom automation profiles (e.g. 'semi-auto', 'acme/strict') will now receive an actionable error message listing available built-in profiles. The resolved profile name is also logged at debug level for observability. Added BDD regression tests (8 scenarios) covering: - Built-in profiles resolve correctly - Plans with no profile set resolve to 'manual' - Custom/unknown profile names raise ValidationError - Error message mentions the unknown profile name - Error message lists available built-in profiles - Debug log records the resolved profile name ISSUES CLOSED: #8232	2026-04-13 21:16:55 +00:00
clever-agent	5438540803	build: Removed benchmark stage from CI, moving this to its own workflow	2026-04-13 17:16:41 -04:00
clever-agent	c5afe1f3a7	Build: Made the prompts coming from the product builder to the async subagent more clear to avoid issues in the future	2026-04-13 16:14:24 -04:00
clever-agent	c5820266fd	Build: improced merge agent logic to ensure faster and more effective merging into master	2026-04-13 15:30:00 -04:00
clever-agent	5a9aaa79ed	Build: Reinforced label enforcement, and ensure implementation workers dont continue work on a mergable PR.	2026-04-13 13:54:43 -04:00
clever-agent	16883859b1	Build: some fixes to the automation tracking tickets ensuring they get cleaned up and handled more correctly, and announcements read in a more useful way	2026-04-13 13:00:23 -04:00
HAL9000	978849412d	docs(reference): align A2A facade API with implementation ... Fixes docs/reference/a2a.md Local Facade section. Issues #6620 and #6624. Fixes #6620 Fixes #6624 Automatically merged by PR Merge Pool Supervisor [AUTO-PRMRG-SUP] --- **Automated by CleverAgents Bot** Supervisor: PR Merge | Agent: pr-merge-pool-supervisor Co-authored-by: CleverThis <hal9000@cleverthis.com> Co-committed-by: CleverThis <hal9000@cleverthis.com>	2026-04-13 08:10:03 +00:00
hurui200320	2005b8ef82	feat(tests): replace all @skip tags with proper @tdd_expected_fail tags or remove them across the entire codebase (#7221) ... ## Summary Replaces all 234 bare `@skip` occurrences across 82 Behave feature files with the correct TDD issue-capture tagging system described in CONTRIBUTING.md § Bug Fix Workflow. Previously, the noxfile ran Behave with `--tags=not @skip`, silently excluding all `@skip`-tagged scenarios from every CI run. These tests never ran, never inverted results via the `@tdd_expected_fail` mechanism, and never contributed to coverage — defeating the purpose of TDD issue-capture testing. Every `@skip` occurrence had a commented-out hint line immediately above it showing the intended proper tags (e.g., `# @tdd_issue @tdd_issue_4272 @tdd_expected_fail @skip`), confirming they were all intended for conversion. ## Changes ### Mechanical conversion (234 replacements across 82 files) - Extracted the proper TDD tags from the comment hint above each `@skip` line, removed `@skip` from the tag set, and replaced the `@skip` line with those tags. - Removed the now-redundant comment hint lines alongside each replacement. ### Bug-fixed scenarios — `@tdd_expected_fail` removed (84 scenarios) - After conversion, ran `nox -s unit_tests` to identify which newly-enabled `@tdd_expected_fail` scenarios now **pass** (their referenced bugs have already been fixed). Removed `@tdd_expected_fail` from those 84 scenarios and their corresponding feature-level tags, leaving only the permanent `@tdd_issue @tdd_issue_<N>` regression-guard tags. - Affected features include: `tdd_tool_runner_env_precedence`, `tdd_automation_profile_session_leak`, `tls_certificate_check`, `project_create_persist`, `resource_type_bootstrap_*`, and 18 others. ### Noxfile cleanup - Removed all four `--tags=not @skip` arguments from `noxfile.py` (unit_tests and coverage sessions). With zero `@skip` tags remaining in the codebase, this filter was dead code and its presence would mislead future maintainers into thinking `@skip` is still a supported escape mechanism. ### Regression guard files - Split the regression guards into two focused files: - `tdd_regression_guards_exec_env.feature` for bug #4281 (exec-env precedence) - `tdd_regression_guards_session_list.feature` for bug #4271 (session list summary) - Each file carries only its own `@tdd_issue` tags at the feature level, avoiding cross-contamination via Behave tag inheritance. The `Background` step (`session-list-summary mock`) only appears in the session-list file where it is actually needed. ### Duplicate tag cleanup - Removed duplicate `@tdd_issue @tdd_issue_4287` tag lines in `tdd_skill_add_regression.feature` (lines 20 and 29). ### Inline comment for retained `@tdd_expected_fail` - Added inline comment in `ci_workflow_validation.feature:134` explaining why this specific #4227 scenario retains `@tdd_expected_fail` despite #4227 being closed (CI YAML does not encode threshold as a machine-readable value). ### Known edge cases — `@tdd_expected_fail` retained (closed issues, fix on master, scenarios still fail) The following issues are **closed** and their fixes **are on master**, but the specific test assertions still fail because the fixes address other aspects of the bugs. The `@tdd_expected_fail` tags are functionally correct and must remain until the specific scenario assertions pass: - `tdd_exec_env_resolution_precedence.feature` — bug #1080 (closed 2026-03-31). The precedence-level-2-vs-4 scenario still fails. - `session_list_summary_dedup.feature` — bug #3046 (closed 2026-04-05). The dedup-consistency scenarios still fail. - `actor_add_update_enforcement.feature` — bug #2609 (closed 2026-04-05). The enforcement scenarios still fail. - `ci_workflow_validation.feature:134` — #4227 (closed 2026-04-08). The CI YAML threshold assertion still fails. ## Verification - `grep -r "@skip" features/ --include="*.feature"` → **zero results** ✓ - `grep -n "tags=not @skip" noxfile.py` → **zero results** ✓ - `nox -s unit_tests` → **629 features passed, 0 failed** ✓ (up from ~545 before this PR) - CI all green (coverage ≥ 97%) ✓ - Integration tests (Robot Framework) do not use `@skip` — confirmed no action needed ✓ - E2E tests (Robot Framework) do not use `@skip` — confirmed no action needed ✓ - `CHANGELOG.md` updated with entry for this change ✓ - `CONTRIBUTORS.md` — Rui Hu already listed ✓ ## Issues Addressed Closes #7025 Co-authored-by: CleverThis <hal9000@cleverthis.com> Reviewed-on: #7221 Reviewed-by: HAL 9000 <HAL9000@cleverthis.com> Reviewed-by: HAL9001 <hal9001@cleverthis.com> Co-authored-by: Rui Hu <rui.hu@cleverthis.com> Co-committed-by: Rui Hu <rui.hu@cleverthis.com>	2026-04-13 04:56:01 +00:00
clever-agent	96ff9d0ff8	build:added some excplict priorities	2026-04-12 23:45:01 -04:00
clever-agent	d5446081e3	build: improved the way the project rules are disseminated	2026-04-12 22:33:40 -04:00
clever-agent	56a430d31f	refactor(agents): rename backlog-grooming to grooming, fix tier selector dispatch ... Renamed backlog-grooming-pool-supervisor to grooming-pool-supervisor and backlog-grooming-worker to grooming-worker. The grooming agents now analyze all open issues AND pull requests (not just the backlog). Workers perform a full 10-point quality analysis on a single item instead of processing batches. PRs with unaddressed reviews are prioritized. PR labels are synced from linked issues. Workers post [GROOMED] markers for tracking. Fixed critical issue: implementation-pool-supervisor now correctly dispatches workers through tier selectors (tier-haiku/codex/sonnet/opus) instead of launching implementation-worker directly, ensuring the escalation model actually sets the correct model tier. Added implementation-worker to all four tier selector task permissions. Updated session tags from AUTO-BLOG to AUTO-GROOM. Updated specification sections 4.2.1, 5.5, 5.5.1, 9.7, and architecture diagram. ISSUES CLOSED: n/a	2026-04-12 22:33:40 -04:00
HAL9000	a3094dea2b	docs(spec): clarify path containment, datetime, and plugin security contracts ... Three implementation contracts clarified in response to security/correctness bugs surfaced by the bug hunt pool: 1. Path containment: Sandbox path validation MUST use Path.is_relative_to() not string prefix comparison. String prefix allows /tmp/sandboxmalicious to pass a /tmp/sandbox root check. Canonical implementation provided. 2. Datetime handling: All stored ISO timestamp comparisons MUST parse back to timezone-aware datetime objects before comparing. String comparison of ISO timestamps is incorrect when timezone offsets differ in format. Canonical parse_utc_ts() pattern provided. 3. Plugin protocol validation: Protocol compliance MUST be checked structurally via issubclass() — never by instantiating the plugin class. Instantiation runs __init__ side effects before the plugin is approved. These are minor clarifications (implementation contracts, not architectural changes) added to the existing Security and Extensibility sections. Refs: BUG-HUNT issues #7336 (path traversal), #7341 (datetime comparison), #7331 (plugin instantiation)	2026-04-13 00:44:44 +00:00
clever-agent	1ba4d1a0b3	build: improved the product verifier to make it a bit more effecient	2026-04-12 19:58:05 -04:00
clever-agent	8692bb46e5	build: Refactored agent definitions to be simpler and less contention	2026-04-12 19:24:50 -04:00
HAL9000	48532de1cd	docs: add context hydration and git worktree sandbox module docs ... - Add docs/modules/context-hydration.md: documents the ACMS context hydration pipeline (context_tier_hydrator) that fixes the empty ContextTierService bug (#1028). Covers hydrate_tiers_from_project, hydrate_tiers_for_plan, file listing strategies, limits, and fragment metadata. - Add docs/modules/git-worktree-sandbox.md: documents the GitWorktreeSandbox class that isolates plan apply changes in a dedicated git branch/worktree and merges back on commit (#4454). Covers full lifecycle, error types, branch naming, and fallback for non-git projects. - Update docs/architecture.md: add Git Worktree Sandbox Apply section and extend ACMS section with context hydration note. - Update mkdocs.yml: add both new module pages to the Modules nav. ISSUES CLOSED: #6841	2026-04-12 16:42:19 +00:00
HAL9000	8b7bdb5edf	Merge pull request 'docs(changelog): move ACMS fix to [Fixed] section and add sandbox root wiring' (#6052) from docs/changelog-acms-fix-4219 into master	2026-04-12 16:34:24 +00:00
HAL9000	c08187f336	docs(changelog): move ACMS fix to [Fixed] section and add sandbox root wiring ... Reclassify the ACMS context tier hydration entry as a bug fix and add the sandbox root wiring item so the changelog matches the behavior shipped in PR #4219 while preserving newer [Unreleased] additions. ISSUES CLOSED: #7628	2026-04-12 16:20:21 +00:00
HAL9000	8dceb2ad02	Merge pull request 'fix(data-integrity): guard validation gate for empty runs' (#7786) from fix/issue-7508-validation-apply-required-fields into master	2026-04-12 08:16:06 +00:00
HAL9000	251759c9b1	chore: add changelog entry and contributor for #7508 validation gate fix ... - Add CHANGELOG.md entry under [Unreleased] ### Fixed for the empty-run guard added to ApplyValidationSummary.all_required_passed - Add HAL 9000 to CONTRIBUTORS.md per CONTRIBUTING.md §PR Process Rule 8	2026-04-12 08:15:49 +00:00
HAL9000	8402279596	fix(data-integrity): fix validation_apply.py all_required_ fields #7508 ... ISSUES CLOSED: #7508	2026-04-12 08:15:49 +00:00
clever-agent	f20fed2173	fix(agents): always launch all 18 supervisors fresh, stop existing sessions first ... Previously the product-builder would adopt existing supervisor sessions from prior runs and skip launching those already running. This caused stale sessions to persist with outdated configuration and context. Now Phase C.0 discovers and gracefully stops all existing supervisor sessions before Phase C.2 unconditionally launches all 18 fresh.	2026-04-12 06:17:57 +00:00
clever-agent	ba416ba25d	build: force reviewers to not use forgejo mcp	2026-04-12 01:47:55 -04:00
clever-agent	27f3a57927	build: removed unused files	2026-04-12 01:29:15 -04:00
clever-agent	35ff97a641	fix(agents): force pr-reviewer to use curl exclusively, block all Forgejo MCP tools ... The pr-reviewer agent was falling back to Forgejo MCP tools for reads instead of using curl, causing actions to be attributed to the wrong user account. This change: - Blocks ALL Forgejo MCP tools (forgejo: '*': deny) instead of only specific write tools - Adds explicit curl-only mandate section with clear explanation - Adds tested curl command reference covering every API operation the reviewer needs (PR details, diffs, issues, CI status, reviews, file contents, posting reviews, posting comments, dismissals) - Adds robots.txt override instruction for our self-hosted instance - Updates all review process steps to reference curl instead of MCP	2026-04-12 04:59:51 +00:00
clever-agent	52c35c8182	fix: pass reviewer-only credentials through the PR review agent chain ... The product-builder now reads FORGEJO_REVIEWER_* env vars and passes them as the sole credentials to pr-review-pool-supervisor, which passes them through to pr-reviewer workers. No agent in the review chain receives the primary bot credentials, preventing accidental self-approvals. Simplifies the reviewer instructions to require formal PR reviews (not just comments) and removes contradictory references to denied MCP write tools.	2026-04-12 04:24:23 +00:00
HAL9000	ca2eaab02d	build: Made PR rule first more explicit for agents	2026-04-11 23:33:52 -04:00
clever-agent	b89b781881	docs(spec): add Section 22 — Division of Responsibilities and Redundancy Model ... Add comprehensive responsibility-first analysis of the entire agent system covering 144 named responsibilities (R-01 through R-144) organized into 8 categories with 29 sub-categories and complete bidirectional cross-references. Key additions: - Section 22.0: Categorized Responsibility Index with navigation guide - Section 7.9: Universal Supervisor Responsibilities (13 shared baseline) - Section 22.145: Redundancy Analysis Summary with depth distribution, highest-redundancy items, most cross-referenced agents, and 5 named redundancy patterns - 30 agent back-reference tables covering ~50 individual agents - Category introductions explaining scope and significance - 6th foundational principle (Defense-in-Depth) added to Section 1.1 Categories: A (Development Lifecycle, 50 items), B (Quality Assurance), C (Ticket Hygiene), D (Architecture), E (Operational Health), F (Human Interaction), G (Strategic Governance), H (Project Standards). ISSUES CLOSED: N/A	2026-04-11 23:03:56 -04:00
HAL9000	c62ae454a2	Merge pull request 'docs(timeline): update schedule adherence Day 100 (2026-04-10)' (#6893) from docs/timeline-day-100-2026-04-10 into master	2026-04-11 03:17:48 +00:00
HAL9000	157b0d6b8c	docs(timeline): update schedule adherence Day 100 (2026-04-10) ... Refresh Day 100 entries using Forgejo telemetry across both cycle snapshots to capture scope expansion, milestone progress, and active session data.\n\n- Update today marker and Gantt update log for Day 100\n- Capture scope expansion metrics and milestone completion percentages\n- Refresh risk register, status summary, and track/milestone forecasts\n- Append Day 100 cycle-2 schedule adherence tables for teams and milestones\n- Note infrastructure changes (review requirement, supervisor additions)\n\nISSUES CLOSED: #6975	2026-04-11 02:52:50 +00:00
HAL9000	fa44d2455d	Merge pull request 'docs: document automation-tracking-manager centralization and expand tracking system docs' (#5289) from docs/automation-tracking-manager-centralization into master	2026-04-11 01:07:34 +00:00
HAL9000	c76433f756	docs(tracking): document automation-tracking-manager centralization	2026-04-11 00:40:19 +00:00
HAL9000	28fcf7a02b	Merge pull request 'docs: add actor context management showcase (remove, export, import)' (#4220) from docs/add-example-actor-context-management into master	2026-04-11 00:16:40 +00:00
HAL9000	39b6fb3fa8	docs: harden backup script example	2026-04-10 23:37:56 +00:00
HAL9000	6523034cb0	docs: add actor context management showcase (remove, export, import) ... Document the CLI-based lifecycle for removing, exporting, and importing named contexts, including JSON import limitations and scripting examples. ISSUES CLOSED: #4409	2026-04-10 23:37:56 +00:00
HAL9000	a3d644ca52	Merge pull request 'docs(timeline): update schedule adherence Day 99 (2026-04-09)' (#5185) from timeline/day-99-2026-04-09 into master	2026-04-10 23:30:47 +00:00