Problem

The Matrix CLI currently accepts out-of-range numeric values in two places:

• openclaw matrix verify self --timeout-ms -1 gets past CLI parsing and reaches the verification flow, where it fails later with a confusing Cannot read properties of undefined (reading 'id') error.\n- openclaw matrix account add --initial-sync-limit -1 does not fail at the CLI boundary even though negative initial sync limits are not meaningful.\n\n## Why this matters\n\nBad CLI input should fail before the command starts Matrix setup or verification work. For self-verification, a negative timeout can start the flow and then fail with an unrelated runtime error. For account setup, an explicit invalid initial sync limit can be silently treated like no setting.\n\n## Reproduction proof\n\nI reproduced this with focused Matrix CLI regression tests on current main. Before the fix, the negative --timeout-ms case reached the verification mock and failed with the unrelated id error, while the negative --initial-sync-limit case did not set a non-zero exit code.\n\n## Expected behavior\n\n- --timeout-ms should require a positive integer.\n- --initial-sync-limit should allow zero and positive integers, but reject negative values.\n