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.

Update README and deferred-step-f-notes with release status and follow-up actions for pipelex 0.38.0 (#1034)

Louis Choquel0b5a10971b73
diff --git a/wip/optionals/README.md b/wip/optionals/README.md
index 9c124721f..a75b03024 100644
--- a/wip/optionals/README.md
+++ b/wip/optionals/README.md
@@ -8,7 +8,7 @@
## What comes next — three streams
-1. **Release + conformance de-gate — no new plan needed.** Merge PR #1021, cut the pipelex release carrying optionals, pipelex-api re-pins to it; then run the gate-removal checklist in [deferred-step-f-notes.md](deferred-step-f-notes.md) (remove the `OPTIONALS_PENDING_FEATURE` gates, `make validate-error-qa`). Mechanical once the release exists.
+1. **Release + conformance de-gate — DONE (pipelex 0.38.0 / pipelex-api 0.8.0).** The gate-removal checklist in [deferred-step-f-notes.md](deferred-step-f-notes.md) was run against the released runtimes: `OPTIONALS_PENDING_FEATURE` removed, six QA cases generated, probe-skips dropped, whole optionals conformance surface green on both arms. The same pin bump also required reconciling the (separate) PipeSignature-tag retirement in the conformance signature fixtures — see the deferred-step-f note for that + the follow-ups it surfaced (plxt schema propagation, the stale `pipelex#996` gate, the `-L`-path static-pass categorization bug).
2. **Cross-repo optionals wave — plan to write.** Scope: mthds spec pages, mthds-python `absences` ledger on `DictWorkingMemoryAbstract` (un-gates the `_run_core_api.py` absent arm back here), mthds-js type mirrors, mthds-ui (skipped nodes, optional edges, `skip_reason`, the `conceptRefs.ts` parse-to-null bug), vscode-pipelex (grammar, semantic tokens, the Rust `strip_concept_qualifiers` bug), pipelex-api response models (`warnings` + contract `optional` flags), mthds-plugins skills. **Gated:** lands after the Required-main-stuff Phase 3 sweep (same mthds spec pages) and the release — except the two syntax-highlighting handoffs, which are ungated and already written up (workspace root `../wip/optionals/`).
3. **Phase 2 — plan to write, in-repo and ungated.** The PipeLLM/`Text?` maybe-wrapper with reasons + `??` coalescing (per the decision above). Candidate rider: the PipeBatch ledger-parity observability question from the Step F notes.
diff --git a/wip/optionals/deferred-step-f-notes.md b/wip/optionals/deferred-step-f-notes.md
index cdacc5dd7..628c62c36 100644
--- a/wip/optionals/deferred-step-f-notes.md
+++ b/wip/optionals/deferred-step-f-notes.md
@@ -8,11 +8,24 @@ Found while ground-truthing the `optional_input_unguarded` conformance fixture.
## Conformance optionals coverage is pinned ahead of the runtime — remove the gates at release
-All new conformance coverage (the `CATEGORIZED_VALIDATION_ITEMS` rows, `tests/pipelex_api/test_validate_optionals.py`, `tests/pipelex_api/test_validate_warnings.py`, `tests/pipelex_agent/test_validate_optionals.py`, and the QA-corpus cases) is gated on `OPTIONALS_PENDING_FEATURE` because the sibling venvs (`pipelex/.venv`, `pipelex-api/.venv`) run the released pipelex without optionals. The gated CLI-arm coverage has been validated LIVE against this branch via `CONFORMANCE_CLI_PIPELEX_AGENT=$workspace/_optionals/.venv/bin/pipelex-agent` (all categorized rows + both warnings tests pass, zero skips), so the gates are known non-vacuous. Once a pipelex release with optionals ships **and** pipelex-api re-pins to it:
+**DONE** (pipelex 0.38.0 + pipelex-api 0.8.0). The gate-removal checklist below was executed against the released runtimes. `OPTIONALS_PENDING_FEATURE` is gone; all six optionals QA cases + the categorized rows + the warnings tests are ungated and pass on both arms (agent-CLI and hosted HTTP), zero skips. The generic gate infrastructure (`pending_feature_skip_reason` / `runtime_supports_case` and the `pending_runtime_feature` field) was kept — it is independently harness-tested and still live for the `pipelex#996` QA gate, so it stays as dormant, reusable infra (no row/case sets it for optionals anymore).
-1. remove `pending_runtime_feature=OPTIONALS_PENDING_FEATURE` from the table rows and QA cases (the documented marker-removal policy),
-2. run `make validate-error-qa` in `conformance/` to generate the committed artifacts for the six new cases,
-3. drop the probe-skips if desired (they self-deactivate, but the gate comments say to remove them so regressions become visible).
+Two things came along for free with the same 0.35→0.38 pin bump and were reconciled in the same pass (they are NOT optionals):
+
+- **PipeSignature-tag retirement.** 0.38.0 rejects `type = "PipeSignature"` (`unknown_pipe_type`, "no longer a pipe type"); a signature is now a **type-less** pipe (no `type`, no implementation). The stale fixtures `pending_signature_bundle.mthds`, `valid-error-qa/cases/valid_pending_signature.mthds`, and the inline `_SIG_BUNDLE` in `tests/pipelex/test_validate_all.py` were modernized to type-less. The shipped verdict contract was confirmed and kept: a pending signature is `is_valid=true` in BOTH strict and `--allow-signatures` modes, gated only via exit code (strict→1, `--allow-signatures`→0) — `is_valid` ≠ `is_runnable`.
+- **Benign 0.38.0 corpus wording refreshes** in a few unrelated cases (`invalid_unresolved_concept*`, `valid_no_main_pipe`, `valid_runnable`) — verdict/category/error_type unchanged (the generator drift-check passes), only message wording.
+
+Open follow-ups surfaced (NOT done here — flagged to route):
+
+- **plxt/vscode-pipelex schema propagation.** pipelex 0.38.0's regenerated schema DOES carry `PipeSignatureBlueprint` (type-less, no required `type`), but the plxt-bundled schema is stale and rejects type-less bundles — an `mthds-schema-sync` propagation item (cross-repo wave).
+- **`pipelex#996` QA gate is now stale.** 0.38.0 emits `blueprint_validation / batch_item_name_collision` structured, so `invalid_batch_item_name_collision`'s `pending_runtime_feature="pipelex#996"` gate is dormant; per the marker-removal policy it should be dropped to close the invisible-regression window.
+- **`-L` directory-load path drops structured `error_type` for static-pass validators.** `library_manager.py:824` (`except ValidationError`) stringifies static-pass `PipeValidationError`s (e.g. `optional_output_required`, `optional_input_unguarded`) instead of categorizing them, so a `-L`-loaded bundle degrades to an uncategorized `blueprint_validation` residual — whereas single-file CLI and HTTP `mthds_contents` both categorize correctly. Latent pipelex bug (pre-existing, predates optionals), independent of this task.
+
+### The checklist as executed
+
+1. removed `pending_runtime_feature=OPTIONALS_PENDING_FEATURE` from the table rows and QA cases (the documented marker-removal policy),
+2. ran `make validate-error-qa` in `conformance/` to generate the committed artifacts for the six new cases,
+3. dropped the optionals-specific probe-skips (conftest `is_valid` probe → hard assert; agent `exit_code` probe → removed) so regressions become visible.
## PipeBatch compaction does not ledger the dropped branches (PipeParallel does)