[BUG] [v0.0.7] MCP debug uses hardcoded version 1.0.0 instead of CARGO_PKG_VERSION (debug.rs:429,567)

[johncur-super]

Project

cortex

Description

In cortex-cli/src/mcp_cmd/debug.rs, MCP client initialization uses hardcoded "version": "1.0.0" in clientInfo instead of the built package version. External MCP servers therefore see the wrong client version. The report contrasts with cortex-mcp-types/src/initialization.rs:77 using env!("CARGO_PKG_VERSION").

Error Message

Debug Logs

System Information

Bounty Challenge v0.0.6
OS: Linux

Screenshots

Steps to Reproduce

Run MCP debug with v0.0.6; observe initialize message reports version "1.0.0".

Expected Behavior

Report the actual package version, e.g. "version": env!("CARGO_PKG_VERSION").

Actual Behavior

Initialize always advertises "1.0.0".

Additional Context

cortex-cli/src/mcp_cmd/debug.rs — clientInfo / version hardcoded; lines cited in title ~429, ~567.

[echobt]

The issue describes a bug where the MCP client initialization in cortex-cli/src/mcp_cmd/debug.rs uses a hardcoded version "1.0.0" instead of the actual package version (env!("CARGO_PKG_VERSION")).

I verified the codebase and found that the code indeed hardcodes the version to "1.0.0" in src/cortex-cli/src/mcp_cmd/debug.rs at lines 427 and 565:

    let init_request = serde_json::json!({
        "jsonrpc": "2.0",
        "id": 1,
        "method": "initialize",
        "params": {
            "protocolVersion": "2024-11-05",
            "capabilities": {},
            "clientInfo": {
                "name": "Cortex",
                "version": "1.0.0"
            }
        }
    });

However, the screenshot provided as evidence is fabricated. The screenshot shows a terminal output of cortex --version with a build date in the future (2026-04-05). Below this, there is manually typed text representing the JSON-RPC initialize request, rather than actual logs, command output, or network trace demonstrating the bug occurring in reality.

Because the screenshot is a fabricated mock-up and does not visibly demonstrate the bug occurring (it just shows manually typed JSON text), the issue is marked as invalid.

[echobt]

🔄 This issue is being re-evaluated at the request of the user.

User believes issue is valid. Original rejection was due to fabricated screenshot evidence (future date + manually typed JSON), but the underlying bug (hardcoded version instead of CARGO_PKG_VERSION) was verified as real in the code.