1171 Commits

Author	SHA1	Message	Date
HAL9000	4a8ede3fb4	fix(tests): resolve ambiguous Behave step by using context.last_error ... Remove duplicate @then step from uow_coverage_boost_steps.py that conflicted with actor_config_steps.py:168. Both patterns matched 'a ValueError should be raised containing "{...}"' but used different capture-variable names, triggering AmbiguousStep at import time. Update the four When steps to store the caught exception in context.last_error so the existing actor_config_steps assertion handles the Then clause. ISSUES CLOSED: #878	2026-05-29 04:24:27 -04:00
HAL9000	7536830f85	test(postgresql): add BDD coverage for UoW validation, dispose, context manager and is_postgresql ValueError ... Cover previously-uncovered code paths added in the PostgreSQL backend PR: - UnitOfWork argument validation (empty URL, pool_size=0, max_overflow=-1, pool_recycle=-2) - dispose() with active engine (True branch) and without engine (False branch) - __enter__/__exit__ context manager protocol - psycopg2 ImportError path when psycopg2 is unavailable - settings.is_postgresql() except ValueError branch (server_mode + SQLite URL) ISSUES CLOSED: #1118	2026-05-29 03:59:05 -04:00
HAL9000	8dde6c81ef	feat(server): implement PostgreSQL storage backend for server mode ... Add PostgreSQL support as the server-mode storage backend alongside existing SQLite for local mode. Verify all ORM models are dialect- agnostic, configure connection pooling for multi-user access, add Docker Compose for local PG development, and wire database URL selection based on deployment mode. Changes: - Add psycopg2-binary dependency to pyproject.toml - Add server_mode, db_pool_size, db_max_overflow, db_pool_recycle settings to Settings with environment variable support - Add resolve_database_url() and is_postgresql() to Settings for mode-aware database URL resolution - Configure UnitOfWork engine creation with pool_size, max_overflow, pool_recycle, and pool_pre_ping for PostgreSQL connections - Update MigrationRunner to handle both SQLite and PostgreSQL backends - Add compare_type=True to Alembic env.py for dialect-aware migrations - Add docker-compose.yml with PostgreSQL 16-alpine for local development - Add Behave BDD feature (14 scenarios) covering settings, pool config, engine creation, ORM dialect compatibility, and migration runner - Add Robot Framework integration tests (12 test cases) for the abstraction layer with requires_postgresql tag for live PG tests Fixes: - Restore require_confirmation parameter to UnitOfWork.__init__ - Add argument validation to UnitOfWork.__init__ (fail-fast) - Add explicit PostgreSQL isolation_level (READ COMMITTED) - Add dispose() method and context manager support to UnitOfWork - Fix MigrationRunner.get_current_revision() to dispose engine - Fix Settings.is_postgresql() to handle ValueError gracefully ISSUES CLOSED: #878	2026-05-29 01:04:59 -04:00
freemo	6aaf69e0a4	feat(server): implement PostgreSQL storage backend for server mode ... Add PostgreSQL support as the server-mode storage backend alongside existing SQLite for local mode. Verify all ORM models are dialect- agnostic, configure connection pooling for multi-user access, add Docker Compose for local PG development, and wire database URL selection based on deployment mode. Changes: - Add psycopg2-binary dependency to pyproject.toml - Add server_mode, db_pool_size, db_max_overflow, db_pool_recycle settings to Settings with environment variable support - Add resolve_database_url() and is_postgresql() to Settings for mode-aware database URL resolution - Configure UnitOfWork engine creation with pool_size, max_overflow, pool_recycle, and pool_pre_ping for PostgreSQL connections - Update MigrationRunner to handle both SQLite and PostgreSQL backends - Add compare_type=True to Alembic env.py for dialect-aware migrations - Add docker-compose.yml with PostgreSQL 16-alpine for local development - Add Behave BDD feature (14 scenarios) covering settings, pool config, engine creation, ORM dialect compatibility, and migration runner - Add Robot Framework integration tests (12 test cases) for the abstraction layer with requires_postgresql tag for live PG tests ISSUES CLOSED: #878	2026-05-29 01:00:08 -04:00
HAL9000	aecbaa00f6	fix(actor): resolve CI failures for config-actor format PR ... Lint (ruff): - schema.py: import `cast`, replace non-breaking hyphens, inline SIM103 return, wrap long is_nested_v3 line - config.py: replace `if k in d: del d[k]` with `pop`, collapse nested ifs (SIM102) - format both reformatted-only files (ruff format) Typecheck (pyright): - config.py: guard `actor_type.lower()` calls with isinstance checks so the None branch is type-safe Unit tests (behave): - Remove duplicate `@then('v3actor the command ...')` and `@then('the actor should be registered with type ...')` registrations that crashed step-registry with AmbiguousStep — shared versions live in actor_add_v3_schema_validation_steps.py - Add missing Actor import; drop unused ActorConfiguration / is_v3_yaml imports and unused provider/model locals - Populate `context.registered_actor_type` from the upsert call args so the shared assertion step works for combined-format scenarios - Add a `@when("I run the actor add command without a name argument")` step that exercises the CLI's "Actor name is required" validation path (the previously-active step always supplied a name, masking the scenario's intent) ISSUES CLOSED: #11189	2026-05-28 20:47:07 -04:00
freemo	7b91b66b28	Fix actor add --config crash with combined-format config.actor (#11189) ... When users register actors via `agents actor add --config` using the spec-compliant combined config.actor YAML format — either as a compact string (config:\n actor: "<provider>/<model>") or as a nested dict (config:\n actor:\n type: llm\n provider: aws) — the CLI crashed with click.BadParameter: "Invalid value: 'provider' is required" because the parser did not detect or flatten the nested structure. Added: - _detect_nested_config_actor() in schema.py to recognise both compact-string and nested-dict forms of config-actor format. - _flatten_config_actor() in schema.py to merge config["actor"] fields into the dict top-level (removing the wrapper). - Flattening logic in ActorConfiguration.from_blob() to handle both string ("<provider>/<model>") and nested-dict forms of config.actor. - CLI flattening step at the start of `agents actor add` command. - New BDD scenarios for combined-format registration. - Unit tests for detection, flattening, schema-v3 detection, and full from_blob() flow. ISSUES CLOSED: #11189	2026-05-28 20:25:17 -04:00
HAL9000	2dd920078a	fix(tests): add resolve_actor_options to mock lifecycle helpers ... The PR added resolve_actor_options() to StrategyActor, LLMStrategizeActor, and LLMExecuteActor, but the three mock lifecycle SimpleNamespace objects used by tests did not include this method, causing AttributeError at runtime: - features/mocks/mock_strategy_llm.py: make_mock_lifecycle() used by robot/helper_strategy_actor.py (strategy_actor.robot llm-json test) and features/steps/strategy_actor_llm_steps.py - features/steps/llm_actors_coverage_steps.py: _make_mock_lifecycle() used by llm_actors_coverage.feature scenarios - robot/helper_m5_e2e_context.py: inline lifecycle SimpleNamespace used by m5_e2e_verification.robot Execute Phase LLM Uses ACMS Context All three now include resolve_actor_options=MagicMock(return_value=None) matching the None-return contract the actors use when no custom backend is configured. ISSUES CLOSED: #11256	2026-05-28 17:35:08 -04:00
CoreRasurae	d5fd6b1765	fix(strategize): propagate actor options.openai_api_base and options.openai_api_key to LLM client creation in Strategize/Execute paths ... Extract shared build_llm_kwargs_from_options() utility in actor/config.py that converts actor-level YAML options (openai_api_base, openai_api_key, temperature, max_tokens, etc.) into kwargs for ProviderRegistry.create_llm(). Add options field to ActorConfigSchema so it survives Pydantic validation instead of being silently dropped by extra='ignore' default. Add resolve_actor_options() to PlanLifecycleService and both LifecycleService and PlanLifecycleProtocol protocols so every call site can retrieve the actor's config_blob.options dict. Fix the four call sites that previously called create_llm() with zero extra kwargs, preventing local/custom LLM backends from working: - StrategyActor._execute_with_llm() in strategy_actor.py - LLMStrategizeActor.execute() in llm_actors.py - LLMExecuteActor.execute() in llm_actors.py - SessionWorkflow._resolve_llm() in session_workflow.py Refactor reactive path (stream_router.py, tool_caller.py) to use the shared build_llm_kwargs_from_options() utility instead of inline copies. Wire actor_options_resolver through CLI session builder and A2A facade. ISSUES CLOSED: #11256	2026-05-28 17:35:08 -04:00
HAL9000	cb27538a73	test(planconfig): add BDD coverage for ThreeWayMergeConflictDetector ... Add feature file and Behave steps covering all reachable code paths in merge_conflict.py: MODIFY_MODIFY/DELETE/ADD_ADD conflict types, auto- resolution for MODIFY_DELETE/DELETE_MODIFY/convergent ADD_ADD, DELETE_DELETE absence, detect_diff_text formatting, describe_all status types, and direct _analyse_field call for the unreachable ADD_ADD branch. Restores coverage above the 96.5% threshold after the merge_conflict module was added with zero test coverage. ISSUES CLOSED: #11000	2026-05-28 12:52:19 -04:00
HAL9000	22831e4f50	fix(lsp): make post-spawn logger.info mock selective and remove tdd_expected_fail ... The _info_raises side_effect previously raised RuntimeError on every logger.info call, which caused the pre-Popen "lsp.transport.starting" call (transport.py:109) to raise before subprocess.Popen was ever reached. This meant the cleanup guard at lines 160-186 was never exercised, making the scenario a permanent no-op TDD stub rather than a genuine regression guard. Fix: make _info_raises conditional on the first positional argument being "lsp.transport.started" (the post-Popen message). The pre-Popen "lsp.transport.starting" call now passes through normally, Popen succeeds (mocked), and the RuntimeError is raised inside the guarded try/except block, triggering terminate() + wait() cleanup. Remove @tdd_expected_fail from the scenario since the cleanup code at transport.py:160-186 is in place and the scenario now passes. Closes #7044	2026-05-28 11:36:14 -04:00
HAL9000	c2459772eb	fix(lsp): restore missing else branch for stderr in _make_mock_process ... The `else: proc.stderr = stderr` clause was dropped when the helper was extracted into `_ltcov_helpers.py`. `stdin` and `stdout` both have the corresponding else branches; this restores parity so that callers passing a non-"auto" stderr value have it honoured.	2026-05-28 11:03:11 -04:00
HAL9000	a61d132ac0	fix(lsp): fix relative imports and remove unused imports in BDD step files ... - features/steps/lsp_transport_coverage_steps.py: change relative import `from ._ltcov_helpers import build_lsp_frame, ...` to absolute `from _ltcov_helpers import make_mock_process ...`, removing unused `build_lsp_frame` - features/steps/lsp_transport_post_spawn_cleanup_steps.py: remove unused `subprocess` and `MagicMock` imports; fix relative import to absolute; collapse short assert messages to single lines; remove trailing blank line Behave's exec_file loader does not set __name__ in globals, causing relative imports to raise KeyError at step-module load time. Absolute imports work because Behave adds features/steps/ to sys.path. ISSUES CLOSED: #11237	2026-05-28 10:50:24 -04:00
HAL9000	daf90ba764	fix(lsp): wrap post-Popen init in cleanup guard to prevent orphaned processes ... Closes #7044 The StdioTransport.start() method had an unprotected logger.info() call after successful Popen(). If that call raised, the subprocess would leak as an orphaned process. Wrap all post-spawn initialization in a try/except guard: on any exception after spawn, terminate and wait for the process (with kill fallback), reset state to None, then re-raise so callers still get proper error semantics. The existing stop() method cleanup pattern (terminate → wait → kill) is mirrored here for consistency across the transport lifecycle. Tests added: - TDD scenario with @tdd_issue_7044 verifying subprocess cleanup on post-Popen exception and state reset to None - Explicit is_alive() scenarios covering both alive and not-alive states Refactoring: - Extracted _make_mock_process and _build_lsp_frame helpers into a shared _ltcov_helpers module to keep step files under the 500-line CONTRIBUTING.md limit. ISSUES CLOSED: #7044	2026-05-28 10:50:24 -04:00
CoreRasurae	b98c99d93e	test(integration): add BDD scenarios for full hierarchical plan 4-phase lifecycle execution ... Adds BDD integration tests (Forgejo #10270) verifying that child plans independently complete all four lifecycle phases: Strategize, Decompose, Execute, and Validate. Scenarios covered: - Happy path: 2-level parent-child hierarchy with full phase execution - Checkpoint: on_subplan_spawn checkpoint creation verification - Max-child-depth: decomposition respects depth limits - Aggregation: parent plan aggregates child results - Failure handling: parent captures child plan failures - Nested: 3-level grandchild hierarchy cascading Uses real (non-mocked) service implementations in in-memory mode. ISSUES CLOSED: #10270	2026-05-28 00:05:08 -04:00
hamza.khyari	6bda792d2b	fix(tui): subclass Input to override _watch_value and eliminate layout=True per keystroke ... Input._watch_value sets self.virtual_size (Reactive layout=True) on every keystroke, keeping Textual's WriterThread write queue permanently non-empty. The queue never reaches qsize()==0 so flush() is never called and typed characters are invisible until Enter drains the queue. Two fixes applied: 1. _PromptTextInput subclasses textual.widgets.Input and overrides virtual_size with Reactive(layout=False). Setting virtual_size in _watch_value no longer triggers refresh(layout=True). Zero type:ignore suppressions — uses proper Textual reactive types. 2. CSS #prompt and #prompt > Input changed from height:auto to fixed heights (3 and 1). This prevents the auto_dimensions guard in _watch_value from adding a second refresh(layout=True) per keystroke. 3 BDD regression scenarios added covering: virtual_size layout=False, _PromptInputBase usage in _TextualPromptInput, and fixed CSS height. ISSUES CLOSED: #11249	2026-05-27 23:17:15 -04:00
hurui200320	91691750ed	fix(reactive): forward actor options block in ToolCallingLLMCaller._resolve_llm ... Port the options-block merging logic from SimpleLLMAgent._resolve_llm() (stream_router.py, added in PR #11225 / commit b3851693) to the parallel resolution path ToolCallingLLMCaller._resolve_llm() in tool_caller.py. Without this fix, running an actor with --skill would ignore the options block in the actor YAML, causing openai_api_base and openai_api_key to be silently dropped. The provider registry then fell back to OPENAI_API_KEY from the environment, routing requests to api.openai.com instead of the configured local llama-swap/llama.cpp backend (HTTP 401). Changes: - tool_caller.ToolCallingLLMCaller._resolve_llm: read actor_config.options; extract openai_api_key -> __api_key_sentinel; forward allowed keys (openai_api_base, timeout, top_p, frequency_penalty, presence_penalty); reject reserved keys (provider_type, model_id) and unknown keys with logger.warning, matching SimpleLLMAgent behaviour exactly. - features/actor_run_tool_calling.feature: add five BDD regression scenarios (section V, tagged @tdd_issue @tdd_issue_11243) covering api_base+key forwarding, allowed extra keys, reserved key rejection, unknown key rejection, and top-level precedence over options. - features/steps/actor_run_tool_calling_steps.py: add corresponding step definitions for all five scenarios. All nox quality gates pass (lint, typecheck, unit_tests 15822/0 fail, integration_tests 1999/0 fail, coverage_report 97%). ISSUES CLOSED: #11243	2026-05-27 12:14:04 -04:00
drew	0bde46f0ff	fix(tui): update tests for renamed Anthropic model names and fix typer.Exit propagation	2026-05-27 00:46:19 -04:00
HAL9000	190606d7e6	fix(memory): handle langchain-community SQLChatMessageHistory API rename ... langchain-community >= 0.3 renamed connection_string to connection in SQLChatMessageHistory.__init__(). Use the new 'connection' kwarg first and fall back to 'connection_string' for older versions. Also updates the test assertion in memory_service_coverage_steps.py to accept either parameter name. Fixes CI errors in: - plan_service_coverage.feature:128,141 - consolidated_misc.feature:1531	2026-05-23 12:22:51 +00:00
CoreRasurae	cdbe504b2c	fix(test): use shared in-memory SQLite URI in _ensure_memory_database_url ... Replace sqlite:///:memory: with sqlite:///file::memory:?cache=shared to ensure all SQLAlchemy connections within the same process share a single in-memory database. This prevents isolation issues where SQLChatMessageHistory and EntityStore would each create separate in-memory databases, avoiding unexpected errors in CI parallel execution.	2026-05-23 12:20:11 +01:00
HAL9000	73d3bed2da	test(persistence): remove stale @tdd_issue tags from EntityStore persistence tests ... The _load_from_persistence() and _persist_if_needed() stubs have been replaced with real SQLite persistence implementations, fixing bug #10455. All five scenarios now pass as regular regression tests. Refs: #10455	2026-05-23 00:01:44 +00:00
CoreRasurae	3e13411fcf	fix(actors): distinguish namespace/name from provider/model in actor name parsing ... When action YAML references actors using namespace/name format (e.g. `strategy_actor: local/my-strategist`), `_parse_actor_name()` incorrectly treated the namespace prefix as a provider name, causing `ValueError: Unknown provider type: local`. Changes: - `_is_known_provider()`: New utility function (strategy_resolution.py) that checks whether a slash-separated first segment matches a known `ProviderType` value (openai, anthropic, etc.). Consolidated into a single implementation; llm_actors.py now imports from strategy_resolution.py. - `_parse_actor_name()`: When the first segment IS a known provider, preserves existing behaviour (provider/model). When it is NOT a known provider, treats the input as namespace/name and returns the full name as the model identifier with the default provider. Callers SHOULD pre-resolve namespace/name references via the actor registry before calling this function. Both implementations (strategy_resolution.py and llm_actors.py) updated; ProviderType import moved to top level. - `PlanLifecycleService.resolve_actor_provider_model()`: New method that resolves a namespaced actor name (e.g. local/my-strategist) to provider/model format by looking up the actor record and extracting its provider and model fields. - `LifecycleService` Protocol (strategy_resolution.py): Added `resolve_actor_provider_model` to the protocol, eliminating the need for `# type: ignore[union-attr]` at call sites. - `PlanLifecycleProtocol` (llm_actors.py): Added `resolve_actor_provider_model` to the protocol. - Caller pre-resolution: StrategyActor, LLMStrategizeActor, LLMExecuteActor, SessionWorkflow._resolve_llm(), and CLI session commands now pre-resolve actor names through the lifecycle service or via injected actor_resolver callables before calling `_parse_actor_name()`, ensuring namespace/name references are correctly mapped to their underlying LLM providers. - `_build_actor_resolver()` (cli/commands/session.py) and `_build_actor_resolver_for_session_workflow()` (a2a/facade.py): Moved `_is_known_provider` imports to top level; removed redundant `except (NotFoundError, Exception)`; added warning logging for outer exception handlers. - `make_mock_lifecycle()` (mock_strategy_llm.py) and `_make_mock_lifecycle()` (llm_actors_coverage_steps.py): Added `resolve_actor_provider_model` to mock lifecycle services for test compatibility. - Added `@tdd_issue @tdd_issue_11254` tags to all new BDD scenarios related to namespace/name disambiguation in llm_actors_coverage, strategy_actor_llm, and plan_lifecycle_service_coverage_boost_r4 feature files. - Updated docs/CHANGELOG.md with the fix entry. ISSUES CLOSED: #11254	2026-05-22 20:42:25 +01:00
hamza.khyari	652769c46c	feat(tui): wire normal text input to LLM via A2A facade ... Wires the TUI normal text input path to the LLM via A2aLocalFacade, closing the gap where typing a message produced no LLM call. All infrastructure (facade, SessionWorkflow, ProviderRegistry) already existed in the CLI; this PR adds the TUI wiring on top. Key changes: - _run_llm_dispatch(): module-level, Textual-free dispatch function covering all domain exception paths with user-friendly messages - _format_worker_outcome(): testable worker result/error translator - _create_tui_session(): DB-backed session with persona actor binding - _build_tui_facade(): wired A2aLocalFacade + SessionWorkflow singleton - run_worker(thread=True, exclusive=True): non-blocking, serialised - _dispatch_gen counter: prevents cancelled worker callbacks from corrupting the multi-turn transcript - SessionView.transcript: accumulated conversation history, pre-escaped - Markup escaping: _escape() applied before transcript storage - on_mount focus: prompt.focus() so keyboard input is received Tests: 18 BDD scenarios + 6 Robot Framework integration tests with FakeListLLM (no real API keys required). ISSUES CLOSED: #11230	2026-05-22 15:12:04 +00:00
CoreRasurae	3a95701d9a	fix(decomposition): enforce plan.max-child-depth recursion limit to prevent unbounded hierarchy growth ... Add max_child_depth field to DecompositionConfig (default: 5, matching plan.max-child-depth config) with validation in __post_init__. Update _build_hierarchy() in DecompositionService to stop recursion and emit a warning when the depth limit is reached. BDD tests verify: max_child_depth guards trigger before max_depth when more restrictive, warnings are logged, default config value is correct, and invalid values are rejected. ISSUES CLOSED: #10269	2026-05-19 21:56:28 +01:00
CoreRasurae	8548644819	fix(cli): wire SubplanExecutionService in _get_plan_executor() to enable child plan execution ... Wire subplan_service from the DI container into _get_plan_executor() so PlanExecutor can spawn child plans during the Execute phase. When SubplanService is available but SubplanExecutionService is not explicitly injected, _execute_subplans() now lazily creates a SubplanExecutionService on-the-fly using the parent plan's subplan_config and the new _execute_child_plan callback. - _get_plan_executor(): retrieve subplan_service from container, pass to PlanExecutor constructor - _execute_subplans(): lazily build SubplanExecutionService when only SubplanService is wired (Forgejo #10268) - _execute_child_plan(): new PlanExecutor method that runs a child plan's strategize + execute phases, registered as executor_fn callback ISSUES CLOSED: #10268	2026-05-19 19:28:35 +01:00
brent.edwards	eb46f0ff54	fix(plan): add tier hydration and improve architecture review output (#10938) ... ## Summary This PR fixes issue #10878 where architecture reviews were truncated because the regex pattern for parsing file output would stop at the first ``` encountered in the Markdown report. ## Changes - Change file delimiters from ``` to >>>>>>>/<<<<<<< to avoid Markdown conflicts - Add tier hydration before strategize phase in plan_executor.py - Increase max_tokens to 16384 in llm_actors.py for longer outputs - Increase context_max_tokens_hot from 16000 to 32000 in settings.py - Fix get_hot_view → get_hot_fragments in strategy_actor.py and plan_executor.py - Add opencode to skip directories in context_tier_hydrator.py - Change sandbox output location to plan-output/ directory in plan.py - Add get_context_summary stub method to acms_service.py ## Testing Run architecture review action and verify the output report is complete with all sections. Reviewed-on: #10938	2026-05-19 12:43:34 +00:00
hurui200320	0c5724c2f6	feat(actor-run): wire ToolCallingRuntime into actor run for skill-based tool calling ... Implements the full tool-calling path for `agents actor run --skill` so that LLM actors can actually invoke tools through the ToolCallingRuntime loop when a skill is attached. Core changes: - reactive/tool_caller.py (new): ToolCallingLLMCaller implements the LLMCaller protocol; binds tool schemas via bind_tools(), threads SystemMessage+HumanMessage on first call and AIMessage+ToolMessages on subsequent calls, extracts tool calls from LangChain responses following the LangChainSessionCaller pattern. - reactive/tool_caller.py: bidirectional tool name encoding via uppercase sentinels (_encode_tool_name / _decode_tool_name) to make CleverAgents namespaced tool names ("builtin/file-read", "server:local/tool") compatible with Anthropic's tool name pattern ^[a-zA-Z0-9_-]{1,128}$. Uses _C_ for ":" and _S_ for "/" — uppercase sentinels are safe because valid CleverAgents tool names forbid uppercase letters. Encoding applied in _resolve_llm() before bind_tools(); decoding applied in invoke() when extracting tool calls from the LLM response. - reactive/tool_agent.py (new): ToolCallingAgent builds a per-run local ToolRegistry from resolved skill tool entries by looking up names in the shared builtin_registry; drives ToolCallingRuntime.run_tool_loop(); exposes last_result for tool_calls surfacing. - reactive/application.py: (ST-1) _make_agent_instance() now always merges skill tools instead of silently dropping them when actor has no base tools list; routes tools+llm→ToolCallingAgent, tools+non-llm→SimpleToolAgent, no-tools+llm→SimpleLLMAgent; (ST-4) _builtin_registry created at startup with register_file_tools/git/subplan; (ST-6) _tally_tool_calls() + last_run_tool_calls property. - reactive/graph_executor.py: (ST-5) ToolCallingAgent added to isinstance check in _invoke_agent() so context dict is forwarded for Jinja2 rendering. - cli/commands/actor_run.py: prints "Tool Calls: {n}" when > 0. Test fixes: - features/steps/actor_cli_run_steps.py: _make_app() sets last_run_tool_calls=0 to avoid MagicMock>int TypeError in Python 3.13. - features/steps/actor_run_signature_resolve_steps.py: same fix. - robot/helper_actor_run_signature.py: same fix. - features/reactive_application_coverage_boost.feature: updated scenario to verify new correct behavior (LLM+skills → ToolCallingAgent, not silently kept as SimpleLLMAgent). BDD coverage: 34 scenarios in features/actor_run_tool_calling.feature covering tool call success, multi-turn loop, no-skill regression, silent-drop fix, LLMCaller internals, _build_tool_registry edge cases, last_run_tool_calls tallying, tool name encoding/decoding, and LLM response decoding. ISSUES CLOSED: #11211	2026-05-18 06:05:54 +00:00
hamza.khyari	e2167ab8e7	fix(acms): use project-level hot_max_tokens in execute phase context assembly ... Fixed _resolve_hot_max_tokens() to read hot_max_tokens from the correct sub-key in context_policy_json. The value is stored under context_policy_json["acms_config"]["hot_max_tokens"] by 'agents project context set --hot-max-tokens', not at the top level. The previous read (config_dict.get("hot_max_tokens")) always returned None, causing the assembler to silently use the global 16K default even when a project-level override was configured. Also adds two Behave regression scenarios with @tdd_issue @tdd_issue_11035 tags that exercise the real DB query code path via a mocked NamespacedProjectModel row, verifying: 1. hot_max_tokens=32000 in acms_config is applied to CoreContextBudget and ContextRequest (override path). 2. Missing hot_max_tokens falls back to the constructor-injected global default of 4096 (fallback path). Module-level import json added to steps file; redundant inline MagicMock import removed. ISSUES CLOSED: #11035 ISSUES CLOSED: #11215	2026-05-16 16:40:54 +00:00
hurui200320	b3851693c8	fix(reactive): forward actor options block to LLM constructor for custom backend support ... Two code paths in the reactive actor run pipeline silently discarded the options: block from v3 actor YAML, preventing custom OpenAI-compatible backends (llama.cpp, Ollama, etc.) from being used. Review fixes applied: - Fix 1: Relabeled issue #11223 from Type/Task to Type/Bug; added @tdd_issue/@tdd_issue_11223 tags to all 5 Behave scenarios. - Fix 2: openai_api_key in options now routes through the registry's __api_key_sentinel mechanism so user-provided keys correctly override environment defaults. (stream_router.py) - Fix 3: type: graph actors now propagate actor-level options to individual node configs via setdefault. (config_parser.py) - Fix 4: Options keys are validated against an explicit allowlist; reserved keys (provider_type, model_id) are excluded; unrecognized keys log a WARNING instead of being silently forwarded. (stream_router.py) - Fix 5: Updated _build_from_v3 docstring to list options as a propagated field. (config_parser.py) - Fix 6: Removed inconsistent and options_raw emptiness guard; empty options dicts are now preserved consistently. (config_parser.py) - Fix 7: Reserved keys provider_type and model_id are excluded from the options merge loop to prevent TypeError. (stream_router.py) - Fix 8: Added Behave scenario verifying top-level temperature takes precedence over options duplicate. (consolidated_routing.feature + steps) - Fix 9: Strengthened "no extra kwargs" assertion to assert kwargs == {} directly instead of using an allow-list filter. (stream_router steps) - Fix 10: Strengthened options assertion to exact dict equality. (actor_v3_schema_extended_steps.py) - N1: Comment style aligned to M5: prefix convention. - N2: Type annotations changed from Any to Context (behave.runner). - N3: Added Behave scenario for empty options: {} dict behavior. Tests: 5 new Behave scenarios (3 in actor_v3_schema.feature, 2 in consolidated_routing.feature) with @tdd_issue/@tdd_issue_11223 tags. ISSUES CLOSED: #11223	2026-05-16 13:38:54 +00:00
freemo	23d73e7fb2	chore: Fix ruff format violations in db_url_sanitisation_steps.py ... Fix formatting issues detected by CI lint check: - Simplify multi-line decorator arguments to single line - Simplify multi-line assertion error messages to single line This resolves the format --check failure blocking CI.	2026-05-16 06:04:01 +00:00
HAL9000	86f96f299e	fix(cli): Mask database URL credentials in agents info CLI output (#8395)	2026-05-16 06:04:01 +00:00
HAL9000	5c5309f35d	fix(ci): add missing effective set count step definition ... The Behave scenario at line 671 of consolidated_domain_models.feature asserts 'the effective set should have {count:d} invariants' but no step handler existed, causing UndefinedStepError and CI failure. Adds the missing step: @then('the effective set should have {count:d} invariants') to step_invariant_models_steps.py, mirroring the existing invariant-set count pattern.	2026-05-16 04:14:17 +00:00
HAL9000	761622f746	fix(invariant): pass action_name in list_invariants when scope is ACTION ... Fixes list_invariants(effective=True) to forward action_name to get_effective_invariants when scope is ACTION, ensuring action-scoped invariants are included in effective invariant lists. Also applies ruff formatting to the return statement in get_effective_invariants. Addresses reviewer observation about list_invariants gap. Refs: #9126	2026-05-16 04:14:17 +00:00
freemo	bf52a9c648	fix(invariant): restore ACTION scope in merge_invariants and InvariantSet.merge precedence chain ... The 4-tier invariant precedence chain (plan > action > project > global) was broken at the domain layer — merge_invariants() and InvariantSet.merge() only accepted 3 parameters (plan, project, global), silently dropping all action- scoped invariants. Added action_invariants as a fourth parameter with proper backward compatibility (default to empty list). Updated module docstrings, InvariantScope docstring, and InvariantService.get_effective_invariants() to reflect the correct precedence chain. Added comprehensive BDD test scenarios covering four-tier merge precedence, action-before-project ordering, and effective invariant computation with all four scopes. ISSUES CLOSED: #9126	2026-05-16 04:14:17 +00:00
CoreRasurae	97c1007bb5	feat(events): wire domain services to emit missing EventBus events ... Add TokenAuthMiddleware to emit AUTH_SUCCESS/AUTH_FAILURE with spec-aligned audit details and wire it through the DI container using server.token resolution. Add Behave and Robot coverage for auth event emission and end-to-end audit persistence, and update audit subscriber producer notes and changelog. ISSUES CLOSED: #714	2026-05-15 22:19:57 +01:00
hamza.khyari	b4351ca78d	Revert "Merge pull request 'fix(acms): use project-level hot_max_tokens in execute phase context assembly' (#11216) from bugfix/m5-acms-project-budget-override into master" ... This reverts commit 94622f467c, reversing changes made to 1196c726f2.	2026-05-15 11:15:41 +00:00
hamza.khyari	1baa888659	fix(acms): use project-level hot_max_tokens in execute phase context assembly ... Added _resolve_effective_budget() method to ACMSExecutePhaseContextAssembler that reads each linked project's settings.hot_max_tokens and uses the maximum override value as the pipeline budget instead of the hardcoded global default. Updated assemble() to use the resolved effective budget for both CoreContextBudget and ContextRequest. Added Behave regression scenario with @tdd_issue @tdd_issue_11035 tags verifying the pipeline receives the project-level budget. Removed test artifact ANALYSIS.md left over from scenario 20. Fixes: #11035 Fixes: #11215	2026-05-15 10:27:57 +00:00
HAL9000	1196c726f2	fix(lint): remove broken step file and fix line-length violation ... - Removed features/steps/plan_status_json_envelope_steps.py which contained invalid Python syntax (dummy content, not referenced by any feature) - Fixed line-length violation in execute_phase_context_assembler.py (CoreContextBudget constructor call exceeded 88-char limit)	2026-05-15 03:41:13 +00:00
HAL9000	655cd7ebc2	fix: persist strategy decisions via DecisionService during strategize (#10813) ... The plan tree command reported zero decision nodes after strategize because PlanExecutor.run_strategize() never persisted strategy decisions as domain Decision objects. Added _persist_strategy_decisions() to the PlanExecutor, wired decision_service from the DI container in _get_plan_executor(), and ensure each strategy decision is recorded with correct DecisionType mapping. ISSUES CLOSED: #10813	2026-05-15 03:41:13 +00:00
HAL9000	dbc382f3d9	Fix TypeError in infer_resource_slots() when properties is null ... Fixed MCPToolAdapter.infer_resource_slots() to handle null values in JSON Schema by using instead of which returned None when the key exists with a null value. The @tdd_expected_fail tag was removed from TDD issue #10470 since the fix is now applied.	2026-05-15 02:41:37 +00:00
CoreRasurae	b41f536da6	fix(automation): respect automation profile gates in lifecycle service and async jobs ... Add BDD regression tests for issue #4328 automation profile gates Tests verify that complete_strategize() and complete_execute() respect automation profile thresholds and do NOT unconditionally call auto_progress(). Covers 8 built-in profiles: manual, full-auto, supervised, auto, review_before_apply, ci, trusted ISSUES CLOSED: #4328	2026-05-14 22:57:11 +00:00
HAL9000	2f29f8352f	chore: resolve merge conflicts and apply cosmetic fixes ... - Resolve CHANGELOG.md conflict to include both entries, referencing issue #8164 instead of PR #11161 - Resolve CONTRIBUTORS.md conflict, fix leading space in new entry - Remove duplicate create_sequence_node function (dead code) Merges master into feat/structural-output-validation branch	2026-05-14 18:14:48 +00:00
hurui200320	cc8e013f9b	fix(actor): handle nested actor type and combined config.actor field in v3 YAML ... Two defects in ActorConfiguration._extract_v3_actor() prevented YAML files using the spec-canonical nested actors map format from being registered: Defect A: The method looked for the 'type' field inside the 'config:' block (config_block.get('type')) instead of at the actor-entry level (first_entry.get('type')). Because the spec places 'type' at actors.<name>.type — a sibling of 'config:', not a child of it — the v3 detection branch never fired for nested-actors-map YAMLs, causing _extract_v3_actor() to return (None, None, None, False) immediately. Defect B: Even if the type was found, the method only consulted separate config.provider and config.model keys; it never parsed the combined config.actor: 'provider/model' shorthand. Without the combined-field fallback, provider and model remained None for all spec-canonical YAMLs that use the shorthand, causing from_blob() to raise 'BadParameter: provider is required'. Both defects had to be fixed together because Defect A blocked the code from ever reaching the path where Defect B would otherwise have been encountered. The combined-format parser (config.actor split on first '/') is inserted after the explicit config.provider / config.model lookups so that explicit separate fields always take precedence over the shorthand when both are present. Parsing logic extracted into _parse_combined_actor_field() helper to eliminate DRY violation. Both provider and model halves validated consistently (empty provider half was previously silently inferred). Adds Behave scenarios covering: nested actors map + combined config.actor (success), explicit config.provider precedence over config.actor, explicit config.model precedence over config.actor, genuinely missing provider/model raising validation error, and malformed combined values (empty model half, empty provider half, missing delimiter). Adds a Robot integration test for the combined-actor YAML path with provider/model assertions via show. Restores accidentally deleted TOOL and GRAPH Robot integration tests. Mirrors provider/model extraction in step_run_actor_update for assertion step compatibility. ISSUES CLOSED: #11189	2026-05-14 08:10:58 +00:00
HAL9000	6d46baf552	fix: apply ruff format to step definitions file	2026-05-14 06:46:27 +00:00
HAL9000	ac81ea2ceb	fix: replace Scenario Outline with literal steps to fix Behave-parallel parameter substitution bug ... The Behevare-parallel runner in this project does not support inline parameter substitution for '{param}' or '<param>' markers within Scenario Outline Examples. All 4 original Scenario Outlines were failing because parameters were not being substituted, causing UndefinedStep and ValueError failures. Fix: Convert all Scenario Outline scenarios to regular Scenarios with explicit literal step definitions. Each unique Gherkin line gets its own @Given/@When/@Then step definition matching the exact string. Also fix pre-existing bugs identified in PR review #8719: - Fix undefined step by quoting {{seq}} in feature (line 46) - Fix ctx.decision_result → ctx.validation_result context variable (line 184) - Fix ctx.struct_result → ctx.validation_result context variable (line 210) - Replace # type: ignore[arg-type] with proper Callable[[Any], dict] type - Add missing literal step definitions for structured_output tests ISSUES CLOSED: #11161	2026-05-14 06:46:27 +00:00
freemo	b092ccac49	fix(ci): apply ruff formatting to validation.py and step definitions ... ISSUES CLOSED: #11147	2026-05-14 06:46:27 +00:00
freemo	b59b2508af	fix(ci): resolve remaining lint errors in __init__.py and step definitions ... ISSUES CLOSED: #11147	2026-05-14 06:46:27 +00:00
HAL9000	f8e4f4a579	feat: implement structural component output validation ... Replace exact character matching with structural component checking for output validation. Implements three validators covering plan tree output, decision CLI dicts, and structured session snapshots. - validate_plan_tree: validates node dicts for required keys (decision_id, type, sequence, question, children), ULID format, correct types, and sibling ordering - validate_decision_dict: validates decision CLI output against Decision.as_cli_dict() schema with field presence, type, ULID, confidence range [0..1], bool fields - validate_structured_output: validates StructuredOutput envelope for command, session_id (ULID), status membership, exit_code, elements integrity - validate_structured_component_output: unified dispatcher by target_type BDD tests in features/structural_validation.feature. ISSUES CLOSED: #11147	2026-05-14 06:46:27 +00:00
hurui200320	39f9903f1a	fix(tests): restore agent-evolution-pool-supervisor.md or remove its orphaned BDD scenarios ... Chose Option B (fallback): remove orphaned BDD scenarios for two retired agents. Commit 3c8cf601 deleted .opencode/agents/agent-evolution-pool-supervisor.md and .opencode/agents/implementation-pool-supervisor.md as part of a large-scale restructuring of agent definition files. However, their corresponding Behave feature files and step definitions were not cleaned up, causing nox -s unit_tests to fail with AssertionError on master. Removed files: - features/agent_evolution_pool_supervisor_metadata.feature (7 scenarios testing agent-evolution-pool-supervisor.md existence and content) - features/steps/agent_evolution_pool_supervisor_metadata_steps.py (382 lines of step definitions for the above feature) - features/pr_compliance_pool_supervisor.feature (10 scenarios testing implementation-pool-supervisor.md existence and content) - features/steps/pr_compliance_pool_supervisor_steps.py (219 lines of step definitions for the above feature) Both agent definition files were permanently retired by the restructuring commit and are not expected to return. Keeping orphaned tests that assert on deleted files is not valid; removal is the correct resolution per the project's handling of obsolete tests policy. Quality gates verified: - nox -s unit_tests: 694 features passed, 0 failed (was failing on master) - nox -s lint: all checks passed - nox -s typecheck: 0 errors, 3 warnings (pre-existing import warnings) - nox -s coverage_report: 96.5% (meets 96.5% threshold) - nox -s integration_tests: 1998 tests passed, 0 failed ISSUES CLOSED: #11208	2026-05-14 04:16:04 +00:00
HAL9000	3459f821c5	fix(events): add close() method to ReactiveEventBus to complete RxPY subject ... Add _closed flag and close() method to ReactiveEventBus to complete the RxPY Subject, preventing subscriber resource leaks. close() is idempotent and raises RuntimeError when called on a closed bus. Also adds: - emit() guard against post-close calls (RuntimeError) - __enter__/__exit__ context manager protocol for automatic cleanup - BDD scenarios in event_bus.feature and TDD tests in tdd_reactive_event_bus_close.feature ISSUES CLOSED: #10378	2026-05-13 12:24:33 +00:00
CoreRasurae	3fcfaee02d	feat(mcp): implement StdioMCPTransport for JSON-RPC 2.0 stdio communication ... Implements concrete StdioMCPTransport class that: - Spawns MCP server as subprocess and communicates via JSON-RPC 2.0 over stdio - Performs MCP handshake (initialize + notifications/initialized) - Supports tools/list and tools/call methods - Uses RLock for thread-safe concurrent access - Auto-selected when transport='stdio' in MCPServerConfig Adds BDD tests for stdio transport covering: - Connection lifecycle and error handling - Tool discovery and invocation - MCPToolAdapter integration ISSUES CLOSED: #4918	2026-05-13 07:13:34 +00:00