Harden rehost queue stop rules

This commit is contained in:
Jan Petykiewicz 2026-04-19 15:49:08 -07:00
commit 2158d1e39e
4 changed files with 14 additions and 2 deletions

View file

@ -202,7 +202,9 @@ The highest-value next passes are now:
instead of guessing another derived leaf field from neighboring raw offsets; the checked-in
`docs/rehost-queue.md` file is the control surface for that work loop, and after each commit the
next queue item should run unless the queue is empty, a real blocker remains that cannot be
advanced by any further non-hook work without guessing, or approval is needed
advanced by any further non-hook work without guessing, or approval is needed; `final`
responses are stop-only there too, so active work should continue under `commentary` updates
rather than placeholder status replies
- `rrt-runtime` now also exposes higher-layer probe commands for the current blocked frontier:
`runtime inspect-periodic-company-service-trace <save.gms>`,
`runtime inspect-region-service-trace <save.gms>`, and