Ticket graphs

Amends the refactor standard #200: every rewritten module MAXIMIZES configuration, telemetry, and logging. (1) CONFIG: every tunable comes from a control-config object (per #200), nothing hardcoded. (2) TELEMETRY, born-instrumented (codebean @debug_decorator idiom): at TRACE level capture control-flow decisions — e.g. which side of an if/else was taken — plus timings and key args. (3) THE ARCHITECTURE the operator specified: trace events are written FIRST to an IN-MEMORY data store (ring buffer / in-mem table) to avoid per-event DB writes crushing hot paths; a flusher drains the buffer to a DB at an IDEAL TIME — batched on a size threshold, a time interval, on idle, and on shutdown (never in the hot path). Backpressure/overflow policy defined (drop-oldest vs block). Levels: TRACE(branches)/DEBUG/INFO/WARN/ERROR, level-gated so TRACE is off in prod but the SAME instrumentation is present. (4) LOGGING: structured, level-gated, correlated to the telemetry trace. This is a shared library every rewritten package depends on -> it is rebuilt FIRST (feeds the #research ordering). ACCEPTANCE: a sample module, rebuilt to this standard, emits trace on a branch into the in-memory store and the flusher persists it to the DB at the ideal time with zero hot-path DB writes.

— browse congruency source (forge-parked tree)

— #207 Build: competitive-rewrite tournament harness — generate 5+ candidates, benchmark, all-agent score, select winner, record deep-dive (spawned · DONE)