vgsp: fail4 r254-r257 - small-fill hold + copy landing ledger + per-launch reloc half

Three fixes on top of 54cf842c, targeting the big-buffer clients:

1. m163 parity for fills: a small failing FILL op with a virtual device
   destination is now held/retried like the small copies (-ENOENT with
   the pins still landing was silently counted nomap and the release
   applied - the 8 MB cudaMemset landed only partially). Verified:
   memcpy_roundtrip now reaches STATUS OK (RT1 bad=0 csum exact,
   MSET bad=0, h_m all 0x5A).

2. svc_copy landing ledger parity with svc_fill: a large virtual-dst
   copy records its landing pages so the GR rec build (m171 ledger
   preference) follows the page the copy actually wrote. streams2's
   c1 moved from a stale-page mix ([28.0, 28.625, 29.25]) to the
   correct-page values ([0.0, 0.125, 0.25]).

3. Per-launch relocated-data base: concurrent forwarded launches
   (streams2's vadd pair) shared one base and their bounce windows
   overlapped; the base now alternates across the grown region's two
   halves keyed to the capture push (retries keep their half), cap
   halved accordingly. Also raise the per-page data attribution budget
   (16 -> 192 pages) for span forensics.

Remaining on streams2/victory_multikernel: the single-slot svc_gr_cand
capture is overwritten by the second concurrent launch before the work
item consumes it - ctaid-probe evidence: c1 == a2+b2 exactly (the
stream-2 result in the stream-1 output) with the in-tree
candidate-overwrite witness present. Next: make the capture a small
FIFO drained in order by the gsp-phys-work item.

0 files changed, 0 insertions, 0 deletions