Repository navigation
v0.12.0
0.12.0
Workflow input planning can now use one original-source catalog for all pending API calls. Core derives values, types and message ownership from source references. The model chooses OAS target templates and compatible original references together, without separately generating values, quotations, message IDs, fingerprints or shared-input indices.
Core compiles each call against its original OAS, explicit bindings and confirmed inputs. Independently checked calls remain available when another call is rejected. Serialized receipts are replayed against the current originals and call contracts before reuse. Missing values remain input questions; there is no type coercion, source reassignment or invented default.
Compatibility
Core adds the shared catalog, target description, compilation, fingerprint and receipt-validation APIs through its public export. LangChain adds generateWorkflowApiArguments. Existing single-call APIs retain their current protocol. The new planner requires strict function-calling structured output and makes one literal planning call per invocation; optional semantic enum interpretation is separate and may add model calls. Hosts own visible bounded replanning and retention of previously returned, validated batches.
No implicit retry or host migration is included in the library. A whole-proposal syntax error can reject the current batch, and an interrupted invocation has no accepted receipt. Previous validated batches can still be retained by the host. Valid source ownership and JSON types do not prove business intent or remote service availability.
Verification and limitations
The verification record separates source tests, host-consumer checks and a private live-model input-planning probe from product installation and execution. The existing Ajv prototype-key runtime regression remains unresolved. This release does not resolve the separately observed remote model timeout or prove full workflow generation, remote n8n registration or business API execution.
Private original messages, OAS documents, host source, credentials and local artifacts are excluded from the public packages. Product integration and service deployment are separate steps.