What problem does it solve? Diagnosing agent errors, latency issues, and tracing behavior in Fredo requires inspecting OpenTelemetry-style spans, metrics, and logs stored in fredo.db, which is tedious to query manually and risky without read-only safeguards. ## Core Features & Use Cases - Read-only SQL querying: A PowerShell wrapper locates fredo.db, enforces SELECT/PRAGMA-only queries, applies default LIMITs, and runs sqlite3 in readonly mode. - 16 ready-made query recipes: Cover error spans, latency percentiles, session traces, throughput, error rates, retention status, schema inspection, and trace-correlated logs across telemetry_spans, telemetry_metrics, and telemetry_logs tables. - Multiple output formats: JSON for programmatic use, markdown tables for GitHub issues, and plain tables for terminal inspection. - Use Case: An agent debugging a failing session runs the session trace recipe with the session UUID to see the full span hierarchy, then correlates ERROR-level logs by trace_id to pinpoint the failing adapter. ## Quick Start Ask the agent to query the telemetry database for all error spans from the last hour and show the results as a markdown table.