Trim dashboard lifecycle detail payload

Proof: Production response sampling showed pretty-printed strategy output exceeded the 1.5 MB budget by 23 KB after the prior bound; display-only successful trade details are now capped at 40 while counts and aggregates remain intact. Full npm test and dashboard build pass.

Assumptions: The dashboard requires at most the recent successful detail rows for usability; durable candidate selection remains bounded at 50 before linked evidence reads.

Still fake: Pod-local query activity and exact all-time submission totals remain unavailable; venue-native fill truth remains limited to retained durable evidence.

src/core/operator-dashboard.mjs

@@ -1983,7 +1983,7 @@ function buildTradeFunnelSummary(lifecycleRows = []) {
     no_trade_count: noTradeRows.length,
     // Keep the dashboard response bounded while retaining the full count and
     // aggregate estimate from the bounded lifecycle input.
-    successful_trades: successfulTrades.slice(0, 50),
+    successful_trades: successfulTrades.slice(0, 40),
     unresolved_submissions: unresolvedSubmissions.slice(0, 20),
     no_trade_rows: [],
     counts,