Repository navigation
Bind native seed preparation to a fixed semantic mapping - #37
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.
Native seed preparation was blocked by the old caller root and unset mapping guards. Bind the fresh caller root and reconstruct one fixed semantic mapping successor without embedding future placement inodes in helper source. Preserve the exact original453 physical rows/ancestors,335 CLR pins and existing physical revalidation; all five new rows still require genuine observed pins before runtime. Native profile JSON now refuses duplicate keys and nonfinite values before validation.
The full delta against protected mainf089 is four helper paths: native caller, mapping validator,15 portable mapping controls and the existing portable-control roster. Controls use synthetic physical rows and explicitly mocked historical digests; committed fixture data contains only semantic source-contract declarations, with no private runtime receipts or original physical metadata.
Validation:114 portable SOURCE controls passed; original physical revalidate body byte-identical; diffcheck passed. No CLR/compiler/Node/Lua/policy/engine/game/browser execution or actual17756-file preparation, policy placement, checksum or native acceptance performed. Native CI already invokes the portable source runner; full native integration/game and new physical closure/current-process joins remain separate gates. Actor/seed/unit acceptance remains pending and useful play0/6.