conductor(track): Initialize 'architecture_boundary_hardening' track
This commit is contained in:
12
TASKS.md
12
TASKS.md
@@ -52,3 +52,15 @@
|
||||
|
||||
**Scope:** Phase 1 (Update MMA Skill prompts) → Phase 2 (Update `workflow.md`).
|
||||
|
||||
### `architecture_boundary_hardening_20260302` (initialized)
|
||||
**Priority:** High
|
||||
**Depends on:** None
|
||||
**Track dir:** `conductor/tracks/architecture_boundary_hardening_20260302/`
|
||||
|
||||
**Audit-confirmed gaps:**
|
||||
- `ai_client.py` loops execute `set_file_slice` and `py_update_definition` instantly without checking `pre_tool_callback`, bypassing GUI approval.
|
||||
- `mma_exec.py` bypasses skeletonization for `mcp_client`, causing token bloat.
|
||||
- `dag_engine.py` does not cascade `blocked` states, causing orchestrator infinite loops.
|
||||
|
||||
**Scope:** Phase 1 (Meta-tooling token fix) → Phase 2 (Seal GUI HITL bypass) → Phase 3 (Fix DAG Engine cascading blocks).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user