chore(media): add tokio dep for Task 2 Reflex<P> consumer (slice-4 §3.2)

Reflex<P> owns a tokio::sync::mpsc::Receiver<AdvisoryEvent> (the advisory
channel the TapEngine feeds from its tokio task), so tokio must be a
runtime dep of rutster-media at lib-compile time, not dev-only. The
crate itself makes no tokio runtime calls — the dedicated media thread
drives Reflex, not an executor (ARCHITECTURE.md; slice-1 spec §3.4).

Signed-off-by: Aaron D. Lee <himself@adlee.work>
This commit is contained in:
2026-07-02 23:41:34 -04:00
parent 8cde52b1d3
commit f5a5a6dd3c
2 changed files with 9 additions and 0 deletions

1
Cargo.lock generated
View File

@@ -1239,6 +1239,7 @@ dependencies = [
"rutster-call-model",
"str0m",
"thiserror 1.0.69",
"tokio",
"tracing",
]

View File

@@ -13,5 +13,13 @@ opus = { workspace = true }
str0m = { workspace = true }
thiserror = { workspace = true }
tracing = { workspace = true }
# tokio: required at lib-compile time because `Reflex<P>` owns a
# `tokio::sync::mpsc::Receiver<AdvisoryEvent>` (the advisory channel the
# TapEngine feeds from its tokio task). rutster-media proper makes NO
# tokio runtime calls — the dedicated media thread drives `Reflex`, not a
# tokio executor (ARCHITECTURE.md "dedicated timing threads, not the
# shared tokio pool" — see slice-1 spec §3.4). The `full` features here
# also cover `#[tokio::test]` + `#[tokio::main]` in the binary/tests.
tokio = { workspace = true }
[dev-dependencies]