fix(npx): execute unknown targets via npx, not npm (#1495)

[ousamabenyounes]

Problem

rtk npx <unknown_binary> (e.g. npx oxlint) failed with npm ERR! Missing script: \"<binary>\" instead of running the binary.

Root cause

src/main.rs Commands::Npx fallback called npm_cmd::run(&args, ...). npm_cmd::run invokes npm and (when args don't match a known npm subcommand) injects run, turning rtk npx oxlint into npm run oxlint. Any binary not declared as a package.json script broke.

Fix

Replace the npm_cmd::run fallback with a proper npx passthrough — the same pattern already used a few lines above for npx prisma <unknown>:

let timer = core::tracking::TimedExecution::start();
let mut cmd = core::utils::resolved_command(\"npx\");
for arg in &args { cmd.arg(arg); }
let status = cmd.status().context(\"Failed to run npx\")?;
let args_str = args.join(\" \");
timer.track_passthrough(
    &format!(\"npx {}\", args_str),
    &format!(\"rtk npx {} (passthrough)\", args_str),
);
core::utils::exit_code_from_status(&status, \"npx\")

This restores correct binary-lookup semantics (npx) instead of script-lookup (npm), keeps tracking visible in rtk gain --history, and propagates the child exit code.

Test plan

• Added regression test `test_try_parse_npx_oxlint_routes_to_npx_command` confirming the dispatcher entrypoint stays correct.
• `cargo test --all` → 1682 passed, 0 failed.
• `cargo fmt --all` clean.
• Manually verified post-fix: `rtk npx oxlint --version` → `Version: 1.61.0` (npx auto-installed and ran the binary). Pre-fix it produced `npm ERR! Missing script: "oxlint"`.
• No behavior change for specialized targets (`npx tsc`, `npx eslint`, `npx prisma`, `npx next`, `npx prettier`, `npx playwright`) — only the catch-all fallback changed.

Closes #1495

[pszymkowiak]

[w] wshm · Automated triage by AI

📊 Automated PR Analysis

🐛 Type	bug-fix
🟢 Risk	low

Summary

Fixes the rtk npx <unknown_binary> command which was incorrectly routing unknown targets through npm_cmd::run (script lookup) instead of npx (binary lookup), causing errors like "Missing script" for binaries not declared in package.json. The fix replaces the fallback with a direct npx passthrough, matching the pattern already used for specialized targets like npx prisma.

Review Checklist

• Tests present
• Breaking change
• Docs updated

Linked issues: #1495

---

Analyzed automatically by wshm · This is an automated analysis, not a human review.

[KuSh]

Closing as #1458 already took care of the problem