#1173 swamp workflow history search OOMs on workflows with large run history

Description

'swamp workflow history search ' crashes the CLI with a fatal JavaScript out-of-memory error instead of returning results, when the target workflow has a large number of accumulated run records.

Steps to reproduce

1. Have a workflow with several thousand recorded runs under .swamp/workflow-runs// (in our case: 3166 runs, ~9.8G total, from a workflow that ran every 2 minutes for weeks).
2. Run: swamp workflow history search k8s-health-sweep --json
3. CLI logs repeated "Incremental Mark-Compact" GC messages, then crashes: "Fatal JavaScript out of memory: Ineffective mark-compacts near heap limit" with a V8 C stack trace.

Environment

• swamp 20260714.215032.0-sha.c8bdff3c
• Linux (WSL2), repo with .swamp/workflow-runs// containing 3166 run YAML+log file pairs for the affected workflow.

Impact

Any workflow that accumulates a few thousand historical runs (easy to hit with a sub-5-minute schedule and no retention, see companion feature request about missing workflow-runs/outputs retention) becomes permanently unqueryable via 'workflow history search' — the command always OOMs. The only way to inspect or diagnose such a workflow's history is to read the raw YAML files directly, which defeats the point of the CLI.