Skip to content

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.

docs(wip): close checkpoint 2 of the open-native-inputs plan

Louis Choquelb87cb43f1a8f
diff --git a/wip/open-native-inputs/plan.md b/wip/open-native-inputs/plan.md
index 9650873d0..22371dc27 100644
--- a/wip/open-native-inputs/plan.md
+++ b/wip/open-native-inputs/plan.md
@@ -64,6 +64,8 @@ Branch `fix/Dynamic-prompt-classification`, PR → `dev`. Independent of Phase 1
**Checkpoint 2** — PR 2 open. Record review outcomes and anything deferred.
> **Checkpoint 2 recorded (2026-09-01):** PR [#1179](https://github.com/Pipelex/pipelex/pull/1179) open against `dev` (branch `fix/Dynamic-prompt-classification`), full `agent-check` + `agent-test` green. R3 implemented as planned: both analyzers return early for a dynamic root concept before any `is_compatible` call — the image analyzer returns `(False, False, False, None)`, the document analyzer `None` — and `| with_images` on `Dynamic` still raises `WithImagesFilterError`. The integration regression lives in `tests/integration/pipelex/pipeline/test_bundle_validator.py` (chosen because PR 1 does not touch that file, so the two PRs cannot conflict there). The compatibility-as-identity sweep across the other operator sites is filed as L-260901-605377. Review outcome pending on both PRs; Phase 3 stays gated on both merges.
+>
+> **Checkpoint 2 closed (2026-09-01):** PR [#1179](https://github.com/Pipelex/pipelex/pull/1179) merged to `dev` as `789726a`, all checks green, and L-260831-635398 is closed `fixed` with that merge as evidence. R3 landed exactly as ruled; nothing was amended in review. One live behaviour is deliberately given up and is now named in `CHANGELOG.md` and `docs/building-methods/pipes/pipe-operators/PipeLLM.md`: an `ImageContent` shaped into a `Dynamic` slot used to reach the model through the DIRECT reference the analyzer wrongly recorded, and now renders as text with no warning. Whether attachment should also be decided at run time, or the silence become a warning, is filed as L-260901-45becb. The merge has not reached `main` — the release that publishes it is L-260828-f4e88c. Phase 3 now waits on PR 1 alone.
## Phase 3 — reopen the corpus coverage (after both PRs merge)