Repository navigation
v0.4.0
openapi-flow 0.4.0
Composable hierarchical planning, explicit boundary intent and source-bound recovery.
Publication and exact source provenance are tracked in the
release record; a library release does not imply a host deployment.
Keep all three packages aligned:
Planning and recovery
Core exposes dependency/goal conflict inspection, source-bound goal/native review
receipts, revisable connection outlines and original-stage material replacement.
Outline bundles retain the global requirements, goals, ports, references and
accepted graph. Scoped writes still pass whole-graph and revision checks.
LangChain exposes independently composable review, outline and recovery calls.
The optional LangGraph example owns scheduling, bounded correction, checkpoints,
failure replay and adoption. No mandatory server or hidden library retry is added.
Selection review is fallible model evidence, not execution approval or a proof of
business semantics. Genuine unsupported work and business decisions remain explicit.
Connection planning selects explicit start/finish intent. Code resolves a unique
declared port and checks the complete proposal. An unconnected node is not
automatically an independent start, and an unused output is not automatically a
finish. Partial work does not place unrelated nodes or become an executable graph.
Official native execution
New adapters use official Edit Fields, Merge and Aggregate nodes for selecting
native fields, explicit string/array length measurement, typed API-array key joins,
exact map-key selection and unchanged native-value collection. Original contracts,
values, types and linked-item ancestry remain checked. Missing values fail rather
than becoming null, zero or a first matching entry. Empty input is not fabricated.
Official-node metadata/configuration/construction helpers use the installed SDK.
They do not infer complete data contracts, grant arbitrary JavaScript generation
or provide automatic planning for every built-in node. Collection is not pagination
or parent-scoped grouping. UTF-16 string length is not a user-perceived character
count or an alternative to OAS validation.
Migration
This pre-1.0 minor release has a required low-level API change:
createNativeParameterGenerationContract now requires planningParametersSchema
alongside the executable capability. Keep model choices separate from the runtime
validator; do not replace the implementation contract with a planning schema.
Higher-level native configuration APIs compose these contracts internally.
Custom provider/test doubles must follow each supplied structured-output schema.
Do not hardcode earlier internal model JSON shapes. Serializable Core connection
sessions and explicit programmatic start/finish patches retain their contracts.
Update custom literals of exported material/description types for their new required
constraint and ownership fields. New options do not authorize automatic defaults.
The public ApiLiteralGenerationOutput union also changes when source tracking or
requested-input tracking is enabled: explicit provided/not-provided presence replaces
the previous flat literal shape. Preserve actually supplied empty values; absence is
not an empty object. The plain { values } mode with both options disabled and the
final ApiCallArguments contract remain unchanged. Follow the updated
input contract guide when supplying a
custom model implementation.
Verification and limitations
Strict build/types, Lint and formatting passed. Enabled unit tests: 1,678/1,679,
with only the known Ajv failure and zero skips/cancellations. Original OAS: 59 checks
across four private documents. All 33 isolated runtime commands and the independent
strict packed-consumer installation/compilation passed. A separate official-node
engine probe passed with five definitions and six instances. Original failing Lint
and stale-fixture logs are retained alongside passing reruns in the detailed record.
The enabled Ajv properties.__proto__ limitation remains. Upstream SDK Zod 3
security findings remain: High 5 with unchanged advisory/dependency records versus
the previously disclosed release, Moderate/Critical 0. No clean audit, dependency
override or exclusion is claimed. The n8n dependency retains its own Sustainable Use License;
this project's code remains MIT.
The original five-scenario end-to-end quality evaluation, remaining native behavior
and private-host hierarchical integration are unfinished. Synthetic compilation,
scripted models and loopback engine checks do not prove natural-language workflow
quality or real-service behavior. Source, npm, GitHub Release, local installation
and service deployment are separate steps; no company push or Cloud deployment is
included.