Bryan Helmkamp 7abc11adc9 feat(server): route worker logs to the same destination as the parent ... Workers are an internal implementation detail; operators should not need to know about them. When the server runs in stdout mode (FABRO_LOG_DESTINATION=stdout, e.g. inside containers), workers now also stream their tracing to stdout so all server-level logs land on the same destination. The parent propagates its resolved destination to each worker via FABRO_LOG_DESTINATION and inherits the worker's stdout when the parent is in stdout mode (so worker stdout flows through to docker logs). The per-run log at <scratch>/runtime/server.log stays a file regardless -- it is read back by the run UI. A CLI-side ServerLogSink::{File(PathBuf),Stdout} replaces Option<PathBuf> so the file/stdout intent is explicit at the type level for both the Server and Worker sinks. LogDestination gains strum::IntoStaticStr so the parent can stringify it for the worker env without a hand-written map. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-26 17:16:03 -04:00
..
crates	feat(server): route worker logs to the same destination as the parent	2026-04-26 17:16:03 -04:00
packages/fabro-api-client	Merge remote-tracking branch 'origin/main'	2026-04-26 16:29:54 -04:00