Repository navigation
Avoid repeated no-op admission in owned source metadata - #740
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.
Owned metadata fallback merges repeatedly scan five component views that the same immutable owner has already admitted. Literal lookup also rescans the same ordered original/scalar namespaces. Reuse those existing owner views and derive one literal namespace, preserving first-use validation, raw mappings, original-before-scalar precedence and every fresh SourceImageIdentity.
Closes #739
Validation: 55 existing owner/provenance controls; exact metadata and fresh-identity checks on 13 captured source cohorts; four strict full-pipeline comparisons against retained qualified native outputs, including exact 3D pixels. Synced with main after #734 and passed its 44 existing spreadsheet export controls.
The captured metadata frontier saves 10.270ms (68.992→58.722ms). No end-to-end speedup is established: illumination total was 0.586→0.592s; 3D total 4.465→4.701s. The 3D processing-contract union rose about289ms versus259ms higher server execution; one pair does not isolate the cause. Both timings exclude server/registry/kernel startup. The attached receiving.json preserves the negative ordinary result. This is removal of redundant admission work, not a claim of a large pipeline gain.