Files
HAL9001 cc3a5a6246
CI / benchmark-publish (pull_request) Has been skipped
CI / helm (pull_request) Successful in 37s
CI / build (pull_request) Successful in 1m0s
CI / lint (pull_request) Failing after 1m4s
CI / quality (pull_request) Successful in 1m20s
CI / security (pull_request) Successful in 1m23s
CI / typecheck (pull_request) Successful in 1m38s
CI / push-validation (pull_request) Successful in 31s
CI / unit_tests (pull_request) Failing after 2m30s
CI / coverage (pull_request) Has been skipped
CI / docker (pull_request) Has been skipped
CI / integration_tests (pull_request) Successful in 3m40s
CI / e2e_tests (pull_request) Successful in 4m20s
CI / status-check (pull_request) Failing after 3s
fix(plan): preserve strategy_decisions_json in error_details during execute and report actual actor mode
Fixed three bugs in _run_execute_with_actor (formerly _run_execute_with_stub):

1. Merged error_details instead of replacing - preserves
   strategy_decisions_json stored by run_strategize() so retry plans
   retain the full decision hierarchy (Forgejo #10874).

2. Used type(self._execute_actor).__name__ instead of hardcoded "stub"
   at all three locations (success, on_error checkpoint, fail) so the
   mode field reflects the actual actor type (Forgejo #10874).

3. Renamed method from _run_execute_with_stub to
   _run_execute_with_actor since it accepts any configured actor
   (stub or LLM), not just ExecuteStubActor.

Added two Behave scenarios verifying strategy_decisions_json survival
and actual actor mode reporting. Updated test step comments and docs.

ISSUES CLOSED: #10874
2026-04-29 14:02:33 +00:00
..
2025-12-05 21:00:46 -05:00
2026-03-10 12:38:35 -04:00