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): record Checkpoint 3's landing and what keeps its item open

Louis Choquel794ddc5828c3
diff --git a/wip/open-native-inputs/plan.md b/wip/open-native-inputs/plan.md
index 7de8672f9..fc0e543af 100644
--- a/wip/open-native-inputs/plan.md
+++ b/wip/open-native-inputs/plan.md
@@ -112,6 +112,8 @@ This is the work L-260831-264cbd had to leave behind, and it lands as a fixture
>
> **And the corpus turned out to be four bundles, not three.** `output_bundle.mthds` has been part of the committed mirror capture since the output-form descriptor landed, but it was never added to the command block on the contributor page, to `CORPUS_BUNDLES` in the CI test, or to the agent rules — which named a glob that also swept it in under the wrong order. Every regeneration recipe therefore said three bundles, and following one produces a capture missing every `input_semantics_output.*` pipe. Because `conformance`'s parity check compares the two mirrors against each other and nothing holds a canonical copy, both mirrors shrinking together is green. All four lists now name the four bundles in the mirrors' own order, with `output_bundle.mthds` last so the existing bytes stay stable.
>
+> **Checkpoint 3 landed — the `pipelex` half.** PR [#1187](https://github.com/Pipelex/pipelex/pull/1187) squash-merged to `dev` as `b182fad40`, every check green. L-260902-543ad0 is **advanced, not closed**: items 1 and 2 of its `## What` are done and item 3, the cross-repo re-commit, is what keeps it open. The merge has not reached `main` — the release that publishes this, together with Phases 1 and 2, is L-260828-f4e88c.
+>
> **The cross-repo half is deliberately not in this branch.** A capture must come from a merged `pipelex` `dev`, and the two mirror pull requests have to merge together or `conformance`'s `check-fixture-drift` goes red on `dev` for everyone. Filed as L-260902-f7d9e7 (`mthds-python`) and L-260902-720ec1 (`mthds-js`), both `blocked_by` this phase's item, each carrying the capture's measured summary so the receiving session can check its own regeneration against it. Note for whoever picks them up: cut the recapture branch from `dev`, not from whatever the mirror checkout happens to be sitting on.
## Ledger