Repository navigation
v0.7.1
openapi-flow 0.7.1
This release fixes a gap between desired-region validation and the
host's bounded connection-replanning loop. Core exposes typed region validation
failures with the unadopted region and structured violations. LangChain can
replay the captured original selection against the exact current source and
create a checked rejection. The reference host counts that rejection under the
existing budget and supplies only the latest current-revision feedback. It does
not deduplicate, adopt invalid edges, fabricate a patch or retry transport errors.
Connection step results and planning errors include a private proposal-attempt
receipt, with a code-generated ID and the pre-call session/source/revision. The
receipt preserves decoded JSON before port resolution and patch derivation.
Sensitive output is explicitly withheld, and non-JSON output is unavailable.
The reference graph checkpoints the attempt before calling a separate private
sink. Its optional file-store example uses owner-only permissions, atomic record
publication and idempotent same-ID writes. Sink failure resumes without another
model invocation while the host checkpoint remains available.
Compatibility: the model's 0.7.0 desired-region wire format is unchanged. The
rejected-proposal union now also accepts canonical set-region proposals;
consumers of that union must handle this variant. Step results expose the new
receipt. Keep it out of browser events, public state, ordinary logs and prompts.
Hosts must wire their own private sink for durable history. Memory checkpoints
still do not survive process replacement.
Verification includes focused rejection/correction, unchanged accepted state,
shared budgets, source-bound feedback validation, private capture, checkpoint
resume and idempotent file tests. A separate private connection-only live-model
trial captured five original proposals and completed six starts and seven edges
with zero SDK errors or warnings. That trial had no duplicate connection proposal
and did not validate a full browser run, business API execution or n8n execution.
Version-aligned verification passed typecheck/build, lint, formatting, 59 OAS
checks, an independently installed strict consumer and four synthetic n8n
executions (20 local requests). The full suite passed 1915/1916; the existing Ajv
prototype-looking-key failure remains. The audit still reports high 6 and
moderate 11. Library verification is separate from product integration,
browser testing and service deployment.
Packages: