materialized view and a bit better ui

README.md

@@ -101,7 +101,13 @@ gRPC services for traces, metrics, and logs using standard OTLP protobuf definit
   filters as `search`, plus `timeout` (seconds, default 30). Rate-limited
   per client IP.
 - `GET /api/traces/{traceId}` - Retrieve all stored entries (spans and
-  correlated logs) referencing a given trace id.
+  correlated logs) referencing a given trace id. With ClickHouse this is an
+  indexed lookup (`entries.trace_ids`) and each payload is trimmed to that
+  trace's own spans/log records.
+- `GET /api/traces/summaries?ids=a,b,c` - Per-trace rollups (name, start/end,
+  duration, span count, error count, services; max 100 ids) without reading
+  span payloads. Maintained on insert by the `trace_summaries` view; empty
+  with the file store.
 
 All endpoints above search the full persistent store, not just the
 in-memory ring buffer.
@@ -133,6 +139,12 @@ Errors seen in traces (spans with an error status) and logs (severity
   Supports `limit`.
 - `GET /api/issues/{id}` - Fetch a single issue, including up to 5 recent
   sample occurrences (timestamp, trace/span id, message).
+- `GET /api/issues/{id}/traces` - Every trace the issue occurred in, most
+  recently hit first, with each trace's summary and its occurrences, in one
+  request (`limit`, `before` = `nextBefore` from the previous page).
+  ClickHouse keeps *all* occurrences (`issue_occurrences`, 90-day TTL);
+  without it the response is built from the 5 in-memory samples and
+  `complete` is `false`.
 - `GET /api/patterns` - List deterministic groups of related exact issues.
   Pattern grouping is explainable and does not merge issue IDs.
 - `GET /api/issues/{id}/similar` - Return bounded, deterministic related-issue