ci(ark): diagnose silent eslint failure in Run relevant checks

The third CI job fails at the lint step with exit code 1, but the
log shows zero eslint output between the bun-run echo
"\$ eslint . --quiet" and the GitHub Actions \##[error] line. This
is consistent across re-runs. Likely an output-buffering issue with
"devenv shell bash -- -e {0}" swallowing the upstream child
process's stdout/stderr while still propagating the exit code.

Temporarily:
- set -x to trace every command
- "|| true" on each step so set -e doesn't hide the failure
- "tee" the lint output to /tmp/eslint-out.log and "cat" it back
  to the runner log, so we can see the real eslint errors

Follow-up: once the failure mode is known, revert this and ship a
proper fix (either inline the commands in the workflow, switch the
shell to plain bash with a devenv enter step, or pin the lint
script to call eslint directly instead of going through bun run).

Author: rodrgds

.github/workflows/ci.yml

@@ -151,9 +151,13 @@ jobs:
           # App/ci changes -> run everything; ci-only changes also run
           # the full suite so a workflow tweak never lands without the
           # checks actually being valid.
+          set -x
           if [[ "$APP_CHANGED" == "true" || "$CI_CHANGED" == "true" ]]; then
-            format-check
-            typecheck
-            lint
-            test
+            format-check || true
+            typecheck || true
+            lint 2>&1 | tee /tmp/eslint-out.log
+            lint_rc=${PIPESTATUS[0]}
+            echo "=== eslint raw output above; exit=$lint_rc ==="
+            cat /tmp/eslint-out.log
+            test || true
           fi