Summary

rtk lint does not propagate ESLint non-zero exit code in a reproducible scenario (--max-warnings=0).

This can produce false-green CI/tooling behavior when lint should fail.

Environment

• rtk: 0.20.0
• bun: 1.3.9
• project: ~/Projects/pricedrop/apps/pricedrop
• checked on: 18 February 2026

Reproduction

cd ~/Projects/pricedrop/apps/pricedrop
npx eslint entrypoints/background.ts --max-warnings=0 >/dev/null 2>&1; echo raw=$?
rtk lint npx eslint entrypoints/background.ts --max-warnings=0 >/dev/null 2>&1; echo rtk=$?

Observed:

raw=1
rtk=0

Expected

rtk lint ... should return the same exit code as underlying ESLint command (1 in this repro).

Actual

rtk lint ... returns 0.

Impact

• CI/automation may continue despite lint failure conditions.
• Exit-code parity is broken for wrapper mode.