--price/--max-tokens/--top/--fail-on-waste accept NaN and negatives

[royalpinto007]

Problem

--max-tokens abc classifies everything source (NaN defeats ?? and all comparisons are false); --max-tokens -5 flags everything trim.

Where

src/cli.js (Number(val()), no validation) + src/scan.js budget comparisons.

Acceptance

Add failing tests first for --max-tokens abc, --price -3, and --top -1, expecting exit 2 instead of exit 0 with nonsense. Then fix.

[mikemikimike]

Implemented in PR #13.

The CLI now rejects non-finite and negative numeric options before scanning or writing ignore files. This covers --max-tokens, --price, --top, and --fail-on-waste, with clear exit status 2 errors and regression coverage for the reported NaN and negative-value cases. The package version is bumped to 0.1.3.

Validation completed:

• npm test — 9 passed, 0 failed.
• CLI JSON smoke test and JavaScript syntax checks passed locally.
• GitHub Actions CI test passed on the PR head: https://github.com/AgentPostmortem/Ctxtrim/actions/runs/34035108636

The PR changes only the CLI, its regression tests, package version, and changelog.