docs(command-center): describe request logging, trace export and mirroring with their conditions - #1115

Summary

Several Agent Command Center pages, plus related Protect, export and release-notes pages, described request logging, trace export and result delivery as if they happened for every call. This change rewrites those passages so each page states the conditions under which they apply. It changes documentation only and describes current behaviour.

What changes

• Observability, core concepts and configuration: request logging is described as applying to eligible calls when logging is enabled. Body capture, trace export and telemetry are described as separate controls, and the configuration precedence notes the request-log content mode exception.
• Platform integration and self-hosting: a control-plane connection is described as receiving request logs when request logging is enabled, and trace export as going to the configured collector. Span metadata is described as conditional on sampling, delivery and the span metadata controls, and self-hosting notes that request-log and trace-export destinations are configured separately.
• Shadow experiments: mirroring is described as a self-hosted gateway setting. Storing shadow results requires routing.mirror.capture_results: true, and delivering them to the Future AGI app also requires a control-plane connection.
• Guardrails, streaming and Protect: guardrail outcomes are described as retainable in request logs for eligible calls when logging is enabled and delivery succeeds. The log action and post-stream checks are no longer described as persisting an entry on their own.
• Cost tracking, custom properties and Assistants: metadata and cost values are described as appearing in retained request logs, and the dashboard grouping text matches the available metadata choices.
• Webhooks: the Delivery Log description matches what the tab shows, and audit-event forwarding is described as coming from ingested request-log entries through active subscriptions.
• Exports (cloud storage, Datadog, Mixpanel, PostHog): exports are described as sending stored request-log rows, with the fields and tags each integration emits.
• Release notes, quickstart and troubleshooting: entries about trace attributes, credential scrubbing, OTLP export and request-log availability now carry the same conditions.

23 files changed.