Export saved-runtime-state loader subgraph

docs/rehost-queue.md

@@ -408,6 +408,13 @@ Working rule:
     `0x00443a50` at depth `3`, giving a 343-node / 989-edge bringup-refresh surface that is
     easier to work from than the broader kind-`8` startup export when the immediate question is
     just ordering and neighboring refresh owners.
+  - the saved-runtime-state loader is boxed in one step lower now too:
+    `artifacts/exports/rt3-1.06/world-load-saved-runtime-state-subgraph.{dot,md}` seeds
+    `0x00446d40` at depth `3` and shows the loader directly reaches
+    `0x00433130 scenario_event_collection_refresh_runtime_records_from_packed_state`, but not
+    `0x00432f40`. That shifts the remaining ordinary kind-`8` question upward: the unresolved
+    service-vs-restore ordering is now specifically inside `0x00443a50`, not inside the loader
+    itself.
     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:

docs/shell-load-graph.md

@@ -220,3 +220,25 @@ python3 tools/py/export_function_subgraph.py \
   --depth 3 \
   --title "World Entry Bringup Refresh Subgraph"
 ```
+
+There is now also a saved-runtime-state loader export for the level below bringup:
+
+- artifact:
+  - `artifacts/exports/rt3-1.06/world-load-saved-runtime-state-subgraph.{dot,md}`
+- seeds:
+  - `0x00446d40`
+- depth:
+  - `3`
+- current size:
+  - `346` nodes / `934` edges
+
+Generate it with:
+
+```bash
+python3 tools/py/export_function_subgraph.py \
+  artifacts/exports/rt3-1.06/function-map.csv \
+  artifacts/exports/rt3-1.06/world-load-saved-runtime-state-subgraph \
+  --seed 0x00446d40 \
+  --depth 3 \
+  --title "World Load Saved Runtime State Subgraph"
+```