Repository navigation
feat: plan native endpoints and local host bindings - #160
Merged
Merged
Conversation
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.
Native configuration could declare managed env references and routes, but could not connect an environment destination to a typed endpoint or inherit a local host target in a linked worktree. This adds pure endpoint planning and allowlisted host binding resolution to the bundled compiler and CLI.
Service, route and logical host-binding references preserve explicit target kinds. Route endpoints use central origin resolution; service and host addresses stay symbolic until an execution backend can provide them. Project and local bindings merge by logical name with provenance and null removals. An endpoint cannot replace an existing managed destination, and host invocations refuse direct guest-service addressing instead of guessing connectivity.
The transport negotiates the additive endpoint capability and cross-checks emitted targets, original local source claims, calling context and preserved managed baselines. Endpoint-free callers retain their wire/hash behavior. Planning performs no hooks, DNS, trust or runtime effects; native-authored execution remains fenced.
Validation:
Release signal:
featadds offline planning capabilities. Native execution/admission, advanced workload fields and locked adoption remain separate work. Refs HACK-1220.