turbo

f88d5148 - refactor: Replace `tracing::log::` bridge imports with `tracing::` directly (#12320)

refactor: Replace `tracing::log::` bridge imports with `tracing::` directly (#12320) ## Summary - Replaces `tracing::log::{warn,debug,trace}` bridge imports with direct `tracing::{warn,debug,trace}` imports across 4 crates - Removes a dead `use tracing::log::warn` import in `turborepo-run-summary` that was shadowed by `turborepo_log::warn` ## Why The `tracing::log::*` bridge macros are a third logging pathway that sits ambiguously between `tracing` (developer diagnostics) and `turborepo-log` (user-facing structured output). All usages in this PR are developer diagnostics and should use `tracing` directly. One remaining `tracing::log::warn` in `turborepo-boundaries` is intentionally excluded — it's user-facing and will migrate to `turborepo_log` in a follow-up PR that adds the `turborepo-log` dependency to that crate. ## Changed crates - `turborepo-run-summary` — dead import removal - `turborepo-ui` (wui/sender) — `tracing::log::warn` → `tracing::warn` - `turborepo-graph-utils` — `tracing::log::trace` → `tracing::trace` - `turborepo-engine` — `tracing::log::debug` → `tracing::debug`