Use canonical context type authority for provenance resolution - #24
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.
resolve_with_provenancenow queries the canonical type keys already admitted byextract_all_configs, eliminating repeated value scans and owner-type recovery for every field/MRO candidate. Selected field reads, scope/MRO precedence, None inheritance, context constructors, provenance and default factories remain at their existing epochs. There is no new cache or value snapshot; the public manually supplied-map resolver is unchanged.Patch version 1.3.1 is separate from immutable 1.3.0. Installed dependencies remain unchanged pending review.
Validation: 27 existing controls PASS, including canonical map admission, saved restoration/MRO, constructor/factory effects, callable identity and detached mutable aliases. One authentic saved-consumer pair passed exact typed values/provenance/canonical source/ancestor-scope parity and all source/eight-dependency/four-ABI/input/helper guards: Illumination 85.65→67.62 ms; subsequent 3D 224.73→190.59 ms. Normal full Registry READY and parsing were outside the clocks. These are single saved-owner observations, not whole compiler/runtime gains or the main performance route; 3D is not an independent cold-first-job measurement. Arbitrary corruption/rebinding of admitted map type keys during an operation is outside the established law; mutable field values remain live.
Durable receiving and scope.
Closes #23