jif acb78a41a0 Stop persisting RMCP service traces (#31789) ...

## Why

The SQLite feedback log enables TRACE by default. `rmcp::service`
renders complete MCP service events at TRACE, including large tool
catalogs and other protocol payloads. In a busy local sample, this was
the largest retained source and individual rows reached about 2 MiB.

These rows can quickly consume the per-thread retention budget, displace
smaller diagnostics, and add unnecessary SQLite insert-and-prune work.

## What changed

- Persist `rmcp::service` at INFO and above in the SQLite feedback log.
- Keep service initialization, shutdown, warnings, and errors available
for feedback.
- Leave other tracing and OpenTelemetry subscribers unchanged.

This is intentionally target-specific. Broader persistent-log policy
changes can remain separate.

Related to #28224.

2026-07-09 14:34:47 +01:00

..

goals_migrations

feat: dedicated goal DB (#23300)

2026-05-19 11:11:41 +02:00

logs_migrations

Align SQLite feedback logs with feedback formatter (#13494)

2026-03-18 22:44:31 +00:00

memory_migrations

Move memory state to a dedicated SQLite DB (#24591)

2026-05-26 20:07:25 +02:00

migrations

feat(app-server): add history_mode to thread (#29927)

2026-06-26 09:12:42 -07:00

src

Stop persisting RMCP service traces (#31789)

2026-07-09 14:34:47 +01:00

BUILD.bazel

build: run buildifier from just fmt (#28125)

2026-06-13 21:43:39 -07:00

Cargo.toml

[codex] Pin bundled SQLite to fixed WAL-reset version (#27992)

2026-06-13 21:28:31 -07:00