Repository navigation
v0.9.0
0.9.0
Connection planning can express a closed API call inventory and exact material values and container sizes as typed, code-checked goals. Hosts opt in with reviewBoundary: 'declared-contract': Core and the model wire schema reject free semantic goals in this mode, while the separate initial coverage review still checks the original requirements. Omission retains the legacy semantic-review contract. Completion assessments cannot override these checks by demanding unrelated proof about hidden service implementation. Explicit unsupported requirements retain their original requirement references, affected nodes, grounds and a classified implementation, material or verification limitation. The verification target is generated configuration under supplied contracts, rather than future response values or hidden handler behavior.
Capability-owned value policies distinguish missing business inputs from generated text and internal references. Native questions identify the exact missing business fields. Undeclared ownership does not authorize a question. Missing internal material is reported as a technical limitation; it is not delegated to the user as a request to invent a schema.
New Core inspection and n8n compilation APIs preserve independently checked execution components while keeping dependent or unresolved graph regions as drafts. They retain actual configuration, prepared API inputs and bindings, diagnostics and accepted wiring. Partial artifacts do not imply that the whole request is fulfilled or that external execution succeeded.
Compatibility
This is a breaking planning-contract change. Use new connection sessions and native question receipts. needs-clarification requires fieldPointers authorized by the capability's parameterValuePolicy. Handle needs-materials in model proposal consumers, NativeParameterMaterialUnavailableError, and WorkflowConnectionUnsupportedRequirementsError. Persisted questions and checkpoints are not migrated automatically. See the contract guide.
Verification and limitations
The source verification record separates static checks, synthetic regressions, real-model probes and isolated n8n execution. Natural-language interpretation remains a model judgment. The existing Ajv prototype-key regression remains unresolved. Configured-source live Dev execution passed the positive, mismatch and missing-price conditions; its wiring was explicitly supplied for the test. Product installation, complete browser regeneration and service deployment remain separate pending steps.
Packages
The release process verifies matching source, tag, public version metadata and downloaded archive integrity before publishing these notes as the GitHub Release. Company product integration and service deployment are separate; no private specifications, credentials, company source or local diagnostic artifacts belong in these packages.