Expand description
trace — a minimal diagnostic readout that surfaces
every relevant ReadoutContext field as text for
whatever event triggered it.
Two purposes:
- Test affordance. Bind it to events in unit tests and assert that events fire with the expected context. Drops the burden of crafting bespoke assertion helpers per surface.
- Reference implementation. This is the smallest
possible custom renderer — every method an author
might want to read from
ReadoutContextis read here, with one line of formatted output per field. A user building a fully custom render format can copy this file and edit it.
trace does not branch on LOD or content mode — it
emits the same fields at every combination. This
intentionally violates SRD-63 §3.3’s monotonicity
guidance for production readouts; trace is a
diagnostic, not a user-facing render, and uniformity
across LODs is what makes it useful for testing.