mirror of
https://github.com/Cesarus85/ringfall-mjolnir-vr.git
synced 2026-10-29 04:01:10 +01:00
Jonas VolmanandClaude Opus 5
67a1117544
Owner ruling 2026-09-20: land it and re-baseline the fuzzy floor; correct source outweighs a misleading byte score; grant zero exact credit and document the backend artifact. ZERO exact credit. The function stays residual at 24,976 padded bytes and this is not scoreboard movement. ai_debug.c:1100 and :1110 had their colour arguments swapped relative to January. Verified from January's bytes before landing: January pins the color local in EBX for the whole loop body, selecting white, yellow or aqua at 0x5a7, 0x5c5 and 0x5cd, then pushes EBX at the first site and _global_real_argb_blue at the second - the latter immediately followed by push 0x3f800000, the 1.f argument of render_debug_vector. Our source had them exactly reversed. The fix takes a 480-byte window from 431 differing bytes to 13. The floor is numerically worse: padded size goes from 24976 to 25024 and REAL regions from 495 to 529. That previous size equality was never a match - it was the padding coincidence recorded in wave C, whose "the code length comes back" claim was already retracted. The new number is an honest floor measured against correct source. No sibling moved; ai_debug is 59/60 before and after. The 48 bytes are NOT caused by the colour fix. They are an independent branch-shortening FIXPOINT, and that is the reusable finding: of the eight branches where January emits SHORT and we emit NEAR, five have final spans comfortably inside +/-127, and for one of them January's span and ours are the identical 123 bytes. Three seed branches one byte over the line block the other five. It is the largest byte family in the function, has no known source lever, and is invisible to every region metric - trap #6 at scale. It also explains the non-additive sizes earlier waves measured. Corollary that changes the plan here: the 4-byte-short frame is currently paying for the branch tax, so correcting it in isolation makes the function +39 rather than +12. No future wave should attack the frame on its own. Verified: full ninja green, halobetacache 1,460,468 / 7,301 unchanged by this commit, parks 181 active / 0 stale / 0 invalid. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>