fix(release): strip ANSI before the subscription-log grep

matter-server colourises its logs, so a `\x1b[0m` reset sits between
'<Node:N>' and the message. The anchored '<Node:N> (Re-)?Subscription
succeeded' pattern never matched, hard-failing check_subscription_log on
otherwise-healthy flashes (node 35 v1.1.4: version confirmed, node
available + subscribed, gate still errored). Strip ANSI first in both
scripts; also bring esp32-release.sh up to the ota-release.sh behaviour
(match Re-Subscription, tail -1 the newest, poll for the late resubscribe).

Assisted-by: AI

Author: AndrewDemsDS

firmware/scripts/esp32-release.sh

@@ -256,14 +256,27 @@ check_subscription_log() {
     say "  PI_HOST/PI_SSH_KEY unset -- cannot read the matter-server log; node availability stands as the subscription assertion (#64)"
     return 0
   fi
-  local line
-  if ! line="$(ssh -o BatchMode=yes -o ConnectTimeout=10 -i "$PI_SSH_KEY" "$PI_HOST" \
-      "docker logs --since 15m matter-server 2>&1 | grep -m1 '<Node:$node> Subscription succeeded' || true" 2>/dev/null)"; then
-    say "  could not read the matter-server log on $PI_HOST -- node availability stands as the subscription assertion (#64)"
-    return 0
-  fi
+  # After an OTA the device REBOOTS, so the healthy post-flash signal is usually a
+  # '<Node:N> Re-Subscription succeeded' logged a few seconds after the re-interview, NOT the
+  # plain 'Subscription succeeded' (that one is the PRE-reboot subscription, often already >15m
+  # old). matter-server also colourises its logs, so an ESC[..m reset sits between '<Node:N>'
+  # and the message -- strip ANSI first or the anchored pattern never matches. Both gaps
+  # false-alarmed an otherwise-healthy node 35 flash on 2026-07-22 (version confirmed, node
+  # available + subscribed, yet the old single-shot grep found nothing). So: strip ANSI, match
+  # BOTH forms, take the most RECENT (tail -1), and poll, since the resubscribe can land a few
+  # seconds after we start looking.
+  local line=""
+  for _ in 1 2 3 4 5 6; do
+    if ! line="$(ssh -o BatchMode=yes -o ConnectTimeout=10 -i "$PI_SSH_KEY" "$PI_HOST" \
+        "docker logs --since 15m matter-server 2>&1 | sed -E 's/\x1b\[[0-9;]*m//g' | grep -E '<Node:$node> (Re-)?Subscription succeeded' | tail -1 || true" 2>/dev/null)"; then
+      say "  could not read the matter-server log on $PI_HOST -- node availability stands as the subscription assertion (#64)"
+      return 0
+    fi
+    [ -n "$line" ] && break
+    sleep 10
+  done
   [ -n "$line" ] \
-    || die "no 'Subscription succeeded' for node $node in the last 15m of the matter-server log -- subscription is broken (#64, docs/10 §16)"
+    || die "no '(Re-)Subscription succeeded' for node $node in the last 15m of the matter-server log -- subscription is broken (#64, docs/10 §16)"
   say "  matter-server log confirms: ${line:0:120}"
 }
 flash() {

firmware/scripts/ota-release.sh

@@ -574,7 +574,7 @@ check_subscription_log() {
   local line=""
   for _ in 1 2 3 4 5 6; do
     if ! line="$(ssh -o BatchMode=yes -o ConnectTimeout=10 -i "$PI_SSH_KEY" "$PI_HOST" \
-        "docker logs --since 15m matter-server 2>&1 | grep -E '<Node:$node> (Re-)?Subscription succeeded' | tail -1 || true" 2>/dev/null)"; then
+        "docker logs --since 15m matter-server 2>&1 | sed -E 's/\x1b\[[0-9;]*m//g' | grep -E '<Node:$node> (Re-)?Subscription succeeded' | tail -1 || true" 2>/dev/null)"; then
       say "  could not read the matter-server log on $PI_HOST -- node availability stands as the subscription assertion (#64)"
       return 0
     fi