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 the ts-emission-gate follow-up landing
Louis Choquel940971f4992a
diff --git a/wip/ts-zod-wire-null/plan.md b/wip/ts-zod-wire-null/plan.mdindex 1b9ad9c2d..82b0e54b9 100644--- a/wip/ts-zod-wire-null/plan.md+++ b/wip/ts-zod-wire-null/plan.md@@ -178,3 +178,5 @@ Phase 4's follow-through is complete on both counts. The consumer cleanup was fi**The fix is merged but not delivered, and the distinction matters for both dependents.** The merge is on `dev` and has not reached `main`, so no release carries it yet; `pipelex` has one open release item, [L-260828-f4e88c](http://localhost:4747/i/L-260828-f4e88c), cut for the input-form work, and a release train that departs after this merge would carry this fix too. Neither dependent can act on the merge alone: both the starter cleanup and the skill's helper-removal consume the projection through the hosted `POST /v1/codegen` route, so the real gate is a `pipelex` release plus an api-dev deploy, not this merge.**Two defects found during the campaign were deliberately not fixed in it, and both remain open.** [L-260901-47759d](http://localhost:4747/i/L-260901-47759d) is the recursive concept's declared-type line overflowing prettier's print width, which makes `codegen check` flag an untouched file as hand-edited; it is pre-existing, and the deferral argument is in the pre-landing review checkpoint above. [L-260901-26da36](http://localhost:4747/i/L-260901-26da36) is the structural one — the TypeScript target still has no always-on guard that *parses* its emission. This campaign advanced it rather than closing it: `test_emitted_ts_never_breaks_a_line_inside_a_string_literal` now runs in CI with no node toolchain and reddens on the whole unterminated-literal class, but the real gate, `test_emitted_ts_is_prettier_clean`, is still skipped wherever prettier is absent, which is CI and every machine here. The `_ts_object_key` deferral recorded in round 2 belongs with it.++**Follow-up: the structural one is now closed.** [L-260901-26da36](http://localhost:4747/i/L-260901-26da36) was completed by `pipelex#1184`, squashed onto `dev` as `753737d459ddcdebbdaafd8eb53ecd7aa314ece7`. `make test-ts-gates` provisions a pinned prettier and zod into a gitignored `.ts-toolchain/` and runs the codegen suite with `PIPELEX_REQUIRE_TS_GATES=1`, under which the two toolchain-dependent gates fail instead of skipping; the `Tests (ts emission gates)` CI job runs that target behind `actions/setup-node`, and `Tests (all)` requires it. The `_ts_object_key` deferral recorded in round 2 was picked up in the same PR — the new gate reddened on it before the fix was written. [L-260901-47759d](http://localhost:4747/i/L-260901-47759d), the recursive-concept print-width overflow, is still open, and the deliberate absence of a `tsc --strict` gate is recorded with it in `docs/contribute/typescript-emission-gates.md`.