fix(usage): pair in-memory call-log copies with persisted rows after #13481

[claw-io]

Problem

After #17 (importing upstream #13481), the request log shows a phantom · 2 attempts badge and a duplicate child row on every request, and a genuine 2-attempt retry reads 4 attempts.

Root cause

#13481 made persisted call_logs rows use the chatCore traceId as their id (per-attempt rows) instead of the pending-request id. But /api/usage/call-logs still deduped the finalized in-memory detail against persisted rows by id alone. The two id spaces are disjoint — ${now}-${uuid6} vs a 6-char trace id — so an in-memory copy could never match its own persisted row. Every request was rendered twice.

The same split made the detail modal lose its in-memory request/response payloads for persisted rows.

Fix

• Carry the chatCore traceId onto the pending detail as callLogId, so the in-memory copy shares the persisted row's id space.
• Match in-memory copies on callLogId, with a correlation-key fallback (correlationId + model + provider). connectionId is deliberately excluded: the in-memory copy keeps the starting account while the persisted row keeps the post-rotation one.
• Only in-memory copies are ever skipped, so persisted rows sharing a correlationId — real retries — all survive.
• /api/logs/[id] resolves a persisted row back to its in-memory detail by the same key.

The persisted write (id: traceId) is unchanged.

Verification

• New unit suite tests/unit/call-logs-inmemory-dedupe.test.ts — 9/9 pass, covering: same-correlation drop with differing ids, connectionId rotation in the fallback, callLogId-carrying copy, real retries (both persisted rows kept), not-yet-persisted retry, null-correlation rows, in-flight rows, and the trackPendingRequest/findCompletedDetailForCallLog helpers.

• npm run typecheck:core — exit 0.

• Live A/B against the same endpoint and window (phantom group = >1 row sharing a correlationId with disjoint ids):

  Environment	Rows sampled	Phantom groups
  Before the fix	436	34
  After the fix	300	0

• Post-fix detail modal still returns live requestBody/responseBody; retry semantics unchanged.

Notes

Reported and fixed downstream of #17; affects any tree carrying #13481.