test/cli-docstring-example-validation
2746 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
f1bb0bf075 |
fix(application): Remove error suppression in reactive_registry_adapter.py
Remove two try...except Exception: blocks that were silently suppressing errors in register_registry_agents(), violating CONTRIBUTING.md fail-fast policy. Changes: - Remove try/except around actor_registry.list_actors() call; exceptions now propagate to the caller instead of silently returning - Remove try/except around route_bridge.agents refresh; exceptions now propagate instead of silently resetting to empty dict - Update docstring to document the fail-fast propagation behaviour - Update Behave scenarios to verify exceptions propagate correctly: * RuntimeError from list_actors() propagates * AttributeError from actors without .name attribute propagates * TypeError from None actors list propagates Closes #9060 |
||
|
|
d512123d1c |
fix(actor): support v3 Actor YAML schema in CLI registration and execution
CI / lint (pull_request) Successful in 48s
CI / benchmark-publish (pull_request) Has been skipped
CI / build (pull_request) Successful in 54s
CI / quality (pull_request) Successful in 1m52s
CI / typecheck (pull_request) Successful in 1m57s
CI / security (pull_request) Successful in 1m58s
CI / helm (pull_request) Successful in 27s
CI / push-validation (pull_request) Successful in 21s
CI / integration_tests (pull_request) Successful in 6m43s
CI / unit_tests (pull_request) Successful in 9m4s
CI / docker (pull_request) Successful in 1m42s
CI / coverage (pull_request) Successful in 11m45s
CI / e2e_tests (pull_request) Successful in 3m22s
CI / status-check (pull_request) Successful in 3s
CI / benchmark-publish (push) Failing after 44s
CI / build (push) Successful in 49s
CI / lint (push) Successful in 1m8s
CI / helm (push) Successful in 38s
CI / quality (push) Successful in 1m25s
CI / security (push) Successful in 1m26s
CI / typecheck (push) Successful in 1m30s
CI / push-validation (push) Successful in 23s
CI / e2e_tests (push) Successful in 3m52s
CI / integration_tests (push) Successful in 4m8s
CI / coverage (push) Successful in 12m30s
CI / unit_tests (push) Successful in 6m32s
CI / docker (push) Successful in 1m39s
CI / status-check (push) Successful in 3s
The actor CLI was ignoring the v3 ActorConfigSchema format, preventing spec-compliant actors with type/route/skills/lsp fields from being registered or executed. Three components were fixed: ActorConfiguration.from_blob() now detects v3 format (top-level "type" key with value llm/graph/tool) and extracts provider from the model string, falling through to v2 extraction when v3 does not match. ActorRegistry.add() now routes v3 YAML through full ActorConfigSchema validation, persists description/skills/lsp in the config blob, and compiles graph actors with compile_actor() storing metadata. Legacy v2 YAML continues through the original path unchanged. ReactiveConfigParser._build() now synthesises reactive agents and graph routes from v3 actor data so that agents actor run can execute v3 actors through the existing ReactiveCleverAgentsApp pipeline. ISSUES CLOSED: #6283 |
||
|
|
69a8bcf7ea |
TDD: Add test for TypeError in infer_resource_slots() with null properties
CI / build (push) Successful in 50s
CI / lint (push) Successful in 1m2s
CI / helm (push) Successful in 32s
CI / quality (push) Successful in 1m10s
CI / typecheck (push) Successful in 1m30s
CI / push-validation (push) Successful in 49s
CI / security (push) Successful in 1m52s
CI / benchmark-publish (push) Failing after 49s
CI / integration_tests (push) Successful in 3m38s
CI / e2e_tests (push) Successful in 4m32s
CI / unit_tests (push) Successful in 9m35s
CI / coverage (push) Successful in 14m49s
CI / docker (push) Successful in 1m33s
CI / status-check (push) Successful in 3s
CI / benchmark-publish (pull_request) Has been skipped
CI / helm (pull_request) Successful in 28s
CI / build (pull_request) Successful in 54s
CI / lint (pull_request) Successful in 1m6s
CI / typecheck (pull_request) Successful in 1m21s
CI / quality (pull_request) Successful in 1m58s
CI / security (pull_request) Successful in 2m22s
CI / push-validation (pull_request) Successful in 27s
CI / e2e_tests (pull_request) Successful in 4m8s
CI / integration_tests (pull_request) Successful in 4m28s
CI / unit_tests (pull_request) Successful in 4m39s
CI / docker (pull_request) Successful in 1m49s
CI / coverage (pull_request) Successful in 10m46s
CI / status-check (pull_request) Successful in 3s
|
||
|
|
323a5d4212 |
TDD: Add test for TypeError in infer_resource_slots() with null properties
Added a new Behave BDD feature file:
- features/tdd_mcp_infer_resource_slots_null_properties.feature, containing
a TDD scenario tagged @tdd_issue @tdd_issue_10470 @tdd_expected_fail that
demonstrates the bug where MCPToolAdapter.infer_resource_slots() raises
TypeError when the input schema has {"properties": None}.
Added features/steps/tdd_mcp_infer_resource_slots_null_properties_steps.py:
- Step definitions for the feature file.
ISSUES CLOSED: #10470
|
||
|
|
acb46d96f7 |
style: fix ruff formatting in tdd_session_tell_stream_redaction_steps.py
CI / benchmark-publish (push) Failing after 39s
CI / lint (push) Successful in 1m23s
CI / helm (push) Successful in 32s
CI / typecheck (push) Successful in 1m25s
CI / build (push) Successful in 48s
CI / quality (push) Successful in 1m22s
CI / security (push) Successful in 1m34s
CI / push-validation (push) Successful in 23s
CI / e2e_tests (push) Successful in 3m28s
CI / unit_tests (push) Successful in 4m32s
CI / integration_tests (push) Successful in 4m59s
CI / docker (push) Successful in 1m27s
CI / build (pull_request) Successful in 52s
CI / lint (pull_request) Successful in 1m15s
CI / typecheck (pull_request) Successful in 1m32s
CI / benchmark-publish (pull_request) Has been skipped
CI / quality (pull_request) Successful in 1m41s
CI / security (pull_request) Successful in 1m42s
CI / helm (pull_request) Successful in 25s
CI / push-validation (pull_request) Successful in 26s
CI / e2e_tests (pull_request) Successful in 4m3s
CI / coverage (push) Successful in 13m55s
CI / unit_tests (pull_request) Failing after 6m59s
CI / docker (pull_request) Has been skipped
CI / integration_tests (pull_request) Successful in 7m4s
CI / status-check (push) Successful in 3s
CI / coverage (pull_request) Successful in 9m56s
CI / status-check (pull_request) Failing after 5s
Reformatted assertion in step_output_contains to satisfy ruff format check. The multi-line assert with parentheses was collapsed to a single line per ruff formatting rules. |
||
|
|
c3691a6eff |
fix(cli): route session tell --stream output through console to apply redaction
Replaced the tell streaming path in src/cleveragents/cli/commands/session.py to route through the Rich console by using console.print(_escape(assistant_content)) instead of writing characters directly to stdout. This ensures the redaction layer is applied before content reaches stdout and removes the now-unused import sys. Added a new TDD/BDD feature: features/tdd_session_tell_stream_redaction.feature with 3 scenarios verifying that session tell --stream does not write directly to sys.stdout, that output contains the assistant response, and that streaming output goes through the Rich console. Added features/steps/tdd_session_tell_stream_redaction_steps.py with step definitions to support the new feature. ISSUES CLOSED: #10460 |
||
|
|
0d086ddc63 |
chore(agents): add git clone permission to bug-hunter worker mode
CI / benchmark-publish (push) Failing after 47s
CI / lint (push) Successful in 59s
CI / build (push) Successful in 41s
CI / helm (push) Successful in 27s
CI / typecheck (push) Successful in 1m32s
CI / quality (push) Successful in 1m38s
CI / security (push) Successful in 1m44s
CI / push-validation (push) Successful in 23s
CI / integration_tests (push) Successful in 4m7s
CI / e2e_tests (push) Successful in 4m18s
CI / unit_tests (push) Successful in 4m38s
CI / docker (push) Successful in 1m58s
CI / coverage (push) Successful in 11m33s
CI / status-check (push) Successful in 3s
CI / benchmark-publish (pull_request) Has been skipped
CI / build (pull_request) Successful in 53s
CI / lint (pull_request) Successful in 1m3s
CI / typecheck (pull_request) Successful in 1m26s
CI / helm (pull_request) Successful in 34s
CI / security (pull_request) Successful in 1m31s
CI / quality (pull_request) Successful in 1m37s
CI / push-validation (pull_request) Successful in 22s
CI / unit_tests (pull_request) Successful in 4m48s
CI / e2e_tests (pull_request) Successful in 5m32s
CI / integration_tests (pull_request) Successful in 5m34s
CI / docker (pull_request) Successful in 1m35s
CI / coverage (pull_request) Successful in 10m13s
CI / status-check (pull_request) Successful in 3s
Approved proposal: #3831 Pattern: permission_gap Evidence: Bug-hunter worker mode requires cloning the repository to analyze source code, but git clone/config/fetch/checkout/reset permissions were missing from the bash permission list. Workers were unable to clone the repo and therefore could not perform any code analysis. Fix: Add git clone*, git config*, git fetch*, git checkout*, git reset*, mkdir *, and rm -rf * permissions to enable workers to clone and clean up their isolated working directories. ISSUES CLOSED: #3831 |
||
|
|
f2b60cc3d6 |
fix(cli): restore session list json contract
CI / benchmark-publish (pull_request) Has been skipped
CI / helm (pull_request) Successful in 35s
CI / push-validation (pull_request) Successful in 21s
CI / build (pull_request) Successful in 52s
CI / lint (pull_request) Successful in 1m0s
CI / quality (pull_request) Successful in 1m33s
CI / security (pull_request) Successful in 1m45s
CI / typecheck (pull_request) Successful in 1m49s
CI / integration_tests (pull_request) Successful in 3m58s
CI / e2e_tests (pull_request) Successful in 4m32s
CI / unit_tests (pull_request) Successful in 5m55s
CI / docker (pull_request) Successful in 1m31s
CI / coverage (pull_request) Successful in 10m47s
CI / status-check (pull_request) Successful in 3s
CI / build (push) Successful in 47s
CI / lint (push) Successful in 57s
CI / helm (push) Successful in 28s
CI / quality (push) Successful in 1m11s
CI / typecheck (push) Successful in 1m34s
CI / security (push) Successful in 1m36s
CI / push-validation (push) Successful in 21s
CI / benchmark-publish (push) Failing after 40s
CI / integration_tests (push) Successful in 3m47s
CI / e2e_tests (push) Successful in 4m9s
CI / unit_tests (push) Successful in 7m0s
CI / docker (push) Successful in 1m31s
CI / coverage (push) Successful in 10m40s
CI / status-check (push) Successful in 3s
Ensure the session list helper only emits the documented fields so downstream consumers stay compliant, and tighten the Behave coverage to enforce the contract.\n\nISSUES CLOSED: #6436 |
||
|
|
b92f0270c2 |
fix(cli): fix session show/list JSON output to not redact input messages (#6436)
ISSUES CLOSED: #6436 |
||
|
|
581dff6b43 |
spec(acms): add comprehensive ACMS v1 specification section (v3.4.0)
CI / push-validation (push) Successful in 30s
CI / helm (push) Successful in 33s
CI / lint (push) Successful in 1m8s
CI / build (push) Successful in 1m0s
CI / quality (push) Successful in 1m39s
CI / typecheck (push) Successful in 1m44s
CI / security (push) Successful in 1m47s
CI / benchmark-publish (push) Failing after 41s
CI / e2e_tests (push) Successful in 4m4s
CI / integration_tests (push) Successful in 4m17s
CI / unit_tests (push) Successful in 4m59s
CI / docker (push) Successful in 1m30s
CI / coverage (push) Successful in 10m50s
CI / status-check (push) Successful in 2s
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Successful in 1m0s
CI / quality (pull_request) Successful in 1m16s
CI / build (pull_request) Successful in 50s
CI / typecheck (pull_request) Successful in 1m36s
CI / security (pull_request) Successful in 1m41s
CI / push-validation (pull_request) Successful in 36s
CI / helm (pull_request) Successful in 38s
CI / integration_tests (pull_request) Successful in 3m54s
CI / e2e_tests (pull_request) Successful in 4m12s
CI / unit_tests (pull_request) Successful in 4m58s
CI / docker (pull_request) Successful in 1m26s
CI / coverage (pull_request) Successful in 12m34s
CI / status-check (pull_request) Successful in 3s
Adds a comprehensive ACMS v1 (Advanced Context Management System) specification section covering all aspects of the context management architecture for milestone v3.4.0 — ACMS v1 + Context Scaling. Sections included: - Overview and design goals - Architecture: UKO (Unified Knowledge Ontology), CRP (Context Request Protocol), Context Pipeline, Storage Tiers (hot/warm/cold) - Module Definitions across all 4 architecture layers (Domain, Application, Infrastructure, Presentation) - Data Models: ContextFragment, ContextBudget, ProjectContextPolicy, ContextView, AssembledContext/ContextPayload, IndexMetadata - Key Interfaces: ACMSPipeline, ContextBudgetEnforcer, UKOStore, ContextTierService, RepoIndexingService - 10-Component Pipeline Architecture (3 phases: Strategy Orchestration, Fragment Fusion, Context Finalization) - Context Strategies: 6 built-in strategies with fallback degradation path - CLI Commands: agents context list/add/show/clear and agents project context set/show/inspect/simulate - Integration Points: Plan Lifecycle, Resource System, Actor/Agent, Configuration, DI Container - Database Schema: repo_indexes and indexed_files tables - v1 Known Limitations with planned conformance path - Acceptance Criteria for milestone v3.4.0 Replaces stuck [AUTO-ARCH-19] worker from Cycle 26. [AUTO-ARCH-20] Cycle 27 # Conflicts: # docs/specification.md |
||
|
|
946c496a50 |
ci: trigger CI re-run — infrastructure failures resolved
CI / lint (push) Successful in 1m3s
CI / helm (push) Successful in 26s
CI / benchmark-publish (push) Failing after 45s
CI / typecheck (push) Successful in 1m20s
CI / quality (push) Successful in 1m18s
CI / build (push) Successful in 48s
CI / push-validation (push) Successful in 26s
CI / security (push) Successful in 1m48s
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Successful in 54s
CI / helm (pull_request) Successful in 24s
CI / push-validation (pull_request) Successful in 32s
CI / build (pull_request) Successful in 37s
CI / typecheck (pull_request) Successful in 1m26s
CI / quality (pull_request) Successful in 1m24s
CI / security (pull_request) Successful in 1m32s
CI / e2e_tests (push) Successful in 3m27s
CI / e2e_tests (pull_request) Successful in 3m30s
CI / integration_tests (push) Successful in 4m44s
CI / integration_tests (pull_request) Successful in 5m18s
CI / unit_tests (push) Successful in 6m29s
CI / docker (push) Successful in 1m44s
CI / unit_tests (pull_request) Failing after 12m45s
CI / coverage (push) Successful in 11m35s
CI / status-check (push) Successful in 3s
CI / coverage (pull_request) Successful in 13m18s
CI / docker (pull_request) Has been skipped
CI / status-check (pull_request) Failing after 6s
|
||
|
|
92feab2a2d | fix(lock): address reviewer suggestions — add ValueError handling and ISO string test scenario | ||
|
|
e249f80339 |
fix(lock): replace fragile ISO string comparison with datetime comparison in LockService
Added a new helper function _to_aware_datetime() in lock_service.py that normalizes ORM timestamp values to timezone-aware datetime objects, handling naive datetimes, timezone-aware datetimes, and ISO strings. Fixed LockService.acquire() to use datetime comparison instead of fragile string comparison for lock expiry detection (bug #10483). Fixed LockService.renew() similarly to use datetime comparison. Added a new TDD Behave feature file features/tdd_lock_service_naive_datetime_expiry.feature with a scenario that proves the fix works. Added step definitions features/steps/tdd_lock_service_naive_datetime_expiry_steps.py. ISSUES CLOSED: #10483 |
||
|
|
2db01fbc17 |
fix(cli): resolve merge conflict and address all reviewer blockers for #993
CI / push-validation (push) Successful in 22s
CI / helm (push) Successful in 27s
CI / lint (push) Successful in 1m7s
CI / build (push) Successful in 1m5s
CI / quality (push) Successful in 1m35s
CI / typecheck (push) Successful in 1m35s
CI / security (push) Successful in 2m13s
CI / benchmark-publish (push) Failing after 42s
CI / integration_tests (push) Successful in 4m36s
CI / e2e_tests (push) Successful in 5m33s
CI / unit_tests (push) Successful in 6m32s
CI / docker (push) Successful in 1m27s
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Successful in 1m15s
CI / quality (pull_request) Successful in 1m17s
CI / typecheck (pull_request) Successful in 1m32s
CI / security (pull_request) Successful in 1m25s
CI / build (pull_request) Successful in 38s
CI / helm (pull_request) Successful in 26s
CI / push-validation (pull_request) Successful in 30s
CI / coverage (push) Successful in 11m9s
CI / status-check (push) Successful in 13s
CI / integration_tests (pull_request) Successful in 3m38s
CI / e2e_tests (pull_request) Successful in 3m48s
CI / unit_tests (pull_request) Successful in 6m27s
CI / docker (pull_request) Successful in 1m21s
CI / coverage (pull_request) Successful in 11m32s
CI / status-check (pull_request) Successful in 5s
- Resolve merge conflict in config_service.py: integrate PR's emit_config_changed() helper with master's scoped config infrastructure (write_scoped_config, scoped set_value) - Remove # type: ignore[assignment] by introducing typed _AutoDiscover sentinel class for project_root parameter - Add exc_info=True to emit_config_changed warning log - Fix server.py: remove invalid scope='global' from emit_config_changed rollback calls; use svc._config_path instead of hardcoded path - Add ReactiveEventBus.close() method for proper resource cleanup - Fix BDD test steps: call event_bus.close() in cleanup handler - Update CHANGELOG.md and CONTRIBUTORS.md Closes #993 |
||
|
|
e3ab8a4e20 |
fix(cli): add scope parameter to compensating emit_config_changed() calls
Pass scope="global" to emit_config_changed() in the server_connect rollback path to maintain consistency with the scoped event details convention established by master's ConfigService.set_value(). ISSUES CLOSED: #993 |
||
|
|
b9a4fa519d |
fix(test): update _FailingConfigService.set_value() to match scoped signature
Update the test double to accept the scope keyword argument added by master's scoped config changes, and pass project_root=None to avoid auto-discovery in test environments. ISSUES CLOSED: #993 |
||
|
|
c2d84c6f09 |
bug(cli): server_connect writes three config values non-atomically — partial update on failure
Make server_connect config persistence all-or-nothing by snapshotting ~/.cleveragents/config.toml before the three set_value calls and restoring the exact prior bytes on any exception. This preserves existing config-change audit events on success while preventing partially written server URL/namespace/TLS state after mid-sequence failures.\n\nAlso promote the #993 TDD feature from expected-fail to active regression coverage and tighten a flaky resource DAG Robot scenario by using a shared session with explicit commits to keep integration gates stable under parallel execution. ISSUES CLOSED: #993 |
||
|
|
3975ad244c |
docs(spec): fix invariant reconciliation, add ACMS thread safety, v3.6.0 section, ADR-049
CI / benchmark-publish (push) Failing after 35s
CI / lint (push) Successful in 53s
CI / quality (push) Successful in 1m9s
CI / typecheck (push) Successful in 1m14s
CI / build (push) Successful in 38s
CI / security (push) Successful in 1m21s
CI / push-validation (push) Successful in 22s
CI / helm (push) Successful in 38s
CI / integration_tests (push) Successful in 3m44s
CI / e2e_tests (push) Successful in 4m5s
CI / unit_tests (push) Failing after 6m56s
CI / docker (push) Has been skipped
CI / coverage (push) Successful in 11m16s
CI / status-check (push) Failing after 3s
CI / lint (pull_request) Successful in 1m15s
CI / build (pull_request) Successful in 54s
CI / quality (pull_request) Successful in 1m27s
CI / benchmark-publish (pull_request) Has been skipped
CI / typecheck (pull_request) Successful in 1m51s
CI / security (pull_request) Successful in 1m52s
CI / push-validation (pull_request) Successful in 20s
CI / helm (pull_request) Successful in 28s
CI / integration_tests (pull_request) Successful in 4m6s
CI / e2e_tests (pull_request) Successful in 4m14s
CI / unit_tests (pull_request) Successful in 4m54s
CI / docker (pull_request) Successful in 1m45s
CI / coverage (pull_request) Successful in 14m1s
CI / status-check (pull_request) Successful in 2s
- Fix invariant glossary entry: reconciliation now documented as occurring at each phase boundary (before Strategize, Execute, Apply, and after Apply) rather than only at start of Strategize (closes #9899) - Add Multi-Phase Invariant Enforcement note to Plan Lifecycle section - Add ACMS Thread Safety subsection documenting threading.RLock concurrency contract for ContextAssemblyPipeline and all context stores (closes #9859) - Append M7: Advanced Concepts and Deferred Features (v3.6.0) milestone spec section covering advanced invariant lifecycle, ACMS observability, plan hierarchy enhancements, and CLI communication pattern migration - Add ADR-049: CLI Communication Pattern documenting local CLI exemption from A2A boundary requirement and M9 migration path |
||
|
|
0f0efe02e3 |
docs: update examples.json index with actor management workflow entry
CI / helm (pull_request) Successful in 34s
CI / build (pull_request) Successful in 50s
CI / lint (pull_request) Successful in 57s
CI / push-validation (pull_request) Successful in 28s
CI / quality (pull_request) Successful in 1m23s
CI / typecheck (pull_request) Successful in 1m28s
CI / benchmark-publish (pull_request) Has been skipped
CI / security (pull_request) Successful in 1m37s
CI / e2e_tests (pull_request) Successful in 3m46s
CI / integration_tests (pull_request) Successful in 4m32s
CI / unit_tests (pull_request) Successful in 5m50s
CI / docker (pull_request) Successful in 1m22s
CI / coverage (pull_request) Successful in 13m4s
CI / status-check (push) Blocked by required conditions
CI / benchmark-publish (push) Failing after 39s
CI / push-validation (push) Successful in 22s
CI / helm (push) Successful in 35s
CI / status-check (pull_request) Successful in 5s
CI / build (push) Successful in 50s
CI / lint (push) Successful in 1m17s
CI / quality (push) Successful in 1m34s
CI / typecheck (push) Successful in 1m36s
CI / security (push) Successful in 1m38s
CI / coverage (push) Has started running
CI / e2e_tests (push) Successful in 3m51s
CI / integration_tests (push) Successful in 4m19s
CI / unit_tests (push) Successful in 5m20s
CI / docker (push) Successful in 2m4s
ISSUES CLOSED: #7539 |
||
|
|
3cfa344110 |
docs(spec): align checkpoint trigger names and config key path with implementation
CI / build (pull_request) Successful in 54s
CI / lint (pull_request) Successful in 1m0s
CI / quality (pull_request) Successful in 1m21s
CI / typecheck (pull_request) Successful in 1m28s
CI / security (pull_request) Successful in 1m56s
CI / helm (pull_request) Successful in 24s
CI / push-validation (pull_request) Successful in 23s
CI / e2e_tests (pull_request) Successful in 5m14s
CI / integration_tests (pull_request) Successful in 6m1s
CI / unit_tests (pull_request) Successful in 7m14s
CI / docker (pull_request) Successful in 1m35s
CI / coverage (pull_request) Successful in 10m48s
CI / status-check (pull_request) Successful in 2s
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (push) Successful in 59s
CI / helm (push) Successful in 33s
CI / quality (push) Successful in 1m18s
CI / build (push) Successful in 50s
CI / security (push) Successful in 1m37s
CI / typecheck (push) Successful in 1m59s
CI / push-validation (push) Successful in 22s
CI / e2e_tests (push) Successful in 3m40s
CI / integration_tests (push) Successful in 4m20s
CI / unit_tests (push) Successful in 6m17s
CI / benchmark-publish (push) Failing after 43s
CI / docker (push) Successful in 1m53s
CI / coverage (push) Successful in 12m7s
CI / status-check (push) Successful in 3s
|
||
|
|
9f583fffeb |
ci: retrigger CI pipeline
CI / push-validation (pull_request) Successful in 25s
CI / helm (pull_request) Successful in 31s
CI / build (pull_request) Successful in 48s
CI / lint (pull_request) Successful in 57s
CI / quality (pull_request) Successful in 1m8s
CI / typecheck (pull_request) Successful in 1m22s
CI / security (pull_request) Successful in 1m42s
CI / integration_tests (pull_request) Successful in 4m3s
CI / e2e_tests (pull_request) Successful in 4m33s
CI / unit_tests (pull_request) Successful in 7m20s
CI / docker (pull_request) Successful in 1m23s
CI / coverage (pull_request) Successful in 11m51s
CI / status-check (pull_request) Successful in 3s
CI / lint (push) Successful in 1m5s
CI / helm (push) Successful in 34s
CI / quality (push) Successful in 1m19s
CI / build (push) Successful in 52s
CI / typecheck (push) Successful in 1m33s
CI / benchmark-publish (pull_request) Has been skipped
CI / security (push) Successful in 1m44s
CI / push-validation (push) Successful in 23s
CI / e2e_tests (push) Successful in 3m50s
CI / integration_tests (push) Successful in 6m24s
CI / unit_tests (push) Successful in 8m34s
CI / docker (push) Successful in 1m34s
CI / benchmark-publish (push) Failing after 41s
CI / coverage (push) Successful in 11m54s
CI / status-check (push) Successful in 4s
|
||
|
|
4c88458519 | ci: retrigger CI pipeline | ||
|
|
da214b101d |
ci: retrigger CI pipeline
Retrigger CI to resolve transient docker build failure. All code quality gates (lint, typecheck, unit_tests, integration_tests, coverage) pass. The docker failure is a CI infrastructure issue unrelated to this documentation-only PR. |
||
|
|
d6f4395869 |
docs(agents): remove extraneous blank line in CHANGELOG entry
Clean up double blank line in the CHANGELOG.md entry for the PR merge supervisor criteria documentation (#8107). ISSUES CLOSED: #8107 |
||
|
|
7c21ca0d6f |
docs(agents): sync pr-merge-pool-supervisor merge criteria with runtime behaviour
Add Ten Merge Criteria section to pr-merge-pool-supervisor.md documenting all 10 criteria the supervisor checks at runtime. Previously only 6 criteria were documented, creating inconsistency with actual runtime behaviour. Also update CHANGELOG.md and CONTRIBUTORS.md. Closes #8107 # Conflicts: # CONTRIBUTORS.md |
||
|
|
087314843a |
ci: remove benchmark-regression job from PR workflow (already in scheduled)
CI / push-validation (pull_request) Successful in 28s
CI / helm (pull_request) Successful in 32s
CI / lint (pull_request) Successful in 1m3s
CI / build (pull_request) Successful in 59s
CI / quality (pull_request) Successful in 1m26s
CI / security (pull_request) Successful in 1m38s
CI / typecheck (pull_request) Successful in 1m46s
CI / e2e_tests (pull_request) Successful in 3m51s
CI / integration_tests (pull_request) Successful in 4m0s
CI / unit_tests (pull_request) Successful in 6m7s
CI / docker (pull_request) Successful in 1m34s
CI / coverage (pull_request) Successful in 11m9s
CI / benchmark-publish (push) Waiting to run
CI / status-check (pull_request) Successful in 3s
CI / helm (push) Successful in 28s
CI / push-validation (push) Successful in 29s
CI / lint (push) Successful in 1m0s
CI / quality (push) Successful in 1m13s
CI / typecheck (push) Successful in 1m23s
CI / build (push) Successful in 1m3s
CI / security (push) Successful in 1m31s
CI / integration_tests (push) Successful in 4m20s
CI / e2e_tests (push) Successful in 5m11s
CI / unit_tests (push) Successful in 10m37s
CI / docker (push) Successful in 1m24s
CI / benchmark-publish (pull_request) Has been skipped
CI / coverage (push) Successful in 12m19s
CI / status-check (push) Successful in 3s
The benchmark-regression job was supposed to be moved to the dedicated benchmark-scheduled.yml workflow (commit
|
||
|
|
05b58630bf |
style(a2a): apply ruff format to integration test helper
Apply ruff format to robot/helper_a2a_session_plan_lifecycle_integration.py to fix CI lint failure. Changes are purely formatting (whitespace, line wrapping) with no logic modifications. ISSUES CLOSED: #10032 |
||
|
|
d306e6e33c |
test(a2a): add integration tests for full A2A session and plan lifecycle
- Added robot/a2a_session_plan_lifecycle_integration.robot: Robot Framework integration test suite with 7 test cases covering the full A2A session and plan lifecycle, event queue publish/subscribe, guard enforcement (budget cap, tool call limit, denylist), and plan rollback with session state consistency. - Added robot/helper_a2a_session_plan_lifecycle_integration.py: Helper script with real service instances (no mocks) using in-memory SQLite, wiring up A2A facade, session service, plan lifecycle service, event queue, and autonomy guardrail service. ISSUES CLOSED: #10032 |
||
|
|
446f447c03 |
style(test): apply ruff format to tdd_lsp_path_containment_steps.py
CI / push-validation (pull_request) Successful in 24s
CI / helm (pull_request) Successful in 31s
CI / build (pull_request) Successful in 49s
CI / lint (pull_request) Successful in 59s
CI / typecheck (pull_request) Successful in 1m21s
CI / quality (pull_request) Successful in 1m23s
CI / security (pull_request) Successful in 1m43s
CI / e2e_tests (pull_request) Successful in 3m59s
CI / integration_tests (pull_request) Successful in 5m54s
CI / unit_tests (pull_request) Successful in 7m44s
CI / docker (pull_request) Successful in 1m21s
CI / coverage (pull_request) Successful in 11m19s
CI / status-check (pull_request) Successful in 2s
CI / status-check (push) Blocked by required conditions
CI / benchmark-regression (push) Waiting to run
CI / benchmark-publish (push) Waiting to run
CI / lint (push) Successful in 59s
CI / helm (push) Successful in 26s
CI / build (push) Successful in 48s
CI / quality (push) Successful in 1m21s
CI / typecheck (push) Successful in 1m34s
CI / security (push) Successful in 1m34s
CI / push-validation (push) Successful in 21s
CI / coverage (push) Has started running
CI / integration_tests (push) Successful in 3m26s
CI / e2e_tests (push) Successful in 4m21s
CI / unit_tests (push) Successful in 5m10s
CI / docker (push) Successful in 1m29s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Successful in 1h4m13s
|
||
|
|
e619c1be58 |
test(lsp/runtime): fix TDD tag to reference bug issue #10490 and add safe-file scenario
Corrected @tdd_issue_10489 → @tdd_issue_10490 so the tag references the actual bug issue (path traversal vulnerability) rather than the TDD issue itself. Added a positive scenario verifying _read_file can still read files inside the workspace, as suggested in review. ISSUES CLOSED: #10489 |
||
|
|
b5110761c2 |
lsp/runtime: add failing test proving LspRuntime._read_file has no workspace path containment check
Added features/tdd_lsp_path_containment.feature: Introduces a TDD Behave feature with a @tdd_expected_fail scenario to demonstrate that LspRuntime._read_file() does not enforce workspace path containment, guiding a fix. Added features/steps/tdd_lsp_path_containment_steps.py: Provides step definitions for executing the new test. ISSUES CLOSED: #10489 |
||
|
|
1b515d529c |
fix(tests): align LLM trace test session factory with flush-based save
CI / lint (pull_request) Successful in 1m22s
CI / typecheck (pull_request) Successful in 1m35s
CI / quality (pull_request) Successful in 1m39s
CI / push-validation (pull_request) Successful in 24s
CI / helm (pull_request) Successful in 27s
CI / build (pull_request) Successful in 56s
CI / security (pull_request) Successful in 1m46s
CI / integration_tests (pull_request) Successful in 4m42s
CI / e2e_tests (pull_request) Successful in 4m26s
CI / unit_tests (pull_request) Successful in 6m3s
CI / docker (pull_request) Successful in 1m26s
CI / coverage (pull_request) Successful in 12m11s
CI / status-check (pull_request) Successful in 3s
CI / lint (push) Successful in 55s
CI / build (push) Successful in 50s
CI / helm (push) Successful in 27s
CI / push-validation (push) Successful in 20s
CI / quality (push) Successful in 1m13s
CI / typecheck (push) Successful in 1m18s
CI / security (push) Successful in 1m31s
CI / integration_tests (push) Successful in 3m55s
CI / e2e_tests (push) Successful in 4m5s
CI / unit_tests (push) Successful in 5m28s
CI / docker (push) Successful in 1m45s
CI / coverage (push) Successful in 13m14s
CI / benchmark-publish (pull_request) Has been skipped
CI / status-check (push) Successful in 4s
CI / benchmark-regression (push) Has been skipped
CI / benchmark-publish (push) Has started running
CI / benchmark-regression (pull_request) Failing after 1h5m16s
Use a shared session in test setup so that data flushed (but not committed) by LLMTraceRepository.save() remains visible to subsequent read operations within the same test scenario. This matches the production UnitOfWork pattern where a single session is shared across repository calls. Also fixes ruff format violations (single quotes, string concatenation) that caused the CI lint gate to fail. ISSUES CLOSED: #10034 |
||
|
|
2a5a37d774 |
fix: remove type: ignore comments and use proper method assignment
Removed type: ignore[method-assign] comments from spy function assignments in test code. Replaced direct method assignment with object.__setattr__ to properly handle method replacement without type suppression, maintaining code quality standards. |
||
|
|
b4b6fe6484 |
fix: replace session.commit() with session.flush() in LLMTraceRepository.save()
Refactor: replace session.commit() with session.flush() in LLMTraceRepository.save() to ensure changes are persisted within the UnitOfWork without prematurely committing the database transaction. - Updated LLMTraceRepository.save() to call session.flush() instead of session.commit() in src/cleveragents/infrastructure/database/llm_trace_repository.py. - Added two new BDD scenarios to features/llm_trace.feature: - 'Repository save() calls flush not commit' to verify save() uses flush not commit. - 'LLM trace rolled back when UnitOfWork transaction rolls back' to verify rollback. - Added corresponding step definitions to features/steps/llm_trace_steps.py. ISSUES CLOSED: #10034 |
||
|
|
927c5a4681 |
chore(ci): optimize Dockerfile layer order to cache Python dependency installation
CI / lint (pull_request) Successful in 1m3s
CI / build (pull_request) Successful in 42s
CI / quality (pull_request) Successful in 1m13s
CI / typecheck (pull_request) Successful in 1m23s
CI / push-validation (pull_request) Successful in 24s
CI / helm (pull_request) Successful in 36s
CI / security (pull_request) Successful in 1m38s
CI / integration_tests (pull_request) Successful in 4m8s
CI / e2e_tests (pull_request) Successful in 5m11s
CI / unit_tests (pull_request) Successful in 7m27s
CI / docker (pull_request) Successful in 2m43s
CI / coverage (pull_request) Successful in 12m6s
CI / status-check (pull_request) Successful in 3s
CI / coverage (push) Blocked by required conditions
CI / docker (push) Blocked by required conditions
CI / status-check (push) Blocked by required conditions
CI / push-validation (push) Successful in 24s
CI / helm (push) Successful in 31s
CI / benchmark-publish (pull_request) Has been skipped
CI / build (push) Failing after 15m55s
CI / e2e_tests (push) Failing after 15m56s
CI / integration_tests (push) Failing after 15m58s
CI / unit_tests (push) Failing after 15m58s
CI / quality (push) Failing after 15m58s
CI / security (push) Failing after 15m58s
CI / typecheck (push) Failing after 16m0s
CI / lint (push) Failing after 16m2s
CI / benchmark-regression (push) Has been skipped
CI / benchmark-publish (push) Has started running
CI / benchmark-regression (pull_request) Successful in 1h3m8s
Reorder COPY and RUN instructions in both Dockerfile and Dockerfile.server to leverage Docker's layer caching for the dependency installation step. Previously, pyproject.toml, README.md, and src/ were all copied together before running uv pip install, meaning any source code change would invalidate the dependency layer cache and force a full reinstall. The new pattern copies only the dependency manifests (pyproject.toml and uv.lock) first, installs the build tool in a cached layer, then copies README.md and src/ for the actual wheel build. This ensures the uv pip install step is only re-executed when pyproject.toml or uv.lock change, not on every source code change. ISSUES CLOSED: #1667 |
||
|
|
4f2122cd9e |
docs: add action module API reference, update CHANGELOG and nav
CI / push-validation (pull_request) Successful in 27s
CI / helm (pull_request) Successful in 32s
CI / lint (pull_request) Successful in 1m6s
CI / build (pull_request) Successful in 1m0s
CI / typecheck (pull_request) Successful in 1m35s
CI / quality (pull_request) Successful in 1m41s
CI / benchmark-publish (pull_request) Has been skipped
CI / security (pull_request) Successful in 2m50s
CI / integration_tests (pull_request) Successful in 5m3s
CI / e2e_tests (pull_request) Successful in 5m27s
CI / unit_tests (pull_request) Successful in 6m49s
CI / docker (pull_request) Successful in 1m23s
CI / coverage (pull_request) Successful in 11m17s
CI / status-check (pull_request) Successful in 3s
CI / lint (push) Successful in 1m14s
CI / security (push) Successful in 1m22s
CI / typecheck (push) Successful in 1m51s
CI / quality (push) Successful in 1m29s
CI / push-validation (push) Successful in 27s
CI / helm (push) Successful in 48s
CI / build (push) Successful in 48s
CI / integration_tests (push) Successful in 4m11s
CI / e2e_tests (push) Successful in 4m19s
CI / unit_tests (push) Successful in 6m14s
CI / docker (push) Successful in 1m33s
CI / coverage (push) Successful in 16m7s
CI / benchmark-regression (push) Has been skipped
CI / benchmark-publish (push) Failing after 1m3s
CI / status-check (push) Successful in 3s
CI / benchmark-regression (pull_request) Failing after 1h11m1s
- Add docs/api/action.md: full API reference for ActionConfigSchema and ActionArgumentSchema — field tables, factory methods, camelCase compat mapping, env-var interpolation, database integrity note, and complete YAML example - Update docs/api/index.md: add cleveragents.action entry to module index - Update mkdocs.yml: add 'Action Schema: api/action.md' to the API Reference nav - Update CHANGELOG.md [Unreleased] Fixed: document plan use UNIQUE constraint violation fix (#4174, #4197) - Clarify from_yaml_file ValueError semantics, document inputs_schema type as dict[str, Any] | None, and update A2A ASV benchmarks to pass method= requests after JSON-RPC migration ISSUES CLOSED: #7472 |
||
|
|
8320f9f4cb |
fix: correct trusted automation profile description to match spec
CI / push-validation (pull_request) Successful in 23s
CI / helm (pull_request) Successful in 32s
CI / build (pull_request) Successful in 54s
CI / lint (pull_request) Successful in 1m11s
CI / quality (pull_request) Successful in 1m14s
CI / typecheck (pull_request) Successful in 1m27s
CI / security (pull_request) Successful in 1m38s
CI / benchmark-publish (pull_request) Has been skipped
CI / e2e_tests (pull_request) Successful in 4m17s
CI / integration_tests (pull_request) Successful in 5m49s
CI / unit_tests (pull_request) Successful in 6m33s
CI / docker (pull_request) Successful in 1m34s
CI / coverage (pull_request) Successful in 10m33s
CI / push-validation (push) Successful in 26s
CI / helm (push) Successful in 30s
CI / lint (push) Successful in 59s
CI / quality (push) Successful in 1m11s
CI / typecheck (push) Successful in 1m30s
CI / security (push) Successful in 1m32s
CI / build (push) Successful in 1m30s
CI / status-check (pull_request) Successful in 5s
CI / benchmark-regression (push) Has been skipped
CI / benchmark-publish (push) Has started running
CI / integration_tests (push) Successful in 4m12s
CI / e2e_tests (push) Successful in 4m17s
CI / unit_tests (push) Successful in 8m8s
CI / docker (push) Successful in 1m31s
CI / coverage (push) Successful in 12m15s
CI / status-check (push) Successful in 2s
CI / benchmark-regression (pull_request) Successful in 1h1m55s
ISSUES CLOSED: #9156 |
||
|
|
48dd67eb84 |
test: add TDD bug-capture test for #991 — AuditService TOCTOU race
CI / benchmark-publish (pull_request) Has been skipped
CI / push-validation (pull_request) Successful in 23s
CI / helm (pull_request) Successful in 31s
CI / build (pull_request) Successful in 1m5s
CI / lint (pull_request) Successful in 1m27s
CI / quality (pull_request) Successful in 1m29s
CI / typecheck (pull_request) Successful in 1m32s
CI / security (pull_request) Successful in 1m32s
CI / e2e_tests (pull_request) Successful in 4m56s
CI / integration_tests (pull_request) Successful in 6m29s
CI / unit_tests (pull_request) Successful in 8m32s
CI / docker (pull_request) Successful in 1m33s
CI / coverage (pull_request) Successful in 11m7s
CI / status-check (pull_request) Successful in 4s
CI / helm (push) Successful in 28s
CI / build (push) Successful in 53s
CI / lint (push) Successful in 1m10s
CI / quality (push) Successful in 1m10s
CI / typecheck (push) Successful in 1m19s
CI / security (push) Successful in 1m35s
CI / benchmark-regression (push) Has been skipped
CI / benchmark-publish (push) Has started running
CI / push-validation (push) Successful in 22s
CI / integration_tests (push) Successful in 4m28s
CI / e2e_tests (push) Successful in 5m13s
CI / unit_tests (push) Successful in 5m44s
CI / docker (push) Successful in 1m27s
CI / coverage (push) Successful in 13m15s
CI / status-check (push) Successful in 3s
CI / benchmark-regression (pull_request) Successful in 1h2m50s
Rebase onto latest master to resolve CHANGELOG.md merge conflict.
All test files unchanged from the approved PR commit (
|
||
|
|
263cbfa45f |
ci: re-trigger CI after transient typecheck runner failure
CI / push-validation (pull_request) Successful in 32s
CI / helm (pull_request) Successful in 38s
CI / build (pull_request) Successful in 1m4s
CI / lint (pull_request) Successful in 1m21s
CI / typecheck (pull_request) Successful in 1m29s
CI / quality (pull_request) Successful in 1m36s
CI / security (pull_request) Successful in 1m51s
CI / benchmark-publish (pull_request) Has been skipped
CI / integration_tests (pull_request) Successful in 5m26s
CI / e2e_tests (pull_request) Successful in 5m31s
CI / unit_tests (pull_request) Successful in 9m41s
CI / docker (pull_request) Successful in 1m57s
CI / coverage (pull_request) Successful in 15m46s
CI / status-check (pull_request) Successful in 6s
CI / lint (push) Successful in 1m7s
CI / typecheck (push) Successful in 1m18s
CI / quality (push) Successful in 1m3s
CI / helm (push) Successful in 25s
CI / build (push) Successful in 54s
CI / push-validation (push) Successful in 42s
CI / security (push) Successful in 2m13s
CI / integration_tests (push) Successful in 4m17s
CI / e2e_tests (push) Successful in 4m19s
CI / unit_tests (push) Successful in 6m7s
CI / docker (push) Successful in 1m38s
CI / coverage (push) Successful in 15m8s
CI / status-check (push) Successful in 3s
CI / benchmark-regression (pull_request) Successful in 1h2m0s
CI / benchmark-regression (push) Has been skipped
CI / benchmark-publish (push) Successful in 1h37m18s
The previous CI run failed with a 5-second typecheck job failure, indicating a transient runner issue rather than a code problem. Pyright reports 0 errors locally (only checks src/, not features/). All quality gates pass: lint, typecheck, unit_tests. |
||
|
|
ef5b8bf986 |
test(agents/graphs/auto_debug): add expected-fail test for _analyze_error in-place state mutation
Added a TDD-style test for issue #10494 by introducing a new features/tdd_auto_debug_analyze_error_mutation.feature with a scenario tagged @tdd_issue @tdd_issue_10494 @tdd_expected_fail, and implemented Behave steps in features/steps/tdd_auto_debug_analyze_error_mutation_steps.py. The test captures the bug that _analyze_error mutates the state in-place and returns the full state object instead of a dict of updates, violating the LangGraph node contract. The @tdd_expected_fail tag inverts the test outcome so CI remains green while the bug exists. ISSUES CLOSED: #10494 |
||
|
|
a47e88016f |
fix(agents): add PR diff and file list permissions to implementation-worker
CI / benchmark-publish (pull_request) Has been skipped
CI / push-validation (pull_request) Successful in 47s
CI / helm (pull_request) Successful in 57s
CI / build (pull_request) Successful in 1m42s
CI / lint (pull_request) Successful in 2m11s
CI / quality (pull_request) Successful in 2m25s
CI / typecheck (pull_request) Successful in 2m30s
CI / security (pull_request) Successful in 2m30s
CI / e2e_tests (pull_request) Successful in 6m23s
CI / integration_tests (pull_request) Successful in 7m38s
CI / unit_tests (pull_request) Successful in 10m5s
CI / docker (pull_request) Successful in 1m35s
CI / coverage (pull_request) Successful in 14m40s
CI / benchmark-regression (push) Has been skipped
CI / status-check (pull_request) Successful in 3s
CI / helm (push) Successful in 31s
CI / benchmark-publish (push) Has started running
CI / build (push) Successful in 53s
CI / lint (push) Successful in 1m11s
CI / typecheck (push) Successful in 1m21s
CI / push-validation (push) Successful in 35s
CI / quality (push) Successful in 1m21s
CI / security (push) Successful in 1m31s
CI / e2e_tests (push) Successful in 4m7s
CI / integration_tests (push) Successful in 6m11s
CI / unit_tests (push) Successful in 6m37s
CI / docker (push) Successful in 1m42s
CI / coverage (push) Successful in 15m5s
CI / status-check (push) Waiting to run
CI / benchmark-regression (pull_request) Successful in 59m41s
The implementation-worker has a PR fix mode that needs to read PR changes to understand what is failing. However, it lacked forgejo_list_pull_request_files and forgejo_get_pull_request_diff permissions, forcing it to clone the entire repository just to inspect what files changed. The pr-reviewer agent already has both permissions. This change aligns the implementation-worker permissions with its actual usage patterns and reduces unnecessary full-repo clones in PR fix mode. Also adds curl, printenv, and echo bash permissions that were inadvertently omitted from the permission block. These are needed for the agent to make Forgejo API calls, check environment variables, and perform basic shell operations. ISSUES CLOSED: #8175 |
||
|
|
49ecf7ff8f |
fix(agents): add PR diff and file list permissions to implementation-worker
The implementation-worker has a PR fix mode that needs to read PR changes to understand what is failing. However, it lacked forgejo_list_pull_request_files and forgejo_get_pull_request_diff permissions, forcing it to clone the entire repository just to inspect what files changed. The pr-reviewer agent already has both permissions. This change aligns the implementation-worker permissions with its actual usage patterns and reduces unnecessary full-repo clones in PR fix mode. Also adds curl, printenv, and echo bash permissions that were inadvertently omitted from the permission block. These are needed for the agent to make Forgejo API calls, check environment variables, and perform basic shell operations. ISSUES CLOSED: #8175 |
||
|
|
1732436edb |
fix(agents): add PR diff and file list permissions to implementation-worker
The implementation-worker has a PR fix mode that needs to read PR changes to understand what is failing. However, it lacked forgejo_list_pull_request_files and forgejo_get_pull_request_diff permissions, forcing it to clone the entire repository just to inspect what files changed. The pr-reviewer agent already has both permissions. This change aligns the implementation-worker permissions with its actual usage patterns and reduces unnecessary full-repo clones in PR fix mode. Also adds curl, printenv, and echo bash permissions that were inadvertently omitted from the permission block restructuring. These are needed for the agent to make Forgejo API calls, check environment variables, and perform basic shell operations. ISSUES CLOSED: #8175 |
||
|
|
f7deab5147 |
chore(agents): add concrete milestone API example and ISSUES CLOSED footer to agent-evolution-worker
CI / push-validation (pull_request) Successful in 38s
CI / helm (pull_request) Successful in 43s
CI / lint (pull_request) Successful in 1m14s
CI / build (pull_request) Successful in 58s
CI / benchmark-publish (pull_request) Has been skipped
CI / quality (pull_request) Successful in 1m54s
CI / typecheck (pull_request) Successful in 2m2s
CI / security (pull_request) Successful in 2m3s
CI / e2e_tests (pull_request) Successful in 6m5s
CI / integration_tests (pull_request) Successful in 6m49s
CI / unit_tests (pull_request) Successful in 9m24s
CI / docker (pull_request) Successful in 1m33s
CI / coverage (pull_request) Successful in 11m49s
CI / benchmark-regression (push) Has been skipped
CI / status-check (pull_request) Successful in 3s
CI / build (push) Successful in 53s
CI / lint (push) Successful in 1m4s
CI / push-validation (push) Successful in 33s
CI / helm (push) Successful in 39s
CI / typecheck (push) Successful in 1m25s
CI / quality (push) Successful in 1m25s
CI / security (push) Successful in 1m32s
CI / e2e_tests (push) Successful in 3m46s
CI / integration_tests (push) Successful in 4m20s
CI / unit_tests (push) Successful in 6m9s
CI / docker (push) Successful in 1m31s
CI / coverage (push) Successful in 11m43s
CI / status-check (push) Successful in 4s
CI / benchmark-publish (push) Has started running
CI / benchmark-regression (pull_request) Successful in 1h2m2s
Added a concrete curl example showing how to query the earliest open milestone via the Forgejo API at PR creation time, and added the ISSUES CLOSED footer requirement to the PR compliance checklist in agent-evolution-worker.md. Also updated CHANGELOG.md to reflect these additions. ISSUES CLOSED: #8370 |
||
|
|
d17d4eebb5 |
chore(agents): fix CHANGELOG.md stale milestone reference in agent-evolution-worker entry
Updated the CHANGELOG.md [Unreleased] > Changed entry for #8370 to accurately reflect the actual implementation: dynamic earliest-open-milestone assignment via Forgejo API (not hardcoded v3.2.0 ID: 105), and Type/Task label (not Type/Chore which does not exist in the org label system). ISSUES CLOSED: #8370 |
||
|
|
c4122f877a |
chore(agents): add CONTRIBUTING.md compliance steps to agent-evolution-worker
ISSUES CLOSED: #8370 |
||
|
|
92c3bd8732 |
fix(tests): update resource_dag.robot SQLite pool and cycle detection types
CI / benchmark-publish (pull_request) Has been skipped
CI / push-validation (pull_request) Successful in 37s
CI / helm (pull_request) Successful in 38s
CI / lint (pull_request) Successful in 1m35s
CI / build (pull_request) Successful in 59s
CI / typecheck (pull_request) Successful in 1m50s
CI / security (pull_request) Successful in 1m48s
CI / quality (pull_request) Successful in 1m42s
CI / e2e_tests (pull_request) Successful in 4m42s
CI / integration_tests (pull_request) Successful in 6m36s
CI / unit_tests (pull_request) Successful in 8m53s
CI / docker (pull_request) Successful in 1m45s
CI / coverage (pull_request) Successful in 12m51s
CI / benchmark-regression (push) Has been skipped
CI / status-check (pull_request) Successful in 3s
CI / benchmark-publish (push) Has started running
CI / helm (push) Successful in 36s
CI / lint (push) Successful in 55s
CI / build (push) Successful in 56s
CI / quality (push) Successful in 1m28s
CI / typecheck (push) Successful in 1m29s
CI / security (push) Successful in 1m35s
CI / push-validation (push) Successful in 22s
CI / e2e_tests (push) Successful in 4m33s
CI / integration_tests (push) Successful in 4m38s
CI / unit_tests (push) Successful in 6m41s
CI / docker (push) Successful in 1m34s
CI / coverage (push) Successful in 10m47s
CI / status-check (push) Successful in 3s
CI / benchmark-regression (pull_request) Successful in 1h2m16s
Replaced direct create_engine usage with StaticPool-based connection in resource_dag.robot to prevent SQLite connection sharing issues in tests. Updated cycle detection test to use distinct resource types (git-checkout and fs-directory) instead of the same type for both resources, improving test coverage of cross-type cycle detection. Split from PR #1204 per reviewer request for atomic commits. ISSUES CLOSED: #1226 |
||
|
|
60c50d3c9f |
Merge pull request 'fix(plan): implement error recovery for execute phase per spec §35958 and §18323' (#10844) from bugfix/reexecute-errored-plan into master
CI / security (push) Successful in 1m12s
CI / build (push) Successful in 40s
CI / benchmark-regression (push) Has been skipped
CI / push-validation (push) Successful in 25s
CI / e2e_tests (push) Successful in 4m22s
CI / benchmark-publish (push) Failing after 1h2m57s
CI / helm (push) Successful in 41s
CI / lint (push) Successful in 1m19s
CI / quality (push) Successful in 1m20s
CI / typecheck (push) Successful in 1m27s
CI / integration_tests (push) Successful in 4m20s
CI / unit_tests (push) Successful in 6m13s
CI / docker (push) Successful in 1m32s
CI / coverage (push) Successful in 11m34s
CI / status-check (push) Successful in 3s
Reviewed-on: #10844 Reviewed-by: Luis Mendes <luis.mendes@cleverthis.com> |
||
|
|
12fc9e089f |
fix(plan): implement error recovery for execute phase per spec §35958 and §18323
CI / lint (pull_request) Successful in 1m8s
CI / quality (pull_request) Successful in 1m7s
CI / typecheck (pull_request) Successful in 1m31s
CI / security (pull_request) Successful in 1m39s
CI / helm (pull_request) Successful in 28s
CI / push-validation (pull_request) Successful in 24s
CI / build (pull_request) Successful in 36s
CI / integration_tests (pull_request) Successful in 4m21s
CI / unit_tests (pull_request) Successful in 4m45s
CI / e2e_tests (pull_request) Successful in 4m8s
CI / docker (pull_request) Successful in 1m29s
CI / benchmark-publish (pull_request) Has been skipped
CI / coverage (pull_request) Successful in 11m24s
CI / status-check (pull_request) Successful in 4s
CI / benchmark-regression (pull_request) Successful in 1h10m52s
Two recovery paths for execute/errored plans using the domain model's classify_error() for canonical error classification: 1. Transient failures (§28530/§35958): rate limit, timeout, connection errors — reset to execute/queued and re-execute with the same strategy. Preserves strategy_decisions_json for decision hierarchy reconstruction. 2. Non-transient failures (§18323-18329): strategy constraint, authentication, unknown — delegate to service.try_auto_revert_from_execute() which enforces MAX_REVERSIONS loop guard, increments reversion_count, records a reversion decision, and respects the delete_content automation threshold. Error findings are redacted via redact_error_details() and stored as JSON for the strategy actor (§18329). Error classification uses the domain model's classify_error() and ErrorCategory enum — single source of truth, no parallel frozenset. AuthenticationError correctly classified as non-transient per domain model. ISSUES CLOSED: #10843 |
||
|
|
43fdc31624 |
chore(agents): improve ca-continuous-pr-reviewer — skip PRs with unchanged HEAD since last review
CI / lint (push) Successful in 1m12s
CI / helm (push) Successful in 33s
CI / push-validation (push) Successful in 35s
CI / quality (push) Successful in 1m21s
CI / build (push) Successful in 52s
CI / benchmark-regression (push) Has been skipped
CI / typecheck (push) Successful in 1m33s
CI / security (push) Successful in 1m43s
CI / benchmark-publish (push) Has started running
CI / integration_tests (push) Successful in 5m9s
CI / e2e_tests (push) Successful in 5m3s
CI / unit_tests (push) Successful in 6m9s
CI / docker (push) Successful in 1m51s
CI / coverage (push) Successful in 11m53s
CI / status-check (push) Successful in 4s
|