fix(deploy): the sidecars' downloads try again within the hour after a failed round

A failed BRouter segment or listing, a failed tile cut or an unwritable folder waited the whole refresh period, 30 days without routes or a map; they try again after an hour, doubling to a day. Photon's failed download backs off from a day to a week, and a dead Photon is noticed within a minute. The downloads' network is an ordinary bridge the three share, as the comments now say.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>

deploy/photon/serve.sh

@@ -2,7 +2,9 @@
 # Serves Photon on the database in /data/current (Halkyon Train's ADR 0030, D50), once
 # data.sh has brought one; and where data.sh has made a newer one (/data/next/ready),
 # stops Photon, puts the new one in the old one's place and starts it again: a
-# minute or two without search, once a month. PHOTON_HEAP is Java's heap (6g).
+# minute or two without search, once a month. Looked at every minute, which also
+# starts a Photon that stopped (killed for memory) again. PHOTON_HEAP is Java's
+# heap (6g).
 set -eu
 
 cd /data
@@ -42,7 +44,7 @@ while [ ! -d current/photon_data ] && ! swap; do
 done
 start
 while :; do
-  sleep 3600 &
+  sleep 60 &
   wait $! || true
   if [ -e next/ready ]; then
     stop