Build AI methods with your coding agent, then run them anywhere: as an MCP for chatbots, as a webapp for people, or via API for your software.
Release v0.35.0
Louis Choquel4715a45dd418
diff --git a/.badges/tests.json b/.badges/tests.jsonindex a6c735a88..32c3bc78c 100644--- a/.badges/tests.json+++ b/.badges/tests.json@@ -1,7 +1,7 @@{"schemaVersion": 1,"label": "tests",- "message": "7943",+ "message": "7981","color": "blue","cacheSeconds": 300}\ No newline at end of filediff --git a/CHANGELOG.md b/CHANGELOG.mdindex 0857231cb..0175aa4b5 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -1,19 +1,26 @@# Changelog-## [Unreleased]+## [v0.35.0] - 2026-06-18### Added-- **Structured wiring/concept/type validation errors** — bundle-validation failures that previously collapsed to a bare message-only `blueprint_validation` residual now emit a structured, categorized `validation_errors[]` item with identity locators. A **pipe-owned unresolved concept reference** (a pipe input/output) → `pipe_validation` / `unresolved_concept` (with the referencing `pipe_code`, the missing `concept_code`, and the `field_name`); a **concept-owned unresolved concept reference** (a concept's `refines` or a structure field's `concept_ref`) → `blueprint_validation` / `unresolved_concept` (with the owning `concept_code`); an **undefined pipe dependency** → `pipe_validation` / `unresolved_pipe_dependency` (with the referencing `pipe_code` and the missing dependency in the new `missing_pipe_code` locator); an **unknown pipe `type`** (a pydantic discriminated-union tag failure) → `blueprint_validation` / `unknown_pipe_type` (with the `pipe_code`). New `PipeValidationErrorType` values: `unresolved_concept`, `unresolved_pipe_dependency`, `unknown_pipe_type`. New `validation_errors[]` locator field: `missing_pipe_code`. `ConceptLibraryError` now extends `LibraryLoadingError` so it carries the per-reference structured items through the existing error cascade (its raised type and message are unchanged; sites that pass only a message behave as before). Machine consumers of `validation_errors[]` get `error_type` + locators for these cases instead of only a `message`.+- **Structured validation errors:** Bundle validation failures now emit categorized `validation_errors[]` items with identity locators, so machine consumers can read `error_type` and locators instead of parsing text. Categories: unresolved concept reference (`pipe_validation`/`unresolved_concept` with `pipe_code`, `concept_code`, `field_name`; or `blueprint_validation`/`unresolved_concept` with owning `concept_code`), undefined pipe dependency (`pipe_validation`/`unresolved_pipe_dependency` with `pipe_code` and the new `missing_pipe_code` locator), and unknown pipe type (`blueprint_validation`/`unknown_pipe_type` with `pipe_code`).+- **New error locators and types:** Added the `missing_pipe_code` locator field and the `PipeValidationErrorType` values `unresolved_concept`, `unresolved_pipe_dependency`, and `unknown_pipe_type`.+- **String utilities:** Added `pluralize` and `count_with_noun` to `pipelex.tools.misc.string_utils` for correct CLI output grammar (e.g. "1 pipe" instead of "1 pipe(s)").+- **Documentation:** Documented the 0/1/2 exit-code policy in `docs/under-the-hood/error-model.md` and added `wip/structured-validation-errors-deferred-findings.md` tracking deferred follow-ups.-### Changed (pre-1.0 breaking)+### Changed-- **Validate exit-code policy (0 / 1 / 2)** — the `validate` surface (both the bare `pipelex validate {bundle,method,pipe}` group and `pipelex-agent validate`) now exits with three codes mirroring the hosted `/validate` 200-verdict-vs-non-2xx-no-verdict split: `0` = valid, `1` = a produced negative verdict (invalid bundle, or valid-but-not-runnable without `--allow-signatures`), `2` = no verdict (bad args, unresolvable target, setup/internal error). Previously every failure exited `1`. Notably, `pipelex validate bundle` **directory-resolution failures** (no `.mthds` found / multiple `.mthds` and no default `bundle.mthds` / a path that is neither a file nor a directory) now exit **2** instead of **1**. Both `1` and `2` remain non-zero, so consumers that only test zero-vs-non-zero are unaffected. The verdict remains in the structured `is_valid` field — machine consumers should read it rather than branch on the exit code.-- **Validate Markdown renderer relocated** — `format_validate_markdown` moved from `pipelex.cli.agent_cli.commands.validate._output_helpers` to the public, non-CLI module `pipelex.pipeline.validation_render`, so other surfaces (e.g. `pipelex-api`'s `/validate` opt-in `rendered_markdown` extra) can import it without pulling in the CLI/Typer stack. Output is byte-identical; only the import path changed.+- **Validate exit-code policy (pre-1.0 breaking):** Both `pipelex validate` and `pipelex-agent validate` now use a three-tier exit code mirroring the hosted `/validate` API: `0` = valid (including valid-but-not-runnable with `--allow-signatures`), `1` = negative verdict (invalid, or valid-but-not-runnable without `--allow-signatures`), `2` = no verdict (bad arguments, unresolvable target, or setup/internal errors). Consumers testing zero vs. non-zero are unaffected; machine consumers should rely on the structured `is_valid` JSON field.+- **Relocated markdown renderer:** Moved `format_validate_markdown` from CLI internals to the public `pipelex.pipeline.validation_render` module so other surfaces (e.g. the `pipelex-api` `/validate` route) can use it without Typer/CLI dependencies, and added `render_invalid_validation_markdown` for invalid verdicts.+- **Error class hierarchy:** `ConceptLibraryError` now extends `LibraryLoadingError` (instead of `LibraryError`) so it can carry per-reference structured items through the existing error cascade.+- **Strict protocol arguments:** `PipelexMTHDSProtocol` now rejects `extra` extension arguments, raising `PipelineRequestError`, since the local runtime defines no extension arguments.+- Bumped `mthds` dependency from `>=0.4.1` to `>=0.5.0`.### Fixed-- **`pipe_code` dropped on categorized pipe blueprint errors** — the blueprint validation-error categorizer matched the wrong pydantic `loc` key (`pipes` instead of the actual blueprint field name `pipe`), so every categorized pipe blueprint item (e.g. `missing_input_variable`) silently lost its `pipe_code` locator. It now populates correctly.+- **Dropped `pipe_code` on blueprint errors:** The blueprint validation-error categorizer matched the wrong Pydantic `loc` key (`pipes` instead of `pipe`), causing categorized items (e.g. `missing_input_variable`) to silently lose their `pipe_code` locator; it now populates correctly.+- **CLI output grammar:** Validation CLI output now uses the new string utilities, fixing awkward pluralizations (e.g. "Validated 1 pipe(s)" is now "Validated 1 pipe").## [v0.34.0] - 2026-06-17diff --git a/pyproject.toml b/pyproject.tomlindex 7d663aad5..798ade004 100644--- a/pyproject.toml+++ b/pyproject.toml@@ -1,6 +1,6 @@[project]name = "pipelex"-version = "0.34.0"+version = "0.35.0"description = "Execute composable AI methods declared in the MTHDS open standard"authors = [{ name = "Evotis S.A.S.", email = "[email protected]" }]maintainers = [{ name = "Pipelex staff", email = "[email protected]" }]diff --git a/uv.lock b/uv.lockindex f2445978e..c9e7024f3 100644--- a/uv.lock+++ b/uv.lock@@ -3693,7 +3693,7 @@ wheels = [[[package]]name = "pipelex"-version = "0.34.0"+version = "0.35.0"source = { editable = "." }dependencies = [{ name = "aiofiles" },