Both sweeps look at the new runtime, which is the point of having them

handles.flan joins the ASan and memcheck corpora; pool-stale-region.flan
joins memcheck as a seventh program that aborts by design, for the reason
the other six are kept — a trap that stopped firing would be silent. Clean
both ways.

test/test_sanitize.ml

@@ -126,6 +126,7 @@ let corpus =
     "programs/edn.flan", [];
     "programs/enum-compare.flan", [];
     "programs/error.flan", [];
+    "programs/handles.flan", [];
     "programs/machine.flan", [];
     "programs/math.flan", [];
     "programs/pkg-diamond.flan", [];

test/test_valgrind.ml

@@ -190,8 +190,9 @@ let check label path args ~checks =
    - shadow-pkg.flan, which is a package fragment with no main and does not
      link on its own.
 
-   The six programs here that abort by design — error, exhausted-unhandled,
-   free-all-refused, map-stale-region, slurp-unhandled, stale-region — are
+   The seven programs here that abort by design — error, exhausted-unhandled,
+   free-all-refused, map-stale-region, pool-stale-region, slurp-unhandled,
+   stale-region — are
    kept. A trap is a controlled abort after an fprintf, and "the trap still
    fires, in the same place, with the same message, under memcheck" is worth
    asserting: the region and epoch traps are the runtime's own answer to the
@@ -214,11 +215,13 @@ let corpus =
     "programs/exhausted.flan", [];
     "programs/exhausted-unhandled.flan", [];
     "programs/free-all-refused.flan", [];
+    "programs/handles.flan", [];
     "programs/machine.flan", [];
     "programs/map-exhausted.flan", [];
     "programs/map-stale-region.flan", [];
     "programs/maps.flan", [];
     "programs/math.flan", [];
+    "programs/pool-stale-region.flan", [];
     "programs/pkg-diamond.flan", [];
     "programs/pkg-return.flan", [];
     "programs/pkg-shadow.flan", [];