Repository navigation
feat(session): register retained callers before suspended execution - #812
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.
The caller primitive accepted an externally supplied retained process handle but had no native launch boundary that registered its own child before execution. An inactive internal launcher now pins the selected image and ancestors, creates the child suspended in an owned kill-on-close Job with arbitrary handle inheritance disabled, verifies the actual image and retained registration, and then resumes its initial thread.
Disposal revokes registration and requires retained root exit and queried Job-empty closure. Natural root exit and owner-death behavior have separate native controls. The fixed-image, expected-hash and session inputs belong to trusted native code; protected installation, principal policy, environment and dependency provenance remain unqualified. Program and production-launch flags remain inactive.
Validation: independent Astra requirements and engineering PASS on the eight-file freeze; eight native controls with actual wrong-image/registration refusals, inherited-sentinel and removed-suspension mutants, descendant cleanup, owner death and pin release. After merging current token master, the combined caller, endpoint and launcher suites passed63/63 without skips and the actual Windows session sidecar built. Final source/Git bindings and receipts are retained for integration review. The five required CI contexts must pass before merge.