Incorrect logging level (error instead of info/debug) in src/mcp_connection_manager.rs

What version of Codex is running?

codex-cli 0.42.0

Which model were you using?

gpt-5, but applied to all model

What platform is your computer?

Darwin 24.6.0 arm64 arm

What steps can reproduce the bug?

Line 111 of src/mcp_connection_manager.rs uses tracing::error! for a log message that appears informational:

tracing::error!(
"new_stdio_client use_rmcp_client: {use_rmcp_client} program: {program:?} args: {args:?} env: {env:?} params: {params:?} startup_timeout: {startup_timeout:?}"
);

This should likely be tracing::info! or tracing::debug! instead of error, since it does not indicate an actual error state. Please review whether the log level categorization is appropriate.

What is the expected behavior?

Log statements should use error level only for actual error conditions. Informational startup details should use info or debug level to avoid misleading users and cluttering error logs.

What do you see instead?

Currently, the statement uses error level for a normal operation log, which may mislead users and systems monitoring error logs.

Additional information

No related open issue was found at time of writing. See line 111 of src/mcp_connection_manager.rs for context. I found this when I used 'codex mcp' MCP server.