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

Rule out shellless event metadata clone path

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-21 19:07:07 -07:00
commit 2b57690c1d
4 changed files with 33 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/rehost-queue/periodic-company-control-lane-2026-04-21.md
View file

@ -180,6 +180,22 @@ The ordinary reload path is narrower in the same negative way now too:
So the remaining periodic-company question stays between reload and service: the checked restore
path repopulates the rows, but the later trigger-kind gate lives only in the service strip.
## Deep-Copy Boundary
The one remaining metadata-copy helper is narrower now too:
- `0x0042e050`
- really does mirror the omitted metadata band `+0x7ee..+0x80e`, including `[event+0x7ef]`
- but the current whole-binary caller search only grounds one caller:
`0x004db8b0`, the shell-side `EventConditions.win` clone-selected-event path
- no grounded post-load, world-entry, or periodic-service caller currently re-enters `0x0042e050`
So the control-lane frontier narrows again:
- shell event cloning can duplicate trigger-kind metadata intact
- but there is still no grounded shellless duplication path between reload `0x00433130` and the
late `kind 8` service
## Current Writer Census
The direct writer set for `[event+0x7ef]` is narrower now too: