v1.4: trace missing Right-side parent transforms

[Datamining00]

Diagnostic derivative of v1.4-baseline-warning-render for the Right-side rear text that is incorrectly rendered over the character's face.

Confirmed from the real-save GroupNode trace

The supplied Livery_0343_20260812130034 / C_livery trace identifies the exact misplaced text groups.

• Right c4g92 has 9 direct shape children whose shape-word sequence spells FLAMEHAZE.
  • It is a direct child of the section-level group (c4g1).
  • Its effective transform remains near the section origin.
  • It is structurally unusual: flags=0xff, marker=0002000100000003.
• Right c4g93 has 22 direct shape children whose sequence spells THOSEWHOHUNTANDDESTROY.
  • It is also a direct child of c4g1 and remains near the section origin.
• The equivalent Left-side text groups are correctly nested beneath outer group c3g94.
  • c3g94 carries the large placement transform (x=371.5, y=9.0, scale≈1.03).
  • Its 9-letter and 22-letter descendants are therefore moved to the correct outer body location.

This rules out source-offset sorting and the renderer's matrix multiplication/decomposition as the primary cause. The structural fault is now localized to group-tree ownership / a missing or misparsed outer parent transform in the Right section.

Raw transform diagnostic v2

The previous JSON intentionally contained the decoded tree but not enough raw bytes immediately before the anomalous group to prove which parser token should create/retain the missing outer parent.

This update therefore remains diagnostic-only and adds:

• raw byte windows around groups selected generically by structural anomalies (flags==0xff or the extended livery marker);
• neighbouring groups in source order;
• every read_livery_transform interpretation found in those windows;
• counted/markerless group candidates and inline-transform metadata;
• output appended to the same *-group-transform.json as raw_transform_anomalies.

No car ID, creator, section name, phrase, shape ID, or source offset is hard-coded. No decoder state, layer order, transform, or renderer output is changed by this diagnostic.

Validation

• Windows CI: success.
• Full regression suite: 171 tests, OK.
• PyInstaller one-file build: success.
• EXE SHA-256: 549b01fddd5a9a1040514581c1dbabeca3e9d86b01962318442a0cb98b96d130.
• Artifact ZIP SHA-256: bc1d2fe82e5d5668037c1a5030fbb570055fa85c5a4d005139b77cf39084d305.

Next evidence required

Run the updated diagnostic once on the same livery and open/render Right. Then provide the regenerated *-group-transform.json. The new raw_transform_anomalies records will be used to determine the exact parser rule before any behavioral fix is applied.

This PR remains draft until that raw-byte interpretation is proven and visually validated.