# UTFANSWF v23 Row 25 stress-registry executable scope

The shipped stress registry is a preserved v19 artifact. During the v23 bundle audit several active resolver mismatches were identified:

- MHG was described as a ringdown test but the old resolver used the 80-point cosmology/GW vector rather than the Row 23 ringdown data.
- CCG was described as a joint CMB/BAO/SN/JWST fit but the resolver called Row 20, which does not include JWST.
- PMG trusted a static `pmg_status.json` rather than the live FRG and positivity gates.
- CIG trusted a static `cig_status.json` for the spectral guard even though Row 22 now computes the full NZ gate.
- The old Row 25 runner wrote resolved values back into `datasets/stress_report.csv`, mixing inputs and outputs.

v23 keeps the v19 `stress_registry.yaml` and `stress_report.csv` unchanged as provenance, and writes new resolved outputs only under `results/row25_stress/`.

The active six-test aggregation is:

- AHG -> live Row 21 axion root-table stress, with the 10-60 ueV coverage boundary explicit.
- MHG -> live Row 23 Kerr QNM frequency/damping benchmark; echo remains open.
- CCG -> live Row 20 cosmology plus the separate Row 20.4 JWST diagnostic-record result; the historical single joint JWST fit remains open.
- CPG -> direct deterministic checks of the shipped `curvaton_sourced_tensors.yaml` and `de_eft.yaml` values rather than trusting `cpg_status.json`.
- PMG -> live Row 19 FRG benchmark plus live Row 0.2 ANSWF positivity.
- CIG -> live Row 22 NZ slacks/spectral guard; the historical unexplained CI-width statistic remains open.

A Row 25 PASS means the historical registry is reconciled to currently executable v23 gates without stale pass flags or silent input mutation. It does not claim that the missing historical joint/uncertainty/echo/full-band subtests have been executed.
