fix(deps): rename Content to ContentBlock for rmcp v2; gate lint on Renovate PRs

[clouatre]

Summary

rmcp v2.2.0 introduced two breaking changes addressed in this PR:

1. Renamed Content to ContentBlock across the MCP model. All import and call sites updated in 10 files. No behavior change.

2. Deprecated LoggingLevel, SetLevelRequestParams, and all LoggingLevel variants (-D warnings promotes these to hard errors in CI). Rather than suppress with #[allow(deprecated)], the deprecated surface is removed entirely, aligned with MCP SEP-2577 which formally deprecated the Logging protocol feature (merged 2026-05-15) citing overlap with stderr and OpenTelemetry.

What was removed:

• set_level ServerHandler override (logging/setLevel request handler)
• notify_logging_message call sites (notifications/message MCP log forwarding)
• log_level_filter field and mutex on CodeAnalyzer
• LoggingLevel, SetLevelRequestParams, LevelFilter imports

What replaces it:

• LogEvent.level is now tracing::Level directly
• Log level is controlled via RUST_LOG env var or --log-level CLI flag
• JSONL metrics and OTel log appender channels are unaffected

Changes

• .github/workflows/ci.yml -- remove Renovate bot skip from Lint job if-condition
• crates/aptu-coder/src/lib.rs -- remove deprecated imports and set_level override; remove log_level_filter field
• crates/aptu-coder/src/logging.rs -- LogEvent.level: LoggingLevel -> tracing::Level; delete level_to_mcp
• crates/aptu-coder/src/tools/server.rs -- remove log_level_filter parameter
• crates/aptu-coder/src/main.rs -- update CodeAnalyzer::new() call
• crates/aptu-coder/src/tools/analyze_directory.rs
• crates/aptu-coder/src/tools/analyze_file.rs
• crates/aptu-coder/src/tools/analyze_module.rs
• crates/aptu-coder/src/tools/analyze_symbol.rs
• crates/aptu-coder/src/tools/common.rs
• crates/aptu-coder/src/tools/edit_overwrite.rs
• crates/aptu-coder/src/tools/edit_replace.rs
• crates/aptu-coder/src/tools/exec_command.rs
• crates/aptu-coder/tests/integration_tests.rs
• docs/ARCHITECTURE.md -- update logging module description to reflect removal
• OBSERVABILITY.md -- replace stale "Log level and MCP client visibility" section; remove notifications/message and logging/setLevel references

Test plan

• Tests pass (662 passed, 0 failed)
• Linter clean (cargo clippy --locked --profile ci -- -D warnings)
• Formatter clean (cargo fmt --check)
• No #[allow(deprecated)] introduced
• Security scan clean (no findings)

Closes #1342

[aptu-dev]

Aptu Review

✅ Approve — This PR updates the codebase to accommodate the breaking change in rmcp v2.2.0 where Content was renamed to ContentBlock. It also removes the conditional gate in the CI pipeline that previously skipped linting for Renovate-generated PRs.

---

_{Posted by aptu}

[aptu-dev]

Aptu Review

✅ Approve — This PR updates the codebase to support the breaking changes in rmcp v2.2.0, specifically renaming 'Content' to 'ContentBlock' and updating related types. It also cleans up the logging infrastructure by removing redundant MCP-specific logging level mappings and enables CI linting for Renovate-generated PRs.

• The removal of the set_level handler and log_level_filter state significantly changes the server's runtime configuration capabilities; ensure this aligns with the intended evolution of the MCP server interface.

---

_{Posted by aptu}

[aptu-dev]

Aptu Review

✅ Approve — This PR updates the codebase to support rmcp v2.2.0 by renaming Content to ContentBlock and removing deprecated logging infrastructure in favor of standard tracing::Level. It also cleans up the CI configuration by removing the Renovate-specific lint gate.

• The removal of the set_level handler is a breaking change for clients relying on dynamic log level adjustment via MCP, though this aligns with the cited SEP-2577.

---

_{Posted by aptu}

[aptu-dev]

Aptu Review

✅ Approve — This PR updates the codebase to support rmcp v2.2.0 by migrating from Content to ContentBlock and removing deprecated MCP logging features. It also cleans up the CI configuration by removing the Renovate-specific skip condition for linting.

• The removal of logging/setLevel removes a runtime configuration capability that some users might have relied upon, though this is justified by the upstream spec change.

---

_{Posted by aptu}