Long-running scan memory profiling + leak detection

[truthixify]

Tier: M (2-4 days) Type: perf

Context

Spectre TEE agents run for months. A small SDK leak becomes an OOM kill in production. Build a long-running harness + CI gate to catch leaks before mainnet.

Scope

• test/leak/scan-leak.test.ts running scanAnnouncements in a tight loop
• Synthetic 10k-announcement dataset, 10k iterations
• v8 heap snapshots at intervals; fail on slope > N KB/iter
• Profiling outputs (flame graphs) committed
• CI nightly job

Acceptance criteria

• Harness committed
• Baseline measurements in PR description
• CI nightly leak-scan job
• Any identified leaks fixed

Files to start with

• New: test/leak/scan-leak.test.ts
• Node v8 docs

[frank0277]

@frank0277 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi i would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @frank0277 to this issue.

[drips-wave]

Congratulations, @frank0277! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @frank0277: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[truthixify]

@frank0277 Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. If you get stuck or context changes, just say so on the PR — silence is the only thing that costs you the assignment.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building. Looking forward to the PR.