Repository navigation
v0.13.0
0.13.0
API request planning can propose actual OAS-typed values for all pending calls in one invocation. Core validates each call against its unchanged contract, retains independently accepted calls, and attributes literal values to the original messages in code. The model no longer selects character positions, original-message IDs or lexical source IDs in this opt-in protocol. Declared enum, boolean and null interpretation can be included in the same proposal and is recorded separately from verbatim source evidence.
generateWorkflowApiValues provides shared value planning; generateApiValues provides the same protocol for a scoped call. analyzeApiValueAnswers handles one actual follow-up reply. selectWorkflowApiBindingSources selects producers jointly while callIds can restrict work to pending calls without removing other source candidates. Field binding, cycle validation, confirmation, checkpoints and visible retry policy retain their existing owners.
Identity checks no longer construct complete value/model contracts. JSON-only source consumers avoid lexical catalog allocation. Anonymous standalone validators share a bounded content-and-dialect cache; exported embedded schema IDs remain source-scoped so equal field schemas do not collide in a parent schema. Explicit OAS resource IDs remain unchanged.
Compatibility
These are additive, opt-in APIs. Existing source-selection APIs and legacy fingerprint bytes remain compatible. New value receipts use a distinct contract and must not be interpreted as previous source-catalog receipts. Hosts must migrate their state, independently replay current receipts and start a fresh planning session across this migration. No automatic host migration, hidden model retry, default insertion, type coercion or local package substitution is included.
Value proposals and reply extraction use function calling with strict: false: partial OAS objects must be allowed to omit unanswered fields, while provider strict mode requires every declared object property. Actual field types and enums remain in the supplied schema, and Core performs the unchanged OAS checks per call. This is not a claim of provider-enforced strict enum output or proof of semantic correctness. The joint producer decision uses a closed strict schema.
Verification and limitations
See the verification record. Source tests, an isolated host-consumer patch, private live-model input planning and local n8n execution are separate verification scopes. The existing Ajv runtime failure for a declared __proto__ property remains unresolved. Previously disclosed transitive dependency limitations are unchanged; no new security-audit claim is made.
Product installation is tracked separately in the verification record. Full product generation, remote n8n registration/execution and service deployment are not verified by these source checks. Private original messages, OAS documents, host source, credentials and local artifacts are excluded from public archives.