Restore environment_value after source layout change - #67
Merged
isomorphisms merged 1 commit intoSep 17, 2026
Merged
Conversation
isomorphisms
force-pushed
the
prelude/restore-environment-value-after-layout
branch
from
September 17, 2026 19:27
0625afb to
49dc31d
Compare
isomorphisms
force-pushed
the
prelude/restore-environment-value-after-layout
branch
from
September 17, 2026 20:21
49dc31d to
3e439eb
Compare
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.
Boundary
Restores the
environment_value : String → IO (Maybe String)surface from #64 in the current buildable_source layout. The later layout rewrite dropped the merged implementation and its receipts.Receipts
Just valueNothing=or NUL are rejected asNothingChez receipt:
This is the same narrow 50-line implementation/test boundary as #64, relocated onto the current tree.
Pre-rebase provenance
Before branch-history cleanup, exact head
0625afbd0d4976485ba766c5c3d3e97ec0099fbbpassed all four current-head workflows:These runs remain evidence for the pre-rebase exact head. They are retained as provenance and are not claimed as verification of any rewritten head.