Check tier2 kind-8 recipe peers against runtime path
This commit is contained in:
parent
b727d36b96
commit
ac227ac48a
2 changed files with 29 additions and 0 deletions
|
|
@ -628,6 +628,11 @@ Working rule:
|
|||
differs on the exact `book00.line01` demanded token and `book00.line02` mode/supplied-token
|
||||
pair. So the current queue head is no longer “find a peer”; it is “find the downstream
|
||||
runtime-facing consequence of Louisiana’s distinct exact `book00` token-bearing signature.”
|
||||
That downstream split is now partially grounded too: direct `inspect-smp` checks show both
|
||||
`Britain.gmp` and `South East USA.gmp` still carry `Port01` and `Warehouse05` names in-file
|
||||
but neither has any add-building dispatch-strip trigger rows at all. So `Louisiana.gmp` is now
|
||||
the first checked member of that `book00.line02` mode-shape family whose exact token-bearing
|
||||
signature also lines up with the shipped add-building runtime path.
|
||||
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:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue