Summary

The cgc analyze complexity command's --threshold option ignored the COMPLEXITY_THRESHOLD config value, always defaulting to hardcoded 10.

Root Cause

In cli/main.py line 2511, the threshold parameter was defined as:

threshold: int = typer.Option(10, "--threshold", "-t", help="Complexity threshold for warnings")

The function body never called config_manager.get_config_value("COMPLEXITY_THRESHOLD") to override this default. So even if a user ran cgc config set COMPLEXITY_THRESHOLD 15, the CLI would still use 10.

Fix

Changed the default to None (making it Optional[int]) and added config-reading logic:

threshold: Optional[int] = typer.Option(None, "--threshold", "-t",
    help="Complexity threshold for warnings (default: from config or 10)")

In the function body, when threshold is None:

1. Read COMPLEXITY_THRESHOLD from config
2. Parse to int, falling back to 10 on ValueError/TypeError
3. Default to 10 if config value is also missing

Testing

• py_compile passes
• cgc analyze complexity --help shows updated description
• Manual verification: cgc config set COMPLEXITY_THRESHOLD 15 now takes effect

Impact

• Users who set COMPLEXITY_THRESHOLD via cgc config set will now see it applied
• Explicit --threshold N CLI flag still takes precedence (not None)
• Backward compatible: if neither config nor CLI flag is set, behavior is identical (default 10)