fix(maestro): use a portable mktemp template in run_maestro

`mktemp -t maestro-run` works on BSD/macOS, which appends the random suffix
itself, but GNU coreutils requires at least 6 X's in the template. So on the
Linux Android runners every flow printed

  mktemp: too few X's in template 'maestro-run'
  '': No such file or directory (os error 2)

— log_file was empty, so the tee redirection failed and maestro never ran.
iOS was unaffected, which is why this passed local and macOS testing.

Use an explicit XXXXXX template, which both implementations accept, and fall
back to a PID-based path if mktemp fails for any other reason: artifact
plumbing must never be what decides whether the tests run.

Audited the rest of the commands added in this series (tr -c, grep -qE) —
both POSIX, and already used by the pre-existing recording code that runs on
Android.

Verified by stubbing a GNU-strict mktemp on PATH: reproduces the CI error with
the old form and run_maestro completes with the new one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: YogendraShelke

maestro/helpers/helpers.sh

@@ -159,7 +159,17 @@ run_maestro() {
   local flow="$1"
   shift
   local log_file
-  log_file="$(mktemp -t maestro-run)"
+  # Explicit XXXXXX template, not `mktemp -t maestro-run`: BSD/macOS mktemp appends the random
+  # suffix itself, but GNU coreutils (the Linux Android runners) requires at least 6 X's in the
+  # template and fails with "too few X's in template", leaving log_file empty and every
+  # redirection to it failing. Works on both.
+  log_file="$(mktemp "${TMPDIR:-/tmp}/maestro-run.XXXXXX")" || log_file=""
+  if [ -z "$log_file" ]; then
+    # Never let artifact plumbing decide whether tests run: fall back to a fixed path so the
+    # flow still executes (classification just loses its input if that also fails).
+    log_file="${TMPDIR:-/tmp}/maestro-run.$$"
+    : > "$log_file" 2>/dev/null || true
+  fi
 
   DEBUG_RUN_DIR="$DEBUG_OUTPUT_DIR/${PLATFORM}-$(basename "${flow%.yaml}" | tr -c 'A-Za-z0-9._-' '_')"
   rm -rf "$DEBUG_RUN_DIR"