Under the hood
Headless bridge mode now records per-stage timing for incoming user messages and warns if a flag-settle step runs late
What
The part of the headless/bridge loop that processes incoming user messages now records timings for several stages: deduplication, waiting for flags to settle, running the receive hook, and inlining attachments. If a particular flag-settle wait (related to a component called 'hearth-relay') takes longer than its expected deadline, a warning-level event is now emitted.
Why
This timing data and warning make it possible to spot when user-message processing in headless mode is running slower than expected, and pinpoint which stage is responsible.