PR #84260: fix(cli): validate debug proxy numeric options

• Repository: openclaw/openclaw
• Author: jbetala7
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/84260

Description (problem / solution / changelog)

Summary

• Reject invalid debug proxy numeric CLI options before runtime dispatch
• Keep --port bounded to an integer 0-65535
• Require positive integers for proxy validate --timeout-ms and proxy sessions --limit
• Add Commander-level regression coverage for bad proxy numeric values

Fixes #84253

Real behavior proof

Behavior or issue addressed: openclaw proxy sessions --limit abc should fail as an invalid CLI argument instead of reaching the debug proxy SQLite store and surfacing datatype mismatch.

Real environment tested: Fresh OpenClaw source checkout rebased onto current origin/main on macOS, using the real source CLI entry with isolated debug-proxy DB/blob/cert paths under /tmp.

Exact steps or command run after this patch:

env OPENCLAW_DEBUG=1 OPENCLAW_DEBUG_PROXY_DB_PATH=/tmp/openclaw-proxy-proof-rebased-invalid.sqlite OPENCLAW_DEBUG_PROXY_BLOB_DIR=/tmp/openclaw-proxy-proof-rebased-invalid-blobs OPENCLAW_DEBUG_PROXY_CERT_DIR=/tmp/openclaw-proxy-proof-rebased-invalid-certs NO_COLOR=1 pnpm exec tsx src/entry.ts proxy sessions --limit abc

Evidence after fix:

OpenClaw could not parse this command: option '--limit <count>' argument 'abc' is invalid. --limit must be an integer.
Try: openclaw proxy sessions --help

Observed result after fix: The invalid --limit abc value is rejected by the CLI parser before runDebugProxySessionsCommand() calls DebugProxyCaptureStore.listSessions(), so the SQLite datatype mismatch no longer leaks to the user. A valid command still works:

env OPENCLAW_DEBUG=1 OPENCLAW_DEBUG_PROXY_DB_PATH=/tmp/openclaw-proxy-proof-rebased-valid.sqlite OPENCLAW_DEBUG_PROXY_BLOB_DIR=/tmp/openclaw-proxy-proof-rebased-valid-blobs OPENCLAW_DEBUG_PROXY_CERT_DIR=/tmp/openclaw-proxy-proof-rebased-valid-certs NO_COLOR=1 pnpm exec tsx src/entry.ts proxy sessions --limit 1
[]

What was not tested: I did not rebuild the packaged dist/entry.js launcher in this source worktree; proof used the real TypeScript source CLI entry. I also did not connect through a live debug proxy, because the changed behavior is argument parsing before proxy runtime startup.

Before-fix evidence

On fresh origin/main (e00cb664ad), the same actual source CLI path accepted the invalid value far enough to hit SQLite:

env OPENCLAW_DEBUG=1 OPENCLAW_DEBUG_PROXY_DB_PATH=/tmp/openclaw-proxy-proof-2.sqlite OPENCLAW_DEBUG_PROXY_BLOB_DIR=/tmp/openclaw-proxy-proof-2-blobs OPENCLAW_DEBUG_PROXY_CERT_DIR=/tmp/openclaw-proxy-proof-2-certs NO_COLOR=1 pnpm exec tsx src/entry.ts proxy sessions --limit abc
[openclaw] Reason: datatype mismatch
[openclaw] Stack:
[openclaw] Error: datatype mismatch
[openclaw]     at DebugProxyCaptureStore.listSessions (.../src/proxy-capture/store.sqlite.ts:211:8)
[openclaw]     at Module.runDebugProxySessionsCommand (.../src/cli/proxy-cli.runtime.ts:294:81)

Checks

• pnpm test src/cli/proxy-cli.test.ts
• pnpm exec oxfmt --check --threads=1 src/cli/proxy-cli.ts src/cli/proxy-cli.test.ts
• git diff --check origin/main...HEAD
• git merge-tree --write-tree HEAD origin/main
• pnpm check:changed

Collision checks

Before filing and again immediately before publishing, I searched open issues and PRs for:

• datatype mismatch proxy
• proxy sessions --limit
• debug proxy sessions limit
• store.sqlite listSessions

No open PR covered this debug-proxy CLI option-validation path.

Changed files

• src/cli/proxy-cli.test.ts (modified, +24/-0)
• src/cli/proxy-cli.ts (modified, +34/-10)