openclaw - 💡(How to fix) Fix tasks audit --limit accepts partially numeric values [1 pull requests]

Observed problem

On current origin/main (e3b77d6d2c), openclaw tasks audit --json --limit 1abc is accepted as if the limit were 1.

Real behavior proof from the source CLI:

$ OPENCLAW_STATE_DIR=$(mktemp -d) node --import tsx src/entry.ts tasks audit --json --limit 1abc
{
  "count": 0,
  "filteredCount": 0,
  "displayed": 0,
  "filters": {
    "severity": null,
    "code": null,
    "limit": 1
  },
  ...
}

Current behavior

The tasks audit CLI accepts a partially numeric --limit value and silently truncates it via integer parsing.

Expected behavior

tasks audit --limit should require a positive integer token. Values like 1abc, 1.5, 0, and -1 should be rejected before running the audit.

Duplicate searches performed

I checked open and closed issues/PRs for:

• tasks audit --limit
• parsePositiveIntOrUndefined
• Limit displayed findings
• parseInt limit CLI
• tasks audit recent open and closed PRs

Closest matches were general task-audit false-positive work, gateway-rpc --timeout validation (#54646), message-format limit handling (#79593), and broad command-validation work (#83391), but none covered this tasks audit --limit parsing path.

Candidate fix shape

Use a strict positive-integer parser for the tasks audit --limit option in both the registered Commander path and the lean JSON route, then add focused regressions that invalid partial values do not reach tasksAuditCommand or tasksAuditJsonCommand.