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

Split tier2 kind-8 setup bridge fields

Browse source
This commit is contained in:
Jan Petykiewicz 2026-04-19 11:39:03 -07:00
commit d3a54b82ca
2 changed files with 36 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/rehost-queue.md
View file

@ -577,7 +577,17 @@ Working rule:
`[profile+0x77/+0xc5]`, while `+0x3b2/+0x3ba` still stop on the setup-panel threshold or
scroll path. The next pass should therefore test whether the unique `Louisiana.gmp`
`+0x14/+0x20` pair is enough to explain its Tier 2 runtime shape through that grounded bridge,
or whether the sparse recipe/runtime side is still the more plausible differentiator.
or whether the sparse recipe/runtime side is still the more plausible differentiator. One
adjacent `compare-setup-launch-payload` check now sharpens that too: `Louisiana.gmp` does not
collapse into the nearest setup-core peers on the launch-token side either, but that band is
still not part of the currently grounded Tier 2 bridge. So the next pass should keep launch
tokens as supporting context while testing the already-grounded `+0x14/+0x20 -> [profile+0x77/+0xc5]`
bridge against the sparse recipe/runtime family. The same widened setup-core note now shows the
split inside that bridge too: `payload_byte_0x20 = 0x3a` is unique to `Louisiana.gmp` across
all 41 bundled `rt3_105` maps, while `payload_word_0x14 = 1870` has only one peer (`Mexico`).
That makes the campaign/setup-byte side of the bridge the strongest remaining setup-core
differentiator, with the year-word side a secondary companion rather than a full peer-group
collapse.
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: