A scheduled run has no task, no chat turn and no workflow behind it, so its
emitted events are the only trace it leaves -- and the engine's Sink is the
emitter shape of a bus it deliberately does not import. Something has to turn
one into the other; this is that seam.
- Sink(mode, bus) returns a sink over the bus for "bus", and nil for
"none"/absent or a nil bus. Nil rather than a no-op sink keeps
"emission is off" visible to whoever reads the composition, and it is
the configuration the engine documents as valid: it still runs, it is
just unobservable.
- The published event carries the engine's own Kind/Detail/Data and no
task-scoped identity. A cron run has none, and borrowing the emitting
daemon's would attach it to an unrelated task's timeline.
- An unrecognised mode is an error; the loader rejects it first, but a
hand-built config must not silently disable observability.
TDD: the sink tests were written first and failed on assertions (Sink("bus")
returned nil; an unknown mode was accepted), not on compilation. The
end-to-end test drives a real engine on an injected clock and subscribes to
the bus, so the Emit -> Publish path is proven rather than assumed -- no
sleeps, no wall-clock deadlines.