v1.7.0

Fragua v1.7.0

Overview

This release introduces a structural refactor of the execution layer to align the agent with the Builder-based architecture. The changes improve separation of concerns, extensibility, and observability of pipeline executions without altering the public contract of pipelines.

---

Key Changes

Agent Refactor: Builder Integration

• The Agent class has been refactored to delegate result construction to a dedicated Result Builder.
• Execution logic is now clearly separated from result assembly, reducing responsibilities within the agent.
• This prepares the execution layer for future extensions (e.g. alternative result formats, persistence, or streaming).

run_pipeline Modernization

• run_pipeline has been updated to:
  • Focus exclusively on step execution and metadata collection.
  • Defer final result creation to _build_result_box, which now relies on the builder.
• Step execution flow remains unchanged from a consumer perspective.

Improved Execution Metadata

• Step metadata collection is now fully centralized and normalized.
• Macro-origin information is preserved and attached passively when present.
• Each step execution records:
  • Execution order
  • Set name
  • Function
  • Inputs used
  • Produced key
  • Parameters
  • Status
  • Macro origin (when applicable)

Internal Consistency

• Validation of execution results is performed before result construction.
• The final FraguaBox is now guaranteed to be built from a validated and complete execution context.

---

Backward Compatibility

• No breaking changes to:
  • Pipeline definitions
  • Registry usage
  • Public APIs
• Existing pipelines continue to execute without modification.

---

Motivation

This refactor establishes a cleaner execution lifecycle and lays the groundwork for:

• Multiple result builders
• Enhanced execution introspection
• More advanced macro and composition features

---