All notable changes to this project will be documented in this file.
The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
- Fixed AutoDebugAgent LangGraph node contract violations (#10496): `_analyze_error` now
returns a proper state update dict (`{"messages": state.get("messages", []) + [new_message]}`)
instead of a mutated full state, preventing duplicate message accumulation when LangGraph
merges state across nodes. Removes `@tdd_expected_fail` from the TDD test now that the
bug is fixed. Also fixes `typer.Exit` propagation in actor CLI commands (`actor_run.py`,
`actor.py`) so exit codes are correctly preserved through exception handler chains, and
adds `typer.Exit` to Behave step exception handlers so test scenarios no longer error
on `typer.Exit` instead of cleanly capturing the exit code. Adds BDD node-contract
tests for `_generate_fix`, `_validate_fix`, and `_finalize`.
Changed `wf10_batch.robot` to be less likely to create files, and
`plan_generation_graph.robot` to give more test answers.
## [Unreleased]
- **feat(a2a): A2A stdio transport for local-mode subprocess communication (#691):** Implemented ``A2aStdioTransport`` class providing JSON-RPC 2.0 message framing over stdin/stdout for communicating with an agent subprocess in local mode. Features include process lifecycle management (``connect``, ``disconnect`` with graceful shutdown via wait-then-terminate-then-kill), request/response serialization and deserialization, type-safe path resolution (Python module paths use ``python -m``, ``.py`` files execute directly, executables run without interpreter prefix), and comprehensive error handling for subprocess lifecycle events. Added full BDD test suite covering all code paths in ``features/a2a_stdio_transport.feature`` with mock-based step definitions.
- **fix(a2a): .py path routing in A2aStdioTransport (#691):** Corrected ``connect()`` to use direct script execution (``[sys.executable, agent_path]``) for literal ``.py`` file paths instead of routing through ``python -m``, which expects a module name. Module paths (``cleveragents.*``) continue to use ``-m``; bare executables remain unchanged.
- **feat(resources): resource type extension interface** (#9998): New `cleveragents.resources` package providing the stable public API third-party developers use to add custom resource types without modifying core code. Includes `ResourceType` ABC with five abstract lifecycle methods (`provision`, `deprovision`, `status`, `validate_config`, `to_dict`), a `ResourceConfig` Pydantic model (`name`, `resource_type`, `properties`), a `ResourceStatus` StrEnum (`PENDING`, `ACTIVE`, `FAILED`, `DEPROVISIONED`), and registry functions `register_resource_type` / `get_resource_type` / `list_resource_types`. Custom types are registered under namespaced names (e.g. `myorg/database`); registration raises `TypeError` for non-`ResourceType` subclasses and `ValueError` for duplicate names. 25 BDD scenarios in `features/resource_type_extension_interface.feature` cover enum values, config instantiation, ABC enforcement, all lifecycle method return types, and registry CRUD + error paths.
- **refactor(a2a): route CLI→Application communication through A2A boundary** (Refs #9962, #4253): Introduced `cleveragents.shared.output_format` as a layer-neutral serialiser (`format_data` supporting `json`/`yaml`/`plain`/`table`) with no dependency on `cleveragents.cli.*`, eliminating a reverse dependency from `PlanApplyService.artifacts()` on the CLI presentation layer. The shared formatter returns raw payloads with no CLI envelope wrapping (`{"data": ..., "command": ..., "status": ...}`); callers that previously parsed `parsed["data"]` from `apply_service.artifacts(fmt="json")` output now read fields at the top level. Updated `features/steps/plan_diff_artifacts_steps.py` (`step_artifacts_json_validation`, `step_artifacts_json_apply_summary`) to drop the stale envelope unwrap that caused `KeyError: 'data'` under the new boundary. Removed stale `@tdd_expected_fail` tag from `WF02 Mocked Generation Produces Test Artifacts Only` in `robot/wf02_test_generation_integration.robot` — the scenario now passes naturally through the A2A facade dispatch path (`_cleveragents/plan/artifacts`) introduced by this refactor.
- **fix(test): move advanced context strategy test doubles to features/mocks** (#7574): Extracted `FakeEmbeddings`, `RelevanceScoringStrategy`, `AdaptiveContextSelector`, `ContextFusionStrategy`, and `_pack_budget` from `features/steps/advanced_context_strategies_steps.py` into a new `features/mocks/advanced_context_strategies_mocks.py` file per CONTRIBUTING.md mock-placement rules. Updated the Robot Framework helper `robot/helper_advanced_context_strategies.py` to import directly from `features.mocks` rather than manipulating `sys.path` to reach the Behave steps file. Added `None` guard in `step_assemble_context_query` before calling `selected.assemble()`, and added explicit `ValueError` for unknown strategy types in both `step_load_yaml_strategy` and `load_strategy_from_yaml_impl`.
- **fix(a2a): regression tests for stale cleveragents.acp removal** (#5566): Added two Behave BDD scenarios verifying that `cleveragents.acp` is not importable (raises `ImportError`) and that `src/cleveragents/acp/` does not exist in the source tree. These guard against regression of the `__pycache__`-based import that allowed the removed ACP module to still be loaded from bytecode after the v3.6.0 rename to `a2a`.
- **Virtual Resource Type Base Class** (#8610): Implemented `VirtualResource` base class with two example concrete implementations (`MetricResource`, `APIEndpointResource`) for abstract/computed resources that are derived rather than mapped to physical files. Virtual resources are computed on demand via a `compute_fn` callable. Includes Behave BDD scenarios in `features/resource_virtual_types.feature` exercising construction, computation, name validation, kwargs passthrough, exception handling, string representation, and subclassing. Resource names are validated against `^[a-zA-Z][a-zA-Z0-9_-]*$` (must start with a letter; alphanumeric, hyphens, and underscores otherwise).
- **test(e2e): restore complete M2 acceptance test** (#11191): Restored the truncated M2 full actor compiler and LLM integration e2e acceptance test to its complete 10-step form. Added dynamic LLM provider selection via `Resolve LLM Actor` (falls back to Anthropic when OpenAI is unavailable or quota-exhausted), replacing hardcoded `gpt-4` / `openai/gpt-4` references in the actor config and action YAML. Added explicit return-code validation (`Should Be Equal As Integers ${r_actor.rc} 0`) for the actor registration step.
- **docs(a2a): ACP to A2A migration guide** (#10230): Added migration guide documenting how to upgrade from the ACP module to the A2A module introduced in v3.6.0, including symbol renames, field renames, operation-name mappings, and YAML configuration updates.
- **feat(plans): parallel subplan execution scheduler** (#9555): Added `ParallelSubplanScheduler` with configurable `max_parallel` concurrency control, dependency-ordered execution (`SEQUENTIAL`, `PARALLEL`, `DEPENDENCY_ORDERED` modes), fail-fast mode, per-subplan timeout enforcement, retry support, and pluggable merge strategies. The scheduler delegates execution to `SubplanExecutionService` and exposes `schedule()`, `get_queue_status()`, `get_available_slots()`, and `can_accept_more()` APIs. Includes comprehensive BDD test coverage in `features/parallel_subplan_scheduler.feature`.
- **Plan Prompt JSON Timing Field** (#9353): `agents plan prompt --format json` now
includes `timing.started` as an ISO 8601 UTC timestamp in the JSON envelope,
matching the spec (§CLI Commands — `agents plan prompt`). Extended
`cleveragents.cli.formatting.format_output` (and `_build_envelope`) with an
optional `started_at: datetime` parameter; when provided, the envelope's
`timing` dict includes a `started` field alongside `duration_ms`. Refactored
`prompt_plan_cmd` to delegate envelope construction to `format_output` so the
envelope keys (`command`, `status`, `data`, `timing.started`, `messages`) are
populated correctly at the JSON root rather than nested under a synthetic
inner `data` field.
- **fix(plan): NamespacedName digit-start validation** (#2145, #2147): `NamespacedName` field validators now reject `namespace` and `name` components whose first character is a digit, raising `pydantic.ValidationError` with message `"must start with a letter"`. BDD constructor scenarios updated to use the `"a Pydantic ValidationError should be raised"` step so the assertion correctly matches the exception type raised by Pydantic model construction.
- **fix(cli/plan): plan correct JSON output envelope fix and BDD test coverage** (#8584 / PR #8662): Restructured `agents plan correct --format json` output to nest correction fields under `data.correction` (e.g., `data.correction.mode`) and populate the spec-required CLI envelope with `command="plan correct"`, `status`, `exit_code`, `timing`, and `messages` fields. Added three BDD scenarios in `features/tdd_plan_correct_json_output.feature` validating the envelope structure for both revert and append modes.
- **fix(cli): add --url flag to resource add for git resource type** (#6322): Added support for the `--url` flag on `agents resource add git` command, allowing users to specify a remote URL for git resources. The flag is validated to only apply to git resource types. Includes Behave BDD tests in `features/resource_cli_git_url_flag.feature` and Robot Framework integration tests verifying correct URL validation and CLI behavior.
- **Session create JSON envelope** (#6441): Fixed `agents session create --format json` returning a flat `data` dict instead of the spec-required nested structure with `data.session`, `data.settings`, and `data.actor_details` sub-objects. The `command` field is now populated correctly. Extended JSON envelope coverage to `agents session list`, `show`, `delete --format json`, `export --output-format json`, and `import --format json` so all session commands emit a structured `messages[].text` field (`"0 sessions listed"`, `"Session details loaded"`, `"Session deleted"`, `"Export completed"`, `"Import completed"`).
@@ -165,8 +135,6 @@ ensuring data is stored with proper parameter values.
- **fix(tui): rename ActorSelectionOverlay._render to _refresh_display (issue #11039)** — `ActorSelectionOverlay._render()` shadows Textual's `Widget._render()` which must return a `Strip`. In textual >=1.0, layout calls `get_content_height()` `self._render()` gets `None` `AttributeError: 'NoneType' object has no attribute 'get_height'`. Renamed the method to `_refresh_display()` and updated all four internal call sites (`show()`, `move_up()`, `move_down()`, `set_search()`) to use the new name.
- feat(cli): implement context show and context clear CLI commands for ACMS (#9586): Added `context show <view>` to display assembled context with per-tier budget utilization summary (hot/warm/cold) and `context clear` with --path, --tag, and --tier filtering plus confirmation prompt with --yes bypass.
- **Structural Component Output Validation** (#8164): Replaces exact character matching with structural component checking for output validation. Implements three validators covering plan tree output, decision CLI dicts, and structured session snapshots. The `validate_plan_tree` function validates node dicts for required keys (`decision_id`, `type`, `sequence`, `question`, `children`), ULID format, correct types, and sibling ordering. The `validate_decision_dict` function validates decision CLI output against the `Decision.as_cli_dict()` schema with field presence, type, ULID pattern, confidence range [0..1], and boolean field checks. The `validate_structured_output` function validates the StructuredOutput envelope for `command`, `session_id` (ULID), status membership, `exit_code`, and elements integrity. A unified dispatcher (`validate_structured_component_output`) enables routing by target_type. BDD test coverage added in `features/structural_validation.feature`. [Epic #8137](https://git.cleverthis.com/cleveragents/cleveragents-core/issues/8137)
- **Fixed `agents actor add --config` crash with nested `actors:` map and `config.actor` combined shorthand** (#11189): The
CLI command `agents actor add --config` now correctly parses spec-canonical YAML using the
@@ -185,26 +153,6 @@ ensuring data is stored with proper parameter values.
the workflow. Step numbering in both procedures has been re-numbered to
accommodate the new step.
- **WF18 container clone e2e test: add `tdd_expected_fail` tag and full test body** (#10815):
The `wf18_container_clone.robot` E2E test was missing its test body — after
`Skip If No LLM Keys` the test case had no steps, but when LLM keys are
present the container clone workflow caused the CLI to be killed by SIGKILL
(rc=-9, OOM) in the memory-constrained CI environment. Added `tdd_expected_fail`
(with `tdd_issue_10815`) so CI correctly inverts the OOM failure to a pass until
the container execution environment is tuned for CI memory limits. Also added the
full WF18 test body covering all acceptance criteria: container-instance resource
registration with `--clone-into`, two-step project creation and resource linking,
action creation with trusted automation profile, and the complete plan lifecycle
(use → execute → apply) with a `WF18 Test Teardown` keyword for diagnostic
for applying strategies to resolve conflicts, comprehensive BDD test suite
(8 scenarios across all three strategies), and Robot Framework integration tests
verifying runtime behavior against live Python modules.
### Fixed
- **fileConfig error handling in alembic env.py** (#7874): Wrapped the `fileConfig()`
@@ -279,9 +186,7 @@ ensuring data is stored with proper parameter values.
### Added
- **A2A module rename BDD test suite** (#8615): Comprehensive Behave tests validating that the ACP→A2A module rename is complete — verifying all 22 A2A symbols are properly exported, no legacy ACP references remain in `.py` files under `cleveragents.a2a/`, and the module docstring uses current A2A naming. The step definitions include self-contained symbol lookups to avoid cross-scenario dependency failures.
- **ContextStrategy protocol and plugin registration system** (#8616): Implemented the domain-model `ContextStrategy` Protocol with supporting value objects (BackendSet, PlanContext, StrategyCapabilities, StrategyConfig, ContextStrategyResult, StrategyRegistryEntry). Six built-in strategies: SimpleKeywordStrategy (text search, quality 0.3), SemanticEmbeddingStrategy (vector similarity, quality 0.6), BreadthDepthNavigatorStrategy (graph-aware traversal, quality 0.85), ARCEStrategy (multi-modal pipeline, quality 0.95), TemporalArchaeologyStrategy (historical pattern discovery, quality 0.5), and PlanDecisionContextStrategy (parent/ancestor plan context, quality 0.7). The StrategyRegistry class provides registration, unregistration, query, configuration updates with Pydantic-validated fields, plugin discovery via register_from_module() with module-prefix allowlist security, per-strategy enable/disable toggling, deterministic fragment ordering, MappingProxyType-immutable config fields, thread-safe concurrent operations, and validation warnings for missing resource types or capabilities. Comprehensive BDD test coverage in `features/context_strategies.feature` (batch 1) and `features/context_strategy_registry.feature` (registry protocol conformance, registration, query, configuration, plugin discovery, thread safety, boundary tests). Based on docs/specification.md sections 25162–25233, 28682–28708.
- **A2A module rename BDD test suite** (#8615): Comprehensive Behave tests validating that the ACP→A2A module rename is complete — verifying all 22 A2A symbols are properly exported, no legacy ACP references remain in `.py` files under `cleveragents.a2a/`, and the module docstring uses current A2A naming. The step definitions include self-contained symbol lookups to avoid cross-scenario dependency failures.
- Fixed `ReactiveEventBus.emit()` exception handler to log the full exception
message (`str(exc)`) and enable traceback forwarding (`exc_info=True`).
@@ -291,6 +196,8 @@ ensuring data is stored with proper parameter values.
traceback in the structlog warning entry. Removed `@tdd_expected_fail` tag
from the TDD test so both scenarios run as normal regression guards. (#988)
### Added
- **`pr-review-worker` review-started notification** (#11028): The `first_review`
and `re_review` modes now post a "review started" notification comment to the
PR at the beginning of the review, giving PR authors immediate visibility
@@ -325,12 +232,7 @@ ensuring data is stored with proper parameter values.
on a completed plan would silently destroy the ``cleveragents/plan-<id>`` git
worktree branch, causing ``plan apply`` to merge zero artifacts. The guard
preserves the branch per spec (§sandbox.cleanup defaults to ``on_apply``).
- **Race condition in ``McpClient.start()`` allows concurrent double initialisation** (#10438):
Added ``_state == McpClientState.STARTING`` check inside the ``threading.RLock`` in
``start()`` so that concurrent callers see the in-progress state and return immediately,
preventing double initialisation of the MCP server connection, resource leaks, and state
corruption. TDD regression test added with BDD scenarios covering concurrent and sequential
start paths.
- **Global CLI options ``--data-dir``, ``--config-path``, and ``-v`` now work correctly**
(#6785): These spec-required flags were absent from ``main_callback()`` in
``src/cleveragents/cli/main.py``, causing any invocation with these flags to crash
@@ -433,7 +335,7 @@ ensuring data is stored with proper parameter values.
untyped `config` dict), the old code always returned an empty string, causing
cross-actor cycle detection to silently fail and leaving the system vulnerable to
infinite recursion at runtime. Added Behave regression tests
(`features/actor_subgraph_cycle_detection.feature`) and a Robot Framework
(`features/actor_subgraph_cycle_detection.feature`) and a Robot Framework
integration test (`robot/actor_compiler.robot`) to prevent regressions.
- **ActorLoader.list_actors TOCTOU race condition** (#8588): Moved the namespace
@@ -466,28 +368,6 @@ ensuring data is stored with proper parameter values.
`hot_context_hash`, `hot_context_ref`, `actor_state_ref`, and `relevant_resources`
are all populated for Strategize-phase decisions.
- **Plan tree JSON output missing `decision_id` field** (#9096): The `step_tree_json_valid`
BDD step was asserting a raw list from `format_output`, but the function wraps all
machine-readable output in a spec-required envelope dict (`{"data": [...]}`). Updated
the assertion to validate envelope structure and removed `@tdd_expected_fail` from the
`@tdd_issue_4254` scenario so it runs as a permanent regression guard. The code producing
`decision_id` in tree nodes was already correct; only the test assertion needed fixing.
### Documentation
- **Spec clarifications: layer boundary DI exception, ULID scope, TUI/ACMS gaps** (#10451): Added targeted clarifications to `docs/specification.md` including: the sole permitted location (`application/container.py`) where application layer may reference infrastructure concrete types; distinction between domain entity IDs (must be ULID) and ephemeral internal implementation IDs; per-stage protocol contracts, storage tier definitions, budget enforcement protocol, and output format for ACMS pipeline stages; and public interface definitions with verifiable checks for 8 TUI components.
### Security
- **PyYAML dependency pinned to secure version** (#9055): Added an explicit
`pyyaml>=6.0.3` constraint to `pyproject.toml` to address CVE-2017-18342
and related advisories. PyYAML 6.x deprecated the unsafe default Loader, but
downstream consumers could still invoke `yaml.load()` without an explicit
safe Loader. A codebase-wide audit confirmed all YAML loading uses
Added BDD regression scenarios in `features/pyyaml_security.feature` to
verify the version constraint and safe-load enforcement are maintained.
### Changed
- Fixed stale `AUTO-BUG-POOL` tracking prefix references in automation-tracking.md documentation and agent-system-specification.md spec document, replaced with correct `AUTO-BUG-SUP` prefix used by the bug-hunt-pool-supervisor agent (#7875).
@@ -529,15 +409,6 @@ ensuring data is stored with proper parameter values.
versions (<3.13.4) cannot be installed even if upstream transitive dependencies have loose
version constraints.
### Changed
- **Timeline dashboard updated with 2026-04-18 progress snapshot** (#10288): Added schedule adherence tables and daily milestone snapshot for April 18, covering M3-M10 status including overdue milestones (M3-M7) and in-progress milestones (M8-M10). Risk assessment shows M6 (v3.5.0) highest risk with 1,130 open issues at 18.1% completion.
- **LSP transport header injection fix** (#10608 / #7112): The `_read_one_message()` method in
`src/cleveragents/lsp/transport.py` now uses `errors="strict"` instead of `errors="replace"` for
ID, type, question, and chosen option. Corrected nodes are visually marked via the
`is_superseded` flag. The command handles empty decision trees gracefully and includes
ULID validation and proper error handling consistent with other plan commands.
- `agents actor context clear` command to reset actor message history and state while preserving the underlying context directory via `ContextManager`
- `agents actor context clear` command to reset actor message history and
state while preserving the underlying context directory via `ContextManager`
(#6370).
- **Quick Start Guide** (PR #9245): Added `docs/quickstart.md` with an end-to-end quick start guide covering prerequisites, installation, project creation, resource registration, plan/apply workflow, and troubleshooting. Updated `mkdocs.yml` navigation to include the Quick Start page.
- **container-instance --clone-into and devcontainer-instance sandbox strategy** (#7555):
Added `--clone-into` CLI argument to `container-instance` resource type for cloning
a git repository into a running container. Implemented `CloneIntoHandler` with
`clone_repo_into_container()` and `validate_clone_into_url()` helpers. Updated
`devcontainer-instance` to use `snapshot` sandbox strategy (was `none`) to enable
safe plan execution inside containers. Added `container-mount`, `container-exec-env`,
and `container-port` as child types of `devcontainer-instance`. Renamed
`ContainerLifecycleState.DETECTED` to `DISCOVERED` (value: `"discovered"`) to align
with specification terminology.
- **Plan checkpoint management CLI commands** (#8683): Added `agents plan checkpoint-list <plan-id>` and `agents plan checkpoint-delete <checkpoint-id>` commands. Listing output now highlights checkpoint ID, type, created timestamp, reason, phase, and decision linkage with a concise field summary footer across rich/table/json/yaml formats. Deletion supports batch IDs, interactive confirmation (skip with `--yes`), and structured JSON/YAML responses for automation-friendly scripting.
- **Invariant Remove CLI Command** (#8530): Implemented `agents invariant remove <id>` command that soft-deletes an invariant by ID. The command displays a confirmation prompt before removal (bypassable with `--yes`/`-y`), outputs the removed invariant ID on success, and shows a clear error message when the invariant ID does not exist. Supports `--format` flag for JSON and YAML output. Full BDD test coverage and Robot Framework integration tests included.
- **TDD: plan tree does not visually mark corrected nodes** (#8576): Added a failing
BDD scenario proving that corrected nodes (decisions with `is_correction=True`) are
not visually distinguished in the `agents plan tree` output. The scenario is tagged
`@tdd_expected_fail` and will pass (by inversion) until the underlying gap described
in Spec Requirement #7 is fixed.
- **Invariant Remove CLI Command** (#8530): Implemented `agents invariant remove <id>` command that soft-deletes an invariant by ID. The command displays a confirmation prompt before removal (bypassable with `--yes`/`-y`), outputs the removed invariant ID on success, and shows a clear error message when the invariant ID does not exist. Supports `--format` flag for JSON and YAML output. Full BDD test coverage and Robot Framework integration tests included.
- **Semgrep guard for broad exception suppression** (#9185): Added two new Semgrep rules
(`python-no-suppressed-exception` and `python-no-suppress-exception`) to `.semgrep.yml`
to automate enforcement of the CONTRIBUTING.md guideline against suppressing `Exception`
or `BaseException`. Rules detect `except Exception`, `except BaseException`,
`contextlib.suppress(Exception)`, and `contextlib.suppress(BaseException)` patterns.
Supports an opt-out escape hatch via Semgrep's native `# nosemgrep` comment combined with
`# error-propagation: allow` audit annotation. Integrated Semgrep into the `nox -s lint`
session in audit mode (with `success_codes=[0,1]`) during phased rollout to prevent CI
failures from ~337 existing violations while they are triaged. Added pre-commit hook for
local enforcement and comprehensive BDD test coverage across all rule patterns and escape
hatch scenarios. Closes #9103.
- **TDD: MCPToolAdapter.infer_resource_slots() TypeError with null properties** (#10470):
Added a TDD issue-capture Behave scenario that reproduces the bug where
`MCPToolAdapter.infer_resource_slots()` raises `TypeError` when the input schema
@@ -800,19 +626,19 @@ back when UnitOfWork transaction rolls back`.
- **Unified provider factory: eliminate divergence between `create_llm()` and `create_ai_provider()`** (#10949):
Introduced `_create_provider_instance()` as the single internal factory so that
both public methods delegate to one place. Creating a new provider now
both public methods delegate to one place. Creating a new provider now
requires changes in exactly one method.
- **Fixed API key regression**: the unified factory now explicitly passes
the validated API key to all LangChain constructors (OpenAI, Anthropic,
Google / Gemini, Azure, Groq, Together, Cohere, and OpenRouter). Users
Google / Gemini, Azure, Groq, Together, Cohere, and OpenRouter). Users
who configure providers via `CLEVERAGENTS_`-prefixed variables are no
longer silently failed when LangChain falls back to raw environment
variable lookup. Pre-validated keys are forwarded through the
variable lookup. Pre-validated keys are forwarded through the
`api_key` kwarg to avoid a second settings lookup in the factory
closure. (Closes #10949)
- **Fixed mock provider accessibility in production**: `ProviderType.MOCK`
is now gated by the `CLEVERAGENTS_ALLOW_MOCK_PROVIDER=true` sentinel
environment variable. Without this flag, both `create_llm()` and
environment variable. Without this flag, both `create_llm()` and
`create_ai_provider()` raise `ValueError` when MOCK is requested,
preventing accidental or malicious use of the fake LLM in production.
`resolve_provider_by_name("mock")` now also respects the guard and
@@ -880,7 +706,7 @@ back when UnitOfWork transaction rolls back`.
`agents actor run` silently returning empty output for v3 `type:llm` actors.
`_build_from_v3()` and `_build()` now synthesise a default single-node
graph route when agents are created without explicit routes, ensuring
`run_single_shot()` can invoke the LLM via `GraphExecutor`. The nested
`run_single_shot()` can invoke the LLM via `GraphExecutor`. The nested
`actors:` map format also translates the v3 `actor: "provider/model"` key
into separate `provider` and `model` keys so the correct LLM provider is
instantiated.
@@ -905,10 +731,10 @@ uko-oo:Class` triple emission in `PythonAnalyzer._extract_class()` so that
- **Actor CLI v3 YAML Schema Support** (#6283): Fixed three components to add
full v3 `ActorConfigSchema` support to the actor CLI registration and
execution paths. `ActorConfiguration.from_blob()` now detects v3 format
execution paths. `ActorConfiguration.from_blob()` now detects v3 format
(top-level `type` key of `llm`/`graph`/`tool`) and correctly extracts
provider, model, and graph descriptors — including `type: tool` actors
without a `model` field. `ActorRegistry.add()` validates against the full
without a `model` field. `ActorRegistry.add()` validates against the full
Pydantic v2 schema, persists `skills`/`lsp`/`description` in the config
blob, and compiles graph actors with proper metadata.
`ReactiveConfigParser._build_from_v3()` now uses correct `source`/`target`
@@ -917,9 +743,9 @@ uko-oo:Class` triple emission in `PythonAnalyzer._extract_class()` so that
integration tests for semantic search, relevance scoring, adaptive selection, and
context fusion strategies. Includes Behave feature file with 30+ scenarios, step
definitions with FakeEmbeddings for deterministic testing, Robot Framework E2E tests
with 20+ test cases, and helper utilities for strategy creation and budget management.
All tests verify strategy selection, token budget handling, result deduplication, YAML
configuration loading, ContextAssembler integration, and error/fallback behavior.
- **TDD Issue-Capture Test Activation** (#7025): Replaced 234 bare `@skip` tags
across 82 Behave feature files with the correct `@tdd_expected_fail@tdd_issue
@@ -1282,8 +1046,8 @@ Documentation Report (Cycle N)` issues every 10 cycles (~3.3 hours). The manager
context during plan execution. Added `context_tier_hydrator.py` that reads files from
linked project resources (via `git ls-files` or `os.walk`) and stores them as
`TieredFragment` objects in the tier service. Hydration runs automatically before context
assembly in `LLMExecuteActor.execute()`. Respects max file size (256KB), total budget
(10MB), binary file exclusion, and `.git`/`node_modules`/`__pycache__` directory
assembly in `LLMExecuteActor.execute()`. Respects max file size (256KB), total budget
(10MB), binary file exclusion, and `.git`/`node_modules`/`__pycache__` directory
skipping. (#1028)
- **Product-Builder Tracking Migration**: `product-builder` now creates individual
@@ -1334,7 +1098,7 @@ iteration` and data corruption under concurrent plan execution. All public
are also protected. The DI container registration as `providers.Singleton`
is now correct and safe.
- **TOCTOU Race Condition in Git Worktree Sandbox** (#7507): Fixed Time-Of-Check-To-Time-Of-Use race condition in `GitWorktreeSandbox.create()` by replacing unsafe mkdtemp+rmdir pattern with persistent parent directory approach. Parent directory is now held throughout operation lifetime and properly cleaned up in all error paths (timeout, CalledProcessError, OSError) and in the cleanup() method, eliminating race window where another process could claim the worktree path. Comprehensive BDD test coverage validates the fix under concurrent execution and confirms proper cleanup behavior.
- **TOCTOU Race Condition in Git Worktree Sandbox** (#7507): Fixed Time-Of-Check-To-Time-Of-Use race condition in `GitWorktreeSandbox.create()` by replacing unsafe mkdtemp+rmdir pattern with persistent parent directory approach. Parent directory is now held throughout operation lifetime and properly cleaned up in all error paths (timeout, CalledProcessError, OSError) and in the cleanup() method, eliminating race window where another process could claim the worktree path. Comprehensive BDD coverage added for all error-path cleanup branches.
In rare cases, you may have specific recovery logic that justifies suppressing a broad exception.
This is permitted **only** when:
1. You have documented recovery logic that handles the exception meaningfully
2. You add the **Semgrep suppression comment**`# nosemgrep: python-no-suppressed-exception` (or `# nosemgrep: python-no-suppress-exception` for contextlib.suppress)
3. You ALSO add the **human-readable annotation**`# error-propagation: allow` on the same line
4. You include an inline comment explaining why the suppression is safe
**Both comments are required together:**
- The `# nosemgrep` comment is the actual suppression mechanism (Semgrep native) that disables the Semgrep rule check
- The `# error-propagation: allow` annotation is required for human auditability and code review clarity
@@ -115,3 +115,4 @@ Below are some specific details of individual PR contributions.
* HAL 9000 has contributed the path containment security hardening fix (PR #7801 / issue #7478): replaced insecure ``str.startswith(root + "/")`` string-prefix path containment checks with semantic ``os.path.relpath`` comparisons in ``tool/path_mapper.py`` (_is_under) and ``application/services/llm_actors.py`` (_write_to_sandbox), eliminating the sibling-directory prefix-collision path traversal bypass vulnerability.
* HAL 9000 has contributed the data-integrity fix for ProjectRepository (#8179): removed unconditional ``session.rollback()`` calls from exception handlers in ``ProjectRepository.create()`` and ``NamespacedProjectRepository.create/update/delete``, delegating transaction rollback to the Unit of Work outer-layer handler where it belongs.
* Jeffrey Phillips Freeman has contributed the `--format`/`-f` flag to `agents session tell` (issue #10466): adds JSON envelope output for machine-readable workflows alongside existing Rich console output, with Behave BDD test coverage verifying all four non-rich format paths (JSON, YAML, plain, table) and the short `-f` flag alias.
* HAL 9000 has contributed the Semgrep guard for broad exception suppression (PR #9185 / issue #9103): added two new Semgrep rules (`python-no-suppressed-exception` and `python-no-suppress-exception`) to automate enforcement of error propagation guidelines, integrated Semgrep into `nox -s lint` in audit mode with migration plan for ~337 existing violations, and comprehensive BDD test coverage across all rule patterns and escape hatch scenarios.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.