Repository navigation
v0.10.0
0.10.0
Tracked API argument generation now selects concrete request destinations before selecting original value sources. Core resolves each selected path against its remaining OpenAPI value contract, including finite paths through recursive schemas and dynamic properties. JSON source candidates must satisfy that destination's schema. A number candidate is no longer offered for a string array item. Text remains text, and the complete request and original source receipts are still checked without coercion.
Core exports describeApiLiteralTargets and ApiLiteralTargetContract. OAS validation issues retain the concrete failing property or array-item path. The reference host reserves both literal-planning calls before starting dependent argument work.
Compatibility
This changes the tracked model tool protocol and invocation count. Custom models and test doubles must handle select_api_literal_targets, followed by generate_api_arguments when literals are supplied. The public generateApiArguments input and result shapes remain unchanged. Supplied literals use two explicit calls, an explicit no-literal decision uses one, and wholly bound or confirmed inputs use none. Optional enum interpretation can add one call. Update host reservations and use new planning sessions rather than replaying old outputs as destination plans. Untracked legacy value generation keeps its single-call protocol. There is no automatic checkpoint migration, hidden retry or value conversion.
Verification and limitations
See the source verification record. The existing Ajv prototype-key runtime regression remains unresolved. Source membership and type compatibility do not prove semantic relevance. A real-model enum proposal copied an entire answer instead of its valid enum substring; validation rejected it and one explicit, source-checked replan succeeded. The change does not guarantee that a model always follows its output schema on its first attempt.
Private live probes verified new argument generation and six independent Dev reads on real n8n 2.37.10. Their test wiring was explicit, and one test specification declared anonymous access after the actual service accepted an anonymous request. This is not full natural-language workflow regeneration, hosted-product verification, remote registration or deployment. No private specifications, credentials, business responses or company application source are included in this release.
Packages
Source synchronization, the matching annotated tag, public package/archive verification and the published GitHub Release are separate release steps. Product integration and service deployment are recorded separately.
Dependency audit reports 16 affected dependency records (10 moderate, 6 high; no critical). Dependency remediation is not included in this scoped release; a clean security audit is not claimed.