v0.35.1

[v0.35.1] - 2026-06-22

Changed

• PipeImgGen documentation: Rewrote the docs to clarify how inputs are consumed. PipeImgGen has no dedicated "prompt concept"; it uses a prompt string template into which declared inputs are injected at runtime — Text variables are interpolated directly, while Image variables (single or lists) are injected as reference images to enable image-to-image and editing workflows. Added examples demonstrating this vision pattern.

Fixed

• Blueprint-stage validation error categorization: PipeValidationErrors raised during blueprint parsing (e.g. PipeBatch or SubPipe item name collisions) previously lost their error_type because Pydantic wrapped them in a generic value_error, degrading them to uncategorized residual errors. The categorizer now unwraps them, preserving their structured error_type, pipe_code, domain_code, and source locators.

Removed

• Native concept ImgGenPrompt (Breaking): Removed the built-in native.ImgGenPrompt concept. It was structurally identical to Text (mapped to TextContent) and added no unique semantics; PipeImgGen never depended on it. Migration: replace ImgGenPrompt (or refines = "ImgGenPrompt") with Text in your .mthds files. The internal ImgGenPrompt runtime model, the TemplateCategory.IMG_GEN_PROMPT category, and ImgGenPromptError are unchanged.
• Dead validation error type (Breaking): Removed the PipeValidationErrorType.img_gen_input_not_text_compatible enum value. It had no raise sites and contradicted the current design, where PipeImgGen accepts image inputs as a first-class feature.

What's Changed

• fix(validate): unwrap blueprint-stage PipeValidationError so error_type survives by @lchoquel in #996
• refactor: remove ImgGenPrompt native concept by @lchoquel in #999
• Release v0.35.1 by @lchoquel in #1002

Full Changelog: v0.35.0...v0.35.1