vgsp: fail4 - device-survival chain for the large-buffer sequence + CE both-side op advance

Survival (the death cascade is gone for the full user sequence):
1. pool residue re-seed applies ABSOLUTE (cur=0) - the UVM assert
   (uvm_channel.c:204) that took the device down no longer fires
   (committed earlier in 67148bd8).
2. completion-hint window 10s->1.5s (67148bd8).
3. status-ring free-space discipline in gsp_rm_send_flags: the
   guest's consumption cursor (msgqRxHeader.readPtr at stat+rxHdrOff,
   the msgqTxGetFreeSpace source) gates EVENT posts; events drop
   freely when short, replies wait (bounded) and proceed. A guard
   rejects a cursor the guest cannot be behind (peer > our writePtr -
   the observed mirror tracks writePtr+1 and gating on it silenced
   every wake-up and wedged the clients).
Verified live: mail OK, nvidia-smi OK, victory_matmul OK,
vector_add completes (content still wrong) and victory_transformer
STATUS OK AFTER it - no ISR panic, no guest death, guest ssh alive.

Content: CE linear auto-advance now applied to BOTH offset registers
after each executed op (the driver re-sets one side per op and the
engine advances the other; H2D ops showed an explicit advancing dst
with a fixed src base: the device a held h_a[0..1MB) replicated).
vector_add content still FAIL (~66% bad) - the H2D operand stream
under retry/replay passes is the next lead (opadd rows show five dst
x two src combos with heavy retry multiplicity).

0 files changed, 0 insertions, 0 deletions