v0.4.5

openapi-flow 0.4.5

Changes

• Add N8nNativeFeature.EvaluateResponses and the public
  createResponseEvaluationCapability factory. Scenario-owned rules return
  per-check normal, warning, abnormal or undetermined results and counts.
  A valid adverse observation continues through the workflow.
• Reuse existing IF/assertion strict comparison and original source-contract
  validation. Explicit policies select a scalar value, each array item or each
  object value. Missing optional values and empty iterated collections stay
  undetermined. Array length is a separate measurement; original arrays and
  source pointers remain intact. Unknown identities, invalid contracts/pointers
  and invalid numeric operator inputs remain errors.
• Export evaluation schemas and named parameter/result/policy types from n8n,
  plus createNativeObjectEntrySchema from Core. Local resource references are
  preserved when deriving the value domain of dynamic object entries.

Packages

• Core
• LangChain
• n8n

Compatibility

The feature is additive. Existing IF/assertion false-result behavior remains
unchanged. Default native inventories gain a family; consumers using exhaustive
feature presentation maps must handle EvaluateResponses. A constructible
definition does not prove that any configured source, value or route exists.
Original contracts are bound and checked during configuration and compilation.

The factory requires explicit API/native source arrays. The library supplies no
business threshold, environment value, arbitrary transformation, API call, join
or retry policy. Independent branches require an explicit join before evaluation.
Default evaluation emits one report; explicit linked execution preserves input
item pairing. The implementation uses an official SDK Code node and the shared
comparison runtime, not a replacement workflow engine. Third-party dependency
versions are unchanged.

Verification and known limitations

Strict type/build, Lint, format and actual graph-document checks passed. The
enabled suite passed 1,814/1,815 with the retained Ajv __proto__ limitation and
no skips/cancellations. Existing private original-OAS checks passed 59 cases.
Five isolated n8n 2.37.10 conditions verified unchanged report transport through
a subsequent API, adverse-result completion, missing optional/empty data and
invalid-OAS rejection.

An independent consumer installed all three working-tree archives without
workspace links and passed strict TypeScript with library checks enabled,
including the new public evaluation factory and parameter contract. This is
candidate archive verification, not registry publication or product adoption.

A separate private original-OAS fixture used actual model-generated evaluation
settings for ten fixed API contracts. Three isolated executions each preserved
ten reads, three service result groups and ten evaluations. Its API inventory
and connections were fixed test materials. This is not a new whole-workflow
generation, UI quality or single-pass/incremental comparison result. No business
API was called.

The existing accepted Ajv special-key limitation and upstream dependency audit
warnings remain. This release does not claim a clean audit, complete native
coverage or product deployment. Package publication and product adoption are
tracked separately in the release record.