Narrow region latch gap to restore seams

crates/rrt-runtime/src/smp.rs

@@ -3670,6 +3670,7 @@ fn build_region_service_trace_report(
                 "atlas already bounds this owner as the direct consumer of [region+0x276], [region+0x302], and [region+0x316]".to_string(),
                 "the new region trace already proves the record envelope and profile subcollection, so the remaining gap is the separate persisted latch seam rather than the service owner".to_string(),
                 "direct disassembly now shows 0x004358d0 calling 0x00420030 twice plus 0x00420280, resolving the linked company through 0x0047efe0, posting company stat slot 4, and then clearing [region+0x276] while stamping [region+0x302] or [region+0x316]".to_string(),
+                "the checked-in constructor owner 0x00421200 now also proves these latches are initialized locally at record construction time, which narrows the remaining gap to post-construction restore or rebuild rather than basic field identity".to_string(),
             ],
             blockers: vec![
                 "persisted owner seam for [region+0x25e/+0x276/+0x302/+0x316]".to_string(),

docs/control-loop-atlas/post-load-generation-paintterrain-and-save-load-restore.md

@@ -83,7 +83,13 @@ The same brush strip is tighter now too:
   `0x0047fd50`, and then tests the candidate status branch through `0x0047de00 -> 0x0040c990`
   before reporting success. The paired selector `0x00420280` is the same scan with the same
   filters, but returns the first matching site id instead of a boolean. So the remaining region gap
-  is now squarely the persisted latch/id seam, not the live peer/service logic itself.
+  is now squarely the persisted latch/id seam, not the live peer/service logic itself. The
+  constructor-side owner is explicit now too:
+  `world_region_construct_entry_with_id_class_and_default_marker09_profile_seed` `0x00421200`
+  clears `[region+0x276]`, `[region+0x302]`, `[region+0x316]`, and neighboring cached bands at
+  record construction time while seeding `[region+0x25a/+0x25e] = 100.0f` and
+  `[region+0x31b] = 1.0f`. That rules out “unknown field identity” as the main blocker for this
+  lane and leaves post-construction restore or rebuild as the remaining closure target.
   That narrows the next closure target
   as well: ordinary-save probes can stop treating `[world+0x66a6]` persistence as the primary
   blocker, because the checked-in negative results on `q.gms`, `p.gms`, and `Autosave.gms` now make

docs/rehost-queue.md

@@ -83,6 +83,13 @@ Working rule:
   `0x0047fd50`, and the status branch `0x0047de00 -> 0x0040c990`; `0x00420280` is the same scan
   returning the first matching site id. So the remaining unknown is the persisted latch/id seam,
   not the live peer/service logic.
+- The checked-in constructor owner `0x00421200`
+  `world_region_construct_entry_with_id_class_and_default_marker09_profile_seed` now also grounds
+  the initialization side of this family: it clears `[region+0x276]`, `[region+0x302]`,
+  `[region+0x316]`, and neighboring cached bands at construction time while seeding
+  `[region+0x25a/+0x25e] = 100.0f` and `[region+0x31b] = 1.0f`. That means the remaining queue item
+  is specifically post-construction restore or rebuild of the same latches, not their basic field
+  identity.
 - Reconstruct the save-side placed-structure collection body on top of the newly grounded
   `0x36b1/0x36b2/0x36b3` header seam so the blocked city-connection / linked-transit branch can
   stop depending on atlas-only placed-structure and local-runtime refresh notes, especially the