Bound event live-retagger control-lane seam
This commit is contained in:
parent
13e1101156
commit
dc620a6714
2 changed files with 16 additions and 0 deletions
|
|
@ -9526,6 +9526,9 @@ fn parse_event_runtime_collection_summary_with_tag_width(
|
|||
control_lane_notes.push(
|
||||
"the first non-editor positive control-lane writer is bounded away from ordinary restore too: 0x00430b50 allocates a fresh live runtime-effect row through 0x00432ea0 -> 0x0042d5a0, seeds [event+0x7ef] to 2 or 3 plus adjacent control bytes, and is reached from 0x004323a0 service at 0x0043232e rather than 0x00433130 load".to_string(),
|
||||
);
|
||||
control_lane_notes.push(
|
||||
"the remaining non-editor [event+0x7ef] mutators are bounded away from restore too: the 0x00443200..0x004436e3 sweep searches existing live runtime-event names through 0x005a57cf (including strings like 'New Beginnings', 'Chicago to New York', 'The American', and 'Labor') and retags already-live records, so it reads as scenario-specific live maintenance rather than the missing 0x4e9a restore owner".to_string(),
|
||||
);
|
||||
}
|
||||
if records_with_trigger_kind != 0 {
|
||||
control_lane_notes.push(format!(
|
||||
|
|
@ -22346,6 +22349,12 @@ mod tests {
|
|||
line.contains("0x00430b50 allocates a fresh live runtime-effect row")
|
||||
})
|
||||
);
|
||||
assert!(summary.control_lane_notes.iter().any(|line| {
|
||||
line.contains("0x00443200..0x004436e3")
|
||||
&& line.contains("0x005a57cf")
|
||||
&& line.contains("New Beginnings")
|
||||
&& line.contains("The American")
|
||||
}));
|
||||
assert!(summary.control_lane_notes.iter().any(|line| {
|
||||
line.contains("0x00431b20 dispatch-strip opcodes present in decoded grouped rows = [4]")
|
||||
}));
|
||||
|
|
|
|||
|
|
@ -364,6 +364,13 @@ Working rule:
|
|||
from the `0x004323a0` follow-on service strip at `0x0043232e`, not from `0x00433130` restore.
|
||||
So the remaining ordinary-owner question is narrower again: neither deep-copy inheritance nor
|
||||
the first positive control-lane builder currently belongs to the non-direct `0x4e9a` load path.
|
||||
- the remaining non-editor control-lane mutators are bounded away from restore too:
|
||||
direct disassembly of `0x00443200..0x004436e3` shows a name-driven live retagger sweep over
|
||||
the already-materialized event collection `0x0062be18`, matching text bands through
|
||||
`0x005a57cf` against scenario strings such as `New Beginnings`, `Chicago to New York`,
|
||||
`The American`, and `Labor`, then mutating `[event+0x7ef/+0x7f9/+0x7fa]` on those live
|
||||
records. That is now a grounded post-load live-maintenance seam, not the missing ordinary
|
||||
`0x4e9a` control-lane owner.
|
||||
- the positive-path caller census is effectively boxed in now too:
|
||||
direct `0x0040ef10` callers are the create-side pair `0x00403ef3 / 0x00404489`, the transport
|
||||
tuple pair `0x0046f073 / 0x004707ff`, and the already-ruled-down live controller
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue