fix: preserve wrapper session safety invariants - #243
Merged
Conversation
ejgallego
changed the title
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
1 participant
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.
This PR makes wrapper session ownership explicit and fail-closed, so one foreground owner controls one frozen workspace while ordinary calls only attach and abnormal state remains fenced for exact recovery.
It provides serve, status, and stop lifecycle vocabulary; explicit machine selectors; single-workspace schema 3 descriptors; authenticated request routing; private session storage; kernel locking; draining fences; typed stop outcomes; and conservative crash recovery. Session paths retain canonical identity before and after creation, failed drains cannot clear authority, and CLI and MCP share semantic operation descriptions without sharing transport ownership.