Skip to content

docs: land the prepare-inputs-selectors tracker #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lchoquel merged 1 commit into from
Sep 7, 2026
Merged

docs: land the prepare-inputs-selectors tracker #24

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion wip/prepare-inputs-selectors/plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
status: active
status: landed
item: L-260829-8a25d5
---

Expand Down Expand Up @@ -45,6 +45,14 @@ Round 1 (2026-09-07) confirmed one defect in two threads and one wrong docstring

Nothing else was raised.

## Landing

PR #21 merged to `dev` as `7b1892f`, closing `L-260829-8a25d5` (kind `fixed`). CI was green across every lint and test job on the reviewed commit; `make agent-check` and `make agent-test` both pass. The merge has not reached `main`, which is the deliberate part — see Release below.

`L-260826-ddd843` was advanced, not closed: the Python half of the two misclassifications is fixed on `dev`, and that item's own bar is a shipped release from **both** SDKs, which neither has cut.

The one thing this landing leaves open for a person: `L-260830-f5b65e` re-points `prepare_inputs` onto `POST /v1/input-form` before the Python release, and it waits on the pipelex-api route `L-260830-352005`.

## Release

None from this item directly. The change lands on `dev` and records its warrant under `## [Unreleased]`; `/release` cuts the version. `L-260826-ddd843` (the two misclassifications) closes only when **both** SDKs have shipped a release carrying the fix — the JS half was still unreleased when this landed.
Loading