Probe save-side region queued notice nodes

docs/rehost-queue.md

@@ -16,7 +16,9 @@ Working rule:
   separate save-owner seam for the pending bonus lane `[region+0x276]`, completion latch
   `[region+0x302]`, one-shot notice latch `[region+0x316]`, severity/source lane `[region+0x25e]`,
   and any stable region-id or class discriminator that can drive shellless city-connection
-  service.
+  service. The newly grounded queue-node probe for the atlas-backed kind-`7` notice records is a
+  negative result on `q.gms`, `p.gms`, and `Autosave.gms`, so the next region pass should not
+  assume that the transient `[world+0x66a6]` queue family is persisted in ordinary saves.
 - Reconstruct the save-side placed-structure collection body on top of the newly grounded
   `0x36b1/0x36b2/0x36b3` header seam so the blocked city-connection / linked-transit branch can
   stop depending on atlas-only placed-structure and local-runtime refresh notes, especially the
@@ -117,6 +119,11 @@ Working rule:
   name pairs match the 56-triplet corpus), which shifts the remaining placed-structure work away
   from “prove these are aliases” toward “find how the separate infrastructure-asset owner seam is
   consumed by city-connection / linked-transit service.”
+- Save inspection now also has a dedicated probe for the atlas-backed region queued-notice node
+  shape (`payload seed 0x005c87a8`, kind `7`, zero promotion latch, region id, amount, `-1/-1`
+  tails), plus a matching lightweight CLI inspector. Grounded `q.gms`, `p.gms`, and `Autosave.gms`
+  all currently return `null`, which is useful negative evidence: the transient region notice
+  queue is not obviously persisted in these ordinary saves.
 - The placed-structure tagged save stream now also exposes repeated `0x55f1/0x55f2/0x55f3`
   triplets with dual name stems, a fixed five-`f32` policy row, and a compact `0x5dc1...0x5dc2`
   footer carrying one raw `u32` payload lane plus one live `i32` status lane, so the remaining