fix: validate default rule path only when used

[binggao1230]

Summary

• stop Click from validating the default --rule path during option parsing
• validate the rule path only when Quark actually loads rules from that path
• add CLI regression tests for custom single-rule use and missing rule-directory use

Fixes #936.

Tests

• uv run --with pytest --with requests --with click --with numpy --with tqdm --with prettytable --with colorama --with pathvalidate --with graphviz --with plotly --with-editable . pytest tests/test_cli.py -q
• uv run --with black black --check tests/test_cli.py
• git diff --check

Note: I did not run because the current file has pre-existing formatting that newer Black would reflow outside this fix. I kept the production diff to the rule option and the runtime path check.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 78.89%. Comparing base (1df1d49) to head (efa3c54).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
quark/cli.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #937   +/-   ##
=======================================
  Coverage   78.89%   78.89%           
=======================================
  Files          81       81           
  Lines        7131     7131           
=======================================
  Hits         5626     5626           
  Misses       1505     1505           

Flag	Coverage Δ
unittests	78.89% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[haeter525]

Hi @gaoflow, thank you for the fix!
I have a few comments below for minor simplifications. Once those are addressed, I think the PR is ready to merge.

[MickeyWzt]

I checked this PR locally on Windows and found one small portability issue in the current test suite.

At 28b0ef7, running:

python -m pytest tests/test_cli.py -q

fails on Windows in test_missing_rules_path_fails_when_rules_are_loaded, because the error message uses {rule!r}. That escapes backslashes in Windows paths, so str(missing_rules) is not found in result.output.

Changing the message to use the plain path keeps the CLI output more readable and makes the assertion portable:

f"Path {rule} does not exist."

I also tried the two requested simplifications locally:

• set exists=False directly on the --rule option
• extract the duplicated Quark mock setup into a pytest fixture

With those changes plus the message tweak:

python -m pytest tests/test_cli.py -q
# 3 passed

uv run --with black black --check tests/test_cli.py
# passed

git diff --check
# passed

[binggao1230]

Thanks both. Addressed in efa3c54:

• Set exists=False directly on the --rule option and dropped the post-hoc param patch (@haeter525).
• Switched the error message to the plain path so the assertion is portable on Windows (@MickeyWzt).
• Extracted the duplicated Quark mock into a mock_quark fixture (@haeter525).

pytest tests/test_cli.py is green here (3 passed).

[haeter525]

Thank you @gaoflow for the fix!