Edit Issue - .issue.db

Title *

Description

PHASE 1: Reflexive Loop (Local Reliability)

CONTEXT FROM PDF (arXiv:2511.00330):
Standard LLM tasks fail often. A 'Reflexive Loop' generates output, verifies it (e.g., runs generated code), and self-corrects if it fails, all within one logical step. This stops error propagation at the source.

PROS:
- Stops error propagation at the source.
- Keeps workflow definition clean (hides the retry loop).

CONS:
- Can be slow and expensive (multiple LLM calls).
- Risks database connection exhaustion if run inline.

ARCHITECTURE (CRITICAL):
- MUST be implemented as an ACTIVITY (Activity Worker).
- The loop happens inside the worker process, not the DB transaction.
- Only the final 'verified' result is committed.

TASKS:
1. Create 'tools.agent.reflexive_loop' tool in engine/tools/agent.py.
2. UPDATE 'highway_dsl' library (highway_python_sdk) to add 'ReflexiveOperator'. This operator should serialize to a TaskOperator using the reflexive_loop tool.
3. Implement the loop logic: Generator -> Verifier -> Retry (up to max_turns).

CODE EXAMPLE (DSL):
# Using the new operator
builder.reflexive(
    task_id='gen_code',
    generator='tools.llm.call',
    verifier='tools.code.run',
    max_turns=3
)

REQUIREMENTS:
- DOCUMENTATION: Update docs/HIGHWAY_WORKFLOW_ENGINE_BOOK.md after implementation.
- TESTING: Add comprehensive tests. Use ollama and deepseek-v3.1:671b-cloud model for testing (in tools/llm provider).
- REGRESSION: No regression allowed. All @tests/integration/test_atomicity_baseline.py tests must pass.

Due Date (YYYY-MM-DD)

Tags (comma separated)

Related Issues (IDs)

Enter IDs of issues related to this one. They will be linked as 'related'.

Edit Issue #331