Stop passing --lazy-mode to the coana CLI

[Oskar Haarklou Veileborg (BarrensZeppelin)]

Summary

The coana CLI no longer accepts --lazy-mode, so a reachability run started with --reach-lazy-mode failed on an unrecognized argument.

--reach-lazy-mode is kept as a hidden no-op (help=argparse.SUPPRESS), matching how --reach-disable-analysis-splitting was deprecated in this repo, so pipelines that still pass the flag keep working rather than failing argument parsing. Nothing is forwarded to coana.

Changes

• socketsecurity/core/tools/reachability.py: drop the lazy_mode parameter, its docstring entry, and the --lazy-mode append.
• socketsecurity/socketcli.py: drop the lazy_mode= argument at the call site.
• socketsecurity/config.py: hide --reach-lazy-mode from --help and mark the CliConfig field deprecated. The field and its args dict entry are retained because the argparse dest still exists, as with reach_disable_analysis_splitting.
• docs/cli-reference.md: remove the flag from the usage synopsis and the reachability parameter table.

Notes

• No version bump, so version-check.yml will report a failure on this PR. That check is not in main's required status checks; the tradeoff is that this fix will not be published until some later version bump ships.
• No changelog entry, for the same reason.

Testing

• --reach-lazy-mode still parses (reach_lazy_mode = True) and no longer appears in --help.
• Full suite: 523 passed, 2 skipped (both pre-existing GitLab-auth skips).

---

Note

Low Risk
Backward-compatible CLI deprecation with no coana behavior change beyond removing an invalid argument; reachability invocation path is narrow and low blast radius.

Overview
Fixes reachability runs that failed when pipelines still passed --reach-lazy-mode, because the coana CLI no longer accepts --lazy-mode.

The Socket CLI no longer forwards lazy mode into coana: lazy_mode is removed from ReachabilityAnalyzer.run_reachability_analysis and from the socketcli call site, along with the --lazy-mode coana argument. --reach-lazy-mode remains accepted for backward compatibility but is a hidden no-op (argparse.SUPPRESS, same pattern as other deprecated reach flags); CliConfig.reach_lazy_mode is kept so existing configs and scripts do not break on parse. CLI reference docs drop the flag from the usage synopsis and reachability parameter table.

^{Reviewed by Cursor Bugbot for commit 71c2b4d. Configure here.}

[github-actions]

❌ Version Check Failed

Please increment...