Allow the test fleet in the instrumented runner, refuse only production

relay1/relay2 are what the fleet is FOR, and the suites need https because
Android blocks cleartext — so a local http relay cannot serve them at all.
Refusing both left no way to run the suite as designed.

Production stays refused outright. The test fleet is allowed with a loud
line saying accounts will be created on it, because they will be.

scripts/instrumented.sh

@@ -34,13 +34,19 @@ MSG
 }
 shift || true
 
-# 🔴 Refused rather than warned about. A run that creates accounts on the
-# production relay cannot be undone by noticing afterwards.
+# 🔴 Production is refused, not warned about. A run that creates accounts on
+# relay.flamenet.io cannot be undone by noticing afterwards.
+#
+# ⚠️ relay1/relay2 are the TEST FLEET and are allowed — that is what they are
+# for, and the suites need https because Android blocks cleartext, so a local
+# http relay cannot serve. Loud rather than silent: accounts really are created.
 case "$RELAY" in
-  *relay.flamenet.io*|*relay1.flamenet.io*)
-    echo "REFUSED: $RELAY is a live relay. These suites create accounts." >&2
-    echo "Point them at a local relay, or edit this check if you truly mean it." >&2
+  *//relay.flamenet.io*|relay.flamenet.io*)
+    echo "REFUSED: $RELAY is the PRODUCTION relay. These suites create accounts." >&2
+    echo "Use a test-fleet relay (relay1/relay2) or a local one." >&2
     exit 1;;
+  *relay1.flamenet.io*|*relay2.flamenet.io*)
+    echo "⚠️  $RELAY is a shared test relay — this run WILL create accounts on it." >&2;;
 esac
 
 CLASSES="${*:-io.flamenet.messenger.app.FeatureUseTest,io.flamenet.messenger.app.CrudSurfaceTest,io.flamenet.messenger.app.ChatFlowTest}"