Extract kind-8 post-reload candidates

artifacts/exports/rt3-1.06/runtime-effect-kind8-post-reload-candidates.md

@@ -0,0 +1,83 @@
+# Runtime Effect Kind-8 Post-Reload Candidate Branches
+
+This note records the currently grounded late bringup branches that remain between ordinary
+runtime-effect reload and the final one-shot kind-`8` service under
+`world_entry_transition_and_runtime_bringup` `0x00443a50`.
+
+## Ordering Boundary
+
+- `world_load_saved_runtime_state_bundle` `0x00446d40`
+  - directly restores event runtime records through
+    `scenario_event_collection_refresh_runtime_records_from_packed_state` `0x00433130`
+  - does **not** directly call
+    `scenario_event_collection_service_runtime_effect_records_for_trigger_kind` `0x00432f40`
+- `world_entry_transition_and_runtime_bringup` `0x00443a50`
+  - owns both the reload phase and the later final kind-`8` service
+  - clears shell-profile latch `[0x006cec7c+0x97]` after that final kind-`8` call
+
+## Still-Plausible Late Branches
+
+Grounded from the current `0x00443a50` note and subgraph artifacts:
+
+- `0x00442c30`
+  - `shell_apply_scenario_name_specific_post_load_world_and_object_fixups`
+  - explicit live event/object mutation branch
+  - already known to rewrite some `[event+0x7ef]` values on scenario-specific cases
+- `0x004354a0`
+  - `world_publish_shell_controller_progress_scalar_from_year_thresholds_or_selector_overrides`
+  - late progress/state publish in the reactivation tail
+- `0x00435603`
+  - `scenario_state_ensure_derived_year_threshold_band`
+  - rerun during late bringup after year refresh
+- `0x00412c10`
+  - `structure_candidate_collection_refresh_named_availability_latch_0x7ac_and_tail_into_cargo_economy_filter_refresh`
+  - rerun after late candidate-side availability restoration/preseed
+- `0x00412bd0`
+  - `structure_candidate_collection_rebuild_cargo_membership_tables_counts_and_scaled_rate_bands_for_all_live_records`
+  - rerun in the same late candidate rebuild band
+- `0x00434130`
+  - `scenario_state_refresh_year_gap_scalar_from_current_year_minus_1850_into_0x4ca2`
+- `0x00436af0`
+  - `scenario_state_refresh_cached_available_locomotive_rating_from_year_baseline_and_live_availability_gates`
+- `0x00437737`
+  - `world_preseed_named_candidate_availability_records_from_live_pool`
+  - late candidate preseed branch called after the second recipe rebuild in the current note
+
+## Weaker / Lower-Priority Candidates
+
+- `0x00433130`
+  - already identified as the ordinary reload owner, not the late materializer
+- `0x00446d40`
+  - already identified as the loader above `0x00433130`, not the final kind-`8` service owner
+
+## Current Bias
+
+- The known title-fixup branch `0x00442c30` remains plausible in general because it explicitly
+  mutates live runtime-event rows.
+- But the shipped add-building carrier corpus currently biases against it as the main explanation
+  for those specific maps:
+  - bundled add-building maps:
+    - `Alternate USA`
+    - `Chicago to New York`
+    - `Louisiana`
+    - `Pacific Coastal`
+    - `Rhodes Unfinished`
+    - `Texas Tea`
+  - grounded `0x00442c30` title list:
+    - `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 leaves the best current recovery question as:
+  - which non-title-specific late bringup branch between `0x00433130` reload and final
+    `0x00432f40(kind 8)` service materializes the ordinary shipped-map mutation-capable records.

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: