Module loop_guard_trips 

Outbound ports for the loop guard’s log: a sink and a reader.

The proxy writes to the sink on the request path; the daemon, the CLI and the GUI read through the reader.

Two traits because the two sides have nothing in common but the data. The sink is synchronous and must never block or fail a request — the proxy holds it as an Option, and no sink at all makes recording a no-op, the UsageSink shape. The reader is asynchronous and only ever runs off the request path. gglib-db implements both; nothing on the proxy’s side of the boundary knows it is SQLite.

What the log holds and why is crate::domain::loop_guard_log.

Traits

LoopGuardTripLog

Reads the loop guard’s log back.

LoopGuardTripSink

Where the loop guard’s step records what it did.