fix(deferral): pass a released agent's queued failed reply once, by its own id

changelog.d/deferred-write-landing-unknown.fixed.md

@@ -24,7 +24,15 @@
     nothing was changed. It's refused the same way while the store can't be
     searched; the host log names the store's error".
   - A conversation fork's or ephemeral run's queue, stored when it's
-    released, looks such an entry up the same way: found, it's neither
-    stored again nor passed to the primary as a failed reply; where the
-    store can't be searched, it's stored anyway where the store takes it,
-    and the log says it may now be stored twice.
+    released, looks such an entry up the same way, and, where the store
+    can't be searched, in the window the release reads: found, it isn't
+    stored again; where neither can see the store, it's stored anyway where
+    the store takes it, and the log says it may now be stored twice. A
+    failed reply, or a channel notice the fork or run could act on, among
+    such entries reaches the primary once, as the entry itself under its own
+    id, so a crash or a restart doesn't tell it twice, as long as the
+    release's sync went through. It isn't passed on where the release finds
+    the fork or run had read the copy that landed, at its release or at the
+    `stop()` that ends it. Where a crash or a failed sync leaves the entry
+    to the next boot, boot passes it on anyway, since it can't read that
+    window.

changelog.d/stop-ends-live-forks.fixed.md

@@ -19,6 +19,9 @@
 - A failed reply still queued for a fork or a run that ended while the
   host was quiesced is now passed to the primary when `stop()` runs, named
   as the registry knows its channel then, and lands when the host resumes.
-  Before, the next boot's flush passed it on. A memory-only queue still
-  loses it at exit. Any other write queued for such an agent is still
-  dropped, logged.
+  It isn't passed on where the fork or run had read the copy of it that
+  landed in its window, unless `stop()`'s pass over that window fails,
+  when it goes on as boot would send it, read or not. Before, the next
+  boot's flush passed it on. A memory-only queue still loses it at exit.
+  Any other write queued for such an agent, but a channel notice it could
+  act on, is still dropped, logged.