From d3f42ed895306ce16854b1b53dcd0708d17e39ad Mon Sep 17 00:00:00 2001 From: Ed_ Date: Mon, 2 Mar 2026 16:51:07 -0500 Subject: [PATCH] conductor(plan): Mark task 'Task 2.4' as complete --- .../tracks/architecture_boundary_hardening_20260302/plan.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conductor/tracks/architecture_boundary_hardening_20260302/plan.md b/conductor/tracks/architecture_boundary_hardening_20260302/plan.md index 7eea32d..8ecb31b 100644 --- a/conductor/tracks/architecture_boundary_hardening_20260302/plan.md +++ b/conductor/tracks/architecture_boundary_hardening_20260302/plan.md @@ -16,7 +16,7 @@ Focus: Expose all native MCP tools in the config and GUI, and ensure mutating to - [x] Task 2.1: Update `manual_slop.toml` and `project_manager.py`'s `default_project()` to include all new tools (e.g., `set_file_slice`, `py_update_definition`, `py_set_signature`) under `[agent.tools]`. e4ccb06 - [x] Task 2.2: Update `gui_2.py`'s settings/config panels to expose toggles for these new tools. 4b7338a - [x] Task 2.3: In `mcp_client.py`, define a `MUTATING_TOOLS` constant set. 1f92629 -- [~] Task 2.4: In `ai_client.py`'s provider loops (`_send_gemini`, `_send_gemini_cli`, `_send_anthropic`, `_send_deepseek`), update the tool execution logic: if `name in mcp_client.MUTATING_TOOLS`, it MUST trigger a GUI approval mechanism (like `pre_tool_callback`) before dispatching the tool. +- [x] Task 2.4: In `ai_client.py`'s provider loops (`_send_gemini`, `_send_gemini_cli`, `_send_anthropic`, `_send_deepseek`), update the tool execution logic: if `name in mcp_client.MUTATING_TOOLS`, it MUST trigger a GUI approval mechanism (like `pre_tool_callback`) before dispatching the tool. e5e35f7 ## Phase 3: DAG Engine Cascading Blocks (Application Core) Focus: Prevent infinite deadlocks when Tier 3 workers fail repeatedly.