P2: stderr INFO logs cause PowerShell to misreport exit code in CI

[Shreyas582]

Description

WraithRun writes INFO-level log lines to stderr (via tracing). In PowerShell, any stderr output causes 0 to sometimes report the process as failed even when the actual exit code is 0.

This breaks CI/CD pipelines where Continue = 'Stop' is set, and confuses users who see red error text in their terminal for informational messages.

Reproduction

wraithrun --dry-run --task ssh-keys 2>
echo 0  # 0

wraithrun --dry-run --task ssh-keys
# stderr shows INFO lines in red
# Some CI systems interpret this as failure

Expected Behavior

Either:

1. Default log level to WARN (use RUST_LOG=info or --verbose to enable INFO)
2. Use a structured logging format that doesn't trigger PowerShell's stderr error detection
3. At minimum, document this behavior for CI users

Affected Files

• cli/src/main.rs (tracing subscriber setup, default log level)