vgsp: fail4 r249-r252 - GRCE slot-run rule + arg-rec order fix; probe fully greenHEADmaster

Two fixes on top of c66a0172:

1. Slot rule for LOAD_INLINE_DATA runs: in the UVM upload pushes
   each run fills a whole 32 KB slot - its data runs to the next
   run header (or to the next 0x8000 boundary for the last run),
   regardless of the count field (observed slot starts every
   0x8000: cnt=4095 and cnt=2497/2753 variants). Compact pushes
   keep the count*4 reading. The old reading truncated each slot
   run to half its data and walked the tail as methods.

2. Argument-ring order: the bridge's arg-block search must see the
   run's START as the inline-write destination; the new cursor
   advance must not leak into rec->dst_va (an end-of-run dst_va
   made the QMD param patch miss and the engine never consumed the
   launch - regression found and bisected against the pre-session
   ko via victory_mail).

Verified one boot (r251/r252, standard params): ctaid_probe RAWA
0 1 2 3 4 5 6 7 + last8 16376..16383, PROBE1/PROBE2/PROBE2B bad=0;
transformer STATUS OK; victory_mail STATUS OK.

Residual (distinct class, NOT the H2D delivery): streams2
bad=65534, memcpy_roundtrip bad=8388608, victory_multikernel
bad=2883066. Their big spans collapse to a single rec/bank entry in
the launch tables ('bank 0 hit @0x168: VA -> reloc' for one page of
the span) and the engine write-back replicates one page across the
span (OUT-ALIAS-WIT partners) - the original span-aliasing class on
the large-buffer paths.

0 files changed, 0 insertions, 0 deletions