vgsp: fail4 r227 - INPUT-ALIAS-WIT rec census + RETIRE-WIT rec-array witness

r227 verdict inputs: GRID-WIT == the guest's own geometry for every kernel
(gemm_nn w12=0x10 w13=0x4, gemm_nt w12=0x4, softmax w12=0x40, block dims in
w18/w19) - no QMD geometry emission bug; the old consecutive-pair IN-ALIAS
stayed silent.

Two new witnesses for the next capture:

- INPUT-ALIAS-WIT: per-launch census of the copy-in recs (the exact
  VA -> HPA -> content triples the engine reads, inputs included; the fill
  already covers them as recs). Every non-zero rec is compared against the
  last 64: distinct VA -> same HPA is the resolver-aliasing smoking gun;
  distinct HPA with equal content is the upstream-write-clone class. Zero
  pages excluded on both sides. Replaces the consecutive-only check.

- RETIRE-WIT: one line per launch at the retirement wait with n_data,
  n_tracked and the first/last recs' va/reloc_va/bi. r227's numbers are
  impossible under this source (retire n_tracked 4/4/4/1/1/16/16 vs
  copy-in/copy-out 1482/1418/1354/913/864/882/1290 recs for the same
  launch), so either the rec array genuinely aliases reloc VAs at run time
  or the deployed module differs from this tree; RETIRE-WIT shows which in
  one line (sequential in-region rels + n_data=1482 with n_tracked=4 would
  prove the former).

Logging-only; no behaviour change; greens safe. Build green.

(cherry picked from commit 1dbde7967bda4ba51dadf8a96e8aeaacc44c5575)

0 files changed, 0 insertions, 0 deletions