v1.4: trace post-fix livery parent ownership - #29
Draft
Datamining00 wants to merge 4 commits into
Draft
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.
Diagnostic derivative of the parser structural audit.
Why
Audit v2 on the real
Livery_0343sample reportsunframed_transform_candidate_count = 0, whileXANADU / THE NEW WORLDstill renders on the character face. This rules out another still-unframed 16-byte transform as the immediate cause.The remaining defect is therefore narrowed to a different parser class: a transform can be recognized, yet its parent/child ownership may still be wrong when the GroupNode tree is built.
What this branch does
Adds a non-invasive post-recovery ownership trace. For every livery section it records:
implicit_bare_transform_pairparent;The trace is installed after the bare-parent fix and Structural Audit v2, so it captures the tree that is actually flattened and rendered. It does not change decoding, group ownership, transforms, masks, z-order, or rendering.
No car ID, phrase, section-specific coordinate, source offset, or creator is hard-coded.
Expected decision
For the real Right section, the trace will show whether the central
XANADUgroup is actually owned by one of the recovered implicit parents or remains a root sibling. That distinguishes a wrong child-span rule from a different group grammar issue before any additional fix is attempted.Validation
62762f526e5891514f9c69549fcd6fc41554ab650753c547620c751cb387c8f4.aa50104ed5749d91d0584def81fe7e008bbd07ad9380e4cf087e74c378319117.This PR remains draft until the real livery ownership JSON is inspected.