Guard overlay entry points before initialization - #23
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
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.
Summary
Make the public overlay dispatch, candidate-query, and native-call entry points fail closed until overlay_loader_init has activated the loader.
Source and credit
Adapted only from the lifecycle checks in Martin Penkava's PR #16, exact source commit e6809ccf7d778a4c2f32d9e27c0ec31a44cbd2ba. Martin Penkava and the source commit's Claude Fable 5 co-author are preserved with Co-authored-by trailers.
Deliberately excluded
The dirty-interpreter decodable-word fallback, SmackDown-specific work, Vulkan, audio/SPU, GPU primitive sizing, MSVC work, and all other PR #16 changes are excluded.
Validation
Draft for focused review.