solverforge-cli: make strict Clippy pass across all targets

[blackopsrepl]

Summary

solverforge-cli currently prevents the documented strict lint gate from passing cleanly.

Problem

cargo clippy --workspace --all-targets -- -D warnings fails because two test modules trigger clippy::module_inception.

Why This Matters

The workspace claims a strict lint bar, but the current state weakens CI confidence and release-readiness signaling.

Proposed Work

• Rename or flatten the nested CLI test modules that trigger module_inception.
• Re-run strict Clippy for the workspace and make it pass cleanly.
• Add or tighten a CI/local validation step so this regresses less easily.

Acceptance Criteria

• cargo clippy --workspace --all-targets -- -D warnings passes.
• No blanket #[allow(clippy::module_inception)] workaround is added unless explicitly documented and justified.

Source

Derived from PR #3 (PRODUCTION_REVIEW_ISSUES_2026-03-20.md).

[blackopsrepl]

Resolved by #15.

We made strict clippy pass across the CLI targets by flattening the nested test modules that were triggering clippy::module_inception, preserving the existing assertions and coverage, and validating the CLI crate cleanly on the release line.