CAT-D3: mirror answers at once and the holder says the copy's end on the seat's events

A large base could outlast a call's bound. The ask is kept in the state mirrors and the copy runs on that state's
watch, so a copy a restart cut is taken on again; published (or refused, with why) on container-image-registry's
events is the end the caller waits on, the place the seat's contract already gives mirror.

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

modules/distribution/module.json

@@ -96,6 +96,11 @@
       "storage": "key-value",
       "template": "state"
     },
+    {
+      "name": "mirrors",
+      "storage": "key-value",
+      "template": "state"
+    },
     {
       "name": "findings",
       "storage": "key-value",