[BUG] [v0.0.7] `cortex compact config --json --log-retention-days 30` early-returns with default JSON and discards the flag — `--log-retention-days` is excluded from the early-return guard condition

[Kuka53]

Project

cortex

Description

run_config has an early-return path for pure display: if args.json && !args.enable && !args.disable && args.interval_hours.is_none(). This guard does not check args.log_retention_days. So cortex compact config --json --log-retention-days 30 satisfies all four conditions (json=true, enable=false, disable=false, interval_hours=None), triggers the early return, and prints the default config JSON without applying or acknowledging the --log-retention-days 30 value. The flag is silently discarded.

Error Message

None (silent ignore with misleading JSON showing default values).

Debug Logs

System Information

- OS: Windows 11
- Cortex version: `cortex 0.0.7 (7954d02 2026-03-30)`

Screenshots

20260406_104052.mp4

Steps to Reproduce

1. Run cortex compact config --json --log-retention-days 30.
2. Observe: JSON output shows the default log_retention_days value, not 30.
3. No confirmation that the flag was received or rejected.
4. Compare: cortex compact config --log-retention-days 30 (without --json) enters the human-readable path and at least reaches the "not yet implemented" message, acknowledging the flag.

Expected Behavior

The early-return guard should also check args.log_retention_days.is_none(). When --log-retention-days is supplied, the early-return should be skipped so the flag can be processed (or the user should receive an error/acknowledgement).

Actual Behavior

args.log_retention_days is not included in the guard condition at line 655; the early-return fires and prints default JSON, making the flag a no-op in JSON mode.

Additional Context

Code Evidence

• Path: src/cortex-cli/src/compact_cmd.rs
• Permalink: src/cortex-cli/src/compact_cmd.rs#L655-L668
• Symbols: run_config — guard if args.json && !args.enable && !args.disable && args.interval_hours.is_none() missing && args.log_retention_days.is_none() check; early return prints default config JSON without processing --log-retention-days

[echobt]

✅ Validation Result: VALID

Reason

The issue describes a bug where cortex compact config --json --log-retention-days 30 silently ignores the --log-retention-days flag and returns the default configuration JSON. This happens because the early-return guard condition for pure display mode does not check if args.log_retention_days is present.

I verified this in the codebase. In src/cortex-cli/src/compact_cmd.rs, the run_config function has the following early-return logic:

async fn run_config(args: CompactConfigArgs) -> Result<()> {
    // Load current config
    let config = AutoCompactionConfig::default();

    if args.json && !args.enable && !args.disable && args.interval_hours.is_none() {
        // Just display current config
        let output = serde_json::json!({
            "enabled": config.enabled,
            "interval_secs": config.interval_secs,
            "interval_hours": config.interval_secs / 3600,
            "log_retention_days": config.log_retention_days,
            // ...
        });
        println!("{}", serde_json::to_string_pretty(&output)?);
        return Ok(());
    }

As shown in the code, the if condition checks args.json, !args.enable, !args.disable, and args.interval_hours.is_none(). However, it completely misses checking args.log_retention_days.is_none().

Because of this missing check, when a user runs cortex compact config --json --log-retention-days 30, the condition evaluates to true (since json is true, enable/disable are false, and interval_hours is None). The function then prints the default configuration (where log_retention_days is 7) and returns early, completely ignoring the --log-retention-days 30 flag provided by the user.

The screenshot provided in the issue is a video that clearly demonstrates this exact behavior, showing the command being run and the output JSON containing "log_retention_days": 7.

The issue is valid, authentic, and the code perfectly matches the described bug. No duplicates were found.

Verification Checklist

• ✅ Screenshot/video provided
• ✅ Images accessible
• ✅ Shows CLI/TUI interface
• ✅ Screenshot shows a visible bug
• ✅ Screenshot matches the issue description
• ✅ Screenshot appears authentic
• ✅ Code matches description
• ✅ No duplicates found