Repository navigation
Align template and inline environment initialization - #39
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.
A Session that referenced an Environment Template previously rejected inline env, files, setup commands and packages. It now composes those fields according to owned official API observations on the fixed 3.13.0 baseline: env overlays by key, files and commands replace complete lists, and packages select per manager. Omission/null inherits and an explicit empty list clears its field.
Composition reuses the shared resolver, validators and encrypted Session transaction. Caller intent remains distinct from frozen configuration, so retries survive template/source deletion without changing committed initialization. There are no Runtime, Provider, adapter or schema-migration changes.
Validation
Null network and other unqualified list semantics remain outside this batch. This is bounded protocol alignment, not full compatibility.
Fresh independent GPT-6 Astra high blind review covered all 11 files and acceptance evidence, with no actionable findings. Owned test resources were cleaned up; skipped optional native probes and retained fixture failures are documented.
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.