Skip to content

v0.4.1

Choose a tag to compare

@carefreelife98 carefreelife98 released this 27 Oct 06:37
· 38 commits to main since this release

openapi-flow 0.4.1

Original request sources and scoped material recovery remain separate from planning
context. Keep Core, LangChain and n8n on the same version:

Source-grounded request inputs

Optional literalSourceMessages supplies the original WorkflowSourceMessage
records independently of formatted scenario context. Exact literal citations,
message identity, value types and coverage are checked against those records.
The code does not unwrap arbitrary JSON or combine separate original messages.

Enum interpretation uses the same explicit original sources. The model selects
existing OAS candidate identities and source spans; code copies the original OAS
value without changing its type. A valid source span does not prove that the model
understood its business meaning. Callers remain responsible for supplying genuine
original messages rather than generated summaries.

Scoped recovery

Native selection and gap review accept explicit same-request contract rejections.
Helpers retain the original invalid output and validation reason only when its
source fingerprint and stage still match. Transport errors, cancellation and source
changes are not corrective proposals. Each library call still runs once. The
optional example graph checkpoints rejections and charges every correction to its
existing shared invocation limit; genuine unsupported work and business questions
are not automatically bypassed. Existing mid-run example checkpoints without the
new rejection ledger must not be silently migrated.

API material repair accepts a separate original literal context and validates its
target and original contracts. Existing native dependency/parameter repair preserves
node identity and declared ownership, re-derives output contracts and checks downstream
references. These are composable functions, not a hidden retry or user-interrupt policy.
The example preserves repair descriptions in serializable checkpoints and receives
executable contracts through runtime configuration.

Compatibility, verification and limitations

The new source context is optional. Existing reply-only callers retain their output
shape; callers opting into explicit messages must preserve original message identities
and citations. No external dependency version changes are included.

Strict build/types, Lint and formatting passed. Enabled unit tests: 1,757/1,758,
with only the retained Ajv failure and zero skips/cancellations. Original OAS:
59 checks across four private documents. All 33 isolated runtime command suites,
the strict independent packed-consumer install and three archive inspections passed.
Focused native contract/recovery and actual-graph checks passed 41 tests.

The enabled Ajv properties.__proto__ limitation remains. Upstream SDK Zod 3 audit
findings remain High 5, Moderate/Critical 0, with unchanged advisory/dependency
records versus 0.4.0. The automatic candidate report remains blocked by the audit;
no clean audit or complete natural-language workflow quality result is claimed.
The fresh public-0.4.0 original-five baseline produced 0/5 workflows in each mode,
all before connection planning. Post-correction five-scenario quality and private-host
recovery integration remain unfinished. This release does not deploy a company service.