Extract kind-8 post-reload candidates

docs/rehost-queue.md

@@ -435,6 +435,21 @@ Working rule:
     late-bringup facts for `0x00446d40`, `0x00443a50`, `0x00442c30`, and the explicit
     `SP - GOLD` / `Labor` trigger-kind rewrites, so the next pass can work from one bounded note
     instead of stitching the same ordering back together from the queue plus function-map prose.
+  - the shipped add-building carrier corpus weakens the current retagger hypothesis too:
+    the six bundled-map titles in
+    `artifacts/exports/rt3-1.05/add-building-compact-dispatch-corpus.json`
+    (`Alternate USA`, `Chicago to New York`, `Louisiana`, `Pacific Coastal`,
+    `Rhodes Unfinished`, `Texas Tea`) do not currently overlap the grounded
+    `0x00442c30` scenario-title set (`Go West!`, `Germany`, `France`, `State of Germany`,
+    `New Beginnings`, `Dutchlantis`, `Britain`, `New Zealand`, `South East Australia`,
+    `Tex-Mex`, `Germantown`, `The American`, `Central Pacific`, `Orient Express`). That biases the
+    remaining add-building source search away from the already-grounded title-fixup branch and
+    toward some other late bringup owner between `0x00433130` reload and final kind-`8` service.
+  - the post-reload candidate set is checked in now too:
+    `artifacts/exports/rt3-1.06/runtime-effect-kind8-post-reload-candidates.md` extracts the
+    currently plausible late `0x00443a50` branches between ordinary reload and final kind-`8`
+    service, with the current bias explicitly shifted away from the known title-fixup branch and
+    toward non-title-specific late bringup owners.
     kinds”; it is the smaller set of scenario-specific records where that sweep explicitly writes
     `[event+0x7ef]` itself or a still-later owner does.
   - two explicit trigger-kind materializations are now grounded inside that retagger: