ArWen 2.1.1

Radar velocity dealiasing has a new default engine, a Rust port of Py-ART's region based method. Identical folds, a fraction of the wall clock, and it keeps the strongest couplets the old engine rejected.

2.1.1 is the published form of the 2.1 train. The v2.1.0 tag was never published.

New

• Default dealias engine region-global: fold for fold identical to Py-ART 2.2.5 on real Level-II volumes, dealias stage 18.3 s to 62 ms, keeps couplet velocities the old engine rejected. --dealias-engine vad-region selects the old solver; --no-dealias-refinement turns the refinement pass off.
• Unfolded gates past 75 m/s are rejected as out of range and counted, never clamped and never passed.
• Correlation coefficient QC at the radar grid build: --cc-qc, off by default, with per moment rules and a tornado debris fringe exemption (--cc-no-tds-fringe-exempt restores the strict rule). Receipts count every kept and turned away gate per radar.
• The old vad-region solver is over 6x faster where it still runs, with every decision identical.
• GPUWM_PERF_TIMING=1 writes per stage wall clock receipts across the observation, verification and I/O paths.
• rw_fieldcmp and rw_runscore: Rust judges for paired frames and paired runs. Output identical to the Python judges, 2.6x and 6.6x faster.
• A stored hour's plots render in parallel: 85 s to 9 s on a 16 core box, every PNG byte identical to the serial render.
• LETKF analyses report solver timing, and tools/da_solve_ab.py A/Bs one analysis between solve devices on byte identical inputs.

Fixed

• The release verifier mishandled bundles carrying more than one library and refused correct artifacts; each library is now proved through the ABI symbol it declares, and vendored artifacts are proved by their contract marker.
• HRRR bridge publication checks hash concurrently; the slowest cases drop from about 270 s to 12 s with identical coverage.
• Two paired run metrics could differ from the reference in the last bit at large sizes; both judges now match at every size.
• The live bundle smoke asserted a stale file count; it now derives from the bundle manifest and passes against the published bundle.

Known issues

• A [tiles] streamed run launched through the prepared forecast routes fails before its first model step with either shipped full radiation option. The failure is immediate and loud, never a silent wrong result. Domains that fit the card run resident and are unaffected. A fix is in progress for the next release.
• The HRRR native route does not expose the [tiles] table.

Full detail in CHANGELOG.md.