Narrow late region reseed owner strip

docs/rehost-queue.md

@@ -385,6 +385,18 @@ Working rule:
   emitter over the world raster, and `0x0044c4b0` is the center-cell bit-`0x10` reseed pass. So
   the next region slice should stop revisiting those later owners and stay focused on the still-
   missing save-owned latch / severity / stable-id seam.
+- The later class-`0` batch at `0x00438087` is narrowed now too: it walks live class-`0` regions
+  through `0x0062bae0`, rescales the mirrored severity/source pair `[region+0x25a/+0x25e]` from
+  the current value using world-side factors, clamps the result, and then hands the collection to
+  `0x00421c20`; it still does not touch `[region+0x276/+0x302/+0x316]`.
+- Its follow-on `0x00421c20` is bounded as a parameterized region-collection helper rather than a
+  latch owner: it loops the same collection with caller-supplied scalar arguments, dispatches each
+  record through `0x004235c0`, and does not write the pending/completion/one-shot lanes directly.
+- The subsequent world follow-ons are narrower too: `0x00437b20` only stages a world-side reentry
+  guard at `[world+0x46c38]`, iterates the live region collection through `0x00423d30`, and tails
+  into `0x00434d40`, while `0x00437220` rebuilds broader world byte-set state around
+  `[world+0x66be/+0x69db]` and other global collections. Those later branches should stay out of
+  the remaining region latch-restore search too.
 - The widened real-save region trace rules out one more false lead too: on grounded saves the
   `0x55f2` fixed-policy chunk keeps all three reserved dwords at `0x00000000` and the trailing word
   at invariant `0x0001`, so that fixed chunk is not currently carrying the missing latch or stable