Repository navigation
Share owned policy transport between native startup and bounded qualification - #34
Merged
EHotwagner merged 11 commits intoOct 4, 2026
Merged
Conversation
EHotwagner
deleted the
routine/bar-shared-policy-transport-final-source-20261004
branch
October 9, 2026 16:28
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 seed startup and the finite no-game qualification caller now use one owned apphost launch, pre-exec handshake, framed parser and settlement path. The native context retains actual host/engine liveness and socket guards. The separate policy-only context uses a real worker-owned writable fixture descriptor, admits no native actors or sockets, and bounds qualification to one positive consume plus malformed-request and held-input controls, at most three sequential apphost launches.
Against protected main
794f5d1037fa1d85e2a3312c28a77a487ef59ccf, the complete delta is exactly seven helper-source paths (473 insertions, 59 deletions), including two new caller/control files. The delivery lineage includes the merged PR33 receive-order repair; its ancestry join preserved the selected transport tree before this narrow diagnostic repair. The malformed control requires natural exit 2 and the exact retainedrequest-evaluation/exceptiondiagnostic, with physical custody and byte checks. The new caller requires a private, single-link, one-use admission before creating its attempt root.Validation and coverage:
The genuine successor helper graph has 38 committed modules/fixtures. Retained actual policy restore/build and PE/PDB proof remain valid compilation evidence; fresh derived provenance placement and actual shared transport qualification are separate gates. Live infrastructure-generation inventory/cardinality must be provided by independently reviewed root supervision; checking a pinned census file alone does not supply it. No-game acceptance, native actor pumping, seed attribution, browser authority, requested-unit production and useful play remain unqualified. Post-last-snapshot disconnect coverage and SourceLink remote-content verification remain unknown. Generated profiles, admissions and private evidence are absent from this PR.