Preserve Tier2 subtype mark pass sequencing

artifacts/exports/rt3-1.06/runtime-effect-kind8-tier2-sequencing-note.md

@@ -38,7 +38,8 @@ The later explicit `0x197` checkpoint at `0x00444ac1` sits:
 - and then `0x00434d40`
 
 So the late Tier 2 strip begins with named-availability preseed and latch refresh, not with the
-shell progress or territory overlay helpers that precede it.
+shell progress or territory overlay helpers that precede it, and it ends with one extra subtype-`2`
+mark pass rather than stopping at the named-availability latch refresh.
 
 ## Internal Tier 2 rebuild relationships
 
@@ -60,8 +61,12 @@ Current grounded internal relationships:
   - rebuilds candidate runtime records from scenario state
   - does not consult the scenario-side recipe-book name at `[state+0x0fe8]`
 - `0x00412fb0`
-  - broader collection load owner that re-enters `0x004120b0`, then `0x00412d70`,
-    then `0x00412ab0`, and only after its later catalog rebuild re-enters `0x00412c10`
+  - broader collection load owner that directly loops through `0x004120b0`, then calls
+    `0x00412d70`, then `0x00412ab0`, and only after its later catalog rebuild re-enters
+    `0x00412c10`
+- `0x00434d40`
+  - late post-refresh sweep over collection `0x0062b26c`
+  - sets `[entry+0x7b0] = 1` for subtype-`2` rows
 
 ## Current recovery implication
 
@@ -75,5 +80,5 @@ The strongest remaining Tier 2 question is sequencing, not naming:
   and the broader load-side rebuild owner
   `0x00412fb0`,
   with the early checkpoint only conditionally refreshing `0x00412c10` but the late checkpoint
-  always rerunning `0x00435630 -> 0x00437737 -> 0x00412c10`,
+  always rerunning `0x00435630 -> 0x00437737 -> 0x00412c10 -> 0x00434d40`,
   rather than on a direct `Warehouse05` availability bit or recipe-book display-name leak.