ci(ark): revert lint diagnostic, run clean

The previous run captured lint_rc=0, which means the lint step
actually passed. The earlier failures (same commit, exit 1, no
eslint output) were transient — likely a flake in the bun run
indirection under the dev shell. Reverting to a clean
{format-check, typecheck, lint, test} body so a real lint failure
surfaces normally. If the flake recurs, follow up with a separate
investigation rather than carrying diagnostic noise in the workflow.

Author: rodrgds

.github/workflows/ci.yml

@@ -151,13 +151,9 @@ 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 || 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
+            format-check
+            typecheck
+            lint
+            test
           fi