The namer inflates the XOVER reply and reads the corpus from the prober's container

xoverRaw gives one zlib/gzip stream, as the corpus stores it; the namer fed
the bytes as text and found nothing. The prober had no corpus mount, so every
move went to the server.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

deploy/compose.yaml

@@ -126,7 +126,9 @@ services:
   prober:
     <<: *app
     command: ['node', 'ace', 'probe:run']
-    volumes: []
+    # The pending namer reads a named release's articles again from the corpus (no spool).
+    volumes:
+      - ./corpus:/corpus:ro
     environment:
       <<: *app-env
       PROBE_CONNECTIONS: ${PROBE_CONNECTIONS:-8}