[Bug] Trade Indexer Returns 200 But Persists No Trade History Records

[realproject7]

Summary

Running the full mainnet E2E verification after the IPFS fallback fix exposed a remaining trade-indexing bug. The trade indexer route returns HTTP 200, but the verification script observes indexed: 0 and no corresponding trade_history records are persisted.

Failure

From issue plotlink-contracts#29 execution:

• Contract E2E: 30/30 PASS
• Indexer verification: 83/86 PASS
• Remaining substantive failure: V3.2 trade_history missing after successful trade indexing responses

T3 reported:

• Trade API returned 200
• Response indicated indexed: 0
• Mint/Burn events were not matched to the token
• Likely areas include token-address matching/casing or event matching in the trade route

Scope

Investigate and fix the PlotLink trade indexing path so successful trade-indexing requests persist the expected trade_history records for the E2E mainnet transactions.

Acceptance Criteria

• Trade indexer correctly matches the E2E mint/burn events to the target token
• Successful trade indexing persists expected trade_history rows
• E2E verification V3.2 passes for the mainnet test data from plotlink-contracts#29
• PR includes the correct original issue number in the title

Notes

• The stale V1.2 F3 verification reference is a separate cleanup item and not the main blocker here
• The V5.4 RPC 429 was reported as transient and does not need to block this fix

[realproject7]

Resolved by applying the existing migration directly to the database. No code merge required; trade indexing now persists rows and the E2E verification passes the substantive trade checks.