jan/rrt
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Export saved-runtime-state loader subgraph

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 10:33:50 -07:00
commit 6ac2100ae3
4 changed files with 2918 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/rehost-queue.md
View file

@ -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: