Epic: Sub-Workflow Support in Preparation/Loop/Finalization Slots

[maddes8cht]

Description

The slots for Preparation Agent, Loop Agents, and Finalization Agent should accept not only individual agents from agents/, but also workflows from the workflows/ directory. This allows workflows to be nested and reused as building blocks.

Example: Instead of just entering "amala" in the loop slot, you could enter "workflow:test_generation" – the sub-workflow is then executed recursively at that position.

Sub-Issues (ToDo)

• Configuration System (core/config.py) #1 WorkflowLoader – New class core/workflow_loader.py analogous to AgentLoader: scans *.json in workflows/, loads and parses workflow definitions.
• Core State Management (core/state.py, core/parser.py) #2 Slot Resolution in Engine – _resolve_slot_entry() and _execute_sub_workflow() in core/engine.py, recursion guard (max 3 levels), shared state, error handling.
• Agent Definition Loader (core/agent.py) #3 GUI: Workflow Pool – Workflow listbox alongside the agent pool in ui/app.py, workflow preview, _refresh_workflow_list().
• Subprocess Runner (core/runner.py) #4 GUI: Transfer to Slots + Serialization – Buttons for workflow → slot, prefix logic ("workflow:name"), correct serialization in _get_workflow_data().
• Execution Engine (core/engine.py) #5 Integration Tests – Sub-workflow scenarios in tests/integration.py, recursion tests, edge cases.

Design Decisions (Proposals)

Decision	Proposal
State Isolation	Shared State – Sub-workflow writes to the same WorkflowState
Recursion Depth	max. 3 levels
Error in Sub-Workflow	Sets agent_error: like agent failures
Slot Syntax	"workflow:name" as prefix (explicit, no guessing)
GUI Pool	Separate pool lists (agents left, workflows right)

Prerequisites

• All sub-issues build on each other linearly (Configuration System (core/config.py) #1 -> Core State Management (core/state.py, core/parser.py) #2 -> Agent Definition Loader (core/agent.py) #3+Subprocess Runner (core/runner.py) #4 -> Execution Engine (core/engine.py) #5)