Repository navigation
v0.11.0
0.11.0
Tracked API arguments now propose their OAS destinations and original sources together as one construction plan. Core checks each destination/source pair, assembles original values through explicit item/property mappings, and validates the resulting request and source receipts. A destination-only choice can no longer freeze the next model call into a source contract with no possible answer.
Finite declared input roots retain OAS-compatible source choices. Generic descendant construction is available only under roots whose original OAS permits objects or arrays. Scalar-only calls do not receive an unrelated global JSON candidate catalog. Wrong message attribution reports the original message identities containing the exact complete literal as rejection facts; code never reassigns a source, splits a comma list, coerces a number to text or invents missing input.
Compatibility
Public argument input/result shapes are unchanged. Core adds listApiLiteralContainerTargets through its public export. Custom models and test doubles must return the complete existing literalInputs/literalSources proposal in generate_api_arguments; the former select_api_literal_targets call is removed. Each attempt uses at most one tracked literal call, while optional enum interpretation may add one call. Fully bound/confirmed inputs remain code-only. Legacy untracked value generation keeps its existing protocol.
The library adds no hidden retry. Hosts own explicit bounded replanning, progress, source identity and budgets. The example graph retains rejection accounting while forwarding only the immediately preceding rejection for the unchanged source. Transport, authentication, configuration and enum errors remain separate failures.
Verification and limitations
The verification record distinguishes source checks, independent package consumption, isolated n8n execution and private live-model checks. The existing Ajv prototype-key runtime regression remains unresolved. Model semantics can still be wrong, and a bounded host may exhaust its attempts; validated provenance and types do not prove business intent.
Private messages, OAS documents, credentials and host application code are excluded. Public installation, full hosted workflow generation, remote registration, business API execution and deployment are separate checks.