v0.8.0

0.8.0

Connection completion now reviews the actual configuration against original requirements. Current API arguments, recorded literal attribution, request/response contracts, native settings and the complete operation inventory are available through code-owned evidence. Recorded literals and their original locations are rechecked before a model can approve changed values.

After structural planning finishes, the adapter uses an independent fixed-material review prompt. Prior verdicts and rejected explanations are not supplied as semantic authority. Evidence is selected from a strict map of existing identities and paths; code supplies original quotations and causal node identities. Unreviewed, satisfied, violated and insufficient-evidence states are distinct. Negative reviews and invalid completion evidence stop explicitly instead of consuming an unchanged proposal loop.

The assertion capability exposes its actual success output contract. The optional compose-native-outputs feature builds one named result object from declared native JSON outputs. Code derives its field contracts, waits for its selected inputs, preserves original JSON values and rejects missing or ambiguous source items. Merge append retains its item-preserving behavior. These additions do not change comparison results or API response values.

Compatibility

This is a breaking planning-contract change. Semantic goals require scope; assessments use status and validated evidence rather than satisfied: boolean. The adapter's model selection shape differs from the Core receipt shape. Native extensions create a new source epoch and return previousSession; hosts retaining extension receipts must keep it. Existing connection checkpoints must start a new session. No automatic conversion, inferred scopes or stale receipt recovery is provided. Material-only judgments survive unrelated graph patches; workflow judgments and changed evidence are invalidated.

Hosts must preserve the original literal source messages when supplying attributed API materials and handle WorkflowConnectionCompletionIncompleteError and WorkflowConnectionCompletionEvidenceError. The reference LangGraph implements explicit termination. See the contract and migration guide.

Verification and limits

Final verification results are recorded in the source verification record. Semantic interpretations remain model assessments, not proofs of arbitrary business meaning. Exact-source verification proves the recorded token and its current value; it does not prove that a model chose the correct business role. Planning readiness is separate from external API or engine execution.

The existing Ajv prototype-key regression from the preceding release remains an acknowledged limitation. Do not interpret the focused completion tests as an entirely clean suite or a clean security audit. No company specifications, credentials or private runtime artifacts are included in this release.

Packages: Core, LangChain, n8n.

Source: d58c3e727e4962df0f59e186a07a67784014103a, annotated tag v0.8.0. All three downloaded public npm archives matched the audited local archives exactly. Product/service deployment is separate.