From 9e86eaf12b4a7e608c6154aecdd421d67d07c97d Mon Sep 17 00:00:00 2001 From: Ed_ Date: Mon, 2 Mar 2026 16:45:57 -0500 Subject: [PATCH] conductor(plan): Mark task 'Task 2.1' as complete --- .../tracks/architecture_boundary_hardening_20260302/plan.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/conductor/tracks/architecture_boundary_hardening_20260302/plan.md b/conductor/tracks/architecture_boundary_hardening_20260302/plan.md index 0a7745d..f120547 100644 --- a/conductor/tracks/architecture_boundary_hardening_20260302/plan.md +++ b/conductor/tracks/architecture_boundary_hardening_20260302/plan.md @@ -13,8 +13,8 @@ Focus: Stop `mma_exec.py` from injecting massive full-text dependencies and remo ## Phase 2: Complete MCP Tool Integration & Seal HITL Bypass (Application Core) Focus: Expose all native MCP tools in the config and GUI, and ensure mutating tools trigger user approval. -- [ ] 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]`. -- [ ] Task 2.2: Update `gui_2.py`'s settings/config panels to expose toggles for these new tools. +- [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 +- [~] Task 2.2: Update `gui_2.py`'s settings/config panels to expose toggles for these new tools. - [ ] Task 2.3: In `mcp_client.py`, define a `MUTATING_TOOLS` constant set. - [ ] 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.