Repository navigation
refactor: expose transport-independent Node API - #67
Merged
Merged
Conversation
Promote native authentication, CAS and dataset branch capabilities above transport and migrate runtime consumers without compatibility aliases. Share candidate validation, preserve-policy publication semantics, and adapter conformance suites with Gateway while keeping Core and accepted-root policy separate. Co-authored-by: Codex <codex@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Applications and synchronization currently import their node contracts from the transport subtree, while Gateway defines a second set of service interfaces. This change exposes
nodeapiabove transport so in-process services and network adapters can share the same authentication, immutable CAS, and dataset-branch contract.nodeapi, remove the superseded package paths, and retain narrow capabilities instead of a catch-all Node interface.preservepublication policy to the common dataset request and reject merged responses for that policy.heads/branch identities across repeated normalization, binding, HTTP requests, response validation, and CLI branch lookup. Ordinary selectors and their namespace aliases still address the same branch.Validation: full runtime
go test ./...,go vet ./..., Linux build, Windows amd64 cross-build, andgit diff --check; real Gateway in-process/HTTP contract tests passed under an exact local integration workspace. Independent pre-PR review reported no actionable findings.Source-breaking pre-release migration: replace
transport/capabilitywithnodeapi, andtransport/capabilitytestwithnodeapi/nodetest. The Go module remainsgithub.com/dewebprotocol/malt-client.Companion implementation: https://github.com/DeWebProtocol/gateway/pull/32. Browser/Core alignment: DeWebProtocol/malt-ts#15.
Integration validation also passed: independent Gateway/runtime binary Product E2E, exact four-module gate, 292 migration entries, and 15 capability parity vectors.