Module logging 

Centralized tracing/logging initialization.

Call ferridriver_test::logging::init() once at startup. It’s safe to call multiple times — subsequent calls are no-ops.

Respects (in priority order):

1. RUST_LOG — standard tracing env filter
2. FERRIDRIVER_DEBUG — category-based filter
3. verbose parameter — 0=warn, 1=debug, 2+=trace

FERRIDRIVER_DEBUG categories

Value	Tracing target
* / all	ferridriver=trace
cdp	ferridriver::cdp=trace
step / steps	ferridriver::bdd::step=trace
hook / hooks	ferridriver::bdd::hook=trace
worker	ferridriver::worker=trace
fixture	ferridriver::fixture=trace
reporter	ferridriver::reporter=trace
action	ferridriver::action=trace
runner	ferridriver::runner=trace

Profiling modes (FERRIDRIVER_PROFILE env var)

Value	Feature flag	Output
chrome	--features profiling	trace-{pid}.json (Chrome DevTools / Perfetto)
console	--features tokio-console	Live tokio-console dashboard

Functions

init

Initialize the tracing subscriber. Safe to call multiple times.

init_from_env

Initialize with env-var-only detection (no verbose flag). Used by standalone harnesses and NAPI where there’s no CLI verbose flag.