Add higher-layer rehost trace probes
This commit is contained in:
parent
dc7215f720
commit
6bfe4d043f
7 changed files with 741 additions and 22 deletions
|
|
@ -167,6 +167,12 @@ guessing one more derived leaf field from nearby offsets, and the checked-in
|
|||
[`docs/rehost-queue.md`](docs/rehost-queue.md) file is now the control surface for that loop:
|
||||
after each commit, check the queue and continue unless the queue is empty, a real blocker remains,
|
||||
or approval is needed. A checked-in
|
||||
The same runtime surface now also exposes higher-layer blocker probes:
|
||||
`runtime inspect-periodic-company-service-trace <save.gms>`,
|
||||
`runtime inspect-region-service-trace <save.gms>`, and
|
||||
`runtime inspect-infrastructure-asset-trace <save.gms>`, so the next city-connection /
|
||||
linked-transit slices can start from explicit owner-seam blockers instead of another generic save
|
||||
scan. A checked-in
|
||||
`EventEffects` export now exists too in
|
||||
`artifacts/exports/rt3-1.06/event-effects-table.json`, and a checked-in semantic closure layer now
|
||||
exists beside it in `artifacts/exports/rt3-1.06/event-effects-semantic-catalog.json`. Recovered
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue