Fix trace replay JSONB metric merge

[cquil11]

What changed

• Bind reconstructed full-response metrics as a JSONB object instead of a string.
• Update the trace replay regression test to require an object parameter and reject double encoding.

Why

Historical AgentX artifacts need full-response metrics reconstructed from retained profiles. Passing the patch through JSON.stringify stored it as a JSON string; PostgreSQL JSONB concatenation then converted benchmark_results.metrics from an object into an array, causing chart metrics to fall back to zero.

This preserves backward compatibility for historical artifacts while leaving current artifacts unchanged.

Validation

Further testing was skipped at request for a quick PR.

---

Note

Low Risk
Small ETL SQL binding change in trace replay ingest with a focused regression test; no auth or broad API surface.

Overview
Fixes corrupted benchmark_results.metrics when trace replay backfills full-response ITL/interactivity from historical AIPerf profiles.

persistPreparedTraceReplay now passes reconstructed metrics through tx.json(fullResponseMetrics) instead of JSON.stringify(...) before the metrics || … update. That keeps the bind as a JSON object so PostgreSQL merges into the existing JSONB document instead of treating the patch as a string and turning metrics into an array (which made charts read zeros).

The trace replay ingest test mock adds tx.json, and the persistence test now requires the metric patch in query values as a plain object and explicitly rejects a stringified duplicate.

^{Reviewed by Cursor Bugbot for commit 5e41a4f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
inferencemax-app	Ready	Preview	Aug 7, 2026 6:36am