Problem

When running gateway update.run, the preflight validation step reported that all 10 recent commits (328b69b → 0a48592) failed linting with "34-35 TypeScript ESLint errors" in various extension files. The update was aborted with reason preflight-no-good-commit.

Actual Behavior

Manual testing shows all commits pass linting cleanly:

# On commit 328b69be1 (latest)
$ pnpm lint
Found 0 warnings and 0 errors.
Finished in 8.4s on 3121 files with 134 rules using 12 threads.

# On commit 97c30738e (previous)
$ pnpm lint
Found 0 warnings and 0 errors.
Finished in 5.7s on 3114 files with 134 rules using 12 threads.

Both commits pass perfectly. The preflight check gave a false negative.

Root Cause

The repo switched from ESLint to Oxlint at some point. The preflight checker appears to be using outdated validation logic or looking for ESLint-specific errors that no longer exist when running the current pnpm lint command (which uses Oxlint).

Impact

• Blocks valid updates
• Forces users to manually checkout commits, run pnpm install, and restart gateway
• Undermines confidence in the automated update system

Workaround

Manual update:

cd ~/Applications/moltbot  # or openclaw install location
git checkout origin/main
pnpm install
# Restart gateway via gateway.restart tool

Environment

• Version before: 2026.2.3 (commit 97c30738e)
• Version after: 2026.2.4 (commit 328b69b)
• Platform: Linux (Ubuntu)
• Install method: pnpm global

Suggested Fix

Update the preflight validation logic to:

1. Use the same linting command as the repo (pnpm lint which runs Oxlint)
2. Or detect which linter is configured and use the appropriate check
3. Add better error reporting to show actual linter output instead of phantom errors